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
Need technical support from FlexRadio? It's as simple as Creating a HelpDesk ticket.
API Xmit command with MultiFlex
Looking at the Xmit command, there doesn't seem to be any way to specify which active station in a multiflex environment is going to transmit.
It works fine when there is a single station connected to the raidio (and thus only one TX slice), but when there are two stations connected and multiflex is active, there are actually two TX slices (one for each connected station). If you issue an Xmit command with multiflex active, it seems to be random as to which of the two TX slices (or stations) ends up doing the actual transmitting.
How do I assign one of the two TX slices (or stations) as being the one that actually does the transmitting when an Xmit command is sent?
Best Answers
-
Your application needs to do a bind to the desired GUI client (i.e. to one of the multiFlex connections) first. Let me know if you are already doing a bind.
0 -
Thanks! I wondered if that was it, but I didn't try it since the documentation states that it doesn't do anything functional …
"Registers that a non-GUI client will be binding to a client with a particular ]Client ID]. From a radio perspective as of v3.0, this command is simply for debugging and troubleshooting and assists developers in determining how non-GUI clients are processing radio data, but in and of itself performs no function in the radio. It is recommended that non-GUI clients send the statement when they bind to maximize information for debugging."
I'll give the bind command a try.
0
Answers
-
Yep, the API documentation is a bit out of date for a few commands, but most of it is accurate.
I do the bind in the GUIClientUpdated routine:
radio.GUIClientUpdated += new Radio.GUIClientUpdatedEventHandler(_thisRadio_GUIClientUpdated); … private void _thisRadio_GUIClientUpdated(GUIClient client)
{ … _thisRadio.BindGUIClient(client.ClientID); … }The CW keying documentation was missing last time I checked, so just ask here if you want to do that.
1 -
Thanks again Len! I'm not using the SDK, I'm rolling my own in Python. :-)
0
Leave a Comment
Categories
- All Categories
- 328 Community Topics
- 2.1K New Ideas
- 593 The Flea Market
- 7.8K Software
- 6.2K SmartSDR for Windows
- 168 SmartSDR for Maestro and M models
- 396 SmartSDR for Mac
- 260 SmartSDR for iOS
- 246 SmartSDR CAT
- 179 DAX
- 369 SmartSDR API
- 9.1K Radios and Accessories
- 15 Aurora
- 158 FLEX-8000 Signature Series
- 7.1K FLEX-6000 Signature Series
- 909 Maestro
- 51 FlexControl
- 854 FLEX Series (Legacy) Radios
- 872 Genius Products
- 446 Power Genius XL Amplifier
- 311 Tuner Genius XL
- 115 Antenna Genius
- 278 Shack Infrastructure
- 196 Networking
- 438 Remote Operation (SmartLink)
- 135 Contesting
- 721 Peripherals & Station Integration
- 136 Amateur Radio Interests
- 942 Third-Party Software