Unable to connect to crio devices after upgrading NI-Rio error 63040

[rex1030]

I have two crio devices with the 9012 RT controller running on the 9103 and 9104 back planes. I had LabVIEW 8.2 running on the host computer and we had the devices hooked up and working on a small network. We recently upgraded to LabVIEW 8.5 and MAX 4.3. Now I am getting some very strange errors and I could really use your help.

After installing the software and drivers on the host computer I wanted to update the software and drivers on the cRIO devices. Here is where I ran into issues. In MAX, I can see the cRIO devices but when I try to expand expand the "Devices and Interfaces" node I get the following errors:
- VISA Error: 0xBFFF00A7 - "The machine does not exist or is not accepting any connections..."
- NI-RIO error 63040 - "A connection could not be established to specified remote device..."

I try expand the software node and I get this error: "Timed out while trying to communicate with the remote target."
I click the software node and try to press the add software button (to upgrade the drivers and software on the cRIO device) and I get
"error 56: could not connect with remote device..."

The strange thing is that when I delete the devices from max, then exit max and come back in it discovers the devices automatically. This tells me that it can see the devices and is communicating with them on some level. However, neither this nor rebooting the cRIO devices makes any difference.

I have read every support article and thread I can find even remotely related to these errors and nothing I have found helps. Most people that get the VISA error: 0xBFFF00A7 have the ip configured incorrectly on the remote device. However, we had it working before. Nothing has changed on the cRIO devices yet. A lot of the support articles suggest a driver conflict and tell the person to update the drivers on the device... I would if I could.

What do you guys think?

rex1030

[NoahR]

Hi rex1030,

Thanks for contacting National Instruments.  I have been looking into your question some and I do have a couple of suggestions for you.  Like you mentioned earlier, a lot of the problems that cause the communication error have to do with the network settings for the device regarding the IP address, Subnet mask, and/or Default Gateway.  I know that you said you have had this working before with the same configuration, so there is a good chance that this isn't the reason why you are having problems.  However, it is still a good idea to double-check the settings to make sure that everything is what it should be.  I have attached a link below that goes through some of the settings that should be configured.  However, if this does not work, you may try to reformat your controller when it is in safe mode.  If you have information on the controller that you would like to keep, I would take it off the controller before doing this.  Reformatting the controller can be helpful if, for some reason, the software on the controller became corrupt.  I hope some of this helps and if you have any more questions, please feel free to reply back!

http://digital.ni.com/public.nsf/websearch/DAB1FE882B565F658625720A002900D7?OpenDocument

[rex1030]

Okay, so after fighting with it for some time, we hooked up the laptop we actually used to configure the devices with originally. We don't know why, but this change of laptops did the trick even though they were both running the same versions of all the software. We were then able to use MAX to update the drivers and software on the cRIO devices.

I am still getting errors though. They are strange too. I am still getting the VISA and NI-RIO errors but only on one device at a time. Sometimes if we press the refresh button in MAX, one com port will be visible while the other gets the visa error and then they might switch if we refresh again. This is confusing because sometimes the com port on a particular device is fine and then if you refresh them it is getting an error.

Does anyone have any idea what this might be? Any insight into why switching laptops would have mattered especially if they are both running the same versions of the software?

Update --------------------
I am getting led status code 4... which doesn't make any sense considering we aren't running a VI on the RT controller at the moment. I think it is very likely software on the RT device is corrupt so we are going to reformat it. I will keep you guys posted.

Message Edited by rex1030 on 10-30-2007 02:14 PM

[JMota]

The only thing I can think of for the different behaviors with different laptops is having different firewalls installed or with different settings. That could explain why MAX reports a communication error for VISA and NI-RIO even though it can discover the devices on the sub-network (different protocols are used, and the firewall may be blocking VISA and NI-RIO but not MAX's discovery).

As far this goes

---

I am still getting errors though. They are strange too. I am still getting the VISA and NI-RIO errors but only on one device at a time. Sometimes if we press the refresh button in MAX, one com port will be visible while the other gets the visa error and then they might switch if we refresh again. This is confusing because sometimes the com port on a particular device is fine and then if you refresh them it is getting an error.

---

have you tried taking off the newtork one of the cRIO controllers and characterize the problem with just one of them? Something I would suggest, is to verify that they have unique IP addresses (might not hurt to make sure they have different MAC addresses from within MAX too; have never seen a case like that though).

J.Mota

[rex1030]

For some reason, reformating the devices fixed the errors. The visa error showed up on one device, but when i hit refresh on the devices and interfaces node, it discovered the visa device (the com port) and the error was gone. This error stayed gone even after a reboot of the cRIO devices.

I think some of the software may have gone corrupt during the upgrade or before. So I really appreciate your support and especially the NI guy's suggestion to reformat. Thanks

rex1030