Re: Serial Port RTS Error upon startup Commander


Joe Subich, W4TV
 

+ Joe, is there a way that Commander can determine that a microHam "RTS must be N" interface is involved?
It's not "RTS must be N". It can be anything but typically RTS=Y
will lock the rig in transmit if the user is using RTS for PTT and
RTS=HANDSHAKE will lock up CAT software expecting a response on
CTS.

All of the microHAM "keyer" interfaces (CW Keyer, DigiKeyer, DigiKeyer
II, microKEYER, microKEYER II, microKEYER III, MK2R+) *require* hardware
PTT in order to perform sound card/mic audio switching and/or provide
(timed) PTT to an amplifier.

If the owner has enabled a "control" port in microHAM USB Device Router
Commander can poll that port (Ports -> SO2R Serial Port) using the
microHAM Control Protocol. The VS; command will identify the device in
the first two characters following the VS in the response. *HOWEVER*
the microHAM Control Protocol is not applicable to USB Interface II,
USB Interface III or DXP.

In addition, polling for a microHAM interface does not resolve the issue
with the hundreds of other CT/NA compatible interfaces (including MFJ!
and some Rigblaster models).

73,

... Joe, W4TV


On 2021-04-28 8:37 PM, Dave AA6YQ wrote:
+ AA6YQ comments below


I disagree with Dave for his "nanny" prompt.
+ That prompt has saved me a ton of time reviewing screen shots and errorlog.txt files in order to determine why a new user can't get Commander configured to control his or her Kenwood or Yaesu transceiver. The time saved went to implementing new capabilities. Some new users might have abandoned DXLab rather than seek help here.
+ Joe, is there a way that Commander can determine that a microHam "RTS must be N" interface is involved?
73,
Dave, AA6YQ

Join DXLab@groups.io to automatically receive all group messages.