cannot detect chassis

[marco2136]

Hi adecold,

The problem is I cannot see the device when I open MAX under Remote Systems, so I can't right click on it to select Format. I also have no idee of which software is currently installed on the device itself.

Is there another way to format a device without using MAX?

I added a picture of the cablemarkings on the ethernetcable I'm currently using.

[TutuAjayi]

It looks like you may be using a patch cable instead of a crossover cable. See http://digital.ni.com/public.nsf/allkb/72AE8CADA1AF075686256A16005D55B1

You can usually peek at the ends of the cable to see the wire arrangement. If they are identical on both sides, then it's a patch cable (not the cable you want). 

Were you able to use this cable for a direct connection from your Laptop to your Controller in the past?

[marco2136]

Thanks, for the link. I peeked the ends and they all follow each other up straight, so it must be indeed a patch cable. I thought I used that cable before for a direct link, but I'm not sure.

I'll try to find a real crossover cable soon, and let you know what's the result.

Later,

marco2136

[marco2136]

Hi guys,

I am able to detect the cRIO device now under Remote Systems. Instead of using a direct link between the cRIO and the Laptop, I branched them seperately to the same subnet, each with a straight ethernet cable.

However, after reformatting the cRIO's disc and reinstalling the software with the new NI-RIO 4.0.0 driver, minimal (no addons), I still am not able to deploy it in a project. When I right-click 'connect' in the project it says 'Real-Time version on cRIO and host are different, unable to connect to cRIO'.

How come those Real-Time versions are not the same?

I just did a complete reinstall on both machines with the latest LabVIEW software.

In attachement you can see the software installed on both machines.

[marco2136]

I figured it out, the Real-Time versions were not the same because I installed the minimal version of NI-RIO on the cRIO, which contains the older version of LV Real-Time.

So thanks fot you guys help, problem solved!

[A_Person]

Hi Marco:

Glad you got your cRIO working in LabVIEW.  I just wanted to clarify one thing from your post.  The version of LabVIEW Real-Time is not dependent on the version of NI-RIO or the Recommended Software Set (e.g. minimal or with Scan Engine Support) you are installing; they need to be compatible with each other but are otherwise separate.  When you look at the Real-Time Software Wizard you should see the versions of NI-RIO that you have installed underneath compatible versions of LabVIEW Real-Time that are installed on the machine.

For example, given the system shown in this image, I have NI-RIO 4.0 installed on my host machine along with LabVIEW Real-Time 2011 and 2010 SP1.  I can choose which version of LabVIEW Real-Time to install on the target by selecting the appropriate RSS.  Whichever version I choose, I need to make sure the host PC I'm using to connect to the cRIO has the same version of LabVIEW Real-Time and NI-RIO installed.

I know you got your setup working, I just wanted to make sure this is clear for anyone else who runs across this thread with the same problem.

[RagMan]

Andrew_E, thanks for posting this.

I had the same problem when I tried to connect by laptop to a cRIO 9012 controller in a 9104 Chassis.

Only the 9012 controller appeared in MAX but the 9104 Chassis was not detected.

I followed the advice of Andrew_E:

1) Put controller in Safe Mode and reboot

2) Format controller

3) Download software from laptop to controller (NI-RIO 12.1)

4) Reboot in Normal Mode.

Now MAX is detecting Chassis! Also able to detect modules from LabVIEW FPGA project.

Sincerely

Sundaram Raghuraman