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.
FlexLib.NET Nickname Property Inconsistency.
K9DUR
Member ✭✭
There is an inconsistency in the value returned by the Nickname property between the API and RADIO objects.
In the Radio Setup for my 6700, I have Nickname set to "Ray" and Callsign set to "K9DUR".
If I access the API.RadioList(0).Nickname property, it returns "Ray". However, if I access the RADIO.Nickname property, it returns "Ray,_K9DUR".
Shouldn't these two properties return the same value?
73, Ray, K9DUR
0
Comments
-
I have entered this into the bug tracker for additional investigation.0
-
Ray,
We went off to try to duplicate this issue and we aren't seeing what you're seeing. The RadioList is a collection of Radio objects, so RadioList[0].Nickname and RADIO.Nickname (meaning the same object) should definitely match as they are literally the same field in the same object.
I suspect that this may be a result of having 2 versions of Discovery packets being sent out (for backwards compatibility). The older version of Discovery packets used a different method to figure out the nickname, however, the newer version should get the right answer and they are always sent back to back. So perhaps if you checked the value immediately after the first packet arrived (and before the second), you might see something like this.
If you need help setting up to test whether this is the case, please shoot me a direct mail and we'll get this figured out.0 -
Eric,
I am still consistently getting this result. Haven't gotten back to you earlier because I have been buried. This week, I am getting ready for the booth at the Fort Wayne Hamfest this weekend, as soon as I get back, my 6700 is heading to Austin for the PEN. I will get with you after I get my radio back.
73, Ray, K9DUR
0 -
We addressed a similar issue recently with the Nickname that may address yours as well. Keep us posted.
0
Leave a Comment
Categories
- All Categories
- 391 Community Topics
- 2.2K New Ideas
- 664 The Flea Market
- 8.4K Software
- 157 SmartSDR+
- 6.5K SmartSDR for Windows
- 186 SmartSDR for Maestro and M models
- 441 SmartSDR for Mac
- 275 SmartSDR for iOS
- 265 SmartSDR CAT
- 206 DAX
- 386 SmartSDR API
- 9.5K Radios and Accessories
- 61 Aurora
- 299 FLEX-8000 Signature Series
- 7.2K FLEX-6000 Signature Series
- 974 Maestro
- 58 FlexControl
- 867 FLEX Series (Legacy) Radios
- 948 Genius Products
- 473 Power Genius XL Amplifier
- 348 Tuner Genius XL
- 127 Antenna Genius
- 308 Shack Infrastructure
- 216 Networking
- 471 Remote Operation (SmartLink)
- 143 Contesting
- 816 Peripherals & Station Integration
- 144 Amateur Radio Interests
- 1.1K Third-Party Software

