![]() |
jaguar scaling factors
My team (3247) just got our bot driving today and we noticed a big problem. With four motors we are using 2 black jags and 2 grey jags. This seemed fine except for a problem where the scaling is not quite right! When driving foward, one side (black side I think) is way faster. As the programer for the team, I was told to fix it. I was thinking that maybe I should attempt to scale the joysticks. The problem with this is that my team also wants to use arcade drive. We used last years DS for testing but they think it will be easier to control with arcade.
My questions are:
Thanks in advance |
Re: jaguar scaling factors
Same issue for our team. Would love to hear the answer. The black jaguars output about 12.5V in full on, the grey/tan jaguars are about 10.5V. Quite a difference to balance.
|
Re: jaguar scaling factors
idk if this would help any but you could always try installing encoders onto each side of the drive train then using those output values and then scaling back each motors output.
|
Re: jaguar scaling factors
Quote:
You can certainly scale back the faster side permanently by multiplying the joystick input to just the Black side by a factor or by using encoder feedback and PID. |
Re: jaguar scaling factors
because these are the CIMple gearboxes from andymark, I don't think it would be advisable to mix controllers. I see ground gears for anyone who tries that...
The voltage data is very helpful, does anyone know if the speed is ramped in a linear fashion? If it is linear, then it would be some very simple math to make them even. |
Re: jaguar scaling factors
I would suggest using PID with encoders to get a closed-loop control.
There's nothing quite like feedback for repeatability and low-speed handling. |
Re: jaguar scaling factors
Can you suggest any good resources for creating PID algorithms? I am used to text based languages on OS/2 so any resources that are labview based would be nice.
|
Re: jaguar scaling factors
If you're using LabVIEW, the FRC version does include a PID toolkit. Note that the LabVIEW toolkit uses the Standard form rather than the Ideal form.
http://en.wikipedia.org/wiki/PID_con...ndard_PID_form Wikipedia has a good article on PID. |
Re: jaguar scaling factors
I read through the article posted and I am trying to make heads or tails of it. I do not understand how exactly a PID loop will allow me to synchronize the movements of the left and rights drivetrains so that the robot drives in a straight line. PID does however seem to be an excellent way of defining the movements during autonomous to place the ubertube.
More questions:
|
Re: jaguar scaling factors
Quote:
2. Yes, PID control on position is a good way to handle dead reckoning forward/back movements in autonomous. PID control on angle using a gyro is a good way to make dead reckoning turns. 3. Nope, not at all. |
Re: jaguar scaling factors
so do I use one PID VI for each input needed on the drive VI?
In my question about autonomous, would I want to use a setpoint VI. Lastly, does the PID VI need to be in a loop to work? Sorry for all the questions, but short and simple answers for APPLYING code are few and far between over at NI's site. |
Re: jaguar scaling factors
Have you tried calibrating the speed controllers?
|
Re: jaguar scaling factors
I have, but there is still a slight variance from straight on.
|
Re: jaguar scaling factors
Yes, yes, and yes.
I think a global variable would work wonderfully for transferring your setpoint from your autonomous code to your PID loops. Put the PID loops in Periodic Tasks so that they run all the time. |
Re: jaguar scaling factors
Should the PID Loop run with a delay or should it run at full speed?
|
| All times are GMT -5. The time now is 10:11. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi