Driver Station Errors

[cilginbilgin]

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_DigitalModuleDIO Allocator.vi>>WPI_DigitalInputOpen.vi>>Begin.vi>>R obot 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!


I would be very grateful if anyone can help me!!!

[cilginbilgin]

I also get these errrors:

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.

[Exernie]

Originally Posted by cilginbilgin

I also get these errrors:

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
.

i also get this multiple times. how do we fix it.

[Tom Line]

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.

[Exernie]

Originally Posted by Tom Line

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.

how do you find the errors and know what to delete.

[Greg McKaskle]

On the driver station, click on the Diagnostics tab. The list will have error information that other posts are referring to.

Greg McKaskle

[cilginbilgin]

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!

Here is my Teleop.vi

[apalrd]

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.

[Tom Line]

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.

[Mark McLeod]

Yea, Teleop looks fine.
There is a small error On your Elevator motor output.
I think you meant to use multiple rather than addition of 0.9

[Alan Anderson]

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.

[cilginbilgin]

Originally Posted by Mark McLeod

Yea, Teleop looks fine.
There is a small error On your Elevator motor output.
I think you meant to use multiple rather than addition of 0.9

Actually I summed it with 0,9 because I just dont want elevator to fall down because of gravity.

[cilginbilgin]

Originally Posted by Tom Line

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.

Is the problem with Robot Main? I didnt even change anything with Robot Main. Should I change Robot Main if yes what should I change with Robot Main?

[dotbran]

I had this problem and I had to change all of the slot values manually in the Open 4 Motor VI - One on each motor and one in the front panel

[cilginbilgin]

Originally Posted by dotbran

I had this problem and I had to change all of the slot values manually in the Open 4 Motor VI - One on each motor and one in the front panel

I didnt really understand what you have done? Where is Open 4 Motor VI? Isnt that enough to have constant slot values and changing slot values from Block Diagram?

Thanks for your help!