Too many PWM's shorting out power?
 

First of all, this could apply to programming, motors, or electrical. I'm a programmer, so i'm going to post this here. If it needs to move somewhere else, someone in authority please do so.

I am programming in this year's LabVIEW.

Okay. We have been putting together a test robot to propel the basketballs into the hoops. We have 4 Jag's running (Drive) and 1 Victor running (Shooter).

All of the Jag's are put into the Digital Sidecar PWM slots 1, 2, 3, and 4.

The Victor is put into PWM slot 5.

When i disable the Victor, and run our Drive code, it runs just fine. No problems, no tinks, nothing. But, when we enable the Victor, and disable the drive code, nothing happens. Absolutely nothing. Could this be something wrong with the sidecar or something wrong with the Victor? All of the code is fine, all of the RefNum's are exactly the same.

Thanks, for any help.
Team Fusion 364

Re: Too many PWM's shorting out power?
 

if you plug the victor in to the PWM where a Jag was, does it enable with the drive code?

What do your LEDs do?

Is the victor response the same with and without a motor connected?

if the victor is not in the system, and you enable the drive and shooter code, does the drive still work?

Are your loops looping?

Re: Too many PWM's shorting out power?
 

When you say "disable the Victor", what do you mean?

Since you're asking about programming, it would help greatly if we could see your code. Show us at least the relevant sections of Begin and Teleop.

Re: Too many PWM's shorting out power?
 

Is your digital sidecar powered by wires coming from the PD board? ie, are the BAT, 5V, and 6V LEDs on? I've heard that could make one or two PWMs work but not all of them. That doesn't theoretically make much sense, since the sidecar circuitry is mostly pass through for PWM, but hey.

Re: Too many PWM's shorting out power?
 

Actually, the PWM signals are buffered on the DSC. It does make sense :)

Re: Too many PWM's shorting out power?
 

Disabling the Victor in the code.
I will post a picture later today, around 5 CST.

@WizendEE
Yes, the 5v and 6v lights are on.

Re: Too many PWM's shorting out power?
 

Troubleshooting information and Ideas:

Do you have your Victor PWM cable plugged in the correct direction?

Does enabling both do anything different?

Does plugging a Jaguar into the victor's cable work? Does plugging the victor into a Jaguars cable work?

Does changing the PWM port to say, 8 make it work?

What the problem sounds like is a hardware problem and not a software problem.

Re: Too many PWM's shorting out power?
 

If the BATT LED isn't also on, that supports the idea that you might not be getting power to the Digital Sidecar properly.

Re: Too many PWM's shorting out power?
 

The reason it works is because the DS leeches power from the cRIO, which is generally enough to run a few of the outputs, but not all.

Re: Too many PWM's shorting out power?
 

A side note: Remember that you must configure your code to use either a Jaguar or a Victor (for each motor instance). Jaguar uses the full range of the Servo PWM signal coming out of the cRIO. If your code is configured for a Victor but you really have a Jaguar hooked up, the Jaguar will not swing to full forward or full reverse.

Re: Too many PWM's shorting out power?
 

The problem is resolved.
Most of the problem was wiring, and some was programming.
We had the code using a Victor, which is what we were using. Thanks.

Re: Too many PWM's shorting out power?
 

Could you specify the solution you found? We have a Crio that will only do 2 motors controlled at the same time and are utterly stumped.

Re: Too many PWM's shorting out power?
 

Our cRIO was plugged into the power supply for a camera, so it wasn't getting enough power.
What are you programming in?

Re: Too many PWM's shorting out power?
 

We are having the same problem.

When we try to control more than 2 motors with the PWMs, the system starts to have problem.

Scenario 1
With the Axis camera, when running the 2 step motor, one of them starts to skip. Adding a third motor, both of step motors jitters.

Scenario 2
Using 2 jags and 1 victor, one jag skips every few seconds.

So what could be the problem? Power?

Thanks for helping

Re: Too many PWM's shorting out power?
 

The same symptoms suggest the same fix: make sure you are properly supplying 12 volts to the Digital Sidecar from a 20 amp breaker on the Power Distribution Board.

Re: Too many PWM's shorting out power?
 

To add to Alan's response, check to make sure that the frame of the Axis camera is isolated from the robot's, as the Axis camera is grounded to its frame.

Re: Too many PWM's shorting out power?
 

Here is a video I made yesterday during the testing.

It's in french but I wrote in a previous post what is happening.


Youtube video here

As you can see, it jitters even when not running.

Here is a screen shot of our begin.vi


Here is the teleop code


Thanks for helping

Re: Too many PWM's shorting out power?
 

el_pablo:

When you said "step motor" before, did you mean "servo"?

You're defining the camX and camY servos, but you never command them to move.

The nouveauMotor device reference is not defined in Begin. You should be seeing an error message on the Driver Station telling you about that.

I can't see YouTube videos from where I am, but I'm going to guess that you haven't installed the servo power jumpers next to the PWM pins on the Digital Sidecar for the camera servos. If they are indeed being powered, then a "twitch" is usually an indication that they're not getting a PWM signal, and are just picking up noise on the wires.

Re: Too many PWM's shorting out power?
 

Sorry my mistake, they are servos not stepmotors.

The diagrams show the second scenario which includes 2 jags + 1 victor and no servo. Althought they are declared we don't use them in this test case.

Concerning the servos, the power jumpers are installed.

We started the project using the default template. Should I delete a few things before coding?

Thank you

Re: Too many PWM's shorting out power?
 

Just figured out that in the begin.vi there were some "junk" declaration out of the screen in which some PWMs were in conflict...

I hope this is source of the problem.