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.

Issues adding Panadapter

Member ✭✭
edited March 2017 in DAX
I have a few issues when adding panadapters: 1. The slice with DAX1 selected goes to no DAX selected and a new slice gets the DAX1 setting. 2. The new slice shows up on the existing panadapter, and the new panadapter has no slice. 3. When slice A on the first panadapter is set to DAX1 and I change bands on the second panadapter where slice B DAX is set to none, then DAX on slice A goes to none and the DAX on slice B goes to DAX1.
Tagged:

Welcome!

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

Comments

  • Administrator, FlexRadio Employee admin
    edited March 2017
    Robert what radio model are you using?
  • Member ✭✭
    edited March 2015
    6700
  • Member ✭✭
    edited December 2013
    This reply was created from a merged topic originally titled The invisible slice and other observations on 1.0.24. After shutting down SmartSDR (running PSK31 on 20 m) and restarting, there is no slice visible. It's there, working, the log program sees it, but not visible. And no clicking dragging, or tugging gets it back. Switching to a different band then back to 20m and the slice reappears right where it was. This is repeatable in my case.

    Have also noticed sometimes there is no audio when going to DAX mode - even though it was just working fine and no changes made. Found toggling both the #1 and TX in the DAX control panel would restore it every time.

    The previous problem with SmartMeter not functioning is solved with new CAT.
    Kudos to Flex for this new version!! Loving the DAX!
  • Administrator, FlexRadio Employee admin
    edited March 2017
    This looks like a persistence issue that we have previously identified and should be addressed in the next released version of SmartSDR.

Leave a Comment