Quote:
|
Video is typically transmitted from the ROBOT by using the software ports specifically set up to support video throughput. This year, the Field Management System will not pass data sent through that port during a match (to ensure adequate system performance during competition events, until the new system is better characterized in actual competition settings). If a team really wants to transmit images from the camera back to the Driver Station during a competition, they can decompose the video frame and pass it as user data in the available 984 bytes per packet. However, the resulting throughput of the video will likely result in a frame rate so slow that it is not particularly useful.
|
You are given 984 bytes 50 times a second to do what ever you please with. Testing has already shown this to be very very very doable, and has been available to you from day 1.
If you want to send back sensor readings, go for it. If you want to send back internal state, go for it. If you want to send back a stream of robotics related limericks that are generated programmaticly in response to field conditions, go for it. You can even use it to send back video if you'd like.
However, 984 bytes at 50Hz is what you get. That won't fit full motion video, but it might be able to fit heavily compressed / decimated video. For example, you could easily send back a black/green/pink thresholded stream. If you are a total nutter, you could send back info on object positions to reconstruct a picture of what things should be on your laptop.
For reference, this is about 7 times faster than a 56k dial up modem. Enough to do a lot of cool stuff, not enough to be wasteful.