Driver Station Errors
 

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!!!

Re: Driver Station Errors
 

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.

Re: Driver Station Errors
 

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.

Re: Driver Station Errors
 

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

Re: Driver Station Errors
 

FRC: The DIO channel has already been allocated.

This means that you have assigned the same channel to multiple DIO's , this could be causing the loop to slow down and cause it to time out.

Re: Driver Station Errors
 

Here is my Digital Input part of the Begin.vi!



Uploaded with ImageShack.us

But I dont think I have assigned same channels to two or more than two DIO s!

Re: Driver Station Errors
 

Actually I am getting lots of those errors!

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!!!

Re: Driver Station Errors
 

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.

Re: Driver Station Errors
 

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.

Re: Driver Station Errors
 

I am getting some other error after I deploy the code:

LabVIEW: Failed to load shared library FRC_UserProgram.out on RT target device.

Deployment completed with errors

Re: Driver Station Errors
 

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

Re: Driver Station Errors
 

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.

Re: Driver Station Errors
 

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

Re: Driver Station Errors
 

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

Greg McKaskle

Re: Driver Station Errors
 

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

Re: Driver Station Errors
 

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.

Re: Driver Station Errors
 

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.

Re: Driver Station Errors
 

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

Re: Driver Station Errors
 

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.

Re: Driver Station Errors
 

Our minibot deployment arm is at the back of our robot and it is to make minibot deployment easier for our driver.

Thank you for the correction!

Re: Driver Station Errors
 

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

Re: Driver Station Errors
 

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?

Re: Driver Station Errors
 

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

Re: Driver Station Errors
 

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!

Re: Driver Station Error 44061
 

Rookie team here looking for some last minute help...

After ongoing LabVIEW programming issues/errors we decided to restart from scratch:

1. Deleted all cRIO Robot Projects
2. Installed updates for LabVIEW, Driver Station, & Utilities
3. Re-ran cRIO Imaging Tool
4. Created new cRIO Project and have not changed anything

When wireless we have intermittent communication (program still runs but is choppy) and we keep getting

ERROR <Code> -44061 occurred at "Left and Right Motors" in the VI path: Robot Main.vi
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.

I am trying to determine if our wireless is causing this error or if this error is causing our wireless to have issues (sending too much info?)... when we are tethered to the cRIO we don't get this error and we can still receive the wireless camera image on the dashboard with no apparent delay.

Please advise...

Re: Driver Station Errors
 

If you flip to the rightmost tab on the DS called Charts, it contains a chart of various robot things. One is the voltage of the robot battery, one is CPU usage, and the two top ones are the communication round trip time in milliseconds and the lost packets. If spikes there correspond to the choppiness, the issues is either with the wifi environment (too many competing networks on the same channel(s)), a badly mounted radio (too far into the robot, too close to motors), or if it is latency and not dropped packets, it may be due to load of the DS computer or cRIO.

Greg McKaskle

Re: Driver Station Errors
 

Ok so looks like this is definitely a wireless issue. To me it looks like it's both dropped packets and latency (see attached for screenshot of Chart with no robot code).

So question now is how to fix...

Our wireless radio is on the perimeter of our robot and about 5" (nearest edge to nearest edge) from the closest motor. It is only about 3" from our battery and cRIO and only about an 1" from the digital sidecar. It has a short power cable though and would take a significant amount of re-wiring to get it any further...

I looked under network connections (see second screenshot) and it appears to have a pretty good connection (72Mbps) but I am no expert in these things.

I am tempted to hit the reset button on the back of the wireless radio but from what I recall it was a nightmare to configure it the first time and I'd like to avoid that if possible.

Please advise...

Re: Driver Station Errors
 

The only thing that stands out is the 255.0.0.0 subnet mask. I'm not sure that alone will impact the lost packets, but I'd drop it to 255.255.255.0. Next I'd run InSSIDer and see if the channel is really a good one. I'm not sure what the green bars on the Windows control panel mean, strong signal, not much traffic, etc.

Please post any solution or improvements that you find.

Greg McKaskle

Re: Driver Station Errors
 

I just tried logging onto the classmate to change the subnet but I get an error:

"Your system is running low on resources. You cannot log on as a new user. Please use an account that has already been logged on."

I get the same error when trying to log onto the driver station.

Battery is fine and I get same error with power cord plugged in. So confused...

Re: Driver Station Errors
 

Restarting the classmate fixed the "Low on Resources" error but now I'm concerned I have something running behind the scenes.

I changed the subnet but it didn't seem to help.

I'm bringing it over to a veteran team now to see if they can figure it out.

Re: Driver Station Errors
 

The user login message suggests that someone may have done the quick switch that allows for multiple users to be logged in. The DS no longer allows this and the new one sends a message to the old one to shutdown. But you could potentially have other programs hogging resources I suppose.

Greg McKaskle

Re: Driver Station Errors
 

From your description of the placement of the robot radio, it needs to be relocated. You listed a lot of things it shouldn't be close to (battery, motor, I bet it's close to speed controllers too isn't it).

Before rewiring, if you can, just take it off the robot and attach an extra Ethernet cable/power cord just so you can hold it in your hand while the robot runs while up on blocks.
Watch the Charts while holding it away from the robot with the motors running, then move it closer and to various places on the robot to see how proximity to various things affects the packet loss and round-trip transit time.

We just did that with a visiting team and it was quite an eye opener for them.
Nice job with the Charts this year Greg. Kudos. :)

Re: Driver Station Errors
 

Thanks. Now we just have to learn how to use it. Thanks Mark.

Greg McKaskle

Re: Driver Station Errors
 

Unfortunately it's not the placement of the wireless radio (rewired and moved it several feet away from our bot)...

Also checked to confirm we are getting a steady 5V from the transformer (it sometimes gives a quiet but high pitched hum) which we are...

The inSSIDer is a great tool and there does seem to be a lot of 2.4Ghz traffic here (see screenshot) but we got the same errors at their campus which had significantly less traffic (although there were brief periods where we had perfect wireless communication).

One of the guys who works at FIRST events managing the wireless systems worked with it for about and hour and said he pretty much narrowed it down to being an issue with the wireless radio itself. He said that it shouldn't be a problem at the event though since we will be running 5Ghz and if it is he'll give us a new radio (for now we'll just run code tethered).

Not the ideal solution but I've wasted far too much time on it already.

Thanks again for looking at this.

Re: Driver Station Errors
 

Did anyone seriously find the answer to this because we need to solve this immediately.

Re: Driver Station Errors
 

Remove as many things from your teleop.vi and put them in periodic tasks! Also, if you're developing code on another laptop and pushing code into RAM, try removing as many controls on the front panel as possible, that REALLY slows everything down.

Re: Driver Station Errors
 

I too am getting the -44061 drive loop is running too slow errors and let me preface this with we are 100% completely new to LabView this year.

I've taken all of my control code that runs the conveyer, aiming, shooting, and trigger servo/morors out of teleop.vi and placed them into a periodic task while loop and it seems to make no difference if I set it to 10 ms or 100ms I still receive the error. We are hardwired to our develop PC and should have next to no communication errors.

Re: Driver Station Errors
 

Are you actually having a problem when using the Robot? In my experience this error isn't a big deal if it throws it every now and then (such as when you Enable) but you will get a lag issue if it continually throws it, which is probably a problem with your code.

See Post #4 in this Thread, specifically concerning the Camera. If you are not using the Camera, make sure to delete all the Camera code in the Begin, Finish and Disable/Delete the Vision VI in the Robot Main.

If that doesn't work post your complete code, it's hard to troubleshoot without it.

Re: Driver Station Errors
 

At the regionals I've attended, I've seen a number of teams throwing this when disabled because they are using a different name for their drive or for other reasons aren't updating the speed. Setting the speed there is useful to avoid jumps when the robot first enables, but otherwise isn't super important.

The most troubling issue with these issues is that they bog down the cRIO so that deploying new code is a bit more difficult, especially when other parallel loops like vision and Timed tasks are running at high CPU usage.

I also saw an error in built apps caused by the calibration code on the Vision diagram. That may not be common, but it makes sense if the panel is being removed during build.

I wish the error messages were a bit easier to understand, but if you are still having ones you can't find, post the Diagnostic messages, including the location info.

Greg McKaskle

Re: Driver Station Errors
 

Disclaimer: This is kind of a hack job solution and should only be tried if the previous suggestions did not work or you don't have time to try them. Also, although this fix worked for us, I can't say I did a ton of research into how exactly it worked so I can't guarantee it will work (Mr. McKaskle probably could better explain exactly why this works, etc.).

Our team encountered this early on in the build season. Drive -> SetSafetyMode vi (I'm not sure if that's the exact name, I don't have LabVIEW up in front of me) has a boolean input labeled something like Enabled? By placing this vi in the Begin vi in between the Open and setRefNum vis, we managed to make the error go away. Again, we only made the error go away, not the problem itself. The above suggested solutions are probably better ideas in general if you have the time to execute them.

Re: Driver Station Errors
 

Disabling the Motor Safety on the Drive motors might actually be an appropriate solution, but only in a very limited set of situations. It's theoretically possible for the robot code to be right at the edge of overtaxing the CPU, and a rare event could cause the safety timeout to throw an error...which uses more processing, which tips the system into a constant cycle of CPU overload and motor safety timeouts and errors eventually leading to watchdog timeouts and a disabled robot. With the safety disabled, there might be an occasional couple hundred milliseconds where the drive motors won't respond to a joystick change, but the robot won't get disabled because of it.

I'd still want to find the underlying reason for having so much CPU usage in the first place.

Re: Driver Station Errors
 

I can confirm that there is not anything wrong with your teleop. something else is using up all of the RIO's processing power. I would look at any vision processing that you have running; that is what caused us problems. Now, as to the watchdog, feed it in the 10 ms loop of timed tasks. this will eliminate all of these errors except when switching modes.

Re: Driver Station Errors
 

The watchdog is not on by default. If it were, feeding it in a parallel loop is equivalent to turning it off, so you may as well just turn it off.

The safety config if "fed" when you update the RobotDrivr. Don't update them in parallel, just update them. Or set it to be disabled. Make sure that anyone else debugging the code knows it is off so the robot doesn't drive through walls.

Greg Mckaskle