Re: FlexRadio V3 flow, volts/PA temp do not work
|
Mark
A great lesson on the workings of multiplex API.
So....the port must be changed based on which client is "bound".? OK.
FYI, the normal Node-Red TCP nodes do not allow for changing the port number, outside of the manual configuration page. ??
So..... I found these TCP nodes that have provisions to input a msg.payload (or whatever) ?to make changes to the ?TCP configuration.? I gave the TCP Client a test run, by injecting msg.payload = 4992 and it works very well.? Other parameters?can be changed too.
Here is the Client Node: ? and the Server Node:?
Not sure what happens next, but it is fun playing.
Alan WA9WUD
The port number used is a factor of the ports in use at the time of client initialization.
The FlexAPI attempts to create a exclusive UDP Socket at Port 4991, if that fails it will try the next and so on until Port 6010.
Once successfully bound it will inform the Radio with the following command "client udpport 4993"
Note that port 4992 is the discovery port so it will not be used.
This is why you will see the traffic on different ports depending on how many clients you are running
On Windows run the following to see UDP ports in use:?netstat -a -p UDP
So when I run FRStack and SmartSDR I see 4991, 4993 in use and 4992 in use 2 times.
I hope this helps.
Mark
W3II
|
