"AFAICR the manual says that if an AUX cable is connected between the KAT500 and the radio, the KAT500 will follow any frequency/band change and if a tuning solution has already been stored for that frequency/band it will be employed before the radio goes into TX. In other words, whilst the radio is still in RX mode.
However, elsewhere in the manual it says that when the KAT500 receives RF, it will also pickup the nearest tuning solution, which is a fail-safe action in case the KAT500 does not receive data from the radio, for any reason." Any KAT500 can have knowledge of the TX frequency either by using the RF counter or by receiving advance notice of theTX frequency by serial data or the Elecraft proprietary AuxBus. The issue is what happens when both data sets are present and they conflict. Both AUXBus and serial port data can provide TX frequency to 1 kHz resolution. The RF counter only has 8 kHz resolution. If the RF count falls outside the bin tuned by serial port data or AUXBus then the tuning solution may change when TX starts. Before formware 1.99 there were various commands available that were intended to tailor the priority given to RF count but they did not work as documented. These commands were replaced by FDT command which is what allows the user to configure the frequency difference for which RF count will override serial / AUXbus frequency. Unlike the earlier "tailoring" commands, FDT does work as documented. Andy, k3wyc ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com