Advisory (ADVISE_ALM) hardware alarms

Hardware alarm message	Description
Channel Error - card_type Card, Cnn, CHnn	An error specific to the channel has occurred on channel CHnn of the I/O card in slot Cnn.
Channel Error - Remote Node ID, card_type Card, Cnn, CHnn	An integrity problem has been detected on channel CHnn of the remote I/O card in slot Cnn of the remote I/O node.
Channel Error - Remote Node node_name, card_type Card, Cnn, CHnn	An integrity problem has been detected on channel CHnn of the remote I/O card in slot Cnn of the node_name remote I/O node.
CHARM Integrity Error - CIOC name, CHARM number, CHARM type	The CHARM's (for example, CIOC-2, CHM1-02, AI CHARM) OINTEG is Bad.
CHARM Integrity Error - Node Id: nn, CHARM number, CHARM type	The CHARM's (for example, 2517893127, CHM1-02, AI CHARM) OINTEG is Bad.
Communications Subsystem Fault - REPEATERnn	The primary (REPEATER01) or secondary (REPEATER02) SISNet Repeater Communications subsystem has detected an error rate greater than 5% for received Railbus messages.
Configuration Mismatch - card_type Card, Cnn, Pnn	A mismatch has been detected between the configuration for port Pnn and the device connected to the I/O card in slot Cnn. Possible causes of this fault condition include: a configured device is not communicating or a device is configured as the incorrect type.
Configuration Mismatch - NVM	A mismatch has been detected between the configuration stored in the cold restart database and controller NVM. To restore current parameter records in controller NVM, download the controller.
Communications utilization beyond supported capability	The amount of CPU utilized to coordinate network input and output data communications has exceeded system guidelines. To eliminate this condition, specify a longer reporting rate for Zone 1 / Zone 2 remote nodes, CHARM I/O Cards, Wireless I/O Cards, decrease the amount of data being sent unsolicited via inter-controller referencing or DeltaV Operate data links. Refer to Inter-Controller communication guidelines for more information.
Control utilization beyond supported capability	The amount of CPU utilized to execute control has exceeded system guidelines. To eliminate this condition, either specify a longer time period for the scan rate of one or more control modules or reduce the load on the controller
Database Space - Allocated database space low, value% free	The amount of free space in the folder allocated for Batch Historian database storage has fallen below 20%. You can increase the maximum size of the Batch Historian database storage folder in DeltaV Explorer by navigating to the Output tab on the Batch Historian Properties dialog for this workstation, selecting a location in the Directory Path column, and clicking Modify.
Device Error - card_type Card, Cnn, Pnn	A communications problem has been detected with a device on the segment connected to port Pnn of the I/O card in slot Cnn. This fault condition can occur if a device is configured on the segment, but not installed on the segment.
Device Error - Profibus Card, Cnn, Pnn	A communications problem has been detected with a device on the Profibus segment connected to port Pnn of the I/O card in slot Cnn. This fault condition can occur if a device is configured on the segment, but not installed on the segment.
Diagnostic Subsystem Fault - REPEATERnn	An error has been detected in the Diagnostics subsystem of the primary (REPEATER01) or secondary (REPEATER02) SISNet Repeater. Diagnostics subsystem errors include the following: A Repeater subsystem task failed to checkpoint (report) properly with the subsystem task monitor. The SISNet Repeater CPU free time fell below 20 percent. The memory self-tests failed to complete in a timely manner.
Disk Space Low	Based on the current number of Alarms and Events records being written per minute, the amount of disk space configured for the active Event Chronicle database is insufficient for the time period specified. Whenever active Event Chronicle records consume the maximum disk space allocated, 10% of the records are removed from the active Event Chronicle, starting with the oldest. The loss of active Event Chronicle records can be prevented by modifying the workstation's Alarms and Events properties. Use one of the following options on the Advanced tab of the Alarms and Events Properties dialog: The Active Event History Data Set Storage Target option sets the maximum allocated amount of disk space for the active Event Chronicle database. The Age for Copying Events to Current History Data Set option defines the age of records in the active Event Chronicle, after which the records are replicated in a current Event Chronicle, if specified. The Automatic Current Event History Data Set Export option allows Event Chronicle records to be concurrently written to an export file on any workstation in the DeltaV network.
Duplicate Link Address - card_type Card, Cnn, Pnn	Two devices on the segment connected to port Pnn of the I/O card in slot Cnn have the same address.
Local Peer Subsystem Fault - REPEATERnn	An error has been detected in the Local Peer subsystem of the primary (REPEATERnn) or secondary (REPEATERnn) SISNet Repeater. Local Peer subsystem errors include the following: The local peer bus is not terminated or is improperly terminated. The local peer bus receiver or transmitter hardware indicates an error. SISNet Repeater messages transmitted to the local peer bus are not received while messages from Logic Solvers on the same bus are being received. In this case, it is likely that the SISNet Repeater transmitter is defective. SISNet Repeater messages transmitted to the local peer bus are not received and neither are messages from Logic Solvers on the same bus. In this case, it is likely that the SISNet Repeater receiver is defective.
Maximum Number of Wireless Devices Reached	WIOC: The Wireless Mesh Network Manager has reached its capacity for number of devices supported.
Memory utilization beyond supported capability	The total amount of used memory has exceeded system guidelines. Refer to Capacity limits for controllers for more information.
Module Slippage - High priority modules not executing at Module Scan Rate	Slippage has been detected in the execution of one or more high priority control modules. A control module configured to run at a scan rate from 100ms thru 200ms is categorized as high priority. If the configuration downloaded to the controller requires more than 65 percent of the CPU, a scheduler clamps control module execution as close to 65 percent as possible, and slippage occurs. To eliminate the slippage, either specify a longer time period for the scan rate of one or more high priority control modules or reduce the load on the controller.
Module Slippage - Low priority modules not executing at Module Scan Rate	Slippage has been detected in the execution of one or more low priority control modules. A control module configured to run at a scan rate from 5 seconds through 60 seconds is categorized as low priority. If the configuration downloaded to the controller requires more than 65 percent of the CPU, a scheduler clamps control module execution as close to 65 percent as possible, and slippage occurs. To eliminate the slippage, either specify a longer time period for the scan rate of one or more low priority control modules or reduce the load on the controller.
Module Slippage - Medium priority modules not executing at Module Scan Rate	Slippage has been detected in the execution of one or more medium priority control modules. A control module configured to run at a scan rate from 500ms through 2 seconds is categorized as medium priority. If the configuration downloaded to the controller requires more than 65 percent of the CPU, a scheduler clamps control module execution as close to 65 percent as possible, and slippage occurs. To eliminate the slippage, either specify a longer time period for the scan rate of one or more medium priority control modules or reduce the load on the controller.
Not Communicating - with Zone zone_name Standby Server	The local Inter-Zone Server has detected that the standby partner of a redundant, remote Inter-Zone Server in the zone_name zone is not communicating with its active partner.
Not Communicating - DeltaV Phase Server	A program execution error has prevented communications between the Batch Manager and the configured DeltaV Phase Server. The Batch Manager attempts to communicate with the DeltaV Phase Server every 30 seconds. If the Batch Manager fails to reconnect to the DeltaV Phase Server after two consecutive attempts, this hardware alarm message appears.
Not Communicating - Primary Network	A communications problem has been detected on the primary connection to a standby controller in the redundancy subsystem of the DeltaV network.
Not Communicating - REPEATERnn	A controller has lost communications with the primary (REPEATERnn) or secondary (REPEATERnn) SISNet Repeater.
Not Communicating - Secondary Network	A communications problem has been detected on the secondary connection to a standby controller in the DeltaV network's redundancy subsystem.
Not Communicating - Soft Phase Server	A program execution error has prevented communications between the Batch Manager and the configured Soft Phase Server. The Batch Manager attempts to communicate with the Soft Phase Server every 30 seconds. If the Batch Manager fails to reconnect to the Soft Phase Server after two consecutive attempts, this hardware alarm message appears.
Not Enabled	Redundancy is not enabled for an active controller that is configured in the DeltaV network's redundancy subsystem.
Out of Memory - NVM	There is insufficient controller NVM to save all specified parameters.
RAM Test Failure - NVM	An error has been detected during a periodic test of the main processor RAM or a power-up test of RAM and NVM.
Remote Peer Subsystem Fault - REPEATERnn	An error has been detected in the Remote Peer subsystem of the primary (REPEATERnn) or secondary (REPEATERnn) SISNet Repeater. Remote Peer subsystem errors include the following: The remote fiber-optic ring is not connected to both the transmit and receive ports. Another SISNet Repeater in the ring is powered down, causing a broken ring condition. The fiber is crossed such that a primary (REPEATERnn) SISNet Repeater is receiving messages from a secondary (REPEATERnn) SISNet Repeater. More than 32 SISNet Repeaters are connected to the same fiber-optic ring. Remote fiber-optic ring hardware indicates a transmitter or receiver error.
Save/Restore Error	An error has been detected in controller NVM while attempting to save or restore parameter records.
Server Integrity - Servernn reported an error	Servernn, an External Asset Server, can transmit device alarms; however, the server is reporting an internal error indicating that the integrAsset Serverity of the device alarm information may be compromised.
Standby Field Link Communications Failed	WIOC: The standby unit is not communicating with its Smart Wireless Field Link.
Inadequate Standby Wireless Radio Coverage	WIOC: The radio coverage between the active and standby radio is lower than the required threshold value for successful switchover.
Standby Wireless Network Manager not Synchronized	WIOC: The Mesh Network Data has not been synchronized between the active and standby units.
Standby Wireless Network Manager Software Version Does Not Match	WIOC: The software version of the Wireless Network Manager on the standby card does not match the one on the active card or the standby card is in a state in which the version number cannot be determined.
System utilization beyond supported capability	The total amount of used CPU has exceeded system guidelines. This is an aggregate measurement of the node's complete CPU usage. Refer to Capacity limits for controllers for more information.
Time sync lost	The node's time is not synchronized with the master time source for the DeltaV system, which can be either the network time server or a DeltaV workstation. Note This message can only occur if the Show integrity error when not in time sync option is enabled on the General tab of the Properties dialog for the workstation, controller, or remote I/O node.
Total	The amount of memory used has exceeded system guidelines. To eliminate this condition, reduce the amount of configured control logic or I/O for this node
Wireless Device(s) Failed to Join the Mesh Network	WIOC: Typically caused by a device with the wrong join key.
Wireless Device Invalid Message Integrity Check	WIOC: A device has been detected that is using an invalid message integrity check on the network.