For the next poor soul that tries to use MixW with a K3! Problem:
I posted the problem outlined below to the MixW Yahoo group I manage, after posting it here. This group correctly tagged the issue as a MixW issue, which I was not sure I believed until K9JWI, Clyde solved this problem as outlined below. Problem: When using the K3 and MixW, (3.11 March 4th, 2012, or as it is sometimes called MixW 3.11h), and selecting Kenwood/K3, (either 2 CH, or non 2 CH), from the rig configuration within MixW, the following actions would occur: A. If "CW is LSB" is checked, (in MixW Serial port configuration), on all bands above and including 21 MHz, the signal on the waterfall and the tuning indicator on the waterfall would operate as expected. i.e. the rig/MixW worked fine. Signal tracked waterfall frequency display. B. If "CW is LSB" is checked on any band below 21 MHz., the tuning indicator on the top of the waterfall would work as expected, however the signal would move in the opposite direction of tuning, (no longer tracking Waterfall frequency), i.e. as I tune up, the waterfall frequency indicator moved in the correct direction, and the signal would take off in the opposite direction. C. Workaround: Unchecking "CW is LSB", would correct the action described in B above, (making the rig work as expected), and break it as described above in A above. D. After posting this to the MixW list, and after several people looked into it, the decision was made that MixW was handling the "CW is LSB" in error, and that the K3 and all macros were fine. Several days later Clyde popped up with this message: ==========CUT========== Dave & Colin, Here is some more fuel for the fire. In CAT settings check "CW is LSB" and select "All Kenwoods" instead of "Elecraft K2,K3". Then all works as expected here. Align works properly on all bands. Signal traces on the waterfall move along with the frequency scale instead of in the opposite direction. All without having to check and uncheck "CW is LSB" depending on which band is in use. Why? 73, Clyde K9JWI ===========CUT========= While I can't answer Clyde's question yet, this pretty well confirms that MixW's implementation for K3 rig control is bogon, and should not be used. The K3 is not at fault in any way for this. This however did not seem to fix the issue of MixW spraying out a lot of excess data for control of the rig when it comes to tuning. The thumbwheel tuning still lags quite a bit... This pretty well gets me back to where I was with my Icom 756 PRO III for rig control, and I like the radio better, so I am a lot happier with my K3 now... -- Thanks and 73's, For equipment, and software setups and reviews see: www.nk7z.net for MixW support see; http://groups.yahoo.com/neo/groups/mixw/info for Dopplergram information see: http://groups.yahoo.com/neo/groups/dopplergram/info for MM-SSTV see: http://groups.yahoo.com/neo/groups/MM-SSTV/info ______________________________________________________________ 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]
