API Xmit command with MultiFlex

K9YK

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.

https://github.com/flexradio/smartsdr-api-docs/wiki/TCPIP-xmit

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?

KD0RC

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.

K9YK

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.

KD0RC

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.

K9YK

Thanks again Len! I'm not using the SDK, I'm rolling my own in Python. :-)