View Single Post
  #2   Spotlight this post!  
Unread 17-02-2014, 14:57
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,855
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: cRio communication problems

Nobody touched the PWM cables since 9am?

It's pretty standard troubleshooting to follow the command trail:
  1. Is the Driver Station (DS) showing any errors?
  2. Is the DS Enabled?
  3. If using LabVIEW switch to Test mode on the DS and test a single controller using the Test controls.
  4. Check the three power status lights on the Power Distribution Panel.
  5. Check the three power status lights on the Digital Sidecar (DSC).
  6. Check the status lights on the cRIO (power and status, Ethernet port lights)
  7. Check the 37-pin cable connection that both ends are tight.
  8. Check the orientation of the PWM cables running from the DSC (black to the outside) to the motor controllers (black to the inside).
  9. Test the PWM output at the DSC with a digital multimeter.
  10. Test the motor controller end of the PWM cable with a multimeter.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle