Go to Post Given the time Banebots has already cost us, what's a little snow? - pfreivald [more]
Home
Go Back   Chief Delphi > Technical > Programming
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 23-02-2016, 06:55
olidem123 olidem123 is offline
Not a community manager
AKA: Olivier Demers
FRC #5618 (PLS)
Team Role: Leadership
 
Join Date: Feb 2016
Rookie Year: 2015
Location: Canada
Posts: 12
olidem123 is an unknown quantity at this point
Question Is robot drive really important?

Hello fellows programmers,
I just wanted to know if this error is really important:
Code:
 Error at java.lang.Thread.run(Thread.java:745): Robot Drive... Output not updated often enough. ERROR  1  Robot Drive... Output not updated often enough.  java.lang.Thread.run(Thread.java:745)
I should probably put you more into context; when we hold a button, the robot drives forward by itself.
We only get this error message when we hold the button in question.
  #2   Spotlight this post!  
Unread 23-02-2016, 07:04
weaversam8 weaversam8 is offline
Team Captain
AKA: Sam Weaver
FRC #4534 (Wired Wizards)
Team Role: Leadership
 
Join Date: Jan 2014
Rookie Year: 2014
Location: Wilmington, North Carolina
Posts: 137
weaversam8 is a splendid one to beholdweaversam8 is a splendid one to beholdweaversam8 is a splendid one to beholdweaversam8 is a splendid one to beholdweaversam8 is a splendid one to beholdweaversam8 is a splendid one to behold
The error "Robot Drive... Output not updated often enough." signifies that the robot is expecting to receive joystick values frequently, and is not. This is a safety measure to ensure that if a joystick fails for some reason, the robot knows about it.

This is probably happening because you have sent the signal to the drivetrain once when the button is pressed, and then you do not keep sending it signals. The drivetrain has a method around this: if you call the method "setSafetyEnabled" and pass it a value of false, it will no longer check for this constant input, which can be useful for autonomous. Be advised, however, that the robot will also not zero the outputs if a joystick fails... I suggest you only disable the safety during autonomous routines, and reenable it when you're done.
__________________
ORB Haow!

  #3   Spotlight this post!  
Unread 23-02-2016, 07:08
olidem123 olidem123 is offline
Not a community manager
AKA: Olivier Demers
FRC #5618 (PLS)
Team Role: Leadership
 
Join Date: Feb 2016
Rookie Year: 2015
Location: Canada
Posts: 12
olidem123 is an unknown quantity at this point
Smile Re: Is robot drive really important?

Thank you very much;
Closed Thread


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 12:56.

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