Power cycle cured CW timing problem.

Pat_W5WTH

@KD0RC Thanks for the help. Yes, I do import the latest. That said, I created a "new" latest based on your comment. I will know in a week or two after the rig loses it's mind and forgets everything I taught in when it decides not to wake up correctly after I do the power cycle to correct the forever ongoing CW timing issue. 🤬

Thanks again for all your help on the forum!!!

reed

Discovered this bug tonight while tuning up my key. Pretty surprising for such an expensive rig to do so poorly on this seemingly simple task.

I tried transmitting from the 6600 into a dummy load while listening with my other rig:

1) using a paddle directly into the rig, I first hold dah continuously, then hold dit continuously. In both cases, you can clearly hear hiccups or glitches in the pattern.
https://youtu.be/cV1cwSREqIU

2) using the CWX SSDR interface, I send "5555555", so the pattern expected is a repeating "di-di-di-di-di [brief pause]". However, the pattern received includes extra pauses, and even some dahs! Yikes!
https://youtu.be/p9qTfHDtS5s

KD0RC

Hi Reed, I know that Flex is aware of this issue, but I don't know if they have been able to recreate it. It might be a good idea to open a help desk ticket with reference to your videos.

Pat_W5WTH

With all due respect...... The only way possible that Flex has not been able to recreate the issue is:

1) they have zero CW operators or

2) they reboot each and every rig they run machine almost every day or

3) they don't care.

sq5nry

Hello,
I'm using FLEX6300 with v3.4 and found same symptoms described in the thread. Is there any viable workaround to make CW work with this model?
Re-start cures the bug but in reality it's always too late after a DX appears. I tried with lower wpm but could never get a better keying than that by hand :(
Any suggestions warmly appreciated.

Best 73,
Paul sq5nry

Rich M5RIC

Was there ever a fix for this, did it get resolved for everyone in a later release?

KD0RC

Hi Rich, this is fixed. I recommend moving to the latest version (3.7.4 or 2.12.1).

Rich M5RIC

Hi Len

A friend is on 3.7.4 and had this issue at the weekend, so just trying to see what is out there and possible solutions. Radio was powered off several times and the issue still remained.

Will put a ticket in if we can't find anything that resolves it.

Cheers

Rich

KD0RC

Hi Rich, yep I would put in a ticket.