|
|
|
 before you post, ask yourself: Is there a good reason to post this? - Jeff Waegelin [more] |
 |
|
|||||||
|
||||||||
 |
| Thread Tools | Rate Thread | Display Modes |
|
|
|
| before you post, ask yourself: Is there a good reason to post this? - Jeff Waegelin [more] |
|
|
|||||||
|
||||||||
|
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
CAN Drive implementation problems
We have implemented CAN Drive with Jags in Labview, and when we connected with the driver station it said the Robot had communication and it said there was code loaded on the robot but any joystick input wouldn't translate to the robot. Here's what the code looks like in (we're using mecanum drive BTW):
Begin.vi  Teleop.vi  We already reimaged the cRIO to use the CAN Serial thingy. We didn't wire the encoders on the jags yet, would that be why? 
|
|
#2
08-02-2014, 00:52
|
||||||
|
||||||
|
Re: CAN Drive implementation problems
Speed mode will not work without encoders on the jaguar. However, I would expect that the jaguars would go full speed, rather then not moving.
I don't believe that RobotDrive is designed to work with speed mode on the CAN Jaguars. I think it only works with %Vbus.
|
|
#3
08-02-2014, 00:55
|
||||
|
||||
|
Re: CAN Drive implementation problems
That would make sense.
Once we get the encoders all wired up I will give you an update. Thank you!
|
|
#4
08-02-2014, 00:55
|
|||||
|
|||||
|
Re: CAN Drive implementation problems
A closed-loop-control mode won't run if all the PID gains are zero.
|
|
#5
08-02-2014, 01:28
|
||||
|
||||
|
Re: CAN Drive implementation problems
Quote:
 That... would make a lot of sense. Would all three (p, i and d) need to have values or just one (ie just p)?
|
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Linear Mode
