Here's a first for me. I've got a wild speed controller. It runs in reverse if I run both driver Jaguars in reverse. You'd think it was a programming error, but the program wasn't changed (and it worked yesterday), and it doesn't matter if I plug the PWM cable into any open PWM output on the Sidecar. In other words, if it's on PWM 3, it runs wild when the Jaguars are in reverse. If I plug it in PWM4, it runs wild when the Jaguars in reverse. As long as that PWM is open in the program and that Speed Controller is plugged into it, it runs wild when the drive Jaguars are in reverse.
To make it worse, an hour earlier, it was a different speed controller behaving similarly (it would run in reverse if either one of the drive Jaguars was running in reverse), so I yanked it and replaced it. Everything seemed to be going fine until at the time we all had to go, another Speed Controller started behaving the same.
Differences? We swapped/put the entire cRIO, sidecar, Jaguars onto the robot from the mock up. We've run the mockup with no issues for several weeks now. We no longer have all the cards in as we pulled everything that wasn't in the program. We don't need to keep all the cards in (like the Analog Card 1) do we?
More symptoms:
The run light isn't turning on even though we are seeing the LED blink on the Sidecar where it's plugged in.
The Speed Controller problems came after the cRIO disabled itself. It seemed to disable going into reverse with the drive Jaguars.
I suspect a short somewhere in the new wiring, but I just can't find anything. Are there crazy issues about this cRIO that I just don't know about?
As a 10 year veteran and the Controls Lead, and a career automation engineer, I can't believe how stumped I am.
Regards,
Fred Agnir
Team 126 Gael Force


Reply With Quote

