Table of Contents
Advertisement
• Behavior when the programmer restarts is linked to the
phase of the step that the programmer is in :
o programmer ramp phase:
• if programmed time 0<= P.TIME_x <= RAMP.T of
step in execution: start from new time
• if programmed time P.TIME_x > RAMP.T of step
in execution: start from hold phase
o programmer in hold phase:
• if programmed time 0 <= P.TIME_x <= HOLD.T
of step in execution: start from new time
• if programmed time P.TIME_x > HOLD.T of step
in execution: start from ramp phase, next step
• make a single change of the step number.
At restart, the programmer goes to the step program-
med at the beginning of the ramp. Program time will
equal ramp phase start time. If the programmed step is
greater than the last step of the program, it goes to the
last step of the program.
• make a single change of the phase (ramp or hold)
Programmer action at restart is linked to the type of
switch forformed:
o going from ramp to hold, the programmer goes to
the start of the hold phase of the active step in hold
status. Program time will equal hold phase start time.
o going from hold to ramp, the programmer goes to
the start of the ramp phase of the active step.
Program time will equal ramp phase start time.
• make a single change of work mode
(from ASYNCHRONOUS to SYNCHRONOUS and
vice versa).
Going from ASYNCHRONOUS to SYNCHRONOUS
mode, the second programmer will take programmer
1 time as program time (at restart)
• make a combined change of step and phase in
order to obtain the following:
o
if you change the step number and phase equals
ramp => you go to the start of the ramp of the
set step, with time P.TIME_x (= duration of ramp\
hold phase) set to 0.
o
if you change the step number and phase equals
hold => you go to the start of the hold phase of
the set step, with time P.TIME_x (= duration of
ramp\hold phase) set to 0.
o
if you change the step number and phase goes
from ramp->hold => you go to the start of the
hold phase of the set step, with time P.TIME_x
(=duration of ramp\hold phase) set to 0.
o
if you change the step number and phase goes
from hold->ramp => you go to the start of the
ramp phase of the set step, with time P.TIME_x
(=duration of ramp\hold phase) set to 0.
Changing programmer work mode from ASYNCHRONOUS
to SYNCHRONOUS invalidates any simultaneous change of:
•
the time assigned to the active phase of the step
(ramp or hold).
•
step number;
•
the phase or segment (ramp or hold); run on
programmer 2.
80209C_MHW_850-1650-1850_01-2020_ENG_pag. 211
But if you make the same combined change on program-
mer 1 (change of mode\time assigned to active phase
of step or change of mode\number of step or change of
mode\phase), the two actions have an effect and also affect
programmer 2 (following SYNCHRONOUS mode).
With asynchronous programmers (parameter PROGR =
On2), if the programs assigned to the two programmers do
not have steps in common, then:
•
you can edit only the steps (submenu PR.STP) of the
program that is not in RUN (those in RUN can only be
displayed together with all the others). All of the steps
will become "editable" again only when both program-
mers are not in RUN (analogous to the case with syn-
chronous programmers);
•
you cannot change the structure of the two programs
assigned to the two programmers (or the structure of
the other 14) until at least one of the two programmers is
in RUN (=> the parameters of the PR.OPT submenu are
in display-only). All of the programs will become "edit-
able" again only when both programmers are not in RUN
(analogous to the case with synchronous programmers);
On the other hand, if the two programs assigned to the two
programmers have at least one step in common, the same
control is maintained in case of synchronous programmers,
i.e., during the RUN phase:
•
all parameters of single steps (PR.STP submenu) and
•
all parameters of single programs (PR.OPT submenu)
are available in display-only.
Consents
You can assign up to 4 consents to each step:
•
a wait step, other than the one in question, run by the
other programmer.
The beginning of the step can therefore be conditioned by:
•
a special state of consents;
•
the start of the step indicated by the other programmer
If both of the above conditions are not satisfied, the time
base stops. If the state agrees with the programmed state,
execution proceeds with restart of the time base. Each digi-
tal input can be assigned to one consent.
Events
You can assign up to 4 events to each step. At the start
of the ramp and at the start of the hold of each step, the
events are changed as programmed. Each digital output
can be assigned to one event.
Other functions
•
End program signal, with or without forcing of control
outputs.
•
Setting of a tolerance band relative to the setpoint. If the
variable is outside the band, the time base is stopped
(HBB alarm, Hold Back Band).
•
Setpoint slaved with the same time base to manage a
slaved controller via analog retransmission output A1.
•
Total modularity of functions and parameters, with easy
exclusion of ones not required.
Advertisement
Table of Contents
