5.13.2. Example of setting a program from digital inputs
If there is a single programmer a) Using the digital input functions:
F.in for digital input 1 = P.PR1.0
= select program for PROGRAMMER bit 0
F.in for digital input 2 = P.PR1.1
= select program for PROGRAMMER bit 1
F.in for digital input 3 = P.PR1.2
= select program for PROGRAMMER 1 bit 2 b) With state of digital inputs: state of digital input 1 = active state of digital input 2 = inactive state of digital input 3 = active
If double programmer is enabled a) Using the digital input functions: binary value = 5 select program 6
F.in for digital input 1 = P.P12.1
= Select program for PROGRAMMER 1 and for PROGRAMMER 2 bit 1
F.in for digital input 2 = P.P12.2
= Select program for PROGRAMMER 1 and for PROGRAMMER 2 bit 2
F.in for digital input 3 = P.P12.3
= Select program for PROGRAMMER 1 and for PROGRAMMER 2 bit 3 b) With state of digital inputs: state of digital input 1 = active state of digital input 2 = inactive state of digital input 3 = active c) With state of digital inputs: state of digital input 1 = active state of digital input 2 = inactive state of digital input 3 = active binary value = 10 select program 11 for PROGRAMMER 1 select program 12 for PROGRAMMER 2 binary value = 12 select program 13 for PROGRAMMER 1 select program 14 for PROGRAMMER 2 d) With state of digital inputs: state of digital input 1 = active state of digital input 2 = inactive state of digital input 3 = active binary value = 14 select program 15 for PROGRAMMER 1 select program 16 for PROGRAMMER 2
5.13.3. Programmer functions
Depending on the model, the controller can combine the two functions of controller and single loop programmer
(PROGRAMMER 1) and double loop programmer
(PROGRAMMER 1 and PROGRAMMER 2).
Base time accuracy is 4 seconds every 10 hours.
Programmer stop and restart modes
The programmer can be started or stopped from:
• digital input;
• key (START), (STOP) and + (RESET) in the absence of other enablings;
• alarm state (ON = START);
• different restart modes after a Power-off; (Power Off);
• setpoint preceding a Power-off;
• process variable value at time of Power-on;
• optimal search for setpoint forward/back in time;
• wait for Start.
Changes possible in stop state
When the programmer is stopped, you can set or change:
• program number;
• the active setpoint;
• the time assigned to the active phase of the step
(ramp or hold).
• step number;
• phase or segment (ramp or hold);
• change the work mode of the programmers from
ASYNCHRONOUS=>SYNCHRONOUS (if and only if both programmers are in STOP);
• change the work mode of the programmers from
SYNCHRONOUS =>ASYNCHRONOUS.
You can:
• make a single change of the program number. This change will take effect only after a reset command.
• make a single change of the time assigned to the active phase of the step (parameter P.TIME_x).
80290E_MHW_850-1650-1850_06-2021_ITA_pag. 215
• 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.
But if you make the same combined change on programmer 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 programmers are not in RUN (analogous to the case with synchronous 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 “editable” 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 digital 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.
80290E_MHW_850-1650-1850_06-2021_ITA_pag. 216
