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.9.19 and the SmartSDR v3.9.19 Release Notes
SmartSDR v2.12.1 and the SmartSDR v2.12.1 Release Notes
The latest 4O3A Genius Product Software and Firmware
SmartSDR v3.9.19 and the SmartSDR v3.9.19 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.
Incorrect command response to slice set 0 tx=0/1
Options
Doug - K3TZR
Member
When I send a command to change the state of TX on a Slice, the desired action takes place (i.e. TX is turned on or off) but the response to the command seems incorrect. Here's a captured sequence:

Notice that the response to C40 and C54 are both |10000003|Nothing to erase
Is this a bug?
When I see a non-zero reply to a command I assume that it indicates a warning or error.

Notice that the response to C40 and C54 are both |10000003|Nothing to erase
Is this a bug?
When I see a non-zero reply to a command I assume that it indicates a warning or error.
0
Answers
-
I think I've answered my own question. Looking in http://wiki.flexradio.com/index.php?title=Known_API_Responses I see that there are a small number of "INFO" responses and that this is one of them.
This response is actually "CWX Nothing to erase" which I'm guessing means that if the radio was in the process of sending CWX, changing the state of TX might necessitate erasing some string of characters from CWX and that, in this case, there was nothing to erase.
Sorry for the fire drill.0 -
With some additional testing I believe that this is a bug in v2.4.9. If you do the same commands using a previous version (e.g. 2.3.9) the response is a simple "Rnn|0|".
I also tried "set slice 0x0 mode=USB", the expected reply would be "Rnn|0|", instead the reply is:
"Rnn|50000096" which translates to an error -> "SL_INVALID_PTT_CMD_IN_CW_MESSAGE"
It appears that SmartSDR simply ignores these messages / errors. The Radio works as expected in spite of the messages / errors.0 -
This does seem like a bug. Thanks for pointing this out. I've entered this as #6786 in our bug tracking system.1
Leave a Comment
Categories
- All Categories
- 328 Community Topics
- 2.1K New Ideas
- 594 The Flea Market
- 7.8K Software
- 6.2K SmartSDR for Windows
- 168 SmartSDR for Maestro and M models
- 397 SmartSDR for Mac
- 260 SmartSDR for iOS
- 247 SmartSDR CAT
- 179 DAX
- 369 SmartSDR API
- 9.1K Radios and Accessories
- 15 Aurora
- 162 FLEX-8000 Signature Series
- 7.1K FLEX-6000 Signature Series
- 909 Maestro
- 51 FlexControl
- 854 FLEX Series (Legacy) Radios
- 873 Genius Products
- 446 Power Genius XL Amplifier
- 312 Tuner Genius XL
- 115 Antenna Genius
- 278 Shack Infrastructure
- 196 Networking
- 439 Remote Operation (SmartLink)
- 135 Contesting
- 725 Peripherals & Station Integration
- 136 Amateur Radio Interests
- 945 Third-Party Software