cRIO Problem

[darthbean18]

According to the How-to PDF, on your last attempt to fix it, you:
1. Installed all of the updates
2. set your IP address to 10.34.13.6 (10.34.13.5 on the classmate)
3. connected the cRIO to your computer via an ethernet cable
4. switched the cRIO into safe mode
5. ran the imaging software to format the cRIO
6. switched the cRIO out of safe mode
7. ran it again to apply an image
8. Built and deployed code
?

[mattiej]

Yeah I did those steps, minus the run and deploy code because LabVIEW could not connect to the cRIO. I still get the error.

[kylelanman]

I'm going to throw this out there because we ran into it tonight.

If you install the imaging tool on a computer that already had it from a previous year you end up with 2 copies of the imaging program. One in the LabView 8.5 folder and one in the LabView 8.6 folder. The shortcut on our desktop got changed but the one in the start menu did not and this stumped us for a while. Because we were running last years or maybe even the crio imaging tool for the year before and got an error that I do not remember off the top of my head.

The other problem we had which probably seems obvious to most people but I will throw it out there any ways because a new team member failed to do it and it caused problems is entering the team number in the imaging tool.

No guaranties, just the problems and the solutions my team ran into when we imaged our cRIO.

[mattiej]

Thanks for the help, but we finally got it resolved. The issue was with the firewalls. Error 60, then sequentially error 1 are firewall errors. Just if anyone else wants to know.