Program deployed, no response from robot

[RahatAhmed]

Here's the error code we get (obviously the date is wrong, I copied and pasted from elsewhere. But the error is identical):

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.

And to give a brief record of what we've done: The laptop, radio, and cRIO were imaged and set up at the kickoff. I installed LabVIEW on the laptop and then installed the three updates that were given to us at the kickoff as well. Then I reset the router, and set it up as the tutorials in LabVIEW say to. Had some trouble with the wireless so we used a long ethernet cable so we could deal with that later. Camera and Joystick work fine.

One thing I'm not clear on is the proper way to upload a program to the cRIO. Do we just press run and wait for it to deploy? Somewhere else on CD I found instructions saying to right click the build target and click "build", then "run on startup". Which is the better way to do it, at least for development?

[RufflesRidge]

You get an instance or two of that error, or does it keep repeating? The first is normal, the second is a problem.

[RahatAhmed]

Originally Posted by RufflesRidge

You get an instance or two of that error, or does it keep repeating? The first is normal, the second is a problem.

It repeats.

[ehlochbr]

We have the same problem and I've triple checked everything!!

I read the posts about the possibly bad cable, but that wouldn't be a problem if we're using last years DB37 cable right?

Would appreciate any suggestions for this because I'm stuck...

Thanks.

[RahatAhmed]

Is it possible that the default project has some bad code? Could someone upload a project that they know works on their robot, to see if the code is the problem?

[ehlochbr]

I'm going to try to create the LV project from scratch tonight. Maybe something got messed when the SW update changed our code to reflect the new slotting in the cRIO.
Perhaps starting fresh and creating the project in LV2011 will work. I'll post when I'm done with the results.

[ehlochbr]

Nothing new. Tried making a new project from scratch and it didn't work... I'm out of ideas for now.

[Greg McKaskle]

What errors are you getting? Have you tried running an example? Can you elaborate on what you've tried and what does work?

Greg Mckaskle

[ehlochbr]

Sure. We mostly have camera errors (error 44003 to be exact as well as some communication errors). It says something about not being able to connect to the camera and authenticity. We manually set up the camera to have the username and password that were recommended so I'm not sure what else to do to eliminate this error.

The only thing I can think to try next is to use the setup program for the camera and see if that helps. Like I said, we manually configured the camera so maybe when we setup the camera manually, we missed something but that's my last idea...

We also, occasionally, get an error that says the loop that contains robot drive is running too slow, but I've looked through everything and all our loops have a delay built-in so there isn't anything starving the processor that I can see. Plus, robot drive is used in many different places. I'm not sure exactly which part of the code it's talking about and the error message doesn't specify.

I appreciate your help.

[RahatAhmed]

Still out of ideas. I'd really appreciate if someone would upload a verified working project that we could test out to see if it really is the code or something else.

[SuperS_5]

Maybe you can post some of your code, the vision code is where I would start. (Post a snippet instead of just a screenshot.) Does this happen regardless of driver station mode?
I am guessing something is hogging all of the cRIOs CPU, and the RobotDrive.vi is not getting enough priority to run, or is never executed in the first place.

One thing I'm not clear on is the proper way to upload a program to the cRIO. Do we just press run and wait for it to deploy? Somewhere else on CD I found instructions saying to right click the build target and click "build", then "run on startup". Which is the better way to do it, at least for development?

*For development, you can simply run the Main.VI, and LabVIEW will automatically deploy, and you still have all the debugging tools available. (It can use a lot of bandwidth.)
*Deploying sets your program to run without the laptop used to deploy. This is more useful for letting the drivers train, while more programming is going on. The code is however erased every time you reboot the cRIO. (That includes power cycles.) If your code is bad, the robot is easily recoverable by simply resetting the power.
*Deploying, and setting "run on start-up" will always run your code, even after power cycles. This is for competition and any time you need to use the robot without the computer used to program it. (EG. Drivers training on days without the programmers.) I typically wouldn't use this until I have tested it by simply deploying first. This will rule out issues with your code maxing out the cRIOs CPU.

[RahatAhmed]

We finally got it working. Our electrical team messed with the pins coming from the jaguars, and said they put them on channels 3 and 4 or something. Basically the pins suggested from the quick build were not the right ones. We're not sure why, or how we would go about adding new motors. I guess we'll figure it out.

[tilky]

you do not need to put code that is in teleop inside a while loop. it loops automatically

[tilky]

the problem is that you put a while loop inside of the teleop code. Because the code automatically repeats itself, if you repeat it inside of the code, and it takes longer than it does to execute teleop again, it would come up with an error. Try taking the while loop out.

[Programmer3941]

Originally Posted by RahatAhmed

We finally got it working. Our electrical team messed with the pins coming from the jaguars, and said they put them on channels 3 and 4 or something. Basically the pins suggested from the quick build were not the right ones. We're not sure why, or how we would go about adding new motors. I guess we'll figure it out.

RahatAhmed, my rookie team has been having a nearly identical problem with our Jaguar when we try to run a program we made to operate a single test motor. We have had absolutely no output response from the motor, and the yellow light on the Jaguar constantly flashes. We have not received any error messages, though, concerning the content of our code or otherwise. Could you explain in more detail what your electrical team did with the pins and channels to get the Jaguars and everything working?

Thanks in advance.