Real-Time Measurement and Control

cancel
Showing results for 
Search instead for 
Did you mean: 

cRio connectivity issues

I am trying to move my cRio 9073 from a previous computer to a new computer. Both computers have windows 7 and the necessary software (Labview 2010, etc.). The system worked fine on the previous computer. 

 

I can't even get the device recognized by the remote systems tab in MAX. Do we need to reset the ip in safe mode? I have read the manuals and tried many things but I'm going in circles. 

 

I haven't checked the part number, but the rio is older so I believe it does not have the automatic DHCP connection, just resets ip to 0.0.0.0

 

Also, do I need to create a new remote device? If so which kind? 

 

Thanks

0 Kudos
Message 1 of 6
(4,236 Views)

Is the cRIO set up with an IP that is on a different subnet from the original computer? If so, it will not be visible in Measurement & Automation Explorer. Try to ping the cRIO to verify it is up and then IP Reset if necessary.

 

Logan H

National Instruments
Applications Engineer
0 Kudos
Message 2 of 6
(4,203 Views)

That is one of the things I am not sure about. It is connected directly to the computer using a crossover cable, and I assumed it is communicating over the LAN connection. I tried pinging it and I believe I was successful (the link light blinked for times for four bits of data), but for some reason I cannot create a new remote system in MAX (field point or device on different subnet). I have tried changing the internet settings on the control panel (ip, subnet mask, etc.) but I can never create a new device or detect the existing one. 

 

Basically the problem is I don't know where to start, besides plugging it in and trying to detect it, messing with the computer's internet settings, and/or reseting the ip on the rio.

 

When I do reset the rio, it does not reset to 0.0.0.0 ip like i think it should, but to 169.254.xxx.xxx. 

 

Is the subnet something I need to setup on the computer that attaches to the rio? I don't exactly understand that part, but I am looking it up now.

 

Thanks,

 

Geoff

0 Kudos
Message 3 of 6
(4,199 Views)

gd86,

 

Was the other computer set up with the cRIO via crossover? There are a few additional setup steps necessary when connecting via crossover since you are basically creating a private network. A great resource for this setup can be found here in our Developer Zone.

 

The IP address that you are seeing your cRIO reset to (169.254.1.0) is the default IP for Link Local. This address is used instead of 0.0.0.0 because a null set IP cannot be pinged.

 

Logan H

National Instruments
Applications Engineer
0 Kudos
Message 4 of 6
(4,169 Views)

hi gd86

try to set different ip addresike 192.168.1.9 & used cross cable nd dont take it on server use it as remote system on ur system

like LAN cable on ur own system

nd u can easily find link how to reset cRIO

one more thing format ur real time controller nd then install ur s=required things

 

hope it will work

tc

0 Kudos
Message 5 of 6
(4,149 Views)

I actually had this issue too. If you have wireless enabled, disable it and rescan.

 

Hope this helps!

0 Kudos
Message 6 of 6
(3,941 Views)