diff --git a/Transceiver/HamlibTransceiver.cpp
b/Transceiver/HamlibTransceiver.cpp
index 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 Sunday, March 5, 2023 at 12:35:49 PM CST, alawler mudhawk.com via wsjt-devel
<[email protected]> wrote:
Morning Everybody,
I recently upgraded to 2.6.1 (Built form source on Linux Mint) and am also
seeing this problem.
Is there a fix, or a pull request I can reference? (I'm building from
source, so it's pretty easy to poke something in if the fix is known.)
Thanks!
--al
WB1BQE
________________________________
From: Chris Elmquist via wsjt-devel <[email protected]>
Sent: Monday, January 23, 2023 9:06 PM
To: [email protected] <[email protected]>
Cc: Chris Elmquist <[email protected]>
Subject: [wsjt-devel] FT-736 fails with 2.6.1
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
