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.
SimpleVOX* setting question

rfoust
Member ✭✭
In the FlexLib API code, I'm not sure what is going on with the SimpleVOXLevel and SimpleVOXDelay code. On most of the settings, there is a check to make sure the min/max levels aren't exceeded (like 0 or 100). But not on those two settings. Also, on SimpleVOXDelay, it is multiplied by 20 when sent to the radio. Could someone explain how that works, or if that was just an oversight? Especially the * 20 multiplier. Thanks! private int _simpleVOXLevel; /// /// The vox level from 0 to 100 /// public int SimpleVOXLevel { get { return _simpleVOXLevel; } set { if (_simpleVOXLevel != value) { _simpleVOXLevel = value; SendCommand("transmit set vox_level=" + _simpleVOXLevel); RaisePropertyChanged("SimpleVOXLevel"); } } } private int _simpleVOXDelay; /// /// Sets the VOX delay from 0 to 100 /// public int SimpleVOXDelay { get { return _simpleVOXDelay; } set { if (_simpleVOXDelay != value) { _simpleVOXDelay = value; SendCommand("transmit set vox_delay=" + _simpleVOXDelay * 20); RaisePropertyChanged("SimpleVOXDelay"); } } }
0
Answers
-
Seems, looking at the Obj-C code, that whatever you pass will be divided by 20, so yes - multiplying by 20 is the correct way - as for why...... can't answer that.
0 -
We probably should be range checking the values in FlexLib since that is one level of API that we are offering. We also do range checking in the over-the-wire TCP protocol inside the radio. Thanks for bringing this to our attention.
As for the *20 and /20, this is likely just a units/range mapping thing. I would have to ask Ed Gonzalez as he is the expert on our codec interface code, but we often map a slider range of 0-100 on the client side of the interface just to simplify things. Then we will adjust the value internally to fit nicely with the data the command modifies. This could probably be moved inside the radio for the sake of clarity.0
Leave a Comment
Categories
- All Categories
- 349 Community Topics
- 2.1K New Ideas
- 615 The Flea Market
- 8K Software
- 2 SmartSDR+
- 6.3K SmartSDR for Windows
- 173 SmartSDR for Maestro and M models
- 412 SmartSDR for Mac
- 267 SmartSDR for iOS
- 249 SmartSDR CAT
- 186 DAX
- 375 SmartSDR API
- 9.2K Radios and Accessories
- 22 Aurora
- 207 FLEX-8000 Signature Series
- 7.1K FLEX-6000 Signature Series
- 921 Maestro
- 53 FlexControl
- 860 FLEX Series (Legacy) Radios
- 894 Genius Products
- 455 Power Genius XL Amplifier
- 323 Tuner Genius XL
- 116 Antenna Genius
- 283 Shack Infrastructure
- 199 Networking
- 444 Remote Operation (SmartLink)
- 138 Contesting
- 754 Peripherals & Station Integration
- 139 Amateur Radio Interests
- 973 Third-Party Software