|
Re: Can we transmit any data from a custom dashboard TO the robot using UDP ?
Thanks for the R75 reference, I suppose that makes it a bit unambiguous if the Driver station is the only tool that can collate the operator/driver inputs.
We’ve also thought about the possibility of a simple “pseudo” (virtual) USB HID device that would be used to mimic a physical HID Joystick could encode operator data from the dashboard (operator or automated calculations) through the various Joystick APIs (GetX(), GetY(), GetZ(), GetThrottle(), etc). A touch screen with on-screen buttons and controls would be an interesting construct and would help to better integrate the Dashboard, which is currently display only, with input options as well. Requiring a physical button for any and all operator inputs when we have a laptop with a full keyboard and so many other I/O opportunities is potentially a bit constraining.
This virtual USB approach from the dashboard seem like it would keep us within the literal interpretation of R75 but I wonder whether it would violate the spirit of the rule. Is the rule in place to prohibit PC communications to the robot or is it simply a rule to simplify filed management and avoid additional communications that could cause unexpected dificulity
|