cRIO setup issue

[brunoUC]

hi, we used to connect our 8 slots cRIO to the the classmate, but recently we changed it for other laptop and we are having some problems while trying to connect the cRIO.
we can see the crio in MAX and we need to reconfigure it with the CompactRIO imaging tool so we can use the labview 2011 on it, but when we press apply the folowing error messege appears:
The cRIO IP address is unreachable. Ensure that one of your computer's network adapters is on the same subnet.

thanks from team #1156

[SenorZ]

We had similar issues. Here is a list of things we fixed and now it works:
Make sure you're wifi is off
Make sure you're IP is set correctly (see tutorial in Labview)
Make sure you set the subnet to 255.255.255.0
Make sure you turn any proxy off.
And make sure you are using the crossover cable

[brunoUC]

i already turned the wi-fi off with the device manager and i already set the ip on both the crio and on the laptop.
thanks

[twetherbee]

One of the team's I mentor also has been having cRIO connection issues.

We have been getting the following error:

Error -2147220304 occurred at nisyscfg.lvlib:Restart.vi:1

Possible reason(s):

NI System Configuration: (Hex 0x800404B0) Timeout while waiting for reboot. System is offline.


Complete call chain:
nisyscfg.lvlib:Restart.vi:1
ConfigUtility.lvlib:2012_FormatSystem.vi
ConfigUtility.lvlib:ReImageTarget.vi
ConfigUtility.lvlibialog.vi

I called NI FIRST Tech support and I gave them the error message. They said that it is a pretty common error they have been seeing this year.

He suggested that we try going through the same sequence to wipe out and reflash the cRIO with the wireless card on your laptop ENABLED, but still connecting to the cRIO with the yellow crossover cable.

They said that depending on the laptop vendor, they have seen that this solves the problem about half of the time. They also said that there is a fix for this issue coming.

The tech support phone number is 800-531-5066 (M-F, 1PM-7PM CST). Their web support forum is also available all day long.

We haven't tried it yet (snowed in today in the Pacific Northwest), so I don't know if it solves our problem.

Good Luck.

[codedr]

We had a similar issue.
When setting ip-addresses on the ethernet port, sometimes windows 'remembers' the old
addresses and it confuses the FIRST cRIO imaging tool, but MAX tool work fine.

Open a command window
type 'ipconfig'
If the output shows multiple ip-addresses for your ethernet port, you can delete them
with netsh.
type 'netsh'
type help and it will show you the syntax to delete the extra addresses.

[ebarker]

read this

[Jon236]

In addition to Ed's excellent advice, turn off any Bluetooth adapters on your PC as well!

[Alan Anderson]

Originally Posted by brunoUC

i already turned the wi-fi off with the device manager

Depending on exactly what you mean by that, it might not be sufficient. You have to DISABLE the wireless interface, not just turn it off.

and i already set the ip on both the crio and on the laptop.
thanks

The error message suggests otherwise. It's pretty specific. Run the ipconfig command and copy its output here so we can make sure everything looks the way it ought to.

[Mastonevich]

twetherbee, I believe we had the same error at first. We found that we didn't install the LabView program/required libraries (it is required to communicate with the cRIO) and after installation the timeout error ceased.

[EricS-Team180]

Adding to the posts by ebarker and jon236, we found that, while doing the update from an Acer Windows 7 laptop, we also had to turn off the Windows Firewall, before we had success.


Interestingly enough, a few days earlier, we updated our other cRio from an Hp Windows XP desktop and had no issues.
Eric

[brunoUC]

here is what the ipconfig shows:
ethernet adapter local area connection:

Connection-specific DNS suffix......:
link-local IPv6 address.................: fe80::b8a8:90c:febe:fec5%11
IPv4 address..............................: 10.11.56.6
subnet mask...............................: 255.255.255.0
default gateway..........................:0.0.0.0
10.11.56.2

[twetherbee]

Originally Posted by Mastonevich

twetherbee, I believe we had the same error at first. We found that we didn't install the LabView program/required libraries (it is required to communicate with the cRIO) and after installation the timeout error ceased.

Thanks for the reply. I'm more of a mechanical guy, so I'm just helping them apply basic problem solving strategies.

I'm pretty sure that they have all the software and updates loaded correctly, though. They had their laptops connected to the cRIO at one point, but couldn't get any of the code to work. Somewhere along the lines of debugging, something got corrupted or they thought to try wiping the cRIO again and start over. That is when this issue began.

Turns out that our original problem was likely due to the modules in our older cRIO not being rearranged to the new configuration for this year. (I keep telling them that documentation is your friend....)

We're all snowed in here for another day (I miss living in Wyoming and Montana where towns actually own enough snow plows that a couple inches of snow doesn't shut everything down.) so we'll have to wait and see if any of these methods work.

[Mastonevich]

One other note I found. I had the connections to the cRIO working fine after initial install. At some point you have register with NI to complete their process which I thought I had done. Then our connections stopped working with your same error. Through troubleshooting I finally restart our programming laptop, and it came up with the registration again. It required the fill in more required fields on the NI registration. From that point forward everything started working.

[ebarker]

Yes indeed - 'disable' all network interfaces, wireless, extra wired, bluetooth, hamachi, and anything that looks like an network interface.

If you do not disable all that then variations occur between PC's depending depending on the local PC configuration and how things are timing out in the NI software. That is why some computer work and some done. It depends on whether it can find the cRio before the timeouts occur.

So just do it to procedure and it will be fine. One day we will get an update that improves things, one day.