Resplendence Software - LatencyMon: suitability checker for real-time audio and other tasks
https://www.resplendence.com/latencymonLatencyMon: suitability checker for real-time audio and other tasks
I noticed after upgrading to Flex smart SDR version 3.8.19 my smart sdr software is prone to crashing. On my Flex 6400. When I turn the radio on the radio seems to boot up normally. Giving me a solid steady green light. Then when I launch Smart SDR version 3.8.19 on my PC. I only get a partial load up. And the right hand column shows up but the scope and radio never loads up completely. I did a total factory reset a two weeks ago. But am still having some hick ups with this new version. After the partial boot up. I get a dialog saying the smart sdr as lost connection to the radio. I get two flashing red lights indicating a software crash. The radio reboots. And then comes up normally. This has happened twice now since I did a factory reset. I had submitted a help desk ticket for this and Ken Wells helped me reset the radio. I had no issues with the 3.7 smart sdr. Is Flex aware of something going on with this new version on the 6400 radios ?
Thank you.
Interesting…. Just a few days ago I had a "sick feeling in the stomach" situation with my 6600M and MacOS SSdr. I was happily minding my own business when suddenly the computer screen "froze" and the radio red-lighted, shut down, and re-booted. Everything back to normal, thank God. Using latest versions of both SSDR for Mac and 6600M version.
I hope it was just a one-off, but you have raised suspicions in my mind, James.
Well If I do not get any responses here I may open anther support ticket.
James,
This sounds more like a PC issue than a radio issue. Is it possible that your PC is in some kind of a slowdown and things are timing out on the SSDR client? This is just one thought of many things that might contribute to the symptoms you are seeing.
You might want to try running a Latency Monitor and see if any ideas come from it.
Mike it does this on the Maestro C and multiple PC's too, But thank you for the links to some great tools.
Thank you.
Crashing it not normal and not something that happens across the entire install base. Now, if all 15,000 radios out showed the same symptoms then resolving it would take a different path. This sounds like an isolated issue.
The good news is that something like this is usually fixable by opening a support ticket so that it can be further isolated.
Occasional spontaneous crashing with a flashing red power button was a symptom of a failing SD card on my Flex-6600. A new SD card was supplied by Flex tech support which fixed the problem.
73,
Larry KB1VFU
SmartSDR 3.8.20 is now available.
Does this problem happen if the radio has a LINK.LOCAL connection?
As a test, use the PC directly connected to the radio with a signal LAN cable.
If you can, let the Helpdesk know. If you can't, then the problem is a communications loss in your network.
You want to run this test to help eliminate parts that can cause this sort of failure and it allows us to focus on the root cause of the problem.
Let us know how you make out.
73
Hi Ezat, have you tried a factory reset yet? If not, export your profiles, do the reset, then try the radio without importing the profiles. If the issue goes away, try importing your profiles and see how that goes. If the problem returns, then you likely have a corrupt profile.
If the issue is resolved after the reset and reimport, then you will probably be good going forward. If not, the help desk will give you next steps.
My crash Issue has been resolved now. I am using version 3.8. 23 now. My Flex 6400 worked great remotely while I drove from Belton TX to Tampa FL and then to Orlando FL for Hamcation 2025. I was able to use my iPhone 14 Pro and Ipad Pro and Dell Laptop to connect remotely to it. With little or no problems. The smartlink worked great. The only exception was when my ISP went offline Friday February 14, 2025. We don't know why. But for the most part from Saturday February 1, to Thursday February 13, 2025. The smartlink worked.
Hi Ezat, it is probably time to submit a help desk ticket, especially if you can show that 3.7 behaves differently.
Thanks Len,
Have already submitted the ticket prior to the post and Tim has been assisting
Many thanks
Ezat
😊