Code Problems

[dmitch]

Hey we're wanting to be able to run our robot from last year but it wont run. The electrical stuff is hooked up correctly, and the code runs. However, we can't get the code to compile onto the cRIO, so the robot won't run. Any Ideas?

[Bot190]

Your going to need to provide more information than that for us to provide any useful help.

First, you say that the code runs, but then you say that it doesn't compile.
Which is it?

Can you connect to the Crio, you can check by opening a command prompt and typing "ping 10.xx.yy.2" where xx.yy is your team number.

[plnyyanks]

Can you be more specific with errors? What language is the robot coded in?

[dmitch]

Ok sorry. First of all, it is coded in LabView. When I say the code runs but doesn't compile I mean that when i click the run arrow in LabView, it shows the code as running, however, it will not compile to the cRIO.
It is my first year being the head programmer because our programmer last year is now in college. As I understand it though, I'm supposed to get a message box saying "compiling to cRIO" (or something along those lines), and then when it has compiled, I can minimize LabView and open up the drivers station.
I wish I had more to say but our coach and I are both confused because everything seems to be hooked up correctly. We are pretty sure that is either a problem with the cRIO itself, the code, or the wiring because we have direct-wired it and it would not run. I believe the code works because I am not recieving any errors stopping it from running. Also, I believe the wiring is correct because it hasn't been touched since last March.
That leaves only the cRIO as we see it. We just want to make sure that there isn't something simple we're overlooking before we attempt to replace the $1000 cRIO.
A final note: my team only meets on Wednesdays before the season so that is when I am able to access the robot. If there is any other info i can provide you please tell me ASAP so I can try to get this solved quickly.

THANK YOU SO MUCH anyone that helps with this for taking some offseason time to help me out.

[aechmtwash11]

is your target set correctly? 10.xx.yy.2?

[jspatz1]

With a Labview program you must do a "build" step to compile, then deploy it to the Crio with "Run as startup." Are you familiar with these steps?

[Ether]

Originally Posted by dmitch

A final note: my team only meets on Wednesdays before the season so that is when I am able to access the robot. If there is any other info i can provide you please tell me ASAP so I can try to get this solved quickly.

Do you meet in the evenings, after normal working hours? Do you have convenient access to the internet in close proximity to where you will be actually working on the robot? Let this forum know in advance what hours you will be at the site working on the robot, and I'll bet you'll get at least a few knowledgeable LabVIEW folks standing by ready to answer questions you post while you are there and you can try the things that are suggested and provide immediate feedback.

Before your next team meeting, watch this video and ask questions here.

[Alan Anderson]

Originally Posted by dmitch

Ok sorry. First of all, it is coded in LabView. When I say the code runs but doesn't compile I mean that when i click the run arrow in LabView, it shows the code as running, however, it will not compile to the cRIO.

How are you trying to get it to "compile to the cRIO"? What happens when you try? You should be choosing the Build option under the right-mouse-button menu from the "FRC Robot Bootup Deployment" object at the very bottom of the project window. That object is nested under "Build Specifications" and "RT CompactRIO Target". Then, after the project has been built successfully, you need to choose the "Run as startup" option from the same menu.

It is my first year being the head programmer because our programmer last year is now in college. As I understand it though, I'm supposed to get a message box saying "compiling to cRIO" (or something along those lines), and then when it has compiled, I can minimize LabView and open up the drivers station.

This sounds suspiciously like you're not running the Driver Station application.

I wish I had more to say but our coach and I are both confused because everything seems to be hooked up correctly. We are pretty sure that is either a problem with the cRIO itself, the code, or the wiring because we have direct-wired it and it would not run. I believe the code works because I am not recieving any errors stopping it from running. Also, I believe the wiring is correct because it hasn't been touched since last March.
That leaves only the cRIO as we see it.

What do the indicators on the Driver Station's "Dagnostics" tab tell you?

If you haven't enabled the robot using the button on the "Operation" tab of the Driver Station application, none of the motors or relays or solenoids will be allowed to work.

[kamocat]

Here's some documentation to help you out. You shouldn't have to struggle through asking us basic questions when there's documents to walk you through it.

"Using the FRC Framework" from 2009 : http://decibel.ni.com/content/docs/DOC-2663
A couple things have changed (use of the global variable deemphasized, refnum registries, and the removal of Autonomous Independent this coming year), but it's still a good document. I would recommend PRINTING this one.
Methods of deployment are on page 13.
By the way, the second method of deployment, "DEPLOYING THE PROGRAM FROM THE PROJECT EXPLORER WINDOW", I have not managed to get work, though I haven't tried in almost two years.

2010 "Bench Test":
http://usfirst.org/uploadedFiles/Com...ed-Rev-0.7.pdf
There's a lot of stuff in this one that is about C++ and Java, so you probably don't want to print the whole thing. This includes methods of deployment.

[dmitch]

I never am going to have internet access during the time I'm actually working on the robot. However, I am running it tomorrow and I will have an answer for you then as to whether or not it works.

[kamocat]

Download it on a different computer and print out the useful sections.
I recommend you print the entirety of "Using the FRC Framework".

[Cecil]

This is a bit off topic.. but you said the last time it was used was in march.. Did you happen to reset the Gaming Adaptor to not have any encryption on it? If your router is unencrypted and the gaming adaptor is, it wont connect. I don't know if this would throw an error when you hit the run button, but it is worth a shot

[dmitch]

Ok sorry its been a while since i've been on. We smelled stuff burning last time we turned on our robot, so we took a further look and saw that several wires had slashes in them like someone had missed with the wire cutters...so we took apart all the wiring and are redoing it. (Yes that was serious.) And my question now is how on earth do you wire a PWM to a Jaguar? As i recall from my rushed intro last year the PWM can either hook into the sidecar or the cRIO slot??? And then go to either Jaguar or sensor??? (My knowledge on this part is REALLY fuzzy) I would prefer a diagram but if you have some words to post that will be very clear that would be great.

[Mark McLeod]

See if these wiring diagrams help explain where what goes.

• Control System Data Wiring Diagram

• Control System Power Wiring Diagram

[mattiej]

Originally Posted by dmitch

Ok sorry its been a while since i've been on. We smelled stuff burning last time we turned on our robot, so we took a further look and saw that several wires had slashes in them like someone had missed with the wire cutters...so we took apart all the wiring and are redoing it. (Yes that was serious.) And my question now is how on earth do you wire a PWM to a Jaguar? As i recall from my rushed intro last year the PWM can either hook into the sidecar or the cRIO slot??? And then go to either Jaguar or sensor??? (My knowledge on this part is REALLY fuzzy) I would prefer a diagram but if you have some words to post that will be very clear that would be great.

Sorry I don't have a picture. But what you do is use servo wires (Red, white, and black with three pronged push connectors) to connect the Jaguar to the Sidecar. The sidecar uses a serial (I think that is what it is called - it is really big) to connect to the cRIO. The Jaguar hooks up to the power supply via the red and black screws, and to the motor via the green and white screws. Hope this helps!

EDIT: Definitely use the diagrams above