Menu
▾
▴
Re: [wsjt-devel] VFO readout on FT8 shutdown
|
From: Marco C. <PY...@ou...> - 2023-07-21 00:14:49
|
In order to provide the deserved public acknowledgments to Mike, I would like to confirm that his latest /rig/ft100.c commit into Hamlib, has resolved definitely my issue. Thanks to Mike W9MDB! Regards, Marco, PY1ZRJ Il 20/07/23 11:45, Marco Calistri via wsjt-devel ha scritto: > I face a similar behavior which last for two or three transmissions > sequences at the beginning of my FT8 session. > > This phenomenal started since some months then if it is due Hamlib, it > is something that is being dragged along the new releases. > > In my case (using an Yaesu FT-100, mode rig split) starting for > example the transmission on 28074 Mhz, on RX vfo, during the 15 > seconds TX displays 28073, at RX switch the RX vfo shifts to 28073, > then TX vfo during the second transmission, shifts to 28072 Mhz. At > third sequence the behavior repeats, so RX is now at 28072 and TX > shifts to 28071. > > To correct it, I need to switch the frequency bands selector of WSJTX > back to 28074. > > Then the next sequences of RX/TX, after my manual intervention, keeps > stably within the 1 Khz shift: 28074 RX and 28073 TX. > > This is not a blocking issue to me but it is a bit annoying having to > correct manually. > > Regards, > > Marco, PY1ZRJ > > Inviato da Outlook per Android <https://aka.ms/AAb9ysg> > ------------------------------------------------------------------------ > *From:* Black Michael via wsjt-devel <wsj...@li...> > *Sent:* Thursday, July 20, 2023 10:42:39 AM > *To:* wsj...@li... <wsj...@li...> > *Cc:* Black Michael <mdb...@ya...> > *Subject:* Re: [wsjt-devel] VFO readout on FT8 shutdown > That's what you get when you start smooshing buttons. > > Here's what happened. > > You swap VFOs -- WSJT-X doesn't care. > You exit -- WSJT-X saves the VFOB frequency as the "last frequency" used. > You start again -- if you have "Monitor returns to last used > frequency" it will then load VFOB's frequency into VFOA. > Of course rig split will set VFOB based on VFOA's frequency. > > So... > > #1 Don't smoosh buttons unless you know what you are doing > #2 Turn off "Monitor returns...." > > Mike W9MDB > > > > > > On Thursday, July 20, 2023 at 01:38:29 AM CDT, Glenn Williams via > wsjt-devel <wsj...@li...> wrote: > > > Hello, > Comment: The following Human Induced confusion of VFO frequency occurs > on FT8 shutdown. Not necessarily a "bug" in WSJT-X. Just thought > I would send out the information. > > Setup: Windows 10, Kenwood TS590SG, USB cable driven, both WSJT-X 2.6.1 > and 2.7.0-rc2. Bands: at least on HF bands. Everything going well as > usual. TX frequency high enough to separate VFO A and VFO B by 1.000 > kHz (RIG SPLIT) in this example. > > Action creating problem: Human manually toggles VFO A/B button. Now VFO > B is in the main position, VFO A on the side, no frequency changes have > occurred in either VFO. Next steps: EXIT out of WSJT-X. Restart > WSJT-X. Now VFO A displays what VFO B was displaying. VFO B is still 1 > kHz higher, which is now 2 kHz from the original. Examples follow. > > TX = 2800 Hz > PC rig rig > FT8 Display VFO A VFO B > 24915.00 24915.00 24916.00 <-A on main, B on side. Not in QSO. > Toggle A/B on rig. > 24916.00 24915.00 24916.00 <-B on main, A on side. Not in QSO. > EXIT and restart. Symptoms begin. > 24916.00 24916.00 24917.00 <-A on main, B on side. Not in QSO. > > This effect also might happen on other CAT-based rigs? > Problem with hamlib? > > --73, Glenn, AF8C > > > > -- > This email has been checked for viruses by Avast antivirus software. > www.avast.com > > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > _______________________________________________ > wsjt-devel mailing list > wsj...@li... > https://lists.sourceforge.net/lists/listinfo/wsjt-devel --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** |
