I recently tripped over an oddity in the way the K3 <-> KPA500 communications handle band switching when commanded from software vs button pushing.
Scenario 1: - KPA500 is set to go to Standby on band change - Operator sets KPA500 to Operate - Operator makes QSOs or not - Operator changes bands from either K3 or KPA500 button push - K3 and KPA500 change bands - KPA500 goes to Standby - K3 gets the word and resumes full output power - All is right in this little corner of the world Scenario 2: - KPA500 is set to go to Standby on band change - Operator sets KPA500 to Operate - Operator is making QSOs with WSJT-X, needing amp to work that "rare one" - Operator uses WSJT-X to change bands - K3 and KPA500 change bands - KPA500 goes to Standby - K3 does NOT get the word and operates as if the KPA500 were still in Operate, putting out low power vs the 100 watts expected - K3 and KPA500 are out of synch with respect to Operate vs Standby I do not think I have seen the case when using WSJT-X to command band changes where the KPA500 is in Operate and the K3 is at full power. this would not be good. So the issue seems to be band changes being commanded by software and not button pushes. Anyone else seen this? Jim N1NK K3 s/n 6xxx ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [email protected]
