View Single Post
  #2   Spotlight this post!  
Unread 25-01-2009, 23:51
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,731
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Jaguars Slow Yellow Blink - Possible Control System Issue

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?
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 25-01-2009 at 23:58.
Reply With Quote