Skip to main content
Submitted by Bill Willems on Tue, 11/09/2004 - 16:43

I'm trying to tune a Bayside motor and I'm having some problems. My setup:

[list]

[*]DMC-1740
[/*]
[*]Bayside rotary motor with worm drive (A screw is attached to the shaft of the motor. The threads of this screw engage a gear attached to my load.)
[/*]
[*]Using Bayside iDrive amplifier
[/*]
[*]Load has a long/heavy arm on one side. This may not be a big issue because when I replace this off-center load with an on-center load I still get the same behavior.
[/*]
[*]Dual Loop (encoder on motor and encoder on load)[/*][/list]

I've tried playing with the different tuning methods in WSDK. All of them work well for the short moves but the motion is very "jumpy" on the longer moves. However, when it stops, it nails the position (I get 0 counts of position error). Looking at a continuous plot of torque I see a sine wave. The best amplitude I've been able to get ranges from +6 to -6. The frequency of this torque sine wave appears to have a direct correllation with speed (i.e. the lower the speed, the lower the frequency).

I have tried adjusting the tuning parameters in Galil as well as in the Bayside iDrive amplifier but I can't seem to get smooth motion. I am more familiar tweaking Galil than the iDrive so more work has gone into tweaking Galil.

Can anyone help?

Thanks!

Comments 2

Buz on 11/10/2004 - 13:26

Try turning off KI during the move and turning it back on when _BGn = 0 (n is your axis letter). I have a similar app where this technique gave the best performance.

Bill Willems on 11/10/2004 - 14:18

I've got it working! :D

It turns out that one of the parameters in the iDrive setup was incorrect. :rolleyes: The parameter in question is the Speed Set-Point Value at 10V (P31). That 10V is the Motor Command from Galil. When our Bayside rep was out here to help us setup, he left this parameter at 3000rpm which worked fine for our initial setup because we didn't have all of the parts to attach the heavy part of the load.

As I was going through the iDrive parameter list and comparing to what was actually set I found it. The motor has a maximum rpm of 5400. When I put 5400 in for this value and ran a General Tuning procedure through WSDK, the resultant motion was finally smooth.