If someone could prepare a MacOS version with patch applied,  I'd love
to try it.

śr., 25 sty 2023 o 05:17 Black Michael <mdblac...@yahoo.com> napisał(a):
>
> This is what the function should look like -- always set mode as long as mode 
> is not UNK
>
> void DXLabSuiteCommanderTransceiver::do_frequency (Frequency f, MODE m, bool 
> /*no_ignore*/)
> {
>   CAT_TRACE (f << ' ' << state ());
>   auto f_string = frequency_to_string (f);
>   auto params =  ("<xcvrfreq:%1>" + f_string).arg (f_string.size ());
>   simple_command (("<command:10>CmdSetFreq<parameters:%1>" + params).arg 
> (params.size ()));
>   if (UNK != m)
>     {
>       auto m_string = map_mode (m);
>       auto params =  ("<xcvrfreq:%1>" + f_string + "<xcvrmode:%2>" + m_string 
> + "<preservesplitanddual:1>Y").arg (f_string.size ()).arg (m_string.size ());
>       simple_command (("<command:14>CmdSetFreqMode<parameters:%1>" + 
> params).arg (params.size ()));
>       update_mode (m);
>     }
>   update_rx_frequency (f);
> }
>
>
>
>
>
>
>
>
>
>
> On Tuesday, January 24, 2023 at 05:36:16 PM CST, Dave AA6YQ via wsjt-devel 
> <wsjt-devel@lists.sourceforge.net> wrote:
>
>
>
>
>
> + AA6YQ comments below
>
> I think there is an issue with DXLab Suite Commander integration (radio 
> settings). Under specific circumstances, on Yeasu FT-991,
> FTdx10 and similar, it doesn't change a TRX mode to USB when "Mode: SSB" is 
> checked in radio settings.
>
> Problem exists in  "DXLabSuiteCommanderTransceiver::do_frequency" function"
>
> Decision about mode change is based on current mode, not a mode after 
> frequency is changed.
>
> Probably that function, in first instance probably should perform CmdSetFreq, 
> then check mode on new frequency via CmdSendMode, and
> finally if it's not USB, CmdSetMode should be performed.
>
> Explanation.
>
> Those who are using Yeasu FT-991, FTdx10 and similar touch screen models, 
> know that Yeasu stores some settings like AMP,  ATT,
> modulation per band. When the band is changed via choosing a touch screen 
> button, band settings are restored. Of course you can turn
> your VFO from 28MHz to 7MHz, but in that case mode and other settings are 
> from the 10m band and do not fit to 40m. That's why Yeasu
> operators are using band change buttons.
>
> When we translate it to Yeasu CAT commands, a simple frequency change is a FA 
> xxxxxx command. But it should be preceded by BS xx
> (band
> switch) command to restore proper band settings.
>
> Original DXLab probably does not perform BS xx, so every time the band is 
> switched from e.g. 10m, to 40m, the operator must dig into
> touch menu and update AMP, ATT and mode.
>
> + When controlling an FT-991, Commander issues a BS command before changing 
> bands. It initially did so for the FTDX-10, but working
> with an FTDX-10 owner and WSJT-X development team leader Bill G4WJS (sadly 
> now SK) back in February 2021 revealed that the BS
> command has undocumented side effects - like changing the contents of VFO B.
>
> This is also happening when switching bands from WSJT-X. In general it's a 
> DXLab UX "bug". On the other hand current WSJT-X "force
> USB mode" works, because of this "bug".
>
> + The defect lies in the FTDX-10 CAT command implementation - not in 
> Commander.
>
>       73,
>
>               Dave, AA6YQ (developer, DXLab)
>
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 
Arek
SO9W


_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to