Power radio on before or after Commander?


Norm - KC1BMD
 

Should it matter whether the radio is powered on before or after Commander is launched?
I have a Lab599 TX-500 that uses a subset of the TS-2000 command set which sometimes will not connect (using 9600, 8, none, 1 and COM6 via FTDI USB cable, RTS enabled). I use it for frequency tracking to assist with DXK logging. Sometimes it connects just fine and sometimes there is no communication (no frequency display in Commander). If it does not connect, I do finally get it connected somehow (but have not figured out the sequence yet) by performing any of the following ("Reset" connection in Commander configuration, power radio off/on, shutdown Commander and launch again, disconnecting/reconnecting USB cable -- usually a combination of these). I also have an installation of the current version of Ham Radio Deluxe (HRD) that does not experience this issue -- and I never have both apps running simultaneously. While having the problem with Commander connecting, if I shut down Commander and launch HRD, it connects just fine using the same USB cable with FTDI chip. Once the radio finally connects with Commander all seems OK. Is there a preferred startup order for Commander and the radio or should it not matter? Is there something I should be looking at to help troubleshoot this? Note: I don't see any associated entries in Commander's error log file but probably because that app is not failing... so maybe debugging needs to be switched on to catch some error?
--
73, Norm/KC1BMD


Joe Subich, W4TV
 

On 3/29/2023 9:55 AM, Norm - KC1BMD wrote:
Should it matter whether the radio is powered on before or after Commander is launched?
If the USB port in the rig is powered by the rig (as many/most are)
instead of being powered by the computer, the rig *MUST* be turned
on before Commander is started in order for Commander to find the
virtual port.

If the port is not present when Commander *starts* it can not find
it later.

73,

... Joe, W4TV

On 3/29/2023 9:55 AM, Norm - KC1BMD wrote:
Should it matter whether the radio is powered on before or after Commander is launched?
I have a Lab599 TX-500 that uses a subset of the TS-2000 command set which sometimes will not connect (using 9600, 8, none, 1 and COM6 via FTDI USB cable, RTS enabled). I use it for frequency tracking to assist with DXK logging. Sometimes it connects just fine and sometimes there is no communication (no frequency display in Commander). If it does not connect, I do finally get it connected somehow (but have not figured out the sequence yet) by performing any of the following ("Reset" connection in Commander configuration, power radio off/on, shutdown Commander and launch again, disconnecting/reconnecting USB cable -- usually a combination of these). I also have an installation of the current version of Ham Radio Deluxe (HRD) that does not experience this issue -- and I never have both apps running simultaneously. While having the problem with Commander connecting, if I shut down Commander and launch HRD, it connects just fine using the same USB cable with FTDI chip. Once the radio finally connects with Commander all seems OK. Is there a preferred startup order for Commander and the radio or should it not matter? Is there something I should be looking at to help troubleshoot this? Note: I don't see any associated entries in Commander's error log file but probably because that app is not failing... so maybe debugging needs to be switched on to catch some error?
--
73, Norm/KC1BMD


BILL KENNAMER
 

With the FDdx101, it doesn't matter. Usually I turn the computer on and leave it all day, and turn the radio and off as needed.

K5FUV

On Wednesday, March 29, 2023 at 10:19:00 AM CDT, Joe Subich, W4TV <lists@...> wrote:




On 3/29/2023 9:55 AM, Norm - KC1BMD wrote:
> Should it matter whether the radio is powered on before or after
> Commander is launched?

If the USB port in the rig is powered by the rig (as many/most are)
instead of being powered by the computer, the rig *MUST* be turned
on before Commander is started in order for Commander to find the
virtual port.

If the port is not present when Commander *starts* it can not find
it later.

73,

    ... Joe, W4TV

On 3/29/2023 9:55 AM, Norm - KC1BMD wrote:
> Should it matter whether the radio is powered on before or after Commander is launched?
> I have a Lab599 TX-500 that uses a subset of the TS-2000 command set which sometimes will not connect (using 9600, 8, none, 1 and COM6 via FTDI USB cable, RTS enabled). I use it for frequency tracking to assist with DXK logging. Sometimes it connects just fine and sometimes there is no communication (no frequency display in Commander). If it does not connect, I do finally get it connected somehow (but have not figured out the sequence yet) by performing any of the following ("Reset" connection in Commander configuration, power radio off/on, shutdown Commander and launch again, disconnecting/reconnecting USB cable -- usually a combination of these). I also have an installation of the current version of Ham Radio Deluxe (HRD) that does not experience this issue -- and I never have both apps running simultaneously. While having the problem with Commander connecting, if I shut down Commander and launch HRD, it connects just fine using the same USB cable with FTDI chip. Once the radio finally connects with Commander all seems OK. Is there a preferred startup order for Commander and the radio or should it not matter? Is there something I should be looking at to help troubleshoot this? Note: I don't see any associated entries in Commander's error log file but probably because that app is not failing... so maybe debugging needs to be switched on to catch some error?
> --
> 73, Norm/KC1BMD
>








Joe Subich, W4TV
 

On 3/29/2023 3:52 PM, BILL KENNAMER wrote:
With the FDdx101, it doesn't matter.
That may be but it depends entirely on the way the manufacturer
designed the radio. *IF* they included the necessary circuitry
to power the USB hub, USB to Serial converter and USB CODEC
from *either* the computer or the radio, you can power up in
either order since the USB to Serial converter will always be
powered before Windows attempts to load the necessary drivers.

*HOWEVER* if the USB to Serial converter is not powered (not
present) when Windows is loading the low level drivers the virtual
serial port will not be created. This is also why turning off some
rigs will cause Commander to "hang" ... the port suddenly goes away.

73,

... Joe, W4TV

On 3/29/2023 3:52 PM, BILL KENNAMER wrote:
With the FDdx101, it doesn't matter. Usually I turn the computer on and leave it all day, and turn the radio and off as needed.
K5FUV
On Wednesday, March 29, 2023 at 10:19:00 AM CDT, Joe Subich, W4TV <lists@...> wrote:
On 3/29/2023 9:55 AM, Norm - KC1BMD wrote:
Should it matter whether the radio is powered on before or after
> Commander is launched?
If the USB port in the rig is powered by the rig (as many/most are)
instead of being powered by the computer, the rig *MUST* be turned
on before Commander is started in order for Commander to find the
virtual port.
If the port is not present when Commander *starts* it can not find
it later.
73,
    ... Joe, W4TV
On 3/29/2023 9:55 AM, Norm - KC1BMD wrote:
Should it matter whether the radio is powered on before or after Commander is launched?
I have a Lab599 TX-500 that uses a subset of the TS-2000 command set which sometimes will not connect (using 9600, 8, none, 1 and COM6 via FTDI USB cable, RTS enabled). I use it for frequency tracking to assist with DXK logging. Sometimes it connects just fine and sometimes there is no communication (no frequency display in Commander). If it does not connect, I do finally get it connected somehow (but have not figured out the sequence yet) by performing any of the following ("Reset" connection in Commander configuration, power radio off/on, shutdown Commander and launch again, disconnecting/reconnecting USB cable -- usually a combination of these). I also have an installation of the current version of Ham Radio Deluxe (HRD) that does not experience this issue -- and I never have both apps running simultaneously. While having the problem with Commander connecting, if I shut down Commander and launch HRD, it connects just fine using the same USB cable with FTDI chip. Once the radio finally connects with Commander all seems OK. Is there a preferred startup order for Commander and the radio or should it not matter? Is there something I should be looking at to help troubleshoot this? Note: I don't see any associated entries in Commander's error log file but probably because that app is not failing... so maybe debugging needs to be switched on to catch some error?
--
73, Norm/KC1BMD


Norm - KC1BMD
 

Thanks Joe. Near as I can determine, it looks like the CAT port on this particular radio (Lab599, TX-500) with GX-12 style CAT connector gets 3.3V(10mA) from the PC side via the FTDI converter (supplied by the radio manufacturer). I'm guessing the PC USB port provides 5V and after the FTDI USB plug the radio then gets the 3.3V it needs. So, in this case the PC, not the radio, is providing power. Since the FTDI converter is getting power when the PC is booted to Windows, would you recommend that the radio be powered up before or after the PC, or does it matter?
--
73, Norm/KC1BMD


Joe Subich, W4TV
 

Since the FTDI converter is getting power when the PC is booted to Windows, would you recommend that the radio be powered up before or after the PC, or does it matter?
I would *always* recommend powering any USB connected radio *before*
powering up the computer. However, in the case of the Lab599
*supplied* cable, the "COM-USB Adapter" is powered by the computer
so the order probably does not matter.

I certainly do not understand why Lab599 requires a separate 3.3V
input for their CAT interface. 'Tis certainly a nonstandard
design.

73,

... Joe, W4TV

On 3/29/2023 4:55 PM, Norm - KC1BMD wrote:
Thanks Joe. Near as I can determine, it looks like the CAT port on this particular radio (Lab599, TX-500) with GX-12 style CAT connector gets 3.3V(10mA) from the PC side via the FTDI converter (supplied by the radio manufacturer). I'm guessing the PC USB port provides 5V and after the FTDI USB plug the radio then gets the 3.3V it needs. So, in this case the PC, not the radio, is providing power. Since the FTDI converter is getting power when the PC is booted to Windows, would you recommend that the radio be powered up before or after the PC, or does it matter?
--
73, Norm/KC1BMD


Greg
 

Joe
It looks like the CAT interface on the TX-500 is actually RS232 and they provide a FTDI USB to RS232 adapter cable which is powered by the USB port. A quote form the manual "any computer with an RS232 or USB port can be used to control
the TX-500
"
Cheers
Greg VK3VT


Joe Subich, W4TV
 

A quote form the manual " any computer with an RS232 or USB port can be used to control the TX-500 "
As long as the signal level is not more than +/- 3.3V! A standard
+/- 10 or 15 V RS-232 port will blow up the CPU. The "serial port"
is built into the CPU with no protection - thus the supplied USB to
serial cable with a specific 3.3V signal level.

73,

... Joe, W4TV

On 3/30/2023 9:25 PM, Greg wrote:
Joe
It looks like the CAT interface on the TX-500 is actually RS232 and they provide a FTDI USB to RS232 adapter cable which is powered by the USB port. A quote form the manual " any computer with an RS232 or USB port can be used to control
the TX-500 "
Cheers
Greg VK3VT


Norm - KC1BMD
 

On Thu, Mar 30, 2023 at 10:19 PM, Joe Subich, W4TV wrote:
supplied USB to
serial cable with a specific 3.3V signal level
Apparently, the supplied cable with FTDI chip drops the USB port voltage from +5V to +3.3V, so you cannot just use any cable without some type of level converter.
 
--
73, Norm/KC1BMD