K3 RTTY bug

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

K3 RTTY bug

Barry
  OK, here's a weird one...

I'm calling some of the PJs in RTTY, using Data Mode FSK and Text
Decode, operating Split.
I have my callsign programmed in M1.  I have my callsign x2 followed by
IM in M2.
When I call with M1 or M2 only, all is OK.  If I call with M1 followed
by M2, chaining them together, when back in Rx, the background noise is
present, but there are no signals.  If I press A/B twice, signals return.

Barry W2UP

--

Barry Kutner, W2UP             Lakewood, CO

______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 RTTY bug

N6JW
This is exactly the same bug I have reported here twice before.
Others have confirmed the same thing.  Wayne has indicated
that he is looking into it.

It is not a new bug.  I noticed it soon after getting my K3 #936,
but at the time I did not realize what was happening and put it
down to my own ineptitude.

While this is clearly not the same issue Wes reported in the "mode
change while in split" problem, I'm suspicious that they may be
somehow related, with the common link being use of RTTY at the
time.  Wes, where you using the FSK D mode by any chance?

The "FSK D mode chaining bug" is now well described,
reproducible, and hopefully solvable.

We await word on a possible firmware fix.

Regards to all, 73

John, N6JW


Barry wrote
I'm calling some of the PJs in RTTY, using Data Mode FSK and Text
Decode, operating Split.
I have my callsign programmed in M1.  I have my callsign x2 followed by
IM in M2.
When I call with M1 or M2 only, all is OK.  If I call with M1 followed
by M2, chaining them together, when back in Rx, the background noise is
present, but there are no signals.  If I press A/B twice, signals return.

Barry W2UP
Reply | Threaded
Open this post in threaded view
|

Re: K3 RTTY bug

n7ws
No, for the moment I'm using AFSK here.

--- On Thu, 10/14/10, N6JW <[hidden email]> wrote:

This is exactly the same bug I have reported here twice before.
Others have confirmed the same thing.  Wayne has indicated
that he is looking into it.

It is not a new bug.  I noticed it soon after getting my K3 #936,
but at the time I did not realize what was happening and put it
down to my own ineptitude.

While this is clearly not the same issue Wes reported in the "mode
change while in split" problem, I'm suspicious that they may be
somehow related, with the common link being use of RTTY at the
time.  Wes, where you using the FSK D mode by any chance?

The "FSK D mode chaining bug" is now well described,
reproducible, and hopefully solvable.

We await word on a possible firmware fix.

Regards to all, 73

John, N6JW



Barry wrote:

>
> I'm calling some of the PJs in RTTY, using Data Mode FSK and Text
> Decode, operating Split.
> I have my callsign programmed in M1.  I have my callsign x2 followed by
> IM in M2.
> When I call with M1 or M2 only, all is OK.  If I call with M1 followed
> by M2, chaining them together, when back in Rx, the background noise is
> present, but there are no signals.  If I press A/B twice, signals return.
>
> Barry W2UP
>
>



     
______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

K3 RTTY (FSK-D mode) message chaining fixed -- looking for testers

wayne burdick
Administrator
In reply to this post by Barry
Hi all,

Finally found the problem with message chaining in FSK-D mode.  
Chaining was selecting the wrong RX-mode crystal filter in some cases  
on exit from transmit. This could result in a receive frequency offset.

If you'd like to test the new field-test firmware (rev 4.15), please  
email me directly (n6kr at elecraft dot com).

73,
Wayne
N6KR

______________________________________________________________
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
Reply | Threaded
Open this post in threaded view
|

Re: K3 RTTY (FSK-D mode) message chaining fixed -- looking for testers

N6JW
Hi Wayne:

As one of the first to report this issue, I would be happy
to try out rev. 4.15.

Thanks so much for your efforts, 73

John, N6JW


wayne burdick wrote
Hi all,

Finally found the problem with message chaining in FSK-D mode.  
Chaining was selecting the wrong RX-mode crystal filter in some cases  
on exit from transmit. This could result in a receive frequency offset.

If you'd like to test the new field-test firmware (rev 4.15), please  
email me directly (n6kr at elecraft dot com).

73,
Wayne
N6KR