Controller, programmer with independent timer

Alarm function

KM3 has the capability to generate various types of alarms based on the process requirements.

• • Absolute low alarm (LoAb)
  • Absolute high alarm (HiAb)

• Absolute band alarm with alarm indication out of the band
• Absolute band alarm with alarm indication inside the band
• Sensor break
• Deviation low alarm (relative)
• Deviation high alarm (relative)
• Relative band alarm with alarm indication out of the band
• Relative band alarm with alarm indication inside the band

kube-alarms-021

The relative and deviation alarms are “relative” to the operative set point value.

kube-alarms-022

The “not active at power up” selection allows to inhibit the alarm function at device power up or when the device detects certain change modes

kube-alarms-023

A “Latched alarm” (manual reset) is an alarm that will remain active even if the conditions that generated the alarm no longer persist. Alarm reset can be done only by an external command.

kube-alarms-024

An “Acknowledgeable” alarm is an alarm that can be reset even if the conditions that generated the alarm are still present. Alarm acknowledge can be done only by an external command (button, digital inputs or serial link).

kube-alarms-025

A “relative alarm not active at set point change” is an alarm that masks the alarm condition after a set point change until process variable reaches the alarm threshold ± hysteresis.

Control function

The device can be programmed for 2 control types:

• • Two control actions (heat & cool) with 2 methods:
  • PID (heat and cool);
  • Heat/Cool ON/OFF control with neutral zone;

and

• • One control action (heat or cool) with 4 methods:
  • PID (heat or cool);
  • ON/OFF asymmetric hysteresis;
  • ON/OFF symmetric hysteresis;
  • Servomotor control (available when Output 2 and Output 3 have been ordered as “M”)

KM1 also has the Fuzzy overshoot control feature that reduces the overshoot usually present at instrument start-up or after a set point change, and by setting a value between 0.00 and 1.00, it is possible to slow down the instrument action during the set point approach.

kube-alarms-026

Two control actions (heat & cool)

kube-alarms-027

One control action (heat or cool)

kube-alarms-028

Fuzzy overshoot control

Timer function

Five timer types are available:

• Delayed start with a delay time and a “end of cycle” time.
• Delayed start at power up with a delay time and a “end of cycle” time.
• Feed-through.
• Asymmetrical oscillator with start in OFF.
• Asymmetrical oscillator with start in ON.

kube-timer-021

Delayed start with a delay time and a “end of cycle” time.

kube-timer-022

Delayed start with a delay time and a “end of cycle” time.

kube-timer-023

Delayed start at power up with a delay time and a “end of cycle” time.

kube-timer-024

Feed-through timer

kube-timer-025

Asymmetrical oscillator with start in OFF

kube-timer-026

Asymmetrical oscillator with start in ON

Programmer function

These instruments are able to perform a set point profile compounded of 4 groups of 2 steps (8 step total).

The first step is a ramp (used to reach the desired set point), the second is a soak (on the desired set point). When a RUN command is detected, the instrument aligns the operative set point to the measured value and starts to execute the first ramp.

In addition, each soak is equipped with a waiting band which suspends the time count when the measured value goes out of the defined band (guaranteed soak).

Moreover, for each segment, it is possible to define the status of two events. An event can drive an output and make an action during one or more specific program steps.

Some additional parameters allow defining the time scale, the automatic RUN conditions, and the instrument behavior at the end of the program.

All steps can be modified during program execution. During program execution, the instrument stores the segment currently in use and, at a 30 minutes interval, stores also the elapsed time of the soaks. If a power down occurs during program execution, at the next power up, the instrument is able to continue the program execution starting from the segment in progress at power down, and if the segment was a soak, it is also capable of restarting from the soak time minus the stored elapsed time.

The first step is a ramp (used to reach the desired set point), and the second is a soak (on the desired set point). When a RUN command is detected, the instrument aligns the operative set point to the measured value and starts to execute the first ramp.

Source: AsconKM3 Official Page