PWM problems

[benjaminDVBD]

Our jaguar isn't getting output from the sidecard.
we have 4, 2 using PWM and 2 using CAN.
the 2 CAN are working fine (even though they have no code. the light is switched on and isn't blinking)
the other 2 PWM jaguars aren't working. they have code, and yet their light is blinking non stop and are not working (even in the slightest).

we have no idea why this is happening.
we checked the code (including past versions) and it isn;t working.
we checked the cables with the FLUKE and there seems to be no problem.
any ideas (please?)

[MagiChau]

Did you update the firmware on the jaguars? That may be one reason.

[ratdude747]

Originally Posted by MagiChau

Did you update the firmware on the jaguars? That may be one reason.

yes. if you updated the FW on the pwm ones, they will not as they must get a heartbeat signal from the crio over CAN.

if thats the issue, you might have to run all you jags on CAN... not very hard to fix in code and pretty easy to accomplish if you already have CAN elsewhere...

[dyanoshak]

Originally Posted by ratdude747

yes. if you updated the FW on the pwm ones, they will not as they must get a heartbeat signal from the crio over CAN.

if thats the issue, you might have to run all you jags on CAN... not very hard to fix in code and pretty easy to accomplish if you already have CAN elsewhere...

That's not correct. Jaguars with updated firmware will still operate with PWM.

I would check to make sure the PWM cables are plugged into the Jaguar and the digital sidecar in the correct orientation.

-David

[DarrinMunter]

We have had the PWM outputs on the side car be bad, with the 2009 robot.
Try a different output location.
The programmers should be able to change that easily.

[XXShadowXX]

Do you also have issues with cRIO connectivity?

2604 had a similar problem to what you are describing. Our drive system is/was 4 wheel CAN mech drive. Then our 'arm' is powered via 4 pwm jags.

The issue we repeatedly had was
"Unable to allocate PWM channel" (as seen in the driver station error window/output text box)

If you have both of these issues what you may want to look at if your labview install, our happened to be corrupted thus our 'compiled' code wasn't actually doing what we programmed it to do. This being the problem all older revisions proved unworkable. (It maybe possible with C++ or Java, I don't know)