Go to Post I'm unconvinced that this thread itself is not a performance art piece. - DCA Fan [more]
Home
Go Back   Chief Delphi > Technical > Programming > Java
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
  #1   Spotlight this post!  
Unread 28-02-2012, 23:24
AlexD744 AlexD744 is offline
Registered User
FRC #0744 (744 Shark Attack)
Team Role: Alumni
 
Join Date: Jan 2009
Rookie Year: 2008
Location: Ft. Lauderdale, FL
Posts: 638
AlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond reputeAlexD744 has a reputation beyond repute
Re: Robot drive... Output not updated enough.

This error message is a frustrating one because it would seem that this error would originate from the RobotDrive class, however, the real problem could be in any part of your code. This displays whenever your code is running too slowly, and will subsequently disable your drive functions (and probably everything else, not sure though, I haven't spent too much time trying the different functions when this has popped up). Anyway, this message appears a lot if you are doing image processing on the cRio because that takes longer than the 20mS loop time. Other (more likely culprits) include infinite loops (or any loop that lasts longer than 20mS), methods that call themselves without end (I had a setMotorSpeed(speed) method that called setMotorSpeed(speed) at the end of it instead of motor.set(speed)), and anything else that potentially stops or slows the code.

It may be helpful to add your own output messages throughout your code, then you will see what is getting called before the RobotDrive message, and it will probably point to the area of code that is causing the stop.
__________________
www.sharkattack744.com
Reply With Quote
  #2   Spotlight this post!  
Unread 02-03-2012, 17:48
sebflippers sebflippers is offline
Registered User
FRC #2914
 
Join Date: Jan 2012
Location: dc
Posts: 56
sebflippers will become famous soon enoughsebflippers will become famous soon enough
Re: Robot drive... Output not updated enough.

Quote:
Originally Posted by AlexD744 View Post
It may be helpful to add your own output messages throughout your code, then you will see what is getting called before the RobotDrive message, and it will probably point to the area of code that is causing the stop.
I did exactly that, and realized that it never even got to the first method (it obviously created the robotdrive object, though). I just switched away from the iterativerobot template and now it works. I found the other templates didn't do what I wanted, so I created the templateOfDoom! No more problems now. If anybody wants, I could try to find some way to share it.
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 09:48.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi