Jaguars Slow Yellow Blink - Possible Control System Issue

[Mark McLeod]

It goes against my grain to say this but that's a software problem not a hardware problem.
(Never trust a DS Rev from October 39, 2008)

It probably comes down to what what was running in the cRIO at what time.

(RSL: solid, jaguar: blink) I'd say that at first what was running on the cRIO code didn't properly enable the PWM outputs you had the Jaguars hooked to.

(RSL: blink, DS: No code) Second, the code eventually failed to maintain the watchdog, or just plain ended execution.

Everything fine and working, the startup code seems to be fine, but you may have a timing condition that leaves a window for the Watchdog to fail and PWMs to fail to initialize.
Are you running parallel processes as in independent LabVIEW loops that could cause synchronization issues where something can get used before it's been properly initialized?

[MikeDubreuil]

Originally Posted by Mark McLeod

It goes against my grain to say this but that's a software problem not a hardware problem.
(Never trust a DS Rev from October 39, 2008)
...
Everything fine and working, the startup code seems to be fine, but you may have a timing condition that leaves a window for the Watchdog to fail and PWMs to fail to initialize.
Are you running parallel processes as in independent LabVIEW loops that could cause synchronization issues where something can get used before it's been properly initialized?

HaHa, thanks. The DS rev is 2008-10-29a.

The part that it might be a software problem also concerns me... I haven't modified the default code very much. I made a "Basic Robot" project in LabVIEW and changed the Arcade Drive in TeleOp to Tank Drive. I've also set the autonomous conditional to allow it to run.That's it. Here is a link to my code if anyone is interested.

[MikeDubreuil]

I have started a thread on the FIRST forum to get additional support.