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 refer to the product documentation or check the Help Center for known solutions.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.

How to get diagnostic details from a problematic radio?

Member
edited March 2020 in SmartSDR for Windows
As the title states, I'm looking for a way I can gather diagnostic information from a Flex-6400 that is currently experiencing issues after issuing commands like: create a new slice, or change band. The radio goes into a state where it shows up as connectable to SmartSDR/DAX/SmartSDR CAT, but upon connection SmartSDR will hang for a few seconds before disconnecting again. This loops endlessly until I manually power off/unplug the radio and restart.

I've tried to connect via Telnet when this is happening to get more information, but no luck. At the very least, I may connect via Telnet and leave a connection open until the radio stops working again so at least that way I have a history of whatever it manages to spit out to the console before getting into a bad state again. It's not a solid 100% repro, and seems to have different triggers.

Welcome!

It looks like you're new here. Sign in or register to get started.

Comments

  • Member
    edited July 2019
    Wireless or thru a LAN cable?
  • Member ✭✭✭
    edited March 2020
    wireshark can look at all network traffic...

    may provide more insight than just telnet traffic

    https://www.howtogeek.com/104278/how-to-use-wireshark-to-capture-filter-and-inspect-packets/


    PAUL K3SF

  • Member ✭✭
    edited July 2019
    I would open up a support ticket with flex support to identify your issue. 

    You can gather quite a bit of data by doing a PCAP with wire shark, but access to the core OS and intellectual property under the hood other than API access are not accessible.
  • Administrator, FlexRadio Employee admin
    edited July 2019
    The only issue I'm familiar with that would fit this description would be when you have upgraded to SmartSDR v2.5+ and then have downgraded.  Unfortunately, the database schema changes result in some strange behavior until you perform a reset to factory defaults.  At that point, I would expect things to improve.  Let us know if you need more info and most likely we'll get you going on a trouble ticket.

Leave a Comment