Help 2013 Robot won't run

[jibicax]

I’m having trouble with either my cRIO, LabVIEW 2013 , or the Driver Station 2013. The problem is that Robot Main.vi will run, but when I press Enable on the Driver Station NOTHING (except the Compressor and the Camera) works. The Jaguars even turn solid yellow, which means their getting some kind of code, but I get no response out of the robot Teleop and Automous. I know my code works, I’ve been making testing vi outside of Robot Main that works fine. AND the old 2012 Robot Main runs and enables fine as well. What is going on? Is this a bug in LabVIEW 2013? If so how do I fix it.

Error codes I usually get (the joystick was plugged in the entire time).

Warning <Code> 44002 occurred at Ping Results: link-bad, DS radio(.4)-bad, robot radio(.1)-GOOD, cRIO(.2)-GOOD, FMS-bad Driver Station
<time>2/15/2013 5:10:20 PM<unique#>5
FRC: Driver Station ping status has changed.
Warning <Code> 44003 occurred at Driver Station
<time>2/15/2013 5:08:39 PM<unique#>4
FRC: No robot code is currently running.
ERROR <Code> -44009 occurred at Driver Station
<time>2/15/2013 5:08:39 PM<unique#>3
FRC: A joystick was disconnected while the robot was enabled.
WARNING <Code> 44007 occurred at FRC_NetworkCommunications <secondsSinceReboot> 1265.594
Warning <Code> 44001 occurred at No Change to Network Configuration: "Local Area Connection""Wireless Network Connection"
FRC: Time since robot boot.

Driver Station
<time>2/15/2013 5:08:39 PM<unique#>2

Warning <Code> 44006 occurred at Driver Station
<time>2/15/2013 5:08:38 PM<unique#>1
FRC: Custom I/O is not enabled or is not connected to the driver station.

[bvisness]

Could you post your Teleop.vi? It would help to diagnose the problem if we could see some of your code. (Posting Robot Main.vi wouldn't be a bad idea either.)

[jibicax]

Here's the Teleop. Please pay no attention to the name of the attachment (I figured that out.)

[bvisness]

Originally Posted by jibicax

Here's the Teleop. Please pay no attention to the name of the attachment (I figured that out.)

Well, I don't really see anything wrong, but you should consider wiring up the Error In and Error Out terminals on the Drive Get and Arcade Drive VI's. Doing that will let you probe the wire for any errors the code might have found with your drivetrain.

[josneville]

This happened to our robot as well. There are many solutions to this:

1. Reboot CRIO
2. Put safety config VIs for your motor controllers
3. Make sure that your router is configured properly


If none of these work, it usually means that you have a corrupt CRIO. Just reformat it with the correct settings and you should be fine.

[Alan Anderson]

Originally Posted by jibicax

FRC: No robot code is currently running.

That's probably a clue. Is Robot Main still running when this happens? Does the Driver Station still have a green light for robot code?

[Greg McKaskle]

Actually, I don't believe in the corrupt cRIO scapegoat.

The No Code is running log is timestamped, and unless we know the timing of other things, it could be misleading. As Alan asked, is the Robot Code light currently on? Since the compressor is running, I assume it is.

I'd take advantage of the debugger. Open up Teleop and see that it is being called. The DS could be in auto, or test mode. If teleop is being called, what are the joysticks returning, what values are being sent to the motors? If you right-click on a wire, you can show a probe on a wire or set a breakpoint.

Probing into the code that is actually running is key to understanding why it isn't doing what you want.

Greg McKaskle

[jibicax]

Here is the Robot Main.

Yes I did check if the Robot was in the proper mode and I checked all the modes. I even made multiple new projects just in case that project was corrupt. But I'm just getting the same result. Probing the wires didn't show anything unusual, highlight execution didn't show anything wrong, and Single Stepping is WAY to much windows.

[jibicax]

I disabled all the safety configurations on the motors. No luck.

[Greg McKaskle]

What did you see when you probed the wires? Were the output values close to zero? Do you have errors on the Diagnostics tab?

Greg McKaskle

[jibicax]

Okay, i guess I did the probes wrong because all I get when I probe a wire in another window that tells me what the wire does/is doing. What do you mean by output?

[jibicax]

The errors I get is the same errors in my first post.

[Greg McKaskle]

LabVIEW uses the term probe, but it could be called a watchpoint or a variable viewer, etc. If you probe a wire and data goes down the wire, that small window lets you see what value your code produced.

So if you probe the wire going into the RobotDrive, it will show you whether it is running at all, and whether the value being sent makes sense and is what you intended.

If the value going into RobotDrive makes sense, then you should verify that PWM channels and wiring and other things make sense. If it never runs or the value is always zero, you debug in the other direction to the driver station or to upstream elements.

So, by probing wires in teleop, what can you deduce?

Greg McKaskle

[jibicax]

I guess I was doing something complete different with the probes before. I checked the code to get the numbers you wanted but and all the probes say Not Executed in begin.vi, Teleop.vi, Auto.vi, and RobotMain.vi. But the code is enabled on the DS.

[Greg McKaskle]

Did you run the code using the run arrow? If you are running a deployed or startup application, the debugger isn't attached. If it is, you should put in the probes and then run in order to verify that Begin does run and determine if where it is running.

Greg McKaskle