Re: problems integrating IC -746 as second radio into commander
toggle quoted messageShow quoted text
Dave, Ok on , that. Well it seems in either case Device manager is a useful tool to see ;
Real DB9 serial ports if known directly connected, such as above, of which there are usually few, numbered low, and ;
usb-ser ports which are well identified, with properties showing the type, ftdi etc which the user may know regarding the adapter ;
So only these would be considered , and the either type of connection of the two groups above, further defining the selectable range to try,
rather than guessing.
+ AA6YQ comments below
I was wondering if Jim has used device manager to identify the CAT comports ?
+ Unlike his IC-7300, the IC-746 does not have a built-in USB CI-V port; thus one can't use the technique of connecting the radio to the PC with a USB cable while watching the Ports section of the Windows Device Manager to see which serial port is created when the connection is made.
+ The IC-746 requires an external CI-V interface that must be connect to a PC serial port, or must be connected to a USB-to-serial-port adaptor. If a USB-to-serial-port adaptor is being used, making the USB connection while monitoring the Device Manager will reveal the serial port. Connecting the CI-V interface directly to a serial port requires knowing that serial port's COM #.
+ Correctly configured, Commander continuously directs the radio to report its frequency, mode, RX/TX status, etc. You can monitor the outgoing and incoming traffic in Commander's Messages window:
+ If the radio is not responding to the directives Commander is sending, one can use an oscilloscope to check the CI-V bus for radio responses. If they are present, you can then trace the signals through the CI-V interface to the serial port.
+ The CI-V interfaces inside Icom transceivers are vulnerable to failure from static discharge damage, but prosaic failures like "wrong baud rate" and "wrong CI-V address" are more common.