|
Getting Driver Station Inputs on Dashboard
So my team needs to do I/O faster than the latency between the Driver Station, Robot, Dashboard loop allows, I suggested they cut out the round trip to to the robot by simply looking at the port that the robot is getting locally. However, it appears that you cannot initiate any sort of UDP listener on the port that dashboard is talking to the robot on.
Ultimately, the timing operation is so critical that the only way to the controls operate correctly (without a significant redesign to the control's system) is to set up a packet sniffer on the Dashboard to look for the correct data and unpackage it accordingly, and then transmit the final value back over using TCP 1180 (see team update 5 on the control system for legality of this).
My question is such a technique legal with the addition of the rules as you are just listening to yourself and sending over what would be the "camera port". Also, when I set up Wireshark to listen for traffic, the ports specified in the document are different from the ones that are specified by the team update 5 (we tried listening on this port as well, to no avail).
|