Elecraft

AUXBUS Troubleshooting

Classic

List

Threaded

5 messages Options

Karin Johnson

AUXBUS Troubleshooting

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 not take up the list with back and forth debugging this
issue. Anyone on the list have
Some knowledge of the AUXBUS protocol that I could communicate with to run
down this issue.
I have posted on the WSPR Yahoo group and the WSPR net site some comments on
this issue.
Regards, Karin K3UU Palm Harbor, FL

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

______________________________________________________________
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 Wilhelm

Re: AUXBUS Troubleshooting

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 pass those signals to the MCU (in TTL compatible voltages) using
pins 24 and 25 of Control Board U6 (TXD and RXD) - in turn the MCU will
either operate the proper K2 circuits directly or communicate with
whichever option firmware IC is needed to complete the request.

What faulty operation are you experiencing? You can email me privately
or send your reply to the reflector.

I have had experience with the K2 since 1998 and regularly service the
K2 (about 3 a week this year) and have never had to debug anything on
the AUXBUS except to verify that it is producing pulses. Even though I
do some of that work for Elecraft, I do not have access to the AUXBUS
protocol, nor have I needed it.

In other words, the AUXBUS has no relationship with the K2 serial
communications, so I believe you may be looking in the wrong area.

73,
Don W3FPR

On 12/22/2017 3:44 PM, Karin Johnson wrote:

> 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 not take up the list with back and forth debugging this
> issue. Anyone on the list have
> Some knowledge of the AUXBUS protocol that I could communicate with to run
> down this issue.

______________________________________________________________
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]

Jack Brindle-2

Re: AUXBUS Troubleshooting

In reply to this post by Karin Johnson

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 thing to remember with the K2 is that the
AUX I/O connector carries more than just RS-232 signals, and when connecting the
radio to the computer these non-RS-232 signals MUST NOT connect to the computer
DE-9 connector at all, or very bad things will happen.

Jack Brindle, W6FB
Elecraft Engineering

> On Dec 22, 2017, at 12:44 PM, Karin Johnson <[hidden email]> wrote:
>
> 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 not take up the list with back and forth debugging this
> issue. Anyone on the list have
> Some knowledge of the AUXBUS protocol that I could communicate with to run
> down this issue.
> I have posted on the WSPR Yahoo group and the WSPR net site some comments on
> this issue.
> Regards, Karin K3UU Palm Harbor, FL
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> ______________________________________________________________
> 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]

wayne burdick

Re: AUXBUS Troubleshooting

Administrator

In reply to this post by Karin Johnson

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 auxbus handler was rewritten in the K3 so it can’t miss such traffic.

73,
Wayne
N6KR

----
http://www.elecraft.com

Don Wilhelm

Re: AUXBUS Troubleshooting

In reply to this post by Jack Brindle-2

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.

73,
Don W3FPR

On 12/22/2017 4:20 PM, Jack Brindle wrote:

> 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 thing to remember with the K2 is that the
> AUX I/O connector carries more than just RS-232 signals, and when connecting the
> radio to the computer these non-RS-232 signals MUST NOT connect to the computer
> DE-9 connector at all, or very bad things will happen.
>
> Jack Brindle, W6FB
> Elecraft Engineering
>
>
>> On Dec 22, 2017, at 12:44 PM, Karin Johnson <[hidden email]> wrote:
>>
>> 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 not take up the list with back and forth debugging this
>> issue. Anyone on the list have
>> Some knowledge of the AUXBUS protocol that I could communicate with to run
>> down this issue.
>> I have posted on the WSPR Yahoo group and the WSPR net site some comments on
>> this issue.
>> Regards, Karin K3UU Palm Harbor, FL
>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>> ______________________________________________________________
>> 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]
>