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.2.20 | SmartSDR v4.2.20 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.2.20 | SmartSDR v4.2.20 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.
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
- 398 Community Topics
- 2.2K New Ideas
- 678 The Flea Market
- 8.6K Software
- 191 SmartSDR+
- 6.6K SmartSDR for Windows
- 196 SmartSDR for Maestro and M models
- 456 SmartSDR for Mac
- 278 SmartSDR for iOS
- 267 SmartSDR CAT
- 218 DAX
- 392 SmartSDR API
- 9.6K Radios and Accessories
- 91 Aurora
- 335 FLEX-8000 Signature Series
- 7.2K FLEX-6000 Signature Series
- 988 Maestro
- 58 FlexControl
- 872 FLEX Series (Legacy) Radios
- 962 Genius Products
- 478 Power Genius XL Amplifier
- 352 Tuner Genius XL
- 132 Antenna Genius
- 317 Shack Infrastructure
- 222 Networking
- 480 Remote Operation (SmartLink)
- 143 Contesting
- 845 Peripherals & Station Integration
- 147 Amateur Radio Interests
- 1.1K Third-Party Software

