|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Resilience of Motors using PID
Quote:
Code:
Data from FRC motor data table "MotorInfo4.1.pdf" as of 1/18/2012 12:30pm am-0914 (PG71) MotorInfo4.1.pdf [spec Option #3] @ 12.00 volts: @ stall: oz-in Nm rpm rpm% amps watts out watts in eff% 3101.0 21.898 0 0.0 22.0 0.0 264.0 0.0 @ max power: oz-in Nm rpm rpm% amps watts out watts in eff% 1550.5 10.949 42 50.0 11.3 48.2 135.6 35.5 DensoL 262100-3040 @ 12.00 volts: @ stall: oz-in Nm rpm rpm% amps watts out watts in eff% 1501.1 10.600 0 0.0 21.0 0.0 252.0 0.0 @ max power: oz-in Nm rpm rpm% amps watts out watts in eff% 750.5 5.300 42 50.0 11.4 23.3 136.8 17.0 |
|
#2
|
||||
|
||||
|
Re: Resilience of Motors using PID
I tend to use the term similar lightly. A window motor should do the job though. Also, since there are left and right hand motors you could gang to of them together doubling the output. You may or may not have to account for the different power levels for left and right hands.
|
|
#3
|
||||
|
||||
|
Re: Resilience of Motors using PID
Quote:
|
|
#4
|
|||
|
|||
|
Re: Resilience of Motors using PID
You may want to consider using the Current Mode control of a CAN enabled Jaguar. This will create less waste heat in your motor, assuming you properly tune the PID parameters.
I'm using the parameters found here, please let me know if I'm looking at the wrong motor. You should expect to use about 6 amps to develop 6 Nm with this motor. It uses 22 Amps to generate 22.5 Nm at stall, so a rough pass is 6 Nm * ((22 A) / (22.5Nm)) = ~6Amps. The no-load current (which is really just another word "the sum of the parasitic torques in the system") is small enough that I'm willing to ignore it for the time being. With a "perfect" motor controller, you will apply a perfectly flat 6 amps. The motor's resistance is roughly half an ohm, so your best case is (6 A)^2 * .5 ohms = 18 Watts. Any imperfections in the motor controller will cause that current to oscillate a bit and become less efficient. For example, lets take one that applies 12 Amps half the time, and 0 amps the other half. Then our heating becomes (12 A) ^2 * .5 ohms * .5 duty = 36 Watts. Worst case scenario, we'd expect something approaching stall current: (22 A)^2 * .5 ohms * (6/22) duty cycle = 66 Watts. This is 3.6 times the heat output! The "flatness" of the current is a function of the ratio of the time constants of the motor and the motor controller. The faster the controller is, with respect to the motor, the flatter the current waveform. The flatter the current waveform, the more efficient the use of that current. I don't know what the time constant of this particular motor is, so I can not calculate where victors and jaguars fall on the continuum. However, the Jaguar's time constant is over a 100 times faster. Note that for this, I've assumed that the mechanical time constants are WAY slower than all of the electrical time constants. As long as you don't see any twitching, this is likely a safe assumption. |
|
#5
|
|||
|
|||
|
Re: Resilience of Motors using PID
Ether helpfully pointed out that the first sentence of my previous post makes a few too many leaps. The remainder of the post supports only that higher frequency motor controllers produce less waste heat. This in turn is based on the premise that torque is proportional the algebraic mean of current, but power is proportional to the geometric mean.
The comment on using Current Mode was unsupported, so let me take a whack at that now. If a PID is not well tuned, it can oscillate. These oscillations can create efficiency losses just like having a low frequency motor controller can. A pathologically mis-tuned loop can have efficiency as bad as a Victor. Using CAN allows the Jaguar to do the PID itself, and runs at 1kHz. Running the PID on the cRIO introduces some communication time, so the loop runs a bit slower. Using current mode removes several variables from the equations, and makes the effective loop quicker: The loop isn't waiting on anything mechanical, and can therefore respond on an electrical time line. It is quite possible to achieve the same stability with other control modes, I just find it easier in current mode generally. For your application, CAN Position Mode might be easiest. |
|
#6
|
||||
|
||||
|
Re: Resilience of Motors using PID
As usual, Ether is wise and full of knowy goodness. Achieving "neutral buoyancy" through the use of surgical tubing, springs, spring steel, or some other deformation is a great way to assist your motors so that they act more effectively, more efficiently, and more robustly.
|
|
#7
|
|||
|
|||
|
Re: Resilience of Motors using PID
I would recommend taking the load off the motor using a mechanical device like others have said.
I'm not sure which locking pins they are talking about in the window motor, but I do know they utilize a worm "drive". You can read more about them on wikipedia (search worm drive), but if the window motor won't give you enough power to move the device using to hold your shooter(not hold it in place) then buy your own worm and worm gear(mcmaster,etc) and make your own worm drive with a more powerful motor. "Worm gear configurations in which the gear can not drive the worm are said to be self-locking. Whether a worm and gear will be self-locking depends on the lead angle, the pressure angle, and the coefficient of friction; however, it is approximately correct to say that a worm and gear will be self-locking if the tangent of the lead angle is less than the coefficient of friction." This is pretty much a super high gear ratio, but typically you will see self locking effects from a worm drive device meaning you DON'T have to provide a constant torque to hold your device in place. |
|
#8
|
||||
|
||||
|
Re: Resilience of Motors using PID
Quote:
More on locking pins: http://wiki.team1640.com/index.php?t...r_Locking_Pins Removing the pins is legal, but for a non-backdriving design, it is essential to leave them in. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|