CW Bug with 6400M internal keyer. Ver. 2.6.1

Paul KB3ML

This one had me going in circles.

  When using CWX memories  and the internal keyer the radio will occasionally lock up in transmit.  It will behave like the t/r relay is sticking and the power button will stay Red indicating transmit.
I first thought it was RF, but ferrites would not help. I even did a Factory reset with no help.

What is happening is if you send with the paddles and send a memory before it has time to drop, it will cause the radio to stay in Transmit mode.  You must press the PTT to unlock the TX.

I sometimes send my call to be sure of his copy and then send the message which causes the problem. I guess I am a little fast on the message button.

This needs corrected in firmware.

KD0RC

Hi Paul, I have been trying to recreate this issue, and cannot make it behave this way.  I am doiing it on a dummy load.  Can you make the issue happen on a dummy load?  If not, then amybe it is RF sneaking in somewhere.

73,
Len, KD0RC

Edit:  I just noticed that you are on V 2.6.1.  I am on V 3.1.11.  That may explain it...

Paul KB3ML

Yes, It will show up with a dummy load or antenna with any power output level.

Just make sure you are still sending with the paddle when you start the memory.

It also works fine if using an external Memory keyer for the memory.

Good to see if newer SW versions have it right. 

TNX.  Len

KD0RC

Under 3.1.11, if the key is pressed when I start the memory, it tries to play the memory and whatever is sent by the paddles at the same time.  As soon as I release the paddles, the memory stops and the rig unkeys.  A bit of strange behavior, but no real issue.  I can't be sure that 3.1.11 fixed the issue, but I can't recreate the problem, so I think it is likely the software version.  Maybe someone from Flex can chime in to confirm.

Len

Uwe - DK3WW

Hello Len, I have exactly the same problem with my Flex6600 and SSDR 3.1.12. The problem should actually be known. The latest updates from SSDR have unfortunately not brought any improvements for CW. It doesn't seem to be a priority ...
73! Uwe
DK3WW

WW1SS - Steve

Nothing seems to be a priority. CW Bugs, NB don't work ,tuner does not work. But still selling known defective equipment.

Uwe - DK3WW

Steve: FLEXRADIO makes a lot of money in the military sector, drone controls, etc. That is probably more important than amateur radio and has priority ...

W5WTH

FWIW, my macros make things on my 6400 wacky if I end them early. It's aggravating.

Paul KB3ML

Very frustrating !

They have been aware of this problem for about a year now .

They assigned a trouble ticket to this problem. G7759

No excuse for such a long wait !

Paul

Lasse SM5GLC

G7759 is not this bug, that is about spurious drop out of power (seems to be OK in 2.4.10).

What I have seen is when CWX (or any computer generated CW for that matter) and the manual keying get in conflict. What I noticed when using N1MM is that aborting a message by tapping the paddle may leave the radio unsure which keying stream that is in charge. By sending one char on keyboard may "flush" the buffer and revert back to normal, a lot faster than trying to buttons on the Maestro trying to drop the PTT. (Or it may be the other way around one need to tap key to release depending on timing that caused the event )

Lasse SM5GLC

Come to think that since reverting back to SSDR 2.4.10 I have yet to see this hanging issue! And if I recall correctly there seems a bit less delay, i.e. everything is more responsive than what I remember from 2.6.2.

Paul KB3ML

G7789 is the number I was given when I had my trouble ticket open. I just checked it again.

That is all I know. I can not argue with that.

Yes , some times the radio can be unlocked by tapping either paddle to send a character.

However some times it is necessary to re boot the radio.

Very frustrating in a contest. I sure wish they can get it right.

Paul

Lasse SM5GLC

Paul,

I just commented on that you posted G7759 :)

And once again, I have yet to notice the lock-up using 2.4.10...

Paul KB3ML

G7759 is what I was given.

Lasse SM5GLC

Paul,

you have me a bit confused, you say: "G7789 is the number I was given..." and the posts "G7759 is what I was given"

The issue with spurious power drop-out was said to me beeing given G7759. And I assume the G7789 is what the transmit lock-up is about. Correct me if I'm wrong :) And by downgrading from 2.6.2 down to 2.4.10 I have not noticed any of these two bugs! And as a bonus the latency seems to be noticable less.

Paul KB3ML

I was wrong when I sent G7789. poor typing.

Sorry, The number they gave me with the trouble ticket was G7759.

I am running 3.1.12 . I am waiting for 3.2 to come.

After I see 3.2, I may fall back to 2.4.10.

TNX Paul