View Single Post
  #6   Spotlight this post!  
Unread 20-02-2015, 14:27
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,795
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Robot Drive Not Running Fast Enough

Quote:
Originally Posted by Ether View Post
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.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 20-02-2015 at 19:18.
Reply With Quote