|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
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.
|
|
#2
|
||||
|
||||
|
Re: [cRIO] Robot Drive... Output not updated often enough.
Quote:
Quote:
|
|
#3
|
||||||
|
||||||
|
Re: [cRIO] Robot Drive... Output not updated often enough.
Just run the driver station software.
|
|
#4
|
|||
|
|||
|
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();
}
|
|
#5
|
||||
|
||||
|
Quote:
Code:
public void robotInit()
{
drive.setSafetyEnabled(false);
Watchdog.getInstance().kill();
}
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. Last edited by sthreet : 23-01-2014 at 22:45. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|