Quote:
Originally Posted by sjspry
No, this doesn't override rule 75. The dashboard is separate from the driver station. So no, all that great stuff you talked about isn't possible.
But yes, you can communicate however you want as long as all teleop goes through the driver station. I'd suggest, however, to not reverse-engineer the current protocol and just make your own (like I did).
|
A literal interpretation of R75 where the driver is the only tool to collated driver/operator inputs seems to preclude ANY such dashboard user interaction (setup, teleoperated, etc.) but could allow for automated control from algorithms in the driver station as long as the data did not derive from the operator/driver inputs. Allowing a powerful laptop to do the vision processing and returning the results via this dashboard UDP port seems like a valid rule interpretation but not the likely intention. I’m still very curious as to some further rule info detailing on this UDP 1130 reference and some further specifics on what is/is not allowed. This “dashboard to robot” communications remains a tad ambiguous until we have a official response. It was very easy to get the basic UDP receiver operational on both the dashboard and the robot and would happily share this. If only we knew what we could do with it….