View Single Post
  #4   Spotlight this post!  
Unread 12-12-2008, 13:21
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,846
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: No connection through Ethernet jacks on DS

Well, you can never go back to testing the OTB, so updating the cRIO will at least get you back to where you can debug the original Jaguar problem.

With the cRIO updated you'll get an additional status light on the Digital Sidecar to help tell you what's happening. A fast blink means no communication, a slow blink means it's in Disabled mode, and a solid light means it's enabled in either Teleop or Auto modes.

One reason the Jaguars will blink is if they aren't connected to an activated PWM output. With the default code you're now downloading I think just pwms 1&2 on the first cRIO digital module are enabled. I was with a team last night where a third party must have moved the DB37 cable to the second module and no one had noticed. As a result their Jaguars were blinking too.

There are lots of combinations that will prevent the code from operating as advertised (including failed hardware), so work your way through triple checks without introducing new complications.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle
Reply With Quote