Problem w/ cRIO sensing other NI modules across backplane

[kblack]

Problem Description :

We are a new team in the FIRST FRC 2010 competition. We have ordered

set of parts and built a drive base with the 2009 kit of parts. And are trying to bring up
the basic as-shipped Labview environment on the CRIO-FRC, and 2009 driver S/W and H/W
to give us a platform to come up to speed with all the H/W and S/W in anticipation of this January's competition.

We ordered and assembled all the bits and parts for the 2009 driver station, and a basic robot drive train.
After installing from the FIRST CD, and having also updated the driver station flash image, and updated the

labview / crio w/ the 3.0.a update zip file. We reimaged the CRIO, and We tried to run the Basic and Advanced robot apps.

The App Driver Station and the CRIO are communicating correctly. We can see Joystick data on the cRIO using Labview.

Likewise, the Dashboard App running on another PC reflects the same info sent back up from the cRIO.

But the PWMs just sit there and blink. And we get no voltages from any of the outputs on the Digital I/O module.

Debugging further, we believe there is something amiss w/ the "connection" between the cRIO CPU / backplane and the

modules. None of the NI modules appear in MAX, and we ran the tool found here:

http://zone.ni.com/devzone/cda/epd/p/id/1717

And just like MAX, it can't see any modules. And it gives the following error out:

==========================

Error code: -61141

==========================

Reference in nirviIntfOpen_cRIO-9074.vi->cri_cRIO-9074 Modules Data.vi->CRI Get cRIO Modules Info.vi->CRI Get cRIO System Info.vi->Detect cRIO Configuration (RT) Example.vi<append>

<b>FPGA activities:</b>

Reserved outside LabVIEW FPGA:  FRC_FPGA Chip-Object.

=====================

I've attached screen shots (and version txt) in case there's something useful there.

We're hoping the problem is some disconnect cause by some install mistake we made, but we're out of ideas.

Thanks

-Ken

[sciencewhiz]

I will defer to the NI engineers on whether the sensing of the cRIO modules is the root cause of the problem, but I don't think so.

Here are some other things you can look for:

Is the DS enabled or disabled? The outputs on the cRIO only worke when enabled. What mode is the DS in (telop or autonomous)? What does the battery voltage read on the DS?

Does the Digital Sidecar have power? What is the state of the RSL LED on the digital sidecar (see Digital Sidecar Status LED Meanings for details).

The control system manual has step by step instructions on how to hook everything up, and most importantly how to test everything one step at a time. While you won't be able to complete all the steps (there were tests to do before you imaged the controller), I would recommend that you read through the instructions, verify your setup, and see if you can start from the instructions where they match what you've already done. The control system manual can be obtained from http://www.usfirst.org/roboticsprograms/frc/content.aspx?id=14532