Power cycle cured CW timing problem.

Rick N0VT

Is there something in SSDR 3.2.39 that would throw my CW timing off? At the start of yesterday's NAQP about 25% of my computer-generated CW was horrendous--spaces in mid-character, dits & dahs the wrong length. Lots of requests for repeats. After checking my PC and N1MM, I finally solved the problem by power cycling the 6600. After that the issue completely disappeared. That's the first and only time that's ever happened so I'm curious if it might have been due to something recently changed in the software.

73

Rick N0VT

W7NGA

Rick,

Thanks for posting. I was just about to post my observations with my 6600 and SDR 3.2.39. I had noticed that the timing on CW was off, both direct keying and CWX. I verified with an oscilloscope that the RF was miscued and not just a sidetone anomaly. Rebooting the 6600 always cures the problem.

What appears to be a memory leak, manifests after a day or two of operation (mainly receiving). After that interval I start experiencing errant timing on CW. It is always returned to normal operation and proper timing after a reboot.

Aggravating and hopefully a fix is imminent since this is a well-documented (and lingering) issue.

W7NGA

K1ESE

Same thing here. I now restart the remote 6300 before each contest. Needs a fix.

Pat_W5WTH

Just to reconfirm the issue….

Same thing here on my 6400 with the last SSDR update. Power recycle fixes it. It’s aggravating to seemingly deal with so any minor Flex issues constantly.

Joe N3HEE

Same thing with my 6600M 2.7.6.

Mike McWhinnie/GM0DYU

Same with my 6400M running 3.2.39, a reboot fixes it for a few days. Think I might shell out for an outboard keyer unit, ZLP Electronics make a nice reasonably priced one in the UK, shame though given the price of the radio. If its a software issue it really needs some effort put into it to resolve.

73 Mike

W7NGA

Mike,

Keep in mind that the problem will still exist using an external keyer. I first noticed the problem when I was using my new Begali Intrepid mechanical bug. I monitor the sampled RF output and could see that the timing was skewed. I then tried to send a string of dits with the internal keyer using a paddle and the stutter was quite evident. It all cleared once I rebooted.

Mike McWhinnie/GM0DYU

Thanks W7NGA for that. I rebooted a few days ago and do not have the issue at present, will check with a straight key plugged in when the fault returns. Intuitively I had thought that using an external keyer with Iambic turned off on the radio would fix the issue, from your comment it appears the internal keyer is still in play even when Iambic is deselected.

73 Mike.

Mike McWhinnie/GM0DYU

OK so the plot thickens, for me at any rate. I have the CW timing issue right now on the 6400M, using the internal keyer and a Kent paddle, CW is mistimed intermittently. So I replaced the paddle with a straight key and set IAMBIC to off, a couple of QSO using the straight key and no issues noted with CW timing. So for me CW timing issue seems to be only apparent using the internal keyer in IAMBIC mode, so I may well try an external CW keyer interface see what happens.

73 Mike.

W7NGA

I am sitting here waiting for my 6600 to reboot. Tried calling a relatively high-speed CQ on 20 meters and the timing was unacceptable. From what I have experienced, the issues are not related to the key source (straight or iambic) or the internal keyer. Easily identifiable by sending a string of dits and the resultant stutter that occurs both in sidetone and RF output. Thankfully, a full reboot restores proper operation.

Pat_W5WTH

The reboot "fixes" my CW timing issues, but it a hassle because I have to re-establish some 3rd party programs I have talking to the FLEX6400 each time I reboot it. And..... that means a trip to the equipment.

Not very convenient for me and I hope it gets corrected. Any word on progress of a fix or acknowledgement that the problem is real?

73!

KD0RC

I have only had the issue when operating remotely, so this may or may not help.

In my case, setting CW Delay up cleared up the sending. I needed anywhere from 30 ms to around 100 ms. 100 was for an atrocious internet connection using a cell phone hotspot.

Steve Ellington

Is Flex looking at this bug? It's horrible. Using the internal keyer produces pure garbage after the 6600 has been running a few days. Reset takes care of it but that isn't a "cure".

Pat_W5WTH

i hope so. It makes the rig near unoperational if I am remote via the Maestro.

I issued a ticket and Flex gave me a few experiments to try. As luck would have it organizing shack cables and thunderstorms have forced a few “natural” reboots thus delaying things.

Les Brown

I also experienced this problem the other day just as I was starting a CWT session. I had to reboot the 6600M. I hope Flex will fix this.

73, Les VE3NNT

Mike-VA3MW

All, yes we are aware of this issue.

The quick fix is to reboot prior to a contest. Once I have more to share on the issue, I will.

Please understand that we have a policy of keeping quiet on issues until they are resolved.

73 all

Erik Carling EI4KF

"Please understand that we have a policy of keeping quiet on issues until they are resolved" - I am sure we all do but that policy does lead to endless reports of the same issue and endless requests for updates due to the Flex user base being kept uninformed.

Dick Illman

I have the same problem and inconvienient solution for CW stuttering on my 6700. It seems to be a long time since the last software update...

Old bugs should fixed before new features.

Ted S

This bug is very repeatable it appears after every 72 to 96 hours of continuous operation on my 6400. It clears with a simple power cycle.

Being so repeatable, it shouldn't be difficult to debug.

Ted WR4T

John KB4DU

Getting it debugged and then getting a bug fix release seem to be two different actions.

Erik Carling EI4KF

Whether it is one or two, the exorbitant length of time in getting something out to us that fixes this timing error is excruciatingly disappointing. In a product of this price and claimed quality, to have a fault in a fundamental mode such as CW that remains unfixed, with the last comment from Flex more than 5 months ago and said fault on-going for much longer, is ..... I don't need to say it, do I?

W7NGA

This is surprising to have an issue so well documented .. ostensibly being wholly ignored. One of the selling points of an SDR is that it is, at heart, a software device, easily updated and extended. Neither is occurring for some odd reason.

73

W7NGA

Pat_W5WTH

Well, on the plus side.....

My cootie sending skills have improved.

Pat_W5WTH

Gee wizz for the love of Pete.....

I hate to add to the negative thread, but.....

OK, I'm used to doing a **** reboot of my Flex every morning to "fix" the CW timing bug.

However, I am getting sick and tired of that reboot causing my Flex to lose all it's setting about once a week after I do that reboot.

I "fix" one issue fully knowing that it's a Russian Roulette game for causing another one.

This has been ongoing for a long time now. Come on Flex, as a consumer I really expect better (please).

Pat_W5WTH

Ha! The forum "starred" out the word "s-t-u-p-i-d". I guess it's a bad word here. HIHI

Steve Ellington

Same issue with CW here. It's almost as if a buffer gets filled up after a few days and after that happens cw just falls apart with erratic code elements galore. Power cycling always cures it. I've gotten to where I power it off every night.

Looks like this thread has been around since last August and not cure from Flex yet.

KD0RC

Hi Pat, I always do a profile export before I do a factory reset. Even if you don't use profiles, the state of the radio is saved. After the reset, do a profile import, and the radio should be back where it was.

Doesn't change the fact that you need to do a reset, but at least the rig is set back where it was.

W7NGA

No reason for a factory reset. Simply power off and back on. Nothing lost.

Steve Ellington

Same issue with CW here. It's almost as if a buffer gets filled up after a few days and after that happens cw just falls apart with erratic code elements galore. Power cycling always cures it. I've gotten to where I power it off every night.

Looks like this thread has been around since last August and not cure from Flex yet.

Pat_W5WTH

@KD0RC

Either I am saving profiles wrong or they just don't save the right settings for me. I'm 99.9% CW and have had the issue so many times (yes, I have entered tickets) that I created a pre flight list to help me recover. It's not a quick process and it's idiotic that I have to do it; takes a bit of the pleasure out of buying a 'premium' rig. All I can say is "PRAISE to FRStack" as it helps reduce the sting.

If I am doing something wrong on the profiles export/import then I ready to learn. :). For those with similar pain, here is my script.

 Profiles... Import Profile with Memories

- Setting.... Radio Setup... CW... Click CWL

- Settings... TX Band Settings.... PTT Inhibit 160 and 6+

- CW   

   - Delay 120

   - 18 WPM

   - Sidetone 10

   - Add CWX Function Keys

      Set QSK Off

      F1      CQ CQ DE W5WTH W5WTH K

      F2      CQ DE W5WTH

      F3      CQ SKCC CQ DE W5WTH W5WTH K

      F4      W5WTH

      F5      QRL?

      F7      CQ SST CQ DE W5WTH W5WTH K   

- DSP Settings

- Per Band:

   - ATU

   - Display

   - PWR

   - AGC

KD0RC

Hi Pat, are you sure that you are importing the most recently exported profile and not grabbing an older one by mistake?

If that is not it, then I am out of ideas...