Rack Unit
A rack unit can be used to combine different devices such as SmartPDUs, MultiSensors or door contacts to represent a physical rack. The rack unit can monitor various total energy values.
General
The basic settings of each device include the activation state (On/Off) as well as a name under which all alarms and warnings reported by this device are displayed. This should be chosen as uniquely descriptive as possible to be able to distinguish between devices.
Alarm Group
By selecting the parent alarm group, the device is integrated into the system hierarchy.
Alarms are signaled in the parent alarm group.
Devices
The selected devices and external sensors are assigned to the rack unit. The devices can be assigned to power lines A and B, which is required for load balancing.
The rack unit forms a new organizational layer in the topology, i.e. all assigned devices and external
sensors are subordinate to it, similar to the alarm groups.
This means that the assigned devices are no longer found in their previously superordinate alarm group.
Load Distribution
The load distribution monitors the distribution of load between devices assigned to power lines A and B. Thresholds for the maximum percentage deviation and power difference between the two power lines can be configured here.
Load distribution helps to ensure an even energy distribution between the two power lines and can trigger warnings when the distribution becomes unbalanced.
Alarm Settings
Warnings and alarms are always triggered when the value measured by the device exceeds (for Max.) or falls below (for Min.) one of the configured thresholds.
Alarm Assignment
| Name | API value | Description |
|---|---|---|
| Off | off | For this input, alarming is disabled and the state/measurement value is not updated. |
| Armed-Active | armed-active | When the parent alarm group has been armed, alarms can be triggered. The state/measurement value of the input is updated. |
| Always-Active | always-active | Alarms can be triggered regardless of the alarm group's switch status. The state/measurement value of the input is updated. |
| Fire | fire | Alarms can always be triggered. These are reported as fire alarms. |
| Sabotage | sabotage | Alarms can always be triggered. These are reported as sabotage/intrusion alarms. |
| System Message | system | Alarms can always be triggered. These are reported as system messages. |
| Display Only | display-only | No alarm evaluation takes place. The state/measured value continues to be updated. |
Active Power
A rack unit can display and record the total active power of all subordinate SmartPDUs and SmartMeters. This can be configured separately for power lines A and B. Individual thresholds and recording options can be set for each supply line.
To activate the recording of active power, the recording and display of consumption must also be active.
Apparent Power
A rack unit can display and record the total apparent power of all subordinate SmartPDUs and SmartMeters. This can be configured separately for power lines A and B.
To activate the recording of apparent power, the recording and display of consumption must also be active.
Consumption
A rack unit can display and record the total consumption of all subordinate SmartPDUs and SmartMeters. This can be configured separately for power lines A and B. When measurement is activated, recording also takes place. The recording of total active power is also based on the recording of total consumption.
Webhooks
Webhooks in KentixONE provide the ability to send an HTTP request to an external server when an event occurs. System-wide Webhooks can be created for this purpose. Such a webhook can be assigned to any number of events.
Webhooks also provide the possibility to implement functions via the KentixONE SmartAPI that are not available through the standard configuration.
For example, when a fire alarm occurs, the switching outputs of an AccessManager could be activated to unlock the connected motor locks.
Events
| Name | Description |
|---|---|
| All Alarms | The webhook is sent for every alarm that occurs. |
| Armed-Active Alarms | When an armed-active alarm occurs, the webhook is sent. |
| Always-Active Alarms | When an always-active alarm occurs, the webhook is sent. |
| Fire Alarms | When a fire alarm occurs, the webhook is sent. |
| Sabotage Alarms | When a sabotage alarm occurs, the webhook is sent. |
| System Messages | When a system message is triggered, the webhook is sent. |
| Before Arming | The webhook is sent when an alarm group is to be armed.(1) |
| After Arming | The webhook is sent after an alarm group has been armed. |
| Before Disarming | The webhook is sent when an alarm group is to be disarmed.(1) |
| After Disarming | The webhook is sent after an alarm group has been disarmed. |
| Change of Switching Status (Arming or Disarming) | When the alarm group is switched, the webhook is sent. |
| Cyclical (5 Min, 10 Min, 15 Min, 30 Min) | The webhook is sent cyclically. |
(1) The webhook is sent when a switching command is triggered either by a user or by automatic arming. Example: (Dis-)Arming command by user → Webhook is sent → (Dis-)Arming is executed