Robot Drive Not Running Fast Enough

[Mark McLeod]

That means your Teleop processing is taking longer than 100ms.
If you'd like to attach your Teleop.vi we could check it for low code.
Generally, no delays, no loops, no massive amounts of complex code.

If the msg occurs just once, then there is not much cause for alarm. It could just be a startup delay.
If it repeats regularly, then the user code is too slow.

[Ether]

Originally Posted by Mark McLeod

If the msg occurs just once, then there is not much cause for alarm. It could just be a startup delay.

Can someone explain where and why this startup delay is occurring?

[Mark McLeod]

Originally Posted by Ether

Can someone explain where and why this startup delay is occurring?

There are a few common reasons for this that I sort of brush over.

For instance, while the default code running at startup doesn't typically throw any "too slow" errors, it will during autonomous because the motors aren't used in there by default.
However if the identical code is run in debug with all it's attendant front panels and comms back to the laptop we might see one "too slow" message during initialization. More msgs will appear as we just drag any front panel around.

Another possible cause might be the addition of code somewhere that takes longer to initialize, for instance a Gyro that has a default calibration time of 2 seconds.

[beanwells5349]

Here's my code:


-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------