|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
||||
|
||||
|
Re: Motors not working with jaguars
The document entitled "Getting Started with your 2012 Control System" located here goes step by step on configuring your Control System.
I assume you are somewhere on page 25 but you should go through this document and verify every step has been performed. Also, while you can use one of the Example Projects (on the Labview Splash Screen click Support and then click "Find FRC Examples" the Default Project has code in it already to control a simple drive-train, to help new teams get started. Which this document references. |
|
#17
|
|||
|
|||
|
Re: Motors not working with jaguars
Problem has been fixed. We forgot to put the jumper on the Analog breakout. Everything else was connected properly.
|
|
#18
|
||||
|
||||
|
Re: Motors not working with jaguars
Erm, that problem would have no effect on Jaguar communication barring some ridiculous short through the breakout. The jumper allows you to see your battery readout accurately, not regulate speed controller signals.
|
|
#19
|
||||
|
||||
|
Re: Motors not working with jaguars
Analog breakout? That has nothing to do with the jaguars. If you are talking about the servo jumpers on the DSC, than there is still something wrong, you shouldn't need those. The only possible thing I can think of that would make this solution make sense would be the new CRIO image disabling all outputs when it can't read battery voltage.
|
|
#20
|
||||
|
||||
|
Re: Motors not working with jaguars
The crimp coming from the cim to the jag seems to be coming out via your picture
|
|
#21
|
|||
|
|||
|
Re: Motors not working with jaguars
From your question, you do not state you tested it with victors, so I'm going to assume "no". If your useing your shiny new ribbon cable, try something else. Thats broken. You can fix it with these instructions, but they are easy to break even more.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|