Kevin, Fred, Found the posts in the archive. The solution/work around was to turn CI-V Transceive OFF. In my case CI-V Transceive has always been off. Don't know what Fred has set on his 7610.
I do see the lag in the frequency update on WSJT when tuning the radio VFO but it always catches up and displays the correct frequency. What Fred and I are seeing appears to be a different issue. This is my take on what is happening from a 50k foot user's perspective. Someone that can dig into the code may have a different take on it The radio is tuned to whatever frequency. Launch WSJT-X. WSJT-X initializes and reads the radio frequency.The frequency display on the main screen is initialized and the correct frequency is displayed. Another register/variable within the code is also initialized with the same frequency. The user manually tunes the radio dial. The frequency tracks correctly on the main screen of WSJT. The mystery register/variable appears to be static and only gets initialized at startup. This value is what gets used in logging the decodes to the ALL.txt file and sent to external apps and servers via the UPD and TCP/IP packets. Logged contacts have the correct frequency which equals the displayed frequency on WSJT+ DF. One additional quirk I am seeing is if the radio is tuned to a normal WSJT FT8 frequency. WSJT is launched all is good as expected. The VFO on the radio can be changed to another frequency and everything appears to track correctly. All.txt and spots on PSKR and Hamspots have the new frequency. If the VFO is tuned again, the frequency is not updated and the All.txt and spotting apps still have the old frequency. Shouldn't be too difficult for someone that is familiar with the code to track the frequency variable that is used for the All.txt file, UDP and TCP/IP packets and see what it is/is not doing when initialized and when the VFO is tuned. 73, Scott AA5AM On Sun, Mar 2, 2025 at 2:26 PM Kevin McQuiggin via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > There was a frequency tracking issue with Icom rigs a couple of years ago > where CAT could not keep up with manual tuning; hence the WSJT-X frequency > and that of the rig could get out of sync. This sounds awfully similar. > > I don’t recall the specific fix, except that it was resolved through > adjustment of a CAT interface setting in the (sometimes confusing) > extensive menu system of my rig (an IC-9700). The setting was > non-intuitive but others with Hamlib experience were able to help me > resolve it. > > On the positive side, if you search the archives for somethign along of > line of "Icom, CAT, tracking, error” then the thread will turn up. > > Hope this helps! > > 73, > > Kevin VE7ZD/KN7Q > > > On Mar 2, 2025, at 10:11 AM, Laurie, VK3AMA via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > > > > On 03/03/2025 4:56 am, Fred Coelho via wsjt-devel wrote: > > 1. Set Radio to 14.000 > > 2. Launch WSJT > > 3. Turn the radio dial to a standard FT8 frequency. > > 4. Observe that spots in HamSpots are not correct. You will also > see that your frequency is not correct on the PSK reporter map. > > > If the Wsjtx VFO frequency does not change following the radio than this > is expected behavior. There is a problem with your CAT connection IMO. > > de Laurie VK3AMA > (HamSpots owner) > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
