Please place this file as described below https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X The WSJT-X_Rigcontrol.log file will be in the same location For Linux put it in ~/.config The WSJT-X_Rigcontrol.log file will be here: ~/.local/share/WSJT-X For MacOS put it in /Users/[username]/Library/Preferences Restart WSJT-X and duplicate the problem. Shut down WSJT-X Then send me the WSJT-X_RigControl.log file Mike W9MDB On Tuesday, January 24, 2023 at 01:58:06 PM CST, Chris Elmquist <chr...@pobox.com> wrote: Hi Mike, Had a chance to try this and unfortunately, no joy. It still fails with the same Hamlib error after apparently trying a few times to send a command to the radio. The "CAT System" indicator on the front panel lights each time it tries and the radio beeps (as it normally does when entering remote control mode) but WSJT-X still ultimately fails after not getting the response to a "ft736_get_freq" call. As before, if I revert the libhamlib-4.dll to version 4.5, in the c:\wsjt\wsjt-x\bin directory, then things start working again. Chris NØJCF On Tuesday (01/24/2023 at 04:37AM +0000), Black Michael wrote: > A change in the FT-736 for gpredict compatibility revealed a missing > statement in WSJT-X. > Try this version which also contains a fix for the K3 on setting VFOB > properly. > https://www.dropbox.com/s/sxikxk9fvzaanwz/wsjtx-2.6.1-win64.exe?dl=0 > > Mike W9MDB > This patch has been applied > iff --git a/Transceiver/HamlibTransceiver.cpp > b/Transceiver/HamlibTransceiver.cppindex 32ea283ea..12d420e32 100644--- > a/Transceiver/HamlibTransceiver.cpp+++ b/Transceiver/HamlibTransceiver.cpp@@ > -659,7 +659,7 @@ int HamlibTransceiver::do_start () rmode_t mb; > pbwidth_t w {RIG_PASSBAND_NORMAL}; pbwidth_t wb;- if > (m_->freq_query_works_+ if (m_->freq_query_works_ && > m_->mode_query_works_ && (!m_->get_vfo_works_ || > !rig_get_function_ptr (m_->model_, RIG_FUNCTION_GET_VFO))) { > // Icom have deficient CAT protocol with no way of reading which > > > > > > On Monday, January 23, 2023 at 03:10:33 PM CST, Chris Elmquist via >wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote: > > Guys, > > I tried to use WSJT-X 2.6.1 on Windows this past weekend in the VHF > contest and discovered that there has been a regression in the support > and/or handling of the FT-736R VHF/UHF rig. > > WSJT-X now fails with a Rig Control Error, reporting: > > Hamlib error: ft736_get_freq: called > rig_get_freq(2103): freqMainA=0, modeMainA=, widthMainA=0 > rig_get_freq(2103): freqMainB=0, modeMainB=, widthMainB=0 > rig_get_cache(259): vfo=VFOA, current_vfo=VFOA > rig_get_cache(435): vfo=VFOA, freq=0, mode=, width=0 > rig_set_cache_freq(122): vfo=VFOA, current_vfo=VFOA > rig_get_freq(2116): freqMainA=0, modeMainA=, widthMainA=0 > rig_get_freq(2116): freqMainB=0, modeMainB=, widthMainB=0 > rig_get_freq(2179): freqMainA=0, modeMainA=, widthMainA=0 > rig_get_freq(2179): freqMainB=0, modeMainB=, widthMainB=0 > rig_set_cache_freq(122): vfo=VFOA, current_vfo=VFOA > rig_get_freq(2186): freqMainA=0, modeMainA=, widthMainA=0 > rig_get_freq(2186): freqMainB=0, modeMainB=, widthMainB=0 > 0:rig_get_freq: elapsed=0ms > 1:rig.c(2409):rig_get_mode entered > 1:rig_get_mode: elapsed=0ms > 1:rig.c(2429):rig_get_mode returning(-11) Feature not available > > Feature not available > Feature not available > while getting current mode > > Timestamp: 2023-01-23T20:46:56.456Z > > --- > > I believe this occurs because the FT-736 has a one-way CAT interface-- you > can only send commands to the radio and it does not send any responses, > ACKs or anything back. > > WSJT-X was working with the -736 up to 2.6.0-rc4 at least and after I > did an upgrade to latest, this problem appeared for me. I do not have > experience with other -RC between. > > I reverted WSJT-X to 2.6.0 and the problem is still present. > > I was unable to revert to the older -RCs because their end-date has been > reached and they will not run. > > I then reverted the Hamlib that is bundled with 2.6.1 to version 4.5 > (no sub-release), > > https://github.com/Hamlib/Hamlib/releases/tag/4.5 > > and this has allowed the -736 to work again. > > So, it appears to be a problem in HamLib although I am not sure why > WSJT-X is calling a function that we know said radio does not support > (namely, querying the frequency from the radio) and then failing when > it cannot get the response. > > Any ideas where things have gone astray? > > Chris NØJCF > -- > Chris Elmquist > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- Chris Elmquist _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
