Compressor running in disabled mode

[Alan Anderson]

Originally Posted by Tom Bottiglieri

Also, our robot drove in disabled mode at the suffield scrimmage.

That's a hardware problem. First suspects are the Digital Sidecar or the 37-pin cable connecting it to the cRIO Digital I/O module in slot 4. Less likely would be the module itself, or the DB-15 connector it plugs into on the cRIO.

[RyanN]

Originally Posted by Alan Anderson

That's a hardware problem. First suspects are the Digital Sidecar or the 37-pin cable connecting it to the cRIO Digital I/O module in slot 4. Less likely would be the module itself, or the DB-15 connector it plugs into on the cRIO.

The sidecars are really finicky, aren't they? We blew out one of our DIO ports yesterday for no good reason at all. We had a standard limit switch connected between Negative and Signal. It returned a false at all times and caused a lot of panicking right before our unveiling. Luckily, we tried the port right next to it (DIO9) and reconfigured the programming for DIO9, and it now works . We're thinking of just taking out the programming for the limit switch altogether as it's not really needed.

So it wasn't electrical, and it wasn't programming.

[Alan Anderson]

Originally Posted by RyanN

...We blew out one of our DIO ports yesterday for no good reason at all...

So it wasn't electrical, and it wasn't programming.

Whenever I've seen a Digital Sidecar go flaky, it has always been traceable to one of two things. Either something put battery voltage on one of the pins, or there was metallic debris present.

Debris is almost always from careless drilling or filing. In both of the cases I saw where it was an accidental connection to battery, the root cause was someone working on the robot structure and letting wires flop around at random. So you're right, it wasn't electrical, and it wasn't programming. It was mechanical. Do we have a new scapegoat?

[RyanN]

Originally Posted by Alan Anderson

Whenever I've seen a Digital Sidecar go flaky, it has always been traceable to one of two things. Either something put battery voltage on one of the pins, or there was metallic debris present.

Debris is almost always from careless drilling or filing. In both of the cases I saw where it was an accidental connection to battery, the root cause was someone working on the robot structure and letting wires flop around at random. So you're right, it wasn't electrical, and it wasn't programming. It was mechanical. Do we have a new scapegoat?

Haha... sounds like it. We'll have to clean it out really well before we put it into the playing field.

[krudeboy51]

the problem is that for some reason the orange light that needs to go on the robot, when it is not lighting up when the robot is disabled or enabled, the compressor does not work

[billbo911]

Oh man, I wish ours would run in disabled mode. If it did, we wouldn't have to try to find the one tiny leak in our complex tubing system.