I am using VHF RMS SSIDs for 2 digi hops with no apparent problems connecting or broadcasting, e,g. WR3G-10 WM3M-10. However, we have found a problem with CQing and with clicking on a callsign in the beacon box, when the station has 2 hops. If you click on such a beacon, it crashes the distant end, probably because the hops are put in the connect box in the wrong order. Also, we observed that simply calling CQ can crash the distant end. Users have to be careful to manually re-order the RMS callsigns into the correct order and only use the Connect box, and not the beacon box when using VarAC FM. Also, it appears that calling CQ is a NO NO. It is a major problem when you can inadvertently crash the program on the distant end by calling CQ or beaconing. Is this because of the SSIDs being used?
Irad - I am seeing my PSK reporter pin at 2200m instead of 2 meters. This was the case on v6.6.13 also, before I updated to the WIP and buggy version and remains the case. On an earlier version there was no problem.
if your VarAC shows a 2M freq in HZ (ex 145.000.000) then it reports 2M. it is possible the PSK report you see is someone else report who has his freq not set up correctly.
I am using VHF RMS SSIDs for 2 digi hops with no apparent problems connecting or broadcasting, e,g. WR3G-10 WM3M-10. However, we have found a problem with CQing and with clicking on a callsign in the beacon box, when the station has 2 hops. If you click on such a beacon, it crashes the distant end, probably because the hops are put in the connect box in the wrong order. Also, we observed that simply calling CQ can crash the distant end. Users have to be careful to manually re-order the RMS callsigns into the correct order and only use the Connect box, and not the beacon box when using VarAC FM. Also, it appears that calling CQ is a NO NO. It is a major problem when you can inadvertently crash the program on the distant end by calling CQ or beaconing. Is this because of the SSIDs being used?
73, Bill N3XL
That´s cool!
Work in progress :) 73