Go to Post When a team is composed completely of robot builders and technical people that team cannot exist just like a company cannot exist if it is only made up of engineers. - Garret [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 Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 22-01-2014, 18:46
RufflesRidge RufflesRidge is offline
Registered User
no team
 
Join Date: Jan 2012
Location: USA
Posts: 989
RufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant futureRufflesRidge has a brilliant future
Re: [cRIO] Robot Drive... Output not updated often enough.

How many times are you seeing the message appear in the Diagnostics window? If it is constant/appearing many times it's something to worry about. If you see it happen only once or twice when the robot is transitioning between states I wouldn't worry about it.
Reply With Quote
  #2   Spotlight this post!  
Unread 23-01-2014, 16:19
sthreet's Avatar
sthreet sthreet is offline
Registered User
AKA: scott threet
FRC #4692
 
Join Date: Oct 2012
Rookie Year: 2012
Location: Toutle Lake
Posts: 84
sthreet is an unknown quantity at this point
Re: [cRIO] Robot Drive... Output not updated often enough.

Quote:
Originally Posted by RufflesRidge View Post
How many times are you seeing the message appear in the Diagnostics window? If it is constant/appearing many times it's something to worry about. If you see it happen only once or twice when the robot is transitioning between states I wouldn't worry about it.
Just once, but I don't know when, I can't see the window while driving it. (Don't know how to drive in developer.)

Quote:
Originally Posted by BradAMiller View Post
I don't see anything wrong with the that would cause that message to be printed. RobotDrive requires the motors to be update every 0.1 seconds (expirationTime) before the robot safety code will stop them.

Make sure that the correct project is loaded in the robot.
I am right click->running, pretty sure I am clicking on the right one.
__________________
Spoiler for gif:
Reply With Quote
  #3   Spotlight this post!  
Unread 23-01-2014, 16:25
Joe Ross's Avatar Unsung FIRST Hero
Joe Ross Joe Ross is offline
Registered User
FRC #0330 (Beachbots)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1997
Location: Los Angeles, CA
Posts: 8,561
Joe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond reputeJoe Ross has a reputation beyond repute
Re: [cRIO] Robot Drive... Output not updated often enough.

Quote:
Originally Posted by sthreet View Post
Just once, but I don't know when, I can't see the window while driving it. (Don't know how to drive in developer.)
Just run the driver station software.
Reply With Quote
  #4   Spotlight this post!  
Unread 23-01-2014, 19:14
nyaculak nyaculak is offline
Registered User
FRC #0053 (Area 53)
Team Role: Programmer
 
Join Date: Oct 2011
Rookie Year: 2011
Location: Maryland
Posts: 28
nyaculak will become famous soon enough
Re: [cRIO] Robot Drive... Output not updated often enough.

This is a problem created by the wpilib's safety system(s)...Actually, you should just kill them. Call this function in the robotInit().
Code:
private void killSafety() {
    drive.setSafetyEnabled(false);
    Watchdog.getInstance().kill();
}
__________________
2013 MUC DC 3rd Place, FRC DC Regional, FRC Chesapeake Regional
2012 FRC DC Regional, FRC Chesapeake Regional
ERHS Robotics Club
- FRC Team 53 "Area 53"
www.erhsroboticsclub.org
Reply With Quote
  #5   Spotlight this post!  
Unread 23-01-2014, 21:19
sthreet's Avatar
sthreet sthreet is offline
Registered User
AKA: scott threet
FRC #4692
 
Join Date: Oct 2012
Rookie Year: 2012
Location: Toutle Lake
Posts: 84
sthreet is an unknown quantity at this point
Question Re: [cRIO] Robot Drive... Output not updated often enough.

Quote:
Originally Posted by nyaculak View Post
This is a problem created by the wpilib's safety system(s)...Actually, you should just kill them. Call this function in the robotInit().
Code:
private void killSafety() {
    drive.setSafetyEnabled(false);
    Watchdog.getInstance().kill();
}
So I added this to my code:
Code:
    public void robotInit()
    {
        drive.setSafetyEnabled(false);
        Watchdog.getInstance().kill();
    }
Changed nothing, except the timeout messege didn't display

EDIT: We appear to be having ping problems. Robot Radio and Crio are fine. other stuff is bad. (forgot what exactly was bad, but their were two things.)

EDIT: Found this error:
Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-bad, cRIO(.2)-bad, FMS-bad Driver Station
We are attempting to switch out digital sidecars to see if that is the problem.
__________________
Spoiler for gif:

Last edited by sthreet : 23-01-2014 at 22:45.
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 11:31.

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