Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
The latest SmartSDR Software:
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software:
The latest 4O3A Genius Product Software and Firmware
SmartSDR v4.1.5 | SmartSDR v4.1.5 Release Notes
SmartSDR v3.10.15 | SmartSDR v3.10.15 Release Notes
The latest 4O3A Genius Product Software:
The latest 4O3A Genius Product Software and Firmware
How to Receive Technical Support::
If you are needing assistance with FlexRadio products, 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.
If you are needing assistance with FlexRadio products, 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.
SmartSDR API - display pan Status Packet get unexpected value id
IW7DMH, Enzo
Member ✭✭
Hello,
using my controller I got the unexpected id (I suppose it is so) for a phantomatic pan object as marked in the picture below.

I was aware that Pan ID start from 0x40000000 and so on, while Waterfall ID start from 0x42000000 and so on. It seems here that also Pan objects can have the 0x4200... id.
Is this correct?
This is anyway a strange behaviour because when it happens I have only one active panadaptor and it happens only when the band is changed from an external software (in my case it is Log4Om). If I change band using SSDR GUI the (wrong) status packet isn't send from the rig.
As Log4OM is using the CAT protocol I suppose it is a specific issue of the CAT APIs as using SSDR GUI everything works properly.
73' Enzo
iw7dmh
using my controller I got the unexpected id (I suppose it is so) for a phantomatic pan object as marked in the picture below.

I was aware that Pan ID start from 0x40000000 and so on, while Waterfall ID start from 0x42000000 and so on. It seems here that also Pan objects can have the 0x4200... id.
Is this correct?
This is anyway a strange behaviour because when it happens I have only one active panadaptor and it happens only when the band is changed from an external software (in my case it is Log4Om). If I change band using SSDR GUI the (wrong) status packet isn't send from the rig.
As Log4OM is using the CAT protocol I suppose it is a specific issue of the CAT APIs as using SSDR GUI everything works properly.
73' Enzo
iw7dmh
0
Answers
-
Good find. This is a bug in the code. I have entered a fix and submitted it for review. (#1963)0
Leave a Comment
Categories
- All Categories
- 390 Community Topics
- 2.2K New Ideas
- 662 The Flea Market
- 8.4K Software
- 157 SmartSDR+
- 6.5K SmartSDR for Windows
- 186 SmartSDR for Maestro and M models
- 440 SmartSDR for Mac
- 275 SmartSDR for iOS
- 265 SmartSDR CAT
- 204 DAX
- 386 SmartSDR API
- 9.4K Radios and Accessories
- 55 Aurora
- 297 FLEX-8000 Signature Series
- 7.2K FLEX-6000 Signature Series
- 971 Maestro
- 58 FlexControl
- 867 FLEX Series (Legacy) Radios
- 945 Genius Products
- 472 Power Genius XL Amplifier
- 347 Tuner Genius XL
- 126 Antenna Genius
- 308 Shack Infrastructure
- 216 Networking
- 468 Remote Operation (SmartLink)
- 142 Contesting
- 814 Peripherals & Station Integration
- 144 Amateur Radio Interests
- 1.1K Third-Party Software