SmartSDR v4.0.1 and the SmartSDR v4.0.1 Release Notes
SmartSDR v3.10.15 and the SmartSDR v3.10.15 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
- 363 Community Topics
- 2.1K New Ideas
- 624 The Flea Market
- 8.1K Software
- 69 SmartSDR+
- 6.4K SmartSDR for Windows
- 182 SmartSDR for Maestro and M models
- 420 SmartSDR for Mac
- 270 SmartSDR for iOS
- 253 SmartSDR CAT
- 188 DAX
- 379 SmartSDR API
- 9.3K Radios and Accessories
- 30 Aurora
- 233 FLEX-8000 Signature Series
- 7.2K FLEX-6000 Signature Series
- 932 Maestro
- 53 FlexControl
- 863 FLEX Series (Legacy) Radios
- 909 Genius Products
- 460 Power Genius XL Amplifier
- 329 Tuner Genius XL
- 120 Antenna Genius
- 291 Shack Infrastructure
- 204 Networking
- 447 Remote Operation (SmartLink)
- 142 Contesting
- 771 Peripherals & Station Integration
- 139 Amateur Radio Interests
- 989 Third-Party Software
