Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Electrical (http://www.chiefdelphi.com/forums/forumdisplay.php?f=53)
-   -   [HELP] Digital Sidecar troubles (http://www.chiefdelphi.com/forums/showthread.php?t=109685)

Al Skierkiewicz 30-11-2012 15:25

Re: [HELP] Digital Sidecar troubles
 
Cal,
Measure from each PWM pin to PD and then check the Crio frame to PD and robot frame. Then check the output of each speed controller. We have had CIMs short to case after they have been stressed in continual demo mode. You know that something on the robot is taking out the DSC, you just have to find it.

EricVanWyk 30-11-2012 15:37

Re: [HELP] Digital Sidecar troubles
 
Quote:

Originally Posted by Mark McLeod (Post 1197508)
Then it's probably an intermittent short that only occurs when a mechanism is in or passes through a particular position. Those are fun to trace down.

Quote:

Originally Posted by CalTran (Post 1197512)
Um...how might we go about tracing that to see if that's the potential fault? And would this be an intermittent short across the PWMs or the motor controllers themselves?

One of my mentors once told me that RF is the easiest electrical engineering field there is, as long as you do it perfectly right the first time and don't ever mess up. Once you have an error in an RF design, put on the robes and start sacrificing chickens.

Tracking down errors like this is much harder than avoiding them in the first place. Use this as a lesson in enforcing clean wiring.

Golto 30-11-2012 15:54

Re: [HELP] Digital Sidecar troubles
 
I remember in the first year or so, our cRIO was killing the D-I/O modules. We went through a few. Check the module in another port if possible, or see if another area team could lend you a D-I/O module to check with.

mikets 30-11-2012 16:54

Re: [HELP] Digital Sidecar troubles
 
Quote:

Originally Posted by Golto (Post 1197537)
I remember in the first year or so, our cRIO was killing the D-I/O modules. We went through a few. Check the module in another port if possible, or see if another area team could lend you a D-I/O module to check with.

If your cRIO was killing the D-I/O module, I am not sure it's a good idea to borrow another team's D-I/O module.:) However, checking your D-I/O module on a known good cRIO may be a better idea.

CalTran 30-11-2012 18:44

Re: [HELP] Digital Sidecar troubles
 
Quote:

Originally Posted by Ether (Post 1197520)
Could it be an RS-775 case short?

Unfortunately, we don't have any RS-775's on the robot. Though, given their nasty tendency for shorts, it wouldn't surprise me if one in our closet was causing problems all the way from there ::rolleyes::

We were having some problems with a motor at CowTown. I'll have to add that to my check list Monday. There wouldn't happen to be any way to fix a sidecar once it's burned, is there?

Al Skierkiewicz 30-11-2012 21:03

Re: [HELP] Digital Sidecar troubles
 
Cal,
It depends...At least one of the photos above shows significant board charring. I would say that one is not repairable. If you have experience or tools to remove surface mount components, then yes you can replace the damaged FET and other parts. This is not for the faint of heart.

Since you have gone through so much already without finding anything significant, there is an off chance that one of the controllers has shorted power to the PWM. This is very unlikely but still possible. Another possibility, though highly unlikely, is a damaged Spike. Suspect everything on the robot, I have seen compressors and all types of motors short to case. If you had trouble with a motor earlier, than start there first.
Here's a thought, remove only the power from the DSC, and power the robot. See if you measure any voltage at the power input to the DSC. If you do, start removing PWM cables from the DSC and see if the voltage goes away.
You are not trying to power LEDs from a digital output are you? Are you using digital inputs/outputs for other purposes or devices?

CalTran 30-11-2012 21:56

Re: [HELP] Digital Sidecar troubles
 
Quote:

Originally Posted by Al Skierkiewicz (Post 1197662)
Cal,
It depends...At least one of the photos above shows significant board charring. I would say that one is not repairable. If you have experience or tools to remove surface mount components, then yes you can replace the damaged FET and other parts. This is not for the faint of heart.

Darn. Guess we'll have to track down a new one.

Quote:

Another possibility, though highly unlikely, is a damaged Spike.
Suspect everything on the robot, I have seen compressors and all types of motors short to case. If you had trouble with a motor earlier, than start there first.
Not running any pneumatics nor Spikes, so I'll be checking motors and motor controllers.

[/quote]
Here's a thought, remove only the power from the DSC, and power the robot. See if you measure any voltage at the power input to the DSC. If you do, start removing PWM cables from the DSC and see if the voltage goes away.
You are not trying to power LEDs from a digital output are you? Are you using digital inputs/outputs for other purposes or devices?[/quote]
We don't have any DIOs on the robot. I'll take some pictures of the entire setup on Monday, but all we had were:
Drive Motors:
2 CIMs -> 1 Black Jaguar and 1 Victor-884 -> PWM-Y -> PWM port 1
2 CIMs ->1 Black Jaguar and 1 Victor-884 -> PWM-Y -> PWM port 2

Ball Acquisition:
2 Window Motors -> 2 Victor-884s -> PWM-Y -> PWM port 4

Shooter:
1 Banebot 550 (20:1) -> 1 Victor-884 -> PWM (straight) -> PWM port 6

2 Banebot 550 (5:1) -> 2 Victor-884 -> PWM-Y -> PWM port 8

The Sidecar, as stated, is hooked up to an 8 slot cRio using a DB37 cable.

Checked all the PWM cables today, they're all continuous, no breakage, and no shorting across strands. Not sure how I would check a motor controller for a short.


All times are GMT -5. The time now is 05:51.

Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi