Quote:
Originally Posted by jhersh
Bryce,
Can you describe exactly what happens? It's possible you found a bug, but we'll need you to do more experimentation to narrow it down...
-Joe
|
Joe,
I'll look for messages tonight and try to get back to you.
Quote:
Originally Posted by apalrd
If you have 4 jags and 1 vic, put the 4 jags on drive and the vic on position control. I would do that much much much faster than putting a drive motor on a jag and a drive motor on a vic. The software will probably thank you too.
What is the advantage of using the CanJaguar's position control? You have analog inputs on the cRio, and since programmable controllers in FRC (back in the day... 1997?) people have been writing simple code to control position.
|
apalrd,
Yes, you are correct about your description. We could set it up that way you specify with closed loop calculations being performed on the cRio itself. I started on SPAM 10 years ago and have seen the capability of even the old controllers (back in the PBasic days). But currently, our final assembly has a motor with quad encoder attached, hence the reason for trying this. I was using the Jag in position control mode because that is what the final configuration will be. Why write code for something that will not be used again? I will repeat myself again though...that is not the focus of my original post. The point is, however stupid it may be, that the RobotDrive class hoses another Jag (at least that appears to be what I'm seeing) when two different SpeedController inherited classes are passed to the RobotDrive class. We meet tonight and I will try to post a more detailed description.
- Bryce
P.S. It's really just a moot point because I have already replaced the Victor with a Jag in the box. I just thought I'd bring up some weird behavior that I witnessed.