During field testing of the newest firmware for the K3, KPA500 and KAT500, after a good exercise of it I was asked to post my observations and I did in a previous email to the list. There have been a few tweaks and the latest field test versions have been released as public Beta versions. They are, K3 version 4.83, KPA500 version 1.37 and KAT500 version 1.58 available for download on the Elecraft website.
I have had all of these loaded since they were released and have found no problems with them. I'm currently taking a break from the ARRL International DX contest where I'm operating Single Op, High Power Unassisted. (Normally I operate Low Power or QRP, but running 600 watts in this one with the KPA500 & KAT500 to really test the new firmware.) Last night, I started out on 10 meters and worked down to 160 meters as the higher bands closed or I had worked all the DX stations I could hear with my meager antenna system (Cushcraft A3S@35 feet and Alpha Delta DX-LB 160/80/40 shortened dipole at about 33 feet). In several previous contests, (before any of the new firmware was even available for field test) I was very annoyed by the KAT500 sporadically initiating a tuning cycle during a contest exchange, mostly on 160 and 80 meters, but occasionally on the others as well. The first iteration of the Field Test FW I was allowed to test cured some but not all of the problems. The Elecraft FW Engineering programmers have been working diligently behind the scenes to correct the bugs I (and all the other testers) reported. Prior to the start of the contest last night, I made sure the KAT500's memories were loaded by training it at appropriate intervals on all the bands which wound up (for my antennas, yours may vary) being every 10 KHz on 160 meters, every 30 KHz on 80 meters, every 50 KHz on 40, and every 100 KHz on 20,15 and 10 meters. During the 8 hours I've operated so far, I've been all the way from the top end of the 10 meter CW band through the 15, 20, 40, 80 and 160 meter bands and NOT ONCE did the KAT500 initiate a tune and the tuner automatically followed the K3's VFO, switching at the necessary points and I never saw over a 1.1:1 SWR on ANY frequency I was on. I was not in contest "run" mode, sitting on a frequency calling CQ, but "search & pounce" the entire operating time to really exercise the FW and I figure if it was going to fail, it would under those conditions. It did not. They finally think they have gotten all the bugs we reported, (bear in mind that with any software/firmware one never gets all the bugs out nor does the program ever do everything that everyone wanted it to). From the results of my operation in this contest I'm very pleased with the equipment and firmware as currently installed and barring any further minor tweaks that Wayne & crew deem necessary to make, I think these versions could very well be ready to become full production versions. Certainly those of you who have been holding back because they are listed as Beta versions ought to re-consider installing them especially if you're still frustrated by random tuning cycles initiated by the ATU at points it shouldn't. The ability for the ATU to follow the K3's RX frequency and set the LC network to a memorized combination without having to transmit is a real plus! If you DO decide to install them, BE SURE to read the release notes and instructions contained in them to properly activate the integration between the K3 and KAT500 in the menu (don't ask me why I'm emphasizing this -- LOL!) Jim Sheldon, W0EB Park City, KS K3 #5027, KPA500 #0443 and KAT500 #0037 ______________________________________________________________ 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
