Driver station not detecting robot code

[captainking]

I've uploaded my code to the cRio, deployed my code on the driver station, reimaged the cRio, and tried everything I can, yet the driver station keeps saying that there is no robot code. Any ideas? The driver station says it's connecting and communicating with the crio

[Ziaholic]

Are there any error messages during the deploy? Uncheck the box and review the messages that scroll by ... sometimes there's an error in there that'll help to diagnose the problem.

... and the driver station console app has a diagnostics tab that shows error messages also ... anything interesting in there?

[kamocat]

There's a similar thread on the USFIRST forums.
Try updating the Driver Station and your development laptop, and re-imaging the cRIO afterwards.
I've been having the same trouble, and I suspect this is the answer.

[Boydean]

Originally Posted by kamocat

There's a similar thread on the USFIRST forums.
Try updating the Driver Station and your development laptop, and re-imaging the cRIO afterwards.
I've been having the same trouble, and I suspect this is the answer.

I can't seem to find this thread on the forums, you mind providing a link?

I have been having this trouble for the past two days, no fix. I'll try what you suggested tomorrow, if it works I'll be singing praises on here ASAP.

[kamocat]

Originally Posted by Boydean

I can't seem to find this thread on the forums, you mind providing a link?

I have been having this trouble for the past two days, no fix. I'll try what you suggested tomorrow, if it works I'll be singing praises on here ASAP.

Sorry about that.
http://forums.usfirst.org/showthread...5328#post35328

There's no new information there, so I didn't see it as useful.

[Bharat Nain]

We had the same issue. It turns out that we did not apply the "Mandatory LabView update". It is really a mandatory update regardless because it contains the 2010 image for the cRio. Since we were using WindRiver/C/C++, we figured this did not apply to us and I think thats what might have happened to you also. Anyway, here is the link to the update: http://joule.ni.com/nidu/cds/view/p/lang/en/id/1534

[Greg McKaskle]

You will want to update the cRIO to image v19 using the 2010 cRIO imaging tool. If you are using 2010 tools to target a 2009 imaged cRIO, it really isn't running your code, at least not in a useful way. Sorry that the error messages didn't point that out more directly.

Greg McKaskle

[2544HCRC]

I'm in the same boat. Following the "benchtop test" procedures in the control system manual. I have updated labview. I have imaged the cRIO. I am uploading v19. I have opened a new program, gone through the steps and uploaded the program "main.vi", all seems to go well. Nothing then seems to happen. The book says I should be able to control the robot, but nothing is happening. I log out of the developer window and into the driver station window. I have a connection (green light), no errors in the diagnostics window, but I have a "no code" in the lower left hand window. I have about wore out the text on the manual pages I've read them so many times. I'm brand new to this so I'm assuming the problem is somewhere between the chair and the computer, but for the life of me I have no idea what. BTW, all other tests to this point seem to be ok, blinky lights are all blinking in the correct way.

[Mark McLeod]

Instead of deploying the main.vi, go under Build Specifications to the project listed there, right click and do a "Build" followed by "Run as startup".

[2544HCRC]

We got it working! Thanks to the help from a student on a neighboring team. In the end I'm not sure what fixed the problem. We reimaged the cRIO for the third time, and then he deployed the code differently. He went to the bottom of the program list (not main.vi) and right clicked and then deployed the software. There was a separate click to start the code after restart and then it worked. It seems that the directions in the "bench test" leave a lot to be desired. He also said that he had to change some things around in the code as far as defining the motors??

It seems that there could be a "cookbook" of sorts that tells you If you want to do X with your robot, then this is what you need to do code wise. It seems that for the most part the robots are all doing pretty much the same things. Does this exist somewhere?