Welcome to the 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 do you get PAN 1 frequency to match Slice A frequency when selecting a Memory Channel? v3.7.1

Member
edited June 2020 in SmartSDR for iOS
Just updated to v3.7.1 ios app and noticed when you select a memory channel, while the Slice shows the correct frequency, the display doesn't update to the selected channel and the Pan 1 display matches the display(previous frequency). Using Flex 6300.

Welcome!

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

Comments

  • Member ✭✭✭✭
    edited June 2020
    Need more information M version, Maestro, computer, or IOS device???
  • Administrator, FlexRadio Employee, Community Manager, Super Elmer, Moderator admin
    edited January 2020
    Jon

    Can you post a screen shot so we can see what you are looking at.  Windows has a built in tool (snipping tool) or you can use another product called GreenShot.

    Mike
  • Member ✭✭✭✭
    edited January 2020
    Using SDRIoS ver 3.7.1. The memory channels I have are for 60M. While the Panadapter is showing 40M,  I select a 60M memory, the pan stays on 40M with no slice visible. If I touch Slice A at the top of the screen, it shows Slice A on the 60M frequency, but the pan is still on 40M. Is this the situation you are reporting?
  • Member
    edited January 2020
    Correct. That is exactly what I am seeing. My device (iOS) and version (3.7.1) are in the comments.
  • Member
    edited January 2020
    Version and device are in the comments
  • Member
    edited January 2020
    My first try at images here. Fingers crossed. I was on 6m before selecting the memory for 7 MHz. Pan1 and display didn’t go to the memory channel freq like it used to image
  • Member ✭✭✭✭
    edited January 2020
    I classify this as a bug.
  • Member
    edited January 2020
    Looks like yesterdays update, Version 3.7.03 fixed this problem for me. Thanks!!!

Leave a Comment