Re: [Elecraft] AUXBUS Troubleshooting

2017-12-22 Thread Don Wilhelm
Karin, Jack makes a very valid point. If you are not using the K2 to PC special cable to the AUX IO connector that removes all but TXD, RXD and SIGNAL GROUND from the RS-232 cable, the K2 may display "strange happenings" or in the worst case can cause damage to both the K2 and serial port.

Re: [Elecraft] AUXBUS Troubleshooting

2017-12-22 Thread Wayne Burdick
The auxbus is activated briefly on band changes to update transverters and the KRC2, whether present or not. It’s possible that during auxbus activation, the K2 may be missing an RS232 character or two. (Interrupts are locked out.) I’d have to dig into the K2 code to determine this. The

Re: [Elecraft] AUXBUS Troubleshooting

2017-12-22 Thread Jack Brindle
Karin; Please elaborate on exactly what you are trying to do and what you are seeing. The AUXBUS data stream is not a part o the CAT system, and is used only internally for communications between our modules. If you are seeing CAT issues, then I strongly suspect something else is going on. One

Re: [Elecraft] AUXBUS Troubleshooting

2017-12-22 Thread Don Wilhelm
Karin, The AUXBUS is Elecraft proprietary and is used to communicate between the MCU and all other firmware devices in the K2 system. So your "Strange bit streams" are not likely to be related to WSPR controls. If WSPR gets the proper data on the RS-232 signals, the KPA100 or KIO2 will

[Elecraft] AUXBUS Troubleshooting

2017-12-22 Thread Karin Johnson
Hello Group: I am trying to debug an issue I am having with CAT control of an Elecraft K2 using the WSPR software. WSPR is setup to use CAT control for turning on the Xmtr. That part works but I'm seeing some very Strange bit streams on the AUXBUS during the WSPR control sequence. I would rather