|
TCP Ports and sockets on the field
This year, I have a Vision Server (which will be released in a couple of days when some bugs are sorted). It communicates using a TCP connection to the roboRIO. That will require one port.
The Vision Server will require another two ports because all of the configuration will be held through the web browser, separate integrated web servers, embedded in the code.
The roboRIO will be having at least one (maybe a couple more as the season progresses, along with my code) port in use. All of the port configurations will take place over a web server.
I am wondering what the port blocks are and why they exist.
If I wanted to run an HTTPd on the roboRIO, on port 890, would I be able to access it during a match? (890 is an arbitrary number that's not in the manual)
|