|
Parameter name in Diagnostics Explorer |
Context in Diagnostics Explorer |
Runtime path |
Description |
|---|---|---|---|
|
FailedAlerts |
CSLS |
CSLS_NAME/FAILED_ALERTS |
Failure alert status of the CHARM smart logic solver |
|
Condition Text in FailedAlerts |
Meaning |
Action |
|---|---|---|
|
Both SISNet Connections on Logic Solver are Bad |
The Logic Solver cannot communicate on the local peer bus or Local Safety Network. |
Replace the logic solver card with the error (check the value of P2P_STATUS). |
|
CHARMbus Communications on CHARMs Logic Solver are Bad |
Both Primary and Secondary CHARMbus on the CHARMs Smart Logic Solver have failed. |
If the fatal condition is persistent, do a manual reset of affected card and contact Emerson Technical Support. If the fatal condition was momentary, contact Emerson Technical Support to report the error. |
|
Control Data Mismatch Between Cores |
The main processors of the Logic Solvers detected a mismatch in outputs or secure parameter data. |
|
|
Control Subsystem Compare Error |
The main processors of the Logic Solvers detected a mismatch in outputs or secure parameter data. |
|
|
Control Subsystem Scheduling Error |
The Control subsystem is unable to complete module execution and output delivery in its scheduled period. |
Change to a slower logic solver scan rate and re-download. |
|
Dual Active [CHARMs] Logic Solvers |
One Smart Logic Solver in a redundant pair has been reset because both Smart Logic Solvers were functioning as the Active. |
If the fatal condition is persistent, do a manual reset of affected card and contact Emerson Technical Support. If the fatal condition was momentary, contact Emerson Technical Support to report the error. |
|
Hardware Watchdog Failure |
One Smart Logic Solver in a redundant pair has been reset because both Smart Logic Solvers were functioning as the Active. |
|
|
Main Processor 2 Compare of I/O Processor Data Failed |
The Main Processor 2 validates the I/O Processor's calculations. This condition is caused by a mismatch in the results of the calculation. |
|
|
Main Processor 2 Compare of I/O Processor Frequency Failed |
The Main Processor 2 validates the I/O Processor's calculations. This condition is caused by a mismatch in the results of the calculation. |
|
|
Memory Test Failure |
A failure was detected in a periodic test of the main processor Random Access Memory (RAM) or a power-up test of RAM and Non-Volatile Memory (NVM). |
|
|
Program Assertion |
An unspecified internal software error causes a null pointer to be returned. |
|
|
Resource Error |
The system software could not obtain a hardware or software resource. |
|
|
SIS Communications on CHARMs Logic Solver are Bad |
The Logic Solver is no longer receiving local peer communications. |
|
|
Task Checkpoint Error |
A Logic Solver software task failed to complete properly or in a timely manner. |
|
|
Timeout Between Main Processor 2 and I/O Processor |
The number of scans, for the I/O Processor to respond to the Main Processor 2, has been exceeded. This condition reveals fatal errors detected by the I/O Processor. |
|
|
Timeout on Inter-Processor Link Between Main Processor 1 and Main Processor 2 |
The number of scans, for one main processor to respond to the other, has been exceeded. |
|
|
Uncommanded Switchover |
The Active redundant Smart Logic Solver has been reset (becoming the standby redundant Smart Logic Solver) because of an internally-detected error. |
|
|
Unspecified Hardware Error |
An unspecified hardware error such as a failure in the commission or power monitor circuitry occurred. |