smartSDR 1.4.16 crashes on 15 meters. It was working OK before until...

  • 1
  • Problem
  • Updated 3 years ago
  • In Progress
Radio: Flex-6300
software: 1.4.16
Direct connection via NIC to computer

The radio was working fine. I had just selected 15 meter. I was adjust things and it suddenly stop working, by that I mean no audio output, there was data on the spectrum scope but nothing on the waterfall, and I lost complete control and then smartSDR crashed.

It displayed the "Connection Lost" popup box with the message "the connection to the radio was lost. Please reconnect". I click the OK button and the radio setup window appeared. It showed that my radio was already in use. So I could not reconnect. I also looked at the activity Ethernet LEDs on the computer and they flashing normal.

 I power cycled the radio and also rebooted my computer. I reconnected to the radio and it works fine on all bands but 15 meters. Whenever I switch to 15 meters, smartSDR crashes in the way described above.
Photo of Dave

Dave

  • 83 Posts
  • 8 Reply Likes
  • confussed

Posted 3 years ago

  • 1
Photo of Larry - W8LLL

Larry - W8LLL

  • 354 Posts
  • 68 Reply Likes
Is it crashing during transmit? If so  I would suggest you have RF getting into the radio or RF getting into the network cable causing it to loose connection.
(Edited)
Photo of Dave

Dave

  • 83 Posts
  • 8 Reply Likes
No, not during transmit.  in receive mode. Like I said up until tonight it was all good.
(Edited)
Photo of N3NER

N3NER

  • 184 Posts
  • 24 Reply Likes
I'm running 1.4.16.63 with no issues at all.
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 8670 Posts
  • 3253 Reply Likes
Dave,

I have converted this topic to a support HelpDesk ticket (http://helpdesk.flexradio.com) for expedited issue resolution.  Please export your profiles and attach it to the ticket e-mail you will be receiving shortly.  I believe there is something amiss in your profile that is causing a problem and I want to capture that data before we try to resolve it.

If anyone else is experiencing an issue similar to this one, please submit a HelpDesk support ticket for issue resolution.