[HELP] cRIO not imaging as it should be

[domingocool]

So, we've been having trouble imaging our cRIO for two days and can't seem to figure out why. We periodically get the two blinks on the status lights so we installed NI MAX 5.5 and re-formatted the cRIO and re installed the software with all the add-ons. We set out LAN IP to 10.46.45.5 and the subnet mask to 255.255.255.0. When we try to image it it still doesn't image(or at least starts but puts an error(Error 7)). Also the modules never show up on the Imaging Tool nor are the little switches usable. We've tried everything we feel that we can so any help would be awesome. Thanks.

[sanddrag]

Have you pulled the modules and checked the condition of the pins in the chassis? The HD15 connectors are susceptible to bent pins if the modules are not installed correctly.

[Tom Line]

Originally Posted by domingocool

So, we've been having trouble imaging our cRIO for two days and can't seem to figure out why. We periodically get the two blinks on the status lights so we installed NI MAX 5.5 and re-formatted the cRIO and re installed the software with all the add-ons. We set out LAN IP to 10.46.45.5 and the subnet mask to 255.255.255.0. When we try to image it it still doesn't image(or at least starts but puts an error(Error 7)). Also the modules never show up on the Imaging Tool nor are the little switches usable. We've tried everything we feel that we can so any help would be awesome. Thanks.

I would start with the basics. Can you go to a command prompt and ping the crio? Let's make sure you have communication first.

Also, you are connecting your ethernet cable directly to the crio from the computer, right?

[Team3266Spencer]

Is it a 4 slot cRio?

[Alan Anderson]

Originally Posted by domingocool

So, we've been having trouble imaging our cRIO for two days and can't seem to figure out why. We periodically get the two blinks on the status lights so we installed NI MAX 5.5 and re-formatted the cRIO and re installed the software with all the add-ons. We set out LAN IP to 10.46.45.5 and the subnet mask to 255.255.255.0. When we try to image it it still doesn't image(or at least starts but puts an error(Error 7)). Also the modules never show up on the Imaging Tool nor are the little switches usable. We've tried everything we feel that we can so any help would be awesome. Thanks.

So far as I can tell, there's never a good reason to use NI MAX on a cRIO-FRC.

You say you installed "all the add-ons"? Does that include the FRC Utilities update? Error 7 usually means that a program can't find a necessary file. Perhaps you tried to run the update from inside the compressed folder without extracting the files first.

[domingocool]

Originally Posted by Team3266Spencer

Is it a 4 slot cRio?

Yes it is

[domingocool]

Originally Posted by Tom Line

I would start with the basics. Can you go to a command prompt and ping the crio? Let's make sure you have communication first.

Also, you are connecting your ethernet cable directly to the crio from the computer, right?

How do you go about pinging the cRIO with CMD?

[BBray_T1296]

Originally Posted by domingocool

How do you go about pinging the cRIO with CMD?

Pinging an IP (or website)

from the desktop with all windows minimized and an Ethernet link directly from your computer to the cRIO (powered on)
-hold /windows key (meta)/ and while holding, press /r/
-type "cmd" (no quotes)
-press /enter/
-type "ping" then /spacebar/ then "your cRIO's IP" (you said before: 10.46.45.5)
-press /enter/

It should look something like picture 1 ("google.com" will be "10.46.45.5"). Of course, the ping values may be different, but that is not what you are pinging to test, you just want any reply at all. If it looks like picture 2, I would try pinging "10.46.45.1" If that fails, you may have a problem. If it works and you DO get a reply, however, there may be hope yet...

Anyways, If it is bricked, NI probably has some sort of warranty on that...

[Aaron.Graeve]

If they used the FRC cRIO Imaging tool, shouldn't the cRIO IP be 10.46.45.2? I think 10.46.45.5 is the IP of their driver station.

[BBray_T1296]

Oh well I don't know. Just try pinging everything from ".1" to ".10" at least one is bound to work (or not)

[domingocool]

Originally Posted by Aaron.Graeve

If they used the FRC cRIO Imaging tool, shouldn't the cRIO IP be 10.46.45.2? I think 10.46.45.5 is the IP of their driver station.

We set the IP of the cRIO to 10.46.45.2 and the IP of the computer to 10.46.45.5 and 6.

[domingocool]

Originally Posted by BBray_T1296

Pinging an IP (or website)

from the desktop with all windows minimized and an Ethernet link directly from your computer to the cRIO (powered on)
-hold /windows key (meta)/ and while holding, press /r/
-type "cmd" (no quotes)
-press /enter/
-type "ping" then /spacebar/ then "your cRIO's IP" (you said before: 10.46.45.5)
-press /enter/

It should look something like picture 1 ("google.com" will be "10.46.45.5"). Of course, the ping values may be different, but that is not what you are pinging to test, you just want any reply at all. If it looks like picture 2, I would try pinging "10.46.45.1" If that fails, you may have a problem. If it works and you DO get a reply, however, there may be hope yet...

Anyways, If it is bricked, NI probably has some sort of warranty on that...

We tried pinging and 10.46.45.9 was the only one that was successful. Our computer is set to 10.46.45.9; did it just ping the computer?

[Alan Anderson]

Originally Posted by domingocool

We tried pinging and 10.46.45.9 was the only one that was successful. Our computer is set to 10.46.45.9; did it just ping the computer?

Yes, I'd say you just pinged yourself. However, that's the address defined for the wireless network adapter. Are you trying this using a wireless connection, or a wired one? It's never a good idea to try to reimage a cRIO over Wi-Fi; too much can go wrong.

[domingocool]

Originally Posted by Alan Anderson

So far as I can tell, there's never a good reason to use NI MAX on a cRIO-FRC.

You say you installed "all the add-ons"? Does that include the FRC Utilities update? Error 7 usually means that a program can't find a necessary file. Perhaps you tried to run the update from inside the compressed folder without extracting the files first.

Well we used NI MAX to re-format and reinstall the software to the cRIO because the status light was showing a software blinking error. There were no compressed folders used. NI MAX was supposed to do the install without the need for extraction of any files.

[Tom Line]

Originally Posted by domingocool

Well we used NI MAX to re-format and reinstall the software to the cRIO because the status light was showing a software blinking error. There were no compressed folders used. NI MAX was supposed to do the install without the need for extraction of any files.

What IP address did you assign to the cRIO in NI MAX?