Quote:
Originally Posted by Hjelstrom
There still might be something to this. In our shop we noticed that our controls could lag a little if we had all of our data running so we implemented a button on our controls that enables and disables data (and data defaults to OFF). Essentially, we don't send any data to our dashboard unless we push a certain joystick button. We also set our cameras to use the lowest quality and resolution that we can tolerate. We also made our data sending function only run a couple of times per second rather than every time through the main loop.
Essentially, we noticed that bandwidth usage could be a problem and we tried to optimize our robot's bandwidth usage down to the minimum.
Still, I don't think it can explain 118 sitting completely dead for the whole match. That was a truly tragic thing to see and I sincerely hope this problem is solved for good by next year.
|
As far as I know we didn't turn down any of the video quality settings for the video stream to the driver's station.
We had:
1 camera
3 encoders
2 breakbeam sensors
2 pots
But all of the processing was left to the cRIO, we didn't offload any of the processing to the driver's station. The only thing that was being output to the driver's station would be the video feed and whatever is the normal packets for sending/receiving joystick inputs.