Alternatively, you use Commander's Secondary CAT port to enable the amplifier to follow the Primary transceiver's frequency - even if the primary transceiver isn't an Icom. + Configuring the RS-232C connector to support CAT control should Commander to control the IC-7800 via the RS-232C port and CT17, and the amplifier to track the transceiver's frequency via the REMOTE port.
he only has wifi and no hub so ethernet is out. Is it possible to control the radio via the RS232 and and the ACOM via the remote jack? My friend lives several states away from me so it is not possible to work at the radio console. EchoLink users: the diagrams do not show the connection of transceiver squelch output and pin 5 of the 25-pin plug.
The ACOM did sense the RF and follow the radio. For dual-channel transceivers (Yaesu FT-1000MP, Icom IC-7800, Ten-Tec Orion), please see the corresponding dual-channel diagrams. He connected the CT17 up and connected it to the radio and the USB to DB9 to the CT17 via a DB25 to DB9 adapter and the radio communicated with commander as expected but connecting the ACOM to the CT17 had no affect on the ACOM, as I expected it would, no ACOM control. To use the RS-232C connector for CAT control, this menu item should be set to "CI-V". + As documented on page 12-22 on the IC-7800 manual, there's an "RS-232C Function" menu item that determines whether the backpanel RS-232C connector conveys CI-V data or decoded PSK/RTTY. When the ICOM 7800 is connected to the radio via the RS232 port using a USB to DB9 DCE there is no response, the error log looks like it is just sitting waiting for a response. When the Acom is connected to the remote port of the radio it follows the radio as it should. He has an Acom 2000a amp which he also is connecting to his radio. I have been helping a fellow HAM to interface his ICOM 7800 with 3.1 firmware to Commander.
0 kommentar(er)
