Hi. Double clicking the decode for /P call does not populate your GL in TX1, which is causing the problem. (Generate Std Msgs does not also.) Adding your GL manually is the only solution at this momen

#JT65 #JT9 #IssueReport

Bill, This also happens to Q65, so please make sure the issue gets fixed for that mode, too. Thanks. Hatt/JO1LVZ

#JT9 #IssueReport #JT65

We might be talking about something different. Decode a sig from /P station. (ex. G4WJS/P) Double click on the decode to generate the message, or populate the DX call manually then click on generate s

#JT9 #IssueReport #JT65

Hi all again. After the release of 2.5.0rc2, we checked the issue again and the result is the following; The issue with /P in Q65/JT65 seems to be fixed. (thank you for working on this.) On Q65 and JT

#JT65 #JT9 #IssueReport

Hi. In JA, we use 144.460 for FT8/FT4/Q65 and BY/BV/HL also are on the frequency when we have Es hop. We might want to consider using Q65 as evening TEP generates signal distortion even on 6m. De JO1L

#FT8 #frequency

144.460MHz for most of digital modes, including Q65. (with exception of MSK144 on 144.440) I usually monitor only FT8 on 2m, but will monitor Q65 when we have TEP. JO1LVZ/Hatt.

#FT8 #frequency

Q65B-60 for 2m usually. Unfortunately, JA band plan (set by law) allows us to QRV between 144.400 and 144.500 for digital. Talk to you on vkspotter for further discussion. Tnx. JO1LVZ/Hatt

#FT8 #frequency