cRIO does not respond to digital inputs

[JDWorden]

We have an 8-slot FRC cRIO which we successfully used last year.   It seems to be fine this year except that the 9403 module does not respond to changes on the DIO inputs.  The problem first showed up after we moved the modules to slots 1 through 3 and reimaged the cRIO.  the mudules are slotted as per the table on page 12 of "Getting Started ...".  We discovered that the comperssor relay was not shutting down the compressor when the pressure switch changed state.  The pressure switch is attached to Digital Module 1, DIO Channel 1.  We use LabView as our development environment.  The problem occurs even with the 2012 initial robot control package before we have made any changes.

All the cRIO modules scan green when using the Imager.  We have wrung out all the wiring, checked that the pressure switch is operating correctly, and swapped out the 9403 module and Digital Sidecar, but the problem persists.  Boolean indicators inserted in Begin.vi confirm that the digital inputs are not sensed.  The problem has persisted as we have added inputs on other DIO channels.

We would greatly appreaciate any ideas.

Thanks in advance,

John Worden

Team 3759

[DAQjr]

Make sure that you are using a DB37 cable between the 9403 and the sidecar that is not swapped.  The ones that came in the kit were manufactured incorrectly.

[JDWorden]

DAQjr

Thanks.  I hadn't thought about the cable.

We are using the same cable we used last year.  As a matter of fact, we are using last year's bot in what used to be its working configuration.  I'll try using the cable delivered in this year's kit

If that doesn't work, would you sugggest a trip to Radio Shack?

JW

[DAQjr]

I would expect the cable in the kit to not work unless you have followed the rework instructions.

[DAQjr]

You should also check your code.  Are you reusing code from last year?  Are you perhaps selecting the wrong module?  The module specification is changed this year.  You no longer specify slot number, you now specify first or second module of a given type (such as digital).

Have you tried using an example to test the hardware?

Are you getting any errors on the Driver Station about the digital lines?

[JDWorden]

All good ideas.  Thanks.

I'll buy a new DB37 cable in case last year's has been damaged somehow.

We recreated the Begin.vi code from last year.  We did not paste a copy from the old program.

We are selecting Module 1.  Sorry about the incorrect reference to the slot.  I believe we have the addressing correct since the PWM channels work.  We can drive the bot.

I'll check for Driver Station errors.

JW

[sciencewhiz · Accepted solution]

If you are trying to read the DIO from the dashboard, be aware that there is a bug that causes the DIO not to update on the dashboard. See http://firstforge.wpi.edu/sf/go/artf1439

[JDWorden]

Thanks to all who replied.

As it turns out, the bug mentioned by sciencewhiz was part of the problem.

In addition, however, we had missed a change in the WPI compressor code delivered with the 2012 system.  The code that worked for us last year was not incorrect given the changes in the WPI.  With help from Joe Ross of BeachBots we programmed the compressor using the new vis.

These two changes resolved all of our issues.

[MarkGryzwa3206]

Can you fill me in on your reference to the changes in the WPI?  We cannot get our compressor to run either using the same coding convention as in the past.