Watchdog Expiration: System 1, User 0
ERROR <Code> -44061 occurred at “Left and Right Motors” in the VI path: Robot Main.vi
<time>19:42:17 02/17/2011
FRC: The loop that contains RobotDrive is not running fast enough. This error can occur if the loop contains too much code, or if one or more other loops are starving the RobotDrive loop.
ERROR <Code> -44061 occurred at “Left and Right Motors” in the VI path: Robot Main.vi
<time>19:41:51 02/17/2011
FRC: The loop that contains RobotDrive is not running fast enough. This error can occur if the loop contains too much code, or if one or more other loops are starving the RobotDrive loop.
ERROR <Code> -44003 occurred at WPI_CameraIssue HTTP Request with Authentication.vi>>WPI_CameraIssue Get.vi>>WPI_CameraSet Image Appearance Property.vi>>WPI_CameraSet Enum Appearance Property.vi>>WPI_CameraSet Image Size.vi>>Begin.vi>>Robot Main.vi
<time>19:41:51 02/17/2011
FRC: Operation failed due to a communication failure with the camera.
Watchdog Expiration: System 10, User 2
ERROR <Code> -44061 occurred at “Left and Right Motors” in the VI path: Robot Main.vi
<time>09:56:40 02/17/2011
FRC: The loop that contains RobotDrive is not running fast enough. This error can occur if the loop contains too much code, or if one or more other loops are starving the RobotDrive loop.
ERROR <Code> -44003 occurred at WPI_CameraIssue HTTP Request with Authentication.vi>>WPI_CameraIssue Get.vi>>WPI_CameraSet Image Appearance Property.vi>>WPI_CameraSet Enum Appearance Property.vi>>WPI_CameraSet Image Size.vi>>Begin.vi>>Robot Main.vi
<time>09:56:34 02/17/2011
FRC: Operation failed due to a communication failure with the camera.
ERROR <Code> -44027 occurred at WPI_DigitalModuleDIOCache.vi>>WPI_DigitalModuleDIOAllocator.vi>>WPI_DigitalInputOpen.vi>>Begin.vi>>Robot Main.vi
<time>09:56:32 02/17/2011
FRC: The DIO channel has already been allocated.
ERROR <Code> -44061 occurred at “Left and Right Motors” in the VI path: Robot Main.vi
<time>09:53:12 02/17/2011
I am getting these kinds of errors when I enable on my driver station!
FRC: The loop that contains RobotDrive is not running fast enough. This error can occur if the loop contains too much code, or if one or more other loops are starving the RobotDrive loop.
ERROR <Code> -44003 occurred at WPI_CameraIssue HTTP Request with Authentication.vi>>WPI_CameraIssue Get.vi>>WPI_CameraSet Image Appearance Property.vi>>WPI_CameraSet Enum Appearance Property.vi>>WPI_CameraSet Image Size.vi>>Begin.vi>>Robot Main.vi
<time>23:40:15 02/16/2011
FRC: Operation failed due to a communication failure with the camera.
No Change to Network Configuration: <noNICConfig><noNICConfig>
I/O unit not detected or not installed correctly.
Watchdog Expiration: System 1, User 0
Don’t worry about this one unless you get a lot of them. One is normal for changing robot modes: Disabled, Teleop, Autonomous
ERROR <Code> -44061
This means your Teleop loop might be running too slowly.
It means you aren’t calling Arcade or Tank Drive quickly enough.
ERROR <Code> -44003
Is if the camera is not connected or if it’s still booting when the cRIO tries to talk to it.
ERROR <Code> -44027
Means you used one of the DIO’s twice.
Probably just left one of your Opens with the default DIO 1 and it conflicted with something else you Opened using that same DIO.
I believe these are common, we recieve these and received them last year and didn’t have a problem.
Your Camera is timing out. If you are not using the camera, make sure the Enable Vision control is False (if using LV, don’t about the other IDE’s). If you are using the Camera, is the indicator ring on the front of the Camera green?
In your Begin.vi, check to make sure you are not opening 2 references with the same Digital Input
Watchdog Expiration: System 8, User 0
Watchdog Expiration: System 7, User 0
Watchdog Expiration: System 6, User 0
Watchdog Expiration: System 5, User 0
Watchdog Expiration: System 4, User 0
This is just the one fourth of the errors I am getting!!!
But I dont think I have assigned same channels to two or more than two DIO s!
Check to make sure that you have initialized all of the DIOs that you are using. We found out recently that if you forget to initialize something in the Begin.vi it will try to use the default values for it. This could be trying to create a default one on your Slot 4 DIO 1 channel. Also while it is trying to figure out the default it will cause a delay that triggers the watchdog problems.
That usually means the communication between the laptop and robot is flakey. It’s slowed way down.
I saw this on one team still using last year’s Classmate setup (with updated 2011 Driver Station).
The Classmate turned out to be “stuttering.” They had too much going on on their laptop and it couldn’t keep up with the robot.
That can be double checked by trying a different laptop running the Driver Station application.
It can also occur due to a weak or subpar wireless connection.
Does it still give these errors when you connect your laptop directly to the DLink on the robot via Ethernet cable?
I can’t see images from Imageshack, so I can’t give advice there.
With regards to the camera call, you can either not open it in begin or plug your camera in so it runs. It’s timing out because it expects the camera to talk on the ethernet port and it isn’t.
With regards to the other problems (loop running slow) we nailed this one tonight after a lot of work. What clued us in to our errors was that it was still happening even when the robot is disabled. We checked the VI’s that were running in disabled and found references to things that we had removed from begin. We also found a duplicated reference in begin. After fixing those our ‘loop too slow’ disappeared.
ERROR <Code> -44061 occurred at “Left and Right Motors” in the VI path: Robot Main.vi
<time>09:00:09 02/18/2011
FRC: The loop that contains RobotDrive is not running fast enough. This error can occur if the loop contains too much code, or if one or more other loops are starving the RobotDrive loop.
This is the error I am getting and I couldnt manage to solve it!
Most times I encounter a tripping watchpuppy are because a semi-unrelated thing is causing an error every time it runs, and the error handling time is enough to trip the watchpuppy. While running, try probing all of the device refs in Teleop, and see if any are creating errors.
It is also possible that bad communication is causing these errors. The Teleop loop is timed to the incoming packets, so if the packets lag enough then the RobotDrive might not run fast enough.
cbilgin, trying checking to see if you are still getting these errors with the robot disabled. The diagnostic is not telling you the problem is with teleop - but in robot main. They are Two different things, and I suspect you’re looking in the wrong place.
This has nothing to do with your error, but it looks like you have a feature where a joystick trigger makes the robot drive backwards. Is that to make it easier for to control it intuitively when the robot is facing the driver? You might want also to swap the left and right motor signals in that case, so that it turns the way the driver expects it to.
