Quote:
Originally Posted by jhellr13
First off, do you have the right pwm cable connected, and connected in the right way? Is your joystick code correct as well? Are your jaguars calibrated? I would assume so. I remember having a problem similar to this, this past season. We killed one jaguar because we forgot to calibrate, so one jaguar killed another. I remember we also played around with what jaguar got what motor. If you try switching around the pwm cables to different jaguars, that can possibly work.
The last thing i can think of in LabVIEW, would be to see what the motor output is. I don't really remember how to do it as the programming computer is not with me, but i think you right click a wire in the code, and something is an option that allows you to see the number/output of something like a jaguar or the speed applied when the joystick is pushed. I think you would have to put it on the wire that is connected from motor to set motor in the teleop code. Not exactly sure as I only learned how to do that at the competition when i had a programming alumni present to help me out.
Let me know how things go
|
Let me try to address the things you've brought up one by one (I'm trying to cross potential problems off of my list):
-I have verified the wiring from the cRIO to the Digital Sidecar and through the PWMs to the Jaguar.
-What do you mean by calibrating Jaguars? I thought they were set to go out of the box.
-Frankly, I doubt switching around PWMs should make any difference. All the Jaguars are the same, right? Or at least they should be.
-I haven't "probed" - that's the word you are looking for - the output wire to the SetOutput.vi while the robot's been running. However, looking at my code, I am most definitely not sending "0s", as my team would say, to the Jaguar.
Because previous code (our competition 2011 code) used that Jaguar as expected, I am guessing the problem has to do with how I am assigning PWM channels. That is why I attached the image of my Begin.vi.