Custom ports

[Griffin]

I know there is this rule out there somewhere but I cant seem to find it.

What ports are we allowed for direct driverstation-to-device_on_the_robot communication?

Long story short we might want to put a computer on the robot and communicate directly to it from the driverstation.

Like, for example, can I just pull up the robots IP and connect on port 1002 to it and send whatever I want over that port to the robot? Is this making any sense?

[omgnocomms]

@dellagd

What ports are we allowed for direct driverstation-to-device_on_the_robot communication?

According to the FMS White Paper1,

@"FMS White Paper

The ports that the teams are able to access on the playing field are as follows:

TCP 1180: This port is typically used for camera data from the robot to the DS when the camera is connected to port 2 on the 8-slot cRIO. This port is bidirectional on the field.
TCP 1735: SmartDashboard, bidirectional
UDP 1130: Dashboard-to-Robot control data, directional
UDP 1140: Robot-to-Dashboard status data, directional
HTTP 80: Camera connected via switch on the robot, bidirectional
HTTP 443: Camera connected via switch on the robot, bidirectional

All these ports are open on the playing field, so a team can use them as they wish if they do not employ them as outlined above (i.e. TCP 1180 can be used to pass data back and forth between the robot and the DS if the team chooses not to use the camera on port 2 of the 8-slot cRIO)

@dellagd"

Like, for example, can I just pull up the robots IP and connect on port 1002 to it and send whatever I want over that port to the robot?

Since this is not one of the ports outlined in the FMS White Paper, this wouldn’t work on the field.

[Mark_McLeod]

The ports were also defined in a 2012 team rules update, so check the rules released in January and watch for those Team Updates this year.

[Griffin]

Thanks! Thats what I needed!