![]() Subsequent presses of the radio's A/B button toggle the radio's VFOs, but flrig remains on VFO A, while changing to theįrequency the radio displays. So, if I'm using VFO A and press the VFO A/B button on the radio, flrig changes frequency correctly, but flrig's active VFO remains VFO A. The radio's own buttons change frequency and the active VFO on the radio, but only change the frequency on flrig. However, the VFO A/B buttons only "track" properly between my Icom 7300 and flrig when I use flrig's onscreen VFO A, VFO B and A B buttons. This weekend I installed flrig for the first time. However the problem I discuss above happens whether or not Log4OM is running. This method fixed that problem: The issue above led to an 80m contact being logged on 40m and the frequency to which the "other" VFO (according to the radio) was set. The "official" Log4OM method uses XML-RPC on the fldigi side, and this grays out the very useful QSY button, which I use all the time. I set up flrig because I wanted fldigi to talk to Log4OM. fldigi has been working fine for nearly 2 years with this setup. I'm running Windows 7 Pro X64, with a single USB cable between the radio and computer. Also, holding down the radio's A/B button for the A=B function has no effect on what flrig displays. ![]() The same thing happens if I set flrig's VFO to B: Presses of the radio's A/B button toggle the frequency properly, but fldigi remains on VFO B. Subsequent presses of the radio's A/B button toggle the radio's VFOs, but flrig remains on VFO A, while changing to the frequency the radio displays.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |