Love my KX3 but ran into some strange behavior as of late with some hangs.
Running MCU 2.25 / DSP 1.30 when trying to change ACC2IO settings, when I turn VFOA to LO=Ptt the unit hangs on the LO=Ptt option - display freezes at LO=Ptt and I can't PWR off using ATU/BAND-. I've tried re-flashing MCU/DSP firmware with KX3 utility and even tried EEINIT reset - still the same hanging on ACC2IO menu. Anyone else having this issue? Any ideas for a fix? TIA. 73's David - KI4UVC |
David,
What do you have connected to the ACC2IO jack? Is there possibly anything there that could be holding that signal to ground? 73, Don W3FPR On 10/18/2014 9:27 AM, David - KI4UVC wrote: > Love my KX3 but ran into some strange behavior as of late with some hangs. > > Running MCU 2.25 / DSP 1.30 when trying to change ACC2IO settings, when I > turn VFOA to LO=Ptt the unit hangs on the LO=Ptt option - display freezes at > LO=Ptt and I can't PWR off using ATU/BAND-. > > I've tried re-flashing MCU/DSP firmware with KX3 utility and even tried > EEINIT reset - still the same hanging on ACC2IO menu. > > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Nothing is connected to ACC2 currently - I was mucking around with menu settings.
I tried reverting back to MCU2.23 and am having the same issue - radio hangs at any change in ACC2 settings. I didn't have this issue until I did the Extended Temp Calibration routine. Radio is in the low 6000 s/n range - has all internal options except for 2m. Might have to send back to Elecraft for some brain surgery... - David |
David,
Contact KX3support(at)elecraft.com to see if they can offer any additional wisdom. If it has to go back to Elecraft for work, that contact at support is the starting place to obtain an RSA. 73, Don W3FPR On 10/18/2014 10:53 AM, David - KI4UVC wrote: > Nothing is connected to ACC2 currently - I was mucking around with menu > settings. > > I tried reverting back to MCU2.23 and am having the same issue - radio hangs > at any change in ACC2 settings. > > I didn't have this issue until I did the Extended Temp Calibration routine. > Radio is in the low 6000 s/n range - has all internal options except for 2m. > > Might have to send back to Elecraft for some brain surgery... > > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
In reply to this post by David - KI4UVC
David,
I did not have my brain fully in gear on this situation before. The GPIO input is just that - an input to a 3 volt logic device with only a 500 ohm series resistor. So there is nothing to make it either a high nor a low level. In the digital world it is known as a 'floating input' and without some other (external) hardware addition, it may appear to be either at a high or a low level depending on the "shifting of the winds in the desert" Sooo - that may be a normal response when a LO function is used on the GPIO input signal. Take note of the part in the menu instructions saying that some external interface circuitry may be required. The GPIO input has no pullup resistor to 3 volts to keep it high - that means the voltage just floats at whatever it happens to be. If that voltage happens to be below the logic threshold for a LO level, the function will become active when that menu option is selected - and will happen with nothing connected to the GPIO input. (The same might happen when HI is selected in the menu too). The solution is to bring that input level to a high state with an external pullup resistor. One end of the resistor goes to a voltage source (ideally 3 volts, but up to 5.5 volts will be tolerated. The other end of the resistor goes to the GPIO input (ACC2 connector tip) - and oh yes, the negative of the source powering it would connect to the connector shell. Two AA battery cells in series and a 33K resistor should work nicely and the batteries should last a long time. Then your PTT switch, footpedal, etc. would place a short between the ACC2 connector tip and shell when it is active. Note also that if you make the GPIO menu selections for either HI or LO, that condition may become active any time the plug is removed from the ACC2 jack. In other words, you must connect an external high or low logic level before turning the KX3 on. You may find it easier to build an adapter and use the microphone jack PTT input which has an internal pullup resistor which assures a high state when the PTT circuit is open or inactive. 73, Don W3FPR ----------------------------------------------------------- David, Contact KX3support(at)elecraft.com to see if they can offer any additional wisdom. If it has to go back to Elecraft for work, that contact at support is the starting place to obtain an RSA. 73, Don W3FPR On 10/18/2014 10:53 AM, David - KI4UVC wrote: > Nothing is connected to ACC2 currently - I was mucking around with menu > settings. > > I tried reverting back to MCU2.23 and am having the same issue - radio hangs > at any change in ACC2 settings. > > I didn't have this issue until I did the Extended Temp Calibration routine. > Radio is in the low 6000 s/n range - has all internal options except for 2m. > > Might have to send back to Elecraft for some brain surgery... > > ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
Don,
Thank you for your very informative and helpful post - this clears up quite a bit of how the ACC2 interfacing is taken care of. I contacted Elecraft support and was given my original settings (I had neglected to save) and restored the unit to "factory fresh" status - with the exception of having the latest up-to-date-firmware. What is interesting about out this is that I have "possibly" discovered a bug not many will run into. When I restored my unit to original factory settings - I am able to move/set the ACC2 to different "states" in the firmware/menu with no issues whatsoever - irregardless of what frequency VFO1 is set to. So I can set ACC2 menu options for all options and the unit functions normally - irregardless of in-band or out-of-amateur band VFO1 settings. Just like in the KX3 manual I can try setting the ACC2 menu options for OFF (output, 0 V), ON (output, 3 V), LO=PTT (input; apply 0 V or ground to activate PTT), HI=PTT (input; apply 3 to 5 V to activate PTT), LO=Inh (input; 0 V inhibits transmit), HI=Inh (input; 3 to 5 V inhibits transmit), TRN CTRL - and everything works just fine and dandy. It's AFTER I run the KX3 Extended VFO Temperature Compensation Procedure that things get interesting. If VFOA is tuned to any of the Amateur bands (in band) I have full access to the ACC2 menu options. If I try any of the ACC2 options while the KX3 is tuned outside the amateur bands (Specifically the XG50 49.380 frequency for instance) the moment that I use VFOA to try and select any of the ACC2 menu options this sequence happens: I select Menu -> ACC2 (via VFOB )-> OFF to ON (VFOA - OK) -> ON to LO=PTT (VFOA - unit hangs - no buttons or knobs operate and unit won't power down unless power is removed) The might not affect many people that try changing ACC2 settings in the amateur bands, but this outside of band behavior with the total lockup of my unit is a bit of a pain. Not that I'm going to be mucking with ACC2 settings that often! - David |
Administrator
|
Bug, now on the list.
tnx Wayne N6KR On Oct 23, 2014, at 10:23 AM, David - KI4UVC <[hidden email]> wrote: > Don, > > Thank you for your very informative and helpful post - this clears up quite > a bit of how the ACC2 interfacing is taken care of. > > I contacted Elecraft support and was given my original settings (I had > neglected to save) and restored the unit to "factory fresh" status - with > the exception of having the latest up-to-date-firmware. > > What is interesting about out this is that I have "possibly" discovered a > bug not many will run into. > > When I restored my unit to original factory settings - I am able to move/set > the ACC2 to different "states" in the firmware/menu with no issues > whatsoever - irregardless of what frequency VFO1 is set to. So I can set > ACC2 menu options for all options and the unit functions normally - > irregardless of in-band or out-of-amateur band VFO1 settings. > Just like in the KX3 manual I can try setting the ACC2 menu options for OFF > (output, 0 V), ON (output, 3 V), LO=PTT (input; apply 0 V or ground to > activate PTT), HI=PTT (input; apply 3 to 5 V to activate PTT), LO=Inh > (input; 0 V inhibits transmit), HI=Inh (input; 3 to 5 V inhibits transmit), > TRN CTRL - and everything works just fine and dandy. > > It's AFTER I run the KX3 Extended VFO Temperature Compensation Procedure > that things get interesting. > If VFOA is tuned to any of the Amateur bands (in band) I have full access to > the ACC2 menu options. > If I try any of the ACC2 options while the KX3 is tuned outside the amateur > bands (Specifically the XG50 49.380 frequency for instance) the moment that > I use VFOA to try and select any of the ACC2 menu options this sequence > happens: I select Menu -> ACC2 (via VFOB )-> OFF to ON (VFOA - OK) -> ON to > LO=PTT (VFOA - unit hangs - no buttons or knobs operate and unit won't power > down unless power is removed) > > The might not affect many people that try changing ACC2 settings in the > amateur bands, but this outside of band behavior with the total lockup of my > unit is a bit of a pain. Not that I'm going to be mucking with ACC2 > settings that often! > > - David > > > > > > -- > View this message in context: http://elecraft.365791.n2.nabble.com/ACC2-PTT-2-25-1-30-bug-tp7593972p7594094.html > Sent from the Elecraft mailing list archive at Nabble.com. > ______________________________________________________________ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[hidden email] > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to [hidden email] ______________________________________________________________ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[hidden email] This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to [hidden email] |
In reply to this post by David - KI4UVC
Thinking about this - perhaps with ACC2 set to Lo=PTT the unit is attempting to transmit and notices it is "out of band" and just hangs up the firmware??? What's strange is that this behavior does not happen until I try the Temp Compensation routine - which you would think would only affect the PLL/Oscillator lookup tables.
- de KI4UVC |
In reply to this post by wayne burdick
Thanks for looking into this Wayne. I hope my discovery helps.
Elecraft support is fantastic- and I'm continually impressed with your active involvement in the Elecraft community. If only all companies were run the same way, the world would be a much better place. Cheers and 73's -David |
Free forum by Nabble | Edit this page |