Error Reporting Application
The C-Bus Error Reporting application is used to notify and manage error of other status information detected by C-Bus devices.
The C-Bus devices can monitor various operational parameters, and
can report error or warning conditions using the
C-Bus
Error Reporting application.
The reports consists of information on the source, severity and nature of the error or fault condition, and also allow independent tracking and acknowledgement of the most recent and most severe conditions.
The reports are monitored by a device such as a SpaceLogic C-Bus Automation Controller, which can:
-
display the status to the user
-
allow them to acknowledge reports
-
and as well as clear any latched errors
A SpaceLogic C-Bus Automation Controller can also make all of this available to a higher layer such as a BMS via BACnet.
There are 5 Error Reporting Modes. The mode controls:
-
which error reports are generated
-
and when they are generated
The mode can either be fixed during commissioning time, or can be changed dynamically by assigning a control group on the Enable Control application.
In addition to controlling the generation of error reports using the mode, a Trigger Control Group may be configured to request an update to ALL error channels at any time. This can be useful to manage traffic in an installation, where a large number of Error Reporting devices or channels exist.
Modes |
Types of errors |
Description |
Mode 0 |
OFF |
In this mode, neither live reports nor regular reports are generated |
Mode 1 |
All channels: Most Recent Errors only |
|
Mode 2 |
All channels: Most Recent and Most Severe Errors |
This mode works the same as Mode 1, but also includes tracking of the Most Severe errors for each channel |
Mode 3 |
Minimum reporting: Most Recent Errors only |
This mode works the same as Mode 1, but excludes the individual channel reports This can be useful to reduce the amount or traffic where there are a large number of channels or a large number of devices exist. The aggregate channel is included, which is a logical OR of all of the channel error bytes, which still allows channel errors to be monitored |
Mode 4 |
Minimum reporting: Most Recent and Most Severe Errors |
This mode works the same as Mode 2, but excludes the individual channel reports |
The following channel error status information is available via the Error Reporting application:
-
Mode Error: The channel has shut down due to the attached load being incompatible with the currently selected mode
-
Incompatible Load: The channel has shut down due to the attached load being incompatible with load profile
-
Over-temperature Windback active: The channel is operating at a reduced operating point due to excessive temperature
-
Over-temperature Shutdown : The channel has shut down due to extreme temperature
-
Over-current Shutdown: The channel has shut down due to an extreme current overload
-
Channel Offline : The channel is not responding
-
Channel Overridden : The channel has been overridden by the local override, and C-Bus priority is disabled
New devices include an aggregate channel (251) which reports the aggregate (logical OR) of all channel errors.
When used in conjunction with Error Modes 3/4 and a Trigger event for requesting update, this can be useful to minimize Error Reporting traffic.
New devices which include a C-Bus Power Supply include a Power Supply Error channel (250).
The power supply error channel allows reporting of up to three error conditions:
-
Load warning : The load current on the C-Bus Power Supply has exceeded the user-configurable warning threshold level
-
Over-current : The load current on the C-Bus Power Supply has exceeded the rated load current
-
Current Limit : The power supply is in current-limit mode, meaning the network is probably inoperable
The load warning and over-current errors are optional. If the warning threshold parameters are not configured, both these errors are disabled. Once the warning threshold parameters are configured, both errors are enabled.
The Current Limit error is always enabled. However due to the nature of the fault, it may only ever appear when most severe errors are enabled, as the network may be made inoperable by this condition.