PI controller of speedcontroller drive

aand74

Member
Join Date
Dec 2005
Location
Deinze
Posts
131
What are the effects of the cycle time the PI control loop of the speedcontroller from a drive is executed?
If I go to faster cycle times with the same PI settings, what will be the behavior of the load? If I go to faster cycle times, is it advisible to change the PI-settings of the speed controller, and in what sense?
 
If the PI controller was written correctly there should be no effect of increasing the scan rate. The Ki gain should be multiplied by the scan time so as the scan time decreases the effect of the integrator gain is less for each scan but since there are more scans per second it works out the same.

This worry about scan time and the integrator is due to poorly written PID controllers.
 
I have done some tests on a drive, and indeed as it should be the scan rate does not influence the reaction of integrator.
But what could be said about the proportional part?
If I have shorter scan times (f.i. 500µs to 125µs), with same proportional settings, will the dynamic be the same? Do shorter scan times allow higher proportional values while overshoot at a step response is not worse then in the original setting with longer scan times?
All these questions relate to an upgrade of drives where the old drives had 400µs cycle of the speed controller and the new ones 125µs.
We know we should tune the new drives to the best possible values, but we should also want to have some comparison with the old drives (which are not present anymore, and of which we have no traces, only parameter settings).
 
But what could be said about the proportional part?
It doesn't change the proportional gain.

If I have shorter scan times (f.i. 500µs to 125µs), with same proportional settings, will the dynamic be the same?
The scan time should be much faster than the frequency of motion. Once the scan time is much faster than the frequency of motion then scanning faster doesn't do much. The frequency of motion can be found by doing a FFT on the motion profile. A simple way is to add the time it takes to accelerate and decelerate together and divide this by 20.

Do shorter scan times allow higher proportional values while overshoot at a step response is not worse then in the original setting with longer scan times?
Yes, but there is a point of diminishing returns and the difference in the P and I gains will be small.

All these questions relate to an upgrade of drives where the old drives had 400µs cycle of the speed controller and the new ones 125µs.
You should be able to copy the gains from one to another if the two drives use the same units for gains. 125 micro seconds is more than fast enough conveyor work.

We know we should tune the new drives to the best possible values, but we should also want to have some comparison with the old drives (which are not present anymore, and of which we have no traces, only parameter settings).
You are in luck. I just made a YouTube video about PI control for a velocity system. I show how to CALCULATE gains to get the response you want but this assumes you know the open loop gain and time constant or bandwidth.
https://www.youtube.com/watch?v=E6tH01GGxDg
 

Similar Topics

Hello! If someone can help me with the following problem. I can't change the phone number. Do I really need the interface (AL-232CAB - Programming...
Replies
0
Views
51
I have Woodward Controller EASYGEN-3500XT and Phoenixcontact make IO CAN-CUPLER part no: 2702230, Analog Input card: 2861412, Analog Output Card ...
Replies
0
Views
42
Hello I have a s7-1200 and I would like to read the tags present in this controller with my controllogix controller. The two controllers don't use...
Replies
5
Views
168
Everything was working fine, but suddenly CPU went into error mode, and the ERR and TER LEDs lit up. Now I can't download or connect with the PLC...
Replies
0
Views
48
I am running CCW 13 trying to upload to a micro 820 vers.12 I get an output message OPC server is unable to load project controller. Please help!
Replies
5
Views
256
Back
Top Bottom