List Of Possible Messages During Tuning - Siemens SIMATIC Manual

Pid temperature control
Hide thumbs Also See for SIMATIC:
Table of Contents

Advertisement

A.4

List of Possible Messages during Tuning

STATUS_H
0
10000
2xxxx
2xx2x
2x1xx
2x3xx
21xxx
22xxx
3xxxx
30002
30005
Note
If you stop the tuning in phase 1 or 2, STATUS_H is set to 0. STATUS_D,
however, continues to indicate the status of the last controller calculation.
The higher the value of STATUS_D, the higher the order of the controlled
process, the higher the ratio TU/TA and the softer the controller parameters.
STATUS_D
0
110
121
200
310
320
111, 122,
201, 311, 321
PID Temperature Control
A5E00125039-02
Description
Default or no new controller
parameters (yet).
Tuning completed and suitable
controller parameters found
Tuning completed and controller
parameters uncertain
Point of inflection not reached
(only with excitation by setpoint
step change)
Estimation error (TU < 3*CYCLE) Reduce CYCLE and repeat the
TU estimated too high
Estimation error N_PTN < 1
Estimation error N_PTN > 10
Tuning terminated in Phase 1
due to bad parameter settings:
Effective manip. var. difference <
5 %
The sampling times CYCLE and
CYCLE_P differ by more than 5%
of the measured values.
Description
No controller parameters were calculated
N_PTN <= 1.5 process type I fast
N_PTN > 1.5 process type I
N_PTN > 1.9 process type II (intermediate range)
N_PTN >= 2.1 process type III fast
N_PTN > 2.6 process type III
Parameters were corrected during Phase 7.
Remedy
If the controller is oscillating, weaken
the controller parameters and repeat
the attempt with a lower manipulated
variable difference TUN_DLMN.
attempt
Special case, purely PT1 process: Do
not repeat, possibly weaken controller
parameters.
Repeat the attempt under better
conditions
Repeat the attempt under better
conditions
Repeat the attempt under better
conditions
Correct manipulated variable
difference TUN_DLMN.
Compare CYCLE and CYCLE_P with
the cycle time of the cyclic interrupt
level and note call distributors which
may exist.
Check the CPU utilization. If your CPU
is highly utilized, you will have
prolonged sampling times which may
not match CYCLE or CYCLE_P.
Appendix
A-17

Advertisement

Table of Contents
loading

Table of Contents