Welcome to the new FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
If you are having a problem, please check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

Remote Latency (RTT) change with Maestro CW keying

K9SO
K9SO Member ✭✭
edited April 2020 in SmartSDR for Windows
I've been receiving reports of bad keying when I try to operate my Wisconsin station remotely from my North Carolina home. I have mirrored systems at each location so I can listen to my Wisconsin signal from North Carolina and vice versa. I have confirmed that my Wisconsin CW is broken ("stuttering"?) when I key it from the NC Maestro. Keying settings are correct since on occasion, keying is just fine. 

I operate via a VPN and not via SmartLink. The system has operated flawlessly for over 5 years this way. 

Since I'm running SmartSDR v. 3.0.27 at all sites, I have the capability of logging into the Wisconsin radio via a PC and via the Maestro simultaneously and I can see network diagnostics on both links. The two access points are side by side and plug into the same network switch. 

Here's the issue causing the bad CW (I think): I normally see a consistent average RTT latency of about 72 mS. When I key the Maestro via the paddle, the Maestro diagnostics shows the latency rising from 72 to nearly double that (130-140mS). The connection "quality" bars go from 3 yellow to 1 red. I do not see any change in latency on the PC connection to the same radio (simultaneously). I see no change in the PC "quality" bars either when I key the Maestro or via CWX.  I believe this rapid change in latency in the Maestro connection is causing the keying problems.

Keying via CWX on the PC is fine, is not distorted, and it does not affect the latency of the connection as does keying on the Maestro. All of my tests on the network itself show no problems. 

I'm puzzled by this one other than to say there's some defect in the Maestro here. Ideas?

Equipment involved:
Wisconsin: 6600 and PowerGenius XL amp
NC: Windows 10 PC and 1 year old Maestro.
PFSense router/VPN and 10/100 unmanaged switch.

 




Comments

  • JohnSweeney
    JohnSweeney Member ✭✭
    edited August 2019
    I believe this is defect #7378 which has yet to be fixed by Flex.  It is the single reason why I stay with V2.49 even though I would love to have Version 3 functionality. See this post:
    https://community.flexradio.com/flexradio/topics/maestro-cw-bug-7378-not-fixed

  • K9SO
    K9SO Member ✭✭
    edited August 2019
    Thanks for that info John. I back loaded 2.5.1  from the startup menu earlier and I think it was showing the same symptoms but admittedly, I didn't test very thoroughly.

    Maybe 2.5.1 has the same issue? I'll try 2.4.9 tomorrow.

    Thanks again,
    73,
    Fred
  • JohnSweeney
    JohnSweeney Member ✭✭
    edited August 2019
    yes, 2.5.1 has the same issue.  It is the only reason i stayed with 2.4.9.   When operating remote most of last Winter, I was extremely impressed with how well CW worked with my keyer plugged into my Maestro.  I am old fashioned and like to send CW with a paddle.  When I heard that Flex broke that capability in the new software releases, I was very disappointed.  I do hope it is fixed before this coming Winter as I really want Version 3 functionality.
  • JohnSweeney
    JohnSweeney Member ✭✭
    edited August 2019
    By the way, I will be happy to eat my words if someone from Flex tells me I am wrong on any of my statements.
  • K9SO
    K9SO Member ✭✭
    edited August 2019
    I have to say that in my view the shine has come off the FlexRadio apple and I've removed my rose-colored glasses. 

    I changed my system back to 2.4.9 this morning and all is working again. To me, that's the smoking gun.  I conclude that FlexRadio, with version 3.x,  has knowingly released a piece of software... THAT THEY CHARGE $300 PER RADIO for... that doesn't work. I say knowingly because they have a defect number assigned to this problem that still hasn't been resolved. I suppose in the minds of software engineers this makes it all right.

    It does not make it right. This defect is a product killer. John isn't being old fashioned here ... paddle keying is what CW is all about. RemoteRig knows this and their system of remote keying actually works. I may have to go back to that if Flex keeps messing with the software without properly vetting it. "We need the revenue ... release 3.0 ... we'll fix it later."

    I changed to FlexRadio and bought two radios, amplifiers, and two Maestros at least partially because of how well the remote paddles worked. I upgraded to 3.0 because it was the latest and greatest. Now my Maestros don't work with a paddle any more?

    I spent $7000 for amplifiers worth $5000 without an auto tune feature that was promised and never delivered.

    Having spent nearly $20,000 on FlexRadio hardware over the past few years, I naively expected more.

    The shine has come off this apple. 




  • JohnSweeney
    JohnSweeney Member ✭✭
    edited August 2019
    I do wish someone from Flex could give us some encouragement on this issue instead of silence.
  • chris1165
    chris1165 Member ✭✭
    edited August 2019
    I just purchased a 6400 and the Maestro.  Both work fantastic except for the CW from the Maestro.  I loaded 3.0.27 because it was the latest version.  Here's what I experienced.

    The 6400 is connected directly to my Wifi Router (TPLINK).  The Maestro is connected via the same Wifi Router; to the same network via 5G.  RTT is 1ms, Total RX rate is 1400 kbs, Max Latency RTT is 110 ms and 7 dropped out of 120,000 packets (0.001%).

    Listening via WebSDR and sending a series of V's, I hear U's.  I press the MOX button, start transmitting the same series and obviously, no issues.  Of course, I have to unpress the MOX if I want to go back into receive mode.  I'm sitting next to the router.  It doesn't matter if I connect to 5G or something lower, the same results.

    I downgraded to 2.4.9 and the problem went away.  Works flawlessly so far.

    Question: What is the harm in using 2.4.9 on the Maestro?  Also, does that mean on the computer I'll have to downgrade to 2.4.9 as well?

    de N3MLB

  • K9SO
    K9SO Member ✭✭
    edited August 2019
    Yes. In order to operate the radio with the Maestro, you had to reload 2.4.9 into the radio also. So in order to access the radio from the PC now, you will have to run 2.4.9.

    Of course, you could still run 3.x, but you would have to select that when connecting and wait for the radio to reload the firmware for that. That just takes a minute or two.

    You should read the release notes for all the SW versions released since 2.4.9 to understand the downside. There were some improvements, but of course as you discovered, the big downside is that CW keying does not work properly with 2.5.x or 3.x versions when using the Maestro on high latency connections (e.g., >50ms RTT). 

    Apparently, you are seeing this with low latency connections as well so you may have something else going on. Check the TX delay settings on your Maestro and make sure your PTT outputs (TX1/TX2/TX3) have a lower timing setting. I use 0 for the PTT and because I have a Genius amp, I use 40 for the TX delay. 

    You should have some TX delay programmed in to allow for other things in your system (relays, etc.) to operate. I'm guessing that the settings are different between the two versions and you haven't transferred the profiles?
  • chris1165
    chris1165 Member ✭✭
    edited August 2019
    Thank you!  I feel silly asking that question about the version numbers.  I found out quickly when the 6400 was rebooting.  ;)

    I seems I spoke too quickly.  I'm not convinced downgrading solved the problem. Eventually the problem came back.  The Transmit Delay and PTT delays may be the key.  I'll run some more tests on both versions and report back for the group.

    Thanks for the help!
  • chris1165
    chris1165 Member ✭✭
    edited August 2019
    Here's a quick update. I did try downgrading but I had the same results.  Actually, it was hit or miss.  Sometimes I had jitters, sometimes I didn't.  It seems I had to reboot and it was about a 60% chance jitters came back.  I upgraded back to the original 3.0.27 and the problem didn't come back as long as the following occurs:

    • I'm running on ac power.  ie - no battery 
    • I had a solid 5 bars and on my 5G WiFi or connected directly into my router (Ethernet)
    I can reproduce the problem 100% of the time when running on battery power.  Since the Ethernet port is disabled when running on battery power, I can't test the Ethernet port.

    I can't explain why the original problem disappeared by downgrading and then upgrading back to the original 3.027.  So to recap, I couldn't send CW most of the time because of jitters.  Rebooting would eventually solve the problem but the problem would eventually come back. Downgrading and then re upgrading solved the issue... so far.

    FYI, SSB works 100% of the time, no jitters on AC power or running on batter power.  I'll continue to test.

    de N3MLB

  • K9SO
    K9SO Member ✭✭
    edited August 2019
    I think at this point you should open a trouble ticket. The engineers are very good at diagnosing issues like this. 
  • chris1165
    chris1165 Member ✭✭
    edited August 2019
    Here's an update and my resolution. I opened a support ticket and I was told that perhaps the battery was dropping below the required power.  To prove this, I was told to use a cell phone charger that was rated for 5v, 2.5 amps.  The problem went away which told me it was the battery.  I drained the new battery and then fully charged it.  I haven't had a problem since.  I've been operating CW for the past two to three hours and haven't had a single hick up or jitter.

    Let me say this also. Support was fantastic!  Wow!

    Now, I'm getting back to working CW from my couch... dit dit...

    de N3MLB


  • K9SO
    K9SO Member ✭✭
    edited August 2019
    Good to hear!

    I've gone back to remote paddle keying using my RemoteRig boxes (which work very well) until Flex can fix the v3.x Maestro keying issue. 

    73,
    Fred
    K9SO
  • chris1165
    chris1165 Member ✭✭
    edited August 2019
    Fred, I'm back to using v3 with no issues except for the battery. Just an FYI.
  • chris1165
    chris1165 Member ✭✭
    edited August 2019
    Let me correct myself. No issues at all with battery or plugged in with version 3. What should I look out for?
  • K9SO
    K9SO Member ✭✭

    Does anyone know if this CW keying "known defect  #7378 " mentioned in this very old thread was ever resolved? Is it safe to move to 3.x (which I paid for long ago) from 2.4.9?

    Fred, K9SO

  • Ted S
    Ted S Member ✭✭
    edited May 19

    Many users have reported improved CW timing with 2.7.3 or 3.2.34, however not every user has reported that their CW issues have been fully resolved. Since Flex is rushing out an emergency update to fix SmartLink, you might want to wait until those are released. But be prepared to downgrade back to your current version if your issue is not resolved. Some have reported full resolution of CW timing bugs, however the issues have not been resolved for all.

    Also, keep all your old profiles backed up for the downgrade as once they are upgraded to the new schema, I don't think you can save them in the older format.

    Here are some of the reports:

    Improved CW Operation - Version 2.7.3 — FlexRadio Community

    CW Too Fast — FlexRadio Community

    New release of SSDR & CW — FlexRadio Community

    CW Bug with 6400M internal keyer. Ver. 2.6.1 - Page 2 — FlexRadio Community

    3.2.31 Maestro CW Keying Slow RX Recovery — FlexRadio Community

    Ted, WR4T

  • Erik Carling EI4KF
    Erik Carling EI4KF Member ✭✭✭

    If you are a SmartLink user without a contingency, you will be locked into the new updated versions. "Downgrading" for you to your current version will not be an option.

  • Ted S
    Ted S Member ✭✭

    I agree any downgrade after this emergency update is released will break SmartLink. If you are using 2.4.9 to avoid some of the CW timing bugs, SmartLink is already broken for those users and will remain broken. The option for those folks will be to use a VPN solution for remote operation as a workaround for SmartLink no longer working with old releases (SSDR for IOS excepted).

    Fortunately, based on the reports it appears the new releases have resolved the CW timing issues for many.

    Ted, WR4T

  • K9SO
    K9SO Member ✭✭

    Ted,

    "If you are using 2.4.9 to avoid some of the CW timing bugs, SmartLink is already broken for those users and will remain broken."

    I am aware of the ongoing SmartLink issue, but have not seen any announcement that 2.4.9 SmartLink access will not be fixed ... ever ... as your post implies. Where may I confirm that information?

    Fred, K9SO

  • Ted S
    Ted S Member ✭✭
    edited May 20

    Well the problem is the Windows version of SmartSDR is using a authentication method that was deprecated by the SmartLink cloud service provider. In order to authenticate with SmartLink going forward a code change is required in the SSDR application, existing versions of SSDR are no longer able to authenticate with the SmartLink service. I don't think their is anything Flex can do with the legacy software versions as it was a change implemented by their third party service provider. Welcome to the Cloud...

    Ted, WR4T

    For confirmation of the above, read the first 5 posts from Flex staff on this thread:

    SmartLink Login Issues — FlexRadio Community

  • Ted S
    Ted S Member ✭✭

    And here is another user confirming CW timing improvements in the latest releases:

    CW TIMING WITH NEW SDR 3.2.31 — FlexRadio Community

    Ted, WR4T

  • K9SO
    K9SO Member ✭✭

    Ted,

    Thanks for the response.

    Yes, new versions will be needed to fix the SmartLInk issues but I'm hopeful that the existing 2.x performances won't be affected. The last post says:

    "Over the past two days, we have released two alpha versions of both Smart SDR v3 and V2 for Windows desktop clients. The feedback from the alpha testing team is excellent, especially with the latest version."

    When I can, I'll try the latest 3.x version remotely with high expectations.

    If not, I'll stick with my current version of SmartSDR and go back to my old VPN. When SmartLink was introduced, my radios only connected through SmartLink and stopped seeing the radios via the VPN for some reason. Since SmartLink worked so well, I never spent the time to investigate why.

    But now ... .

    73,

    Fred, K9SO

Leave a Comment

Rich Text Editor. To edit a paragraph's style, hit tab to get to the paragraph menu. From there you will be able to pick one style. Nothing defaults to paragraph. An inline formatting menu will show up when you select text. Hit tab to get into that menu. Some elements, such as rich link embeds, images, loading indicators, and error messages may get inserted into the editor. You may navigate to these using the arrow keys inside of the editor and delete them with the delete or backspace key.