Quote:
Originally Posted by Greg McKaskle
You may need sleep
|
Ain't that the truth! Anyway... It's the default that's used in the default program for vision tracking... 320x240 maybe...
On another topic... sorry to disrupt this thread....
We pass some status info back to the Driver Station to be displayed on the Cypress LEDs.
We've noticed a large delay in those status LEDs changing.
Eg: We have a "Compressor on " feedback light to indicate that the compressor has been "Enabled" by the operator.
The "Compressor On" status is simply the input (switch) bit echoed to the output (LED) bit inside the 100ms Periodic Loop.
In watching the I/O screen, and listening to the compressor we see a minimal delay between presing the Compressor On switch, seeing the DS Dig-In LED go on, and the compressor starting. However, there is an appreciable delay before the Robot returns a "Compressor On" feedback to the operator. It's not the Cypress because the DS I/O Screen Dig-Out LED shows the same delay.
The delay can be upwards of 2 seconds.
We can press and release the compressor ON button, hear the compressor start and stop, before the status LED changes. After about a second, we see the LED go on, and then off, so it seems like there is a message Queue that is full, and is taking about a second+ for any messages to pass through. (it takes me back to FTC Bluetooth issues)
This delay only seems to be related to uplink traffic, and based on the visual delay on the camera may also be effecting camera packets.
As far as I can see, Digital IO Output bits are sent with every uplink packet... so is there anything else that could be causing this lag?
Note: It happens even if we are running a BUILT program (not debugging)
Phil.