cRIO not letting me deploy code.

[CNettles11]

I'm trying to deploy code to my cRIO but i keep getting the error "Unable to resolve from current dialog"
I've tried connecting using patch cables, crossover cables and the router. Can anyone help? Thanks

Chris Nettles
Team 3556

[Alan Anderson]

Are you talking about the LabVIEW dialog that shows a bunch of running VIs on the cRIO? That's not an error. It's just an informative message, basically letting you know that it's going to have to stop those VIs in order to replace them with the copies you're trying to deploy, and giving you a chance to change your mind before continuing.

Just tell it everything is okay and it should work as you want.

[CNettles11]

no, our cRIO is band new and we formatted it to read our team number/IP address. When i build the Robot Deployment VI, it works fine but when i try to deploy code to the cRIO, it starts, then tells me "Unable to connect to the RT cRIO Device, Abort?" and when it does find it, it brings up the "Unable to resolve from current dialog error.

[Alan Anderson]

Originally Posted by CNettles11

When i build the Robot Deployment VI,...

When you do what? That's not an action I recognize.

Your original description of the problem didn't say anything about the first error. I can't tell whether you're leaving out any other relevant information that might help us help you. What code are you trying to deploy? Could you describe exactly what steps you're doing, and what happens when you do it?

[CNettles11]

http://imgur.com/Cuc51
LabVIEW Startup screen
http://imgur.com/n8exY
The lvproj file

Selecting to build the VI

Successful build

Deploying VI files

LabVIEW asking to save changes. I saved the changes

Unsuccessful deploy

I'm limited to 5 images so you'll have to open the first 2 in your browser.

[apalrd]

The deployment message is what is important: Failed to connect to real-time target.

Possible causes:
Robot is turned off
Radio(s) are turned off or improperly connected
Robot is still booting up
Robot has crashed (see the Driver Station, and look for the Communications light to go off. If only Robot Code goes off, you're fine).
Something is improperly configured (wrong IP address, other IP settings)
Computer has wrong IP address

Try:
ping the cRio. If it fails, then the problem is not in LabVIEW.

Connect directly to the cRio via a crossover cable and try again - If this works then the problem is in the radio(s), and they are not configured correctly.

[Alan Anderson]

Don't "Deploy" the code.

In the same menu containing the "Build" command, there is a "Run as Startup" command. That's the one you should be using to transfer the built program to the cRIO.

[CNettles11]

i clicked run as startup but i still get the same error. i CAN ping the cRIO.

[Greg McKaskle]

Perhaps you should try formatting again, and make sure that the format checkbox is checked. The imaging tool can be used to simply change IP info to match the team, or it can change language or version of the image.

I suspect that the cRIO is not running v25.

Greg McKaskle

[CNettles11]

I suspect not having all of the labview updates could be hindering the process. it it doesn't work, i'll try to post tomorrow.

[mattiej]

I'm not sure if it is different for you, but I don't run my robot code (in LabVIEW) through that VI. I open up the Robot Main VI and run that code (also build). Maybe that is your problem?

[CNettles11]

ive tried both, to no avail.

[Greg McKaskle]

When I looked at the screenshots above, I noticed that you were building the build spec at the bottom of the project window, but you were deploying at the top of the target.

Did you right click on the bottom element, the build spec, and set to run as startup?

If you still cannot deploy, please open up Robot Main and see that it is not broken. Also open up the Autonomous VI and see that it is not broken.

If that doesn't work, do you want to share your VIs so that we can determine what is causing the error?

Greg McKaskle

[Mark McLeod]

I ran into a similar problem at a rookie last night, but didn't have time to investigate. Too much training going on.
It could have been as simple as a cross-over cable, but I just didn't have the time or cause.

Their Classmate would fail on the "Run as startup," in the same way as yours, connecting to a traveling cRIO I use.
The cRIO works with our older team Classmate and other laptops without issue, and everything has been fully updated and operating for a week.
In that particular case, which may not be the same as yours, it makes me think the issue is with the classmate.

I have a different rookie visit today and I'll see if their Classmate demonstrates the same issue.

[Greg McKaskle]

Mark. Feel free to submit some code if you have it narrowed down. Doug has a variety of laptops to test with, but I don't believe we have seen this issue yet.

Greg McKaskle