Differences between revisions 3 and 4
Revision 3 as of 2010-04-24 03:29:48
Size: 1801
Editor: AA6YQ
Comment:
Revision 4 as of 2010-04-24 03:55:58
Size: 1796
Editor: AA6YQ
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
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. 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.
Line 11: Line 11:
With no other devices connected to the CI-V bus, this arrangement enables the PW-1 to accurately 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 collision; the result is that the PW-1 fails to accurately track the transceiver's frequency. 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.

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.


[:TransceiverControl:Transceiver Control]

[:GettingStarted:Getting Started with DXLab]

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