Differences between revisions 7 and 8
Revision 7 as of 2010-04-24 04:09:44
Size: 2625
Editor: AA6YQ
Comment:
Revision 8 as of 2010-04-24 04:13:58
Size: 3163
Editor: AA6YQ
Comment:
Deletions are marked like this. Additions are marked like this.
Line 23: Line 23:
With the physical connectivity established as shown above,

 1. configure Commander to control your [:TranceiverControlAlinco:Alinco], [:TranceiverControlElecraft:Elecraft], [:TransceiverControlFlexradio:FlexRadio], [:TranceiverControlIcom:Icom], [:TranceiverControlKachina:Kachina], [:TranceiverControlKenwood:Kenwood], [:TranceiverControlTenTec:TenTec], or [:TranceiverControlYaesu:Yaesu] transceiver via Commander's Primary CAT Port

 1. verify that Commander can track and control your transceiver's frequency and mode




Controlling an Icom PW-1 Amplifier

The Icom PW-1 Amplifier can automatically track the frequency of an Icom transceiver if

  • The PW-1 and transceiver are connected to the same CI-V bus
  • The transceiver's CI-V Transceive setting is enabled

During an initial programming step, the PW-1 learns the transceiver's CI-V address. From then on, the PW-1 monitors the CI-V bus for new frequency messages emitted by the transceiver when it QSYs with its CI-V Transceive setting enabled, and adjusts its frequency accordingly. If 10 seconds elapse without a "new frequency" message, the PW-1 begins sending the transceiver "report frequency" directives via the CI-V bus.

With no other devices connected to the CI-V bus, this arrangement enables the PW-1 to track the transceiver's frequency. However, if the user wishes to run a PC-hosted transceiver control application to support logging, digital mode operations, DX spot collection, etc., the required connection of a PC-controlled CI-V interface to this CI-V bus generates collisions between PC-initiated CI-V commands and the transceiver's responses to the PW-1's report frequency commands. Unfortunately, the PW-1 lacks the logic required to detect and reject CI-V messages damaged by collisions; the result is that the PW-1 fails to accurately track the transceiver's frequency.

Commander's Secondary CAT Port can be configured to interact with a PW-1 connected to a private CI-V bus, enabling the PW-1 to accurately track the primary transceiver's frequency. This configuration allows the PW-1 to accurately track the frequency of any primary transceiver, not just Icom transceivers. If your transceiver is an Icom, you must establish this connectivity:

[http://www.dxlabsuite.com/Wiki/Graphics/Commander/PW1a.jpg]

If your transceiver is not an Icom, you must establish this connectivity:

[http://www.dxlabsuite.com/Wiki/Graphics/Commander/PW1b.jpg]

Recent Icom transceivers like the IC-7700 and IC-7800 can be directly connected to an RS-232 cable without need of a CI-V interface; the IC-7200 and IC-7600 can be directly connected to one of a PC's USB ports, eliminating the need for a serial port, RS-232 cable, and CI-V interface. The CI-V interfaces required by older Icom tranceivers and by the PW-1 can be [:ConnectingIcom: acquired or assembled]. Some non-Icom transceivers cannot be directly connected to an RS-232 cable, requiring a [:TransceiverConnection: level conversion interface].

With the physical connectivity established as shown above,

  1. configure Commander to control your [:TranceiverControlAlinco:Alinco], [:TranceiverControlElecraft:Elecraft], [:TransceiverControlFlexradio:FlexRadio], [:TranceiverControlIcom:Icom], [:TranceiverControlKachina:Kachina], [:TranceiverControlKenwood:Kenwood], [:TranceiverControlTenTec:TenTec], or [:TranceiverControlYaesu:Yaesu] transceiver via Commander's Primary CAT Port

  2. verify that Commander can track and control your transceiver's frequency and mode


[:TransceiverControl:Transceiver Control]

[:GettingStarted:Getting Started with DXLab]

PW1Control (last edited 2019-02-09 23:06:05 by AA6YQ)