TCP Ports and sockets on the field

[yash101]

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)

[Thad House]

Originally Posted by yash101

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)

Pg 16 of the game manual has all the ports that are open on the field. TCP 5800-5810 are open for team use, so that is what I would recommend using.

[yash101]

Originally Posted by Thad House

Pg 16 of the game manual has all the ports that are open on the field. TCP 5800-5810 are open for team use, so that is what I would recommend using.

I know, but does that mean that other ports are closed? I don't see any point in that!

[Thad House]

Originally Posted by yash101

I know, but does that mean that other ports are closed? I don't see any point in that!

Yeah I believe the other ports are closed. That way they can control field access, and make sure nothing rogue goes through the system with other ports.

[adciv]

From our experience, the other ports are closed. This bit us badly in 2012, the first year we think they did that. It was updated partway through the build season and we didn't notice that "detail".

For consistency, I'd recommend using the same port as the Axis cameras and try to use the same format.

Side note, it is possible to develop a library which will allow you to integrate an interface with the build in web-browser on the RIO. I think you just need to drop a library into a specific folder. This would be advantageous as it would reduce overhead on the RIO.