cRIO Imaging Issue

[Joe Ross]

I've noticed that the imaging tool will not display the modules unless it is on the same class C network as the cRIO, even if the netmask of the computer is class A.

Additionally, having multiple network interfaces on the same network can confuse the imaging tool and driver station. Have you disabled unused network interfaces?

[nheft]

The laptop is 10.5.33.5 and the cRIO is 10.5.33.2. I have to check what I had the subnet mask set to on the laptop. I think I have it set it to 255.255.255.0 but I may have set it to 255.0.0.0. Can't check it until I get to the school tonight.

Once the cRIO has been properly imaged (I have another computer that works in the lab at the school), the laptop properly sees the modules and can deploy new software. That is why I think the laptop is incorrectly imaging the cRIO.

[vintagecoke]

If I remember right, it needs to be 255.0.0.0. We got our successfully flashed on a Windows 7 laptop with that subnet mask.

[litchbots]

We are having exactly the same issue with the modules not showing up. Our cRio is a brand new 4 slot however. I am trying to image it with a Widows 8 laptop. When I get to school tomorrow I will try to image it with our old laptop and see if that will help. Thing is - the new Windows * laptop imaged the old 8 slot cRio not problem. This was my second day spent messing around with this new cRio. I was able to place Lab View code on it (no errors returned) using run as startup, but when I pull up the drivers station it does not recognize the cRio - no robot code. Any advice would be welcome. Could it be the drivers that came with the cRio? Should I re-install them?

[Greg McKaskle]

Just to clarify, the laptop can't actually see the modules. The cRIO has to be imaged with a recent enough image to publish its module list to the imaging tool. Just graying out the image doesn't make that crystal clear, but that is one thing that can cause it.

Greg McKaskle