Sidecar pwm ports 5 and up aren't responding

[Dragonbots]

I really need help on this, im using labview to program our robot
Apparently when i download the code to contol the motors that are connected to PMW ports 5 and 6, they dont respond. When in the driver station, it gives me the error of it being invalid, i dont know how to fix this problem, any help and or advice will be really appreciated.

[DavisC]

mind sharing a snippet of your begin.vi and teleop.vi?

[Dragonbots]

sorry but the laptop i program with isn't this one

[EricH]

Try taking a screenshot (or a photo of the screen that shows the blocks and connections clearly), and transferring that to the computer you're posting on.

[Dragonbots]

Although, i used the defualt robot main vi. given in labview and insted of PWM 1 and 2 to be use to move the motors, i switched to 5 and 6 and it wouldnt respond, its the default code with nothing changed.

[DavisC]

What wire are you using for the connection from cRIO - DSC? (if it is the ribbon, make sure it is properly assembled, or try a cable you know works).

Also, do the victors/jaguars have a solid light? or flashing? or any?

Are the 3 lights on the DSC lit green too?

And is the module in the proper slot of the cRIO (can open Imaging Tool and make sure the one labled 9403 is green).

[Michael Corsetto]

Originally Posted by DavisC

Are the 3 lights on the DSC lit green too?

We had a similar problem with "higher up" pwm ports (5 and higher) weren't responding. The problem was from lack of 12 volt power to the DSC. Check to make sure it's getting 12 volt power from the PDB to the DSC. Then all three lights should light up and the DSC should function properly. At least this is what fixed the problem for us. (Just fyi, without 12 volt power, only the middle light on the DSC lights up.)

-Mike

[EricH]

Originally Posted by DavisC

What wire are you using for the connection from cRIO - DSC? (if it is the ribbon, make sure it is properly assembled, or try a cable you know works).

[snip]
And is the module in the proper slot of the cRIO (can open Imaging Tool and make sure the one labled 9403 is green).

I can attest that they're using a KOP cable, reassembled per the instructions, and the last time I checked, their cRIO modules were in the right places.

They've also been able to run on port 1.

[Dragonbots]

also, when i do download the code to run ports 5 and 6, it gives error code
-44061 and that the code is running too slow. any help on how to fix this.

[EricH]

Light status: all green on DSC; Jags 1-4 good.

[Dragonbots]

Yes, thats our status so far, i did disabled our safety config VI's and i dot get the error any longer, but the motors still dont respond

[DavisC]

when you enable the DS, do the Jaguar/Victor lights turn solid (if not, try rotating the PWM wire around, if still does not work then the code isn't properly getting to the Motor Controllers).

[slijin]

http://www.chiefdelphi.com/forums/sh...72&postcount=3
http://www.chiefdelphi.com/forums/sh...49&postcount=2
http://www.chiefdelphi.com/forums/sh...29&postcount=3

[EricH]

Originally Posted by DavisC

when you enable the DS, do the Jaguar/Victor lights turn solid (if not, try rotating the PWM wire around, if still does not work then the code isn't properly getting to the Motor Controllers).

I think we've established that it probably isn't electrical. I got them on the flipped PWM a couple weeks back, when we were trying to get a motor running from PWM 1. They should remember that one...

It's something in code, I'm reasonably certain--but in that case, why isn't anything showing up on anything higher than Port 4 on the Sidecar?

In other words: PWM 1, working. PWM 2, working. PWM 3, working. PWM 4, working. PWM 5 or higher, not working. Using the default code and switching say PWM 1 to PWM 5 doesn't help (though where the switch was made, I don't know).

[DavisC]

I would attempt changing only the PWM back to 1 in the code (and the DSC). And if it works then I guess you have a broken DSC; but if it does not work then it leaves the potential for something else to be the problem (including the rest of the code).