Welcome to the FlexRadio Community! Please review the new Community Rules and other important new Community information on the Message Board.
Need the latest SmartSDR or 4O3A Genius Product Software?
SmartSDR v3.10.10 and the SmartSDR v3.10.10 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
The latest 4O3A Genius Product Software and Firmware
SmartSDR v3.10.10 and the SmartSDR v3.10.10 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
The latest 4O3A Genius Product Software and Firmware
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.
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
Getting transmitting slice ID using CAT commands

IW7DMH, Enzo
Member ✭✭
Hello,
I am wondering what is the "official" algorithm, I have to use, to get the transmitting Slice ID using serial commands.
I am aware of the operational notes on page 3 of the SSDR Cat manual and I would like to solve the issue when "Commands that access VFO B information before one of the commands mentioned above is issued or after the Split Slice is manually closed will receive a ‘?;’ response."
I am missing something but another question could be "Why the FT; and ZZSW; commands can't return the plain TX slice ID?"
73' Enzo
iw7dmh
I am wondering what is the "official" algorithm, I have to use, to get the transmitting Slice ID using serial commands.
I am aware of the operational notes on page 3 of the SSDR Cat manual and I would like to solve the issue when "Commands that access VFO B information before one of the commands mentioned above is issued or after the Split Slice is manually closed will receive a ‘?;’ response."
I am missing something but another question could be "Why the FT; and ZZSW; commands can't return the plain TX slice ID?"
73' Enzo
iw7dmh
0
Answers
-
Enzo,
The CAT API was developed WAY before we had more than 2 VFOs. For that reason, it is all oriented around a 2 VFO system. As such, it is a tough task to try and wrap a modern transceiver like a FLEX-6700 (8 Slices) onto such a system.
The way that we have chosen to implement the system is to leave the command set as is and abstract one or 2 Slices per CAT port. This gives us the best compatibility with existing applications that only expect a 1 or 2 VFO type of radio.
The right way to get the transmit Slice ID is probably not to use CAT at all, but rather to use the radio API. It is a much richer API that comprehends more Slices (VFOs) and is accessible over the network. See the FlexADP page (http://www.flexradio.com/amateur-products/flex-6000-signature-series/smartsdr-api/) for more info on the APIs that we offer.0 -
Thank you Eric,
in the last weeks I ported my switchbox project, from Arduino based platform to Raspberry Pi 2/3 and I was going to give a try to the new embedded serial port.
But, as you pointed out, there are more cons than pros so I'll go on with the smartsdr APIs.
This time I have to deal with Python and I hope I'll be able to do it as well.
73' Enzo
0
Leave a Comment
Categories
- All Categories
- 352 Community Topics
- 2.1K New Ideas
- 615 The Flea Market
- 8K Software
- 3 SmartSDR+
- 6.3K SmartSDR for Windows
- 173 SmartSDR for Maestro and M models
- 412 SmartSDR for Mac
- 267 SmartSDR for iOS
- 250 SmartSDR CAT
- 187 DAX
- 375 SmartSDR API
- 9.2K Radios and Accessories
- 22 Aurora
- 212 FLEX-8000 Signature Series
- 7.1K FLEX-6000 Signature Series
- 922 Maestro
- 53 FlexControl
- 860 FLEX Series (Legacy) Radios
- 894 Genius Products
- 455 Power Genius XL Amplifier
- 323 Tuner Genius XL
- 116 Antenna Genius
- 284 Shack Infrastructure
- 200 Networking
- 444 Remote Operation (SmartLink)
- 138 Contesting
- 756 Peripherals & Station Integration
- 139 Amateur Radio Interests
- 974 Third-Party Software