Can't see crio 9014 in max

[crock]

I have a CompactRio 9014 that I have not been able to connect to using MAX.  I have labview 8.2 with the real-time module and compactRio drivers 2.1.0.  The windows firewall is off but the crio never shows up in MAX no matter what I do.  I have done a packet capture from another computer that is connected to the same hub as the crio and Labview machine.  I can see the two hosts talking and the last message sent by the crio contains a the string "Unconfigured" in the payload of the UDP packet.

Any ideas what is wrong?  I have NI VISA version 4.0 so the 4.2 issue shouldn't be a problem.  Maybe the 9014 isn't supported by crio drivers 2.1.0?  Do I need to be an Administrator (currently a power user)?

Thanks,
Marshall

[Bassett_Hound]

Marshall,

You kinda answered the question your self already.  The cRIO-9014 controller is supported by LabVIEW Real-Time 8.2.1 and above and NI RIO 2.1.3 and above.

Software Support for cRIO Hardware

Currently, NI RIO 2.3.1 is the latest version.

Hope that helps,

Bassett

[crock]

 Thanks, that is the problem.  I couldn't find anywhere that listed what driver/labview versions were needed for the 9014.  I guess I just wan't looking in the right place.

[ericnya]

My problem is that

I can see the Crio in MAX but i can not see the chassis with the NI 9201 and 9403 set in.

[CarlaU]

Hi ericnya,

I'm a little confused as to what you can and cannot see in MAX. Do you see any aspect of your setup in MAX? Also, which version of the NI-RIO driver do you have installed? I would recommend installing the most recent NI RIO driver, which is 2.4.

Some other basic things to check would be:

• Have you tried isolating the network by just using a cross-over network?  Can you still reproduce it?  Unusually heavy network traffic can cause communication to get interrupted.
• When you reconnect the power and you redetect the controller, do you have to reassign the IP address?  Are you using a static IP address that is not being used elsewhere? A duplicate IP can often be assigned by a DHCP network, causing issues.  One good check is to shut off your controller when you lose communication, and try to ping that IP address from the Windows Command Prompt.

I hope this helps a bit.