Well, now, I am both confused and eating crow! Now it is working as expected. I have no idea what I was doing wrong before. Both the VOX function and the indicator are now going on with VX1;.
Talk of a tempest in a teapot! 73 and thanks - George On 9/25/2019 7:22 PM, Dick Dievendorff wrote: > [This message came from an external source. If suspicious, report to > ab...@ilstu.edu<mailto:ab...@ilstu.edu>] > > Setters don't respond. Try ^VX1; and then follow it with ^VX; to see what it > set. > > rvm; <_ commands in lower case > RVM05.67; <- responses in upper case. > vx; > VX1; > vx0; > vx; > VX0; > vx1; > vx; > VX1; > > 73 de Dick, K6KR > > > > -----Original Message----- > From: elecraft-boun...@mailman.qth.net <elecraft-boun...@mailman.qth.net> On > Behalf Of Kidder, George > Sent: Wednesday, September 25, 2019 15:54 > To: elecraft@mailman.qth.net > Subject: Re: [Elecraft] VX commands don't work > > GE Wes - Is your success on a K3 or K3s? Just installed latest firmware > (5.67) and there is still no SET response to "VX1", although "VX" does GET > the state. Just like Don said, but this is not what is in the manual. > > George > > On 9/24/2019 2:27 AM, Wes wrote: >> [This message came from an external source. If suspicious, report to >> ab...@ilstu.edu<mailto:ab...@ilstu.edu>] >> >> Works for me too. Latest F/W installed. >> >> Wes >> >> On 9/22/2019 4:17 PM, David Box wrote: >>> VXn works for me, don't remember the firmware change that activated >>> the set feature about a year ago. >>> de Dave K5MWR >>> >>> On September 22, 2019 4:30:54 PM MDT, Don Wilhelm >>> <donw...@embarqmail.com> wrote: >>>> George, >>>> >>>> The VX command is "GET" only, so you can determine the VOX status, >>>> but you cannot SET it. >>>> See the K3 Programmer's Reference Manual. >>>> >>>> 73, >>>> Don W3FPR >>>> >>>> On 9/22/2019 6:16 PM, Kidder, George wrote: >>>>> GE all, >>>>> >>>>> I recently tried to incorporate the VX command into some macros for >>>> my >>>>> older K3. With the K3 utility connected directly to Com1, the VXn >>>>> command has no effect on the VOX state, although other commands >>>>> work >>>> as >>>>> expected. I run the VOX on AUTO OFF (CW WT tap 5) to avoid startup >>>>> problems, but returning to NOR has no effect. Is this a known bug >>>>> or >>>> a >>>>> single-unit flaw. Any others have this experience? >>>>> >>>>> I can certainly live without this feature - I have for nearly a >>>> decade, >>>>> but it would be nice to have it in some macros. >>>>> >>>>> George, W3HBM >>>>> Bar Harbor, ME >> >> ______________________________________________________________ >> 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 >> gkid...@ilstu.edu > ______________________________________________________________ > 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 d...@elecraft.com > ______________________________________________________________ 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
