|
Parameter name in Diagnostics Explorer |
Context in Diagnostics Explorer |
Runtime path |
Description |
|---|---|---|---|
|
MaintAlerts |
SLS |
SLS_NAME/MAINT_ALERTS |
Maintenance alert status of the logic solver, combination of both cards when redundant |
|
Condition Text in MaintAlerts |
Meaning |
Action |
|---|---|---|
|
Calibration Data Questionable |
One or more calibration values outside of valid range or no manufacturing calibration data is present. |
Logic solver card should be returned to Emerson. |
|
Modules Not Executing at Configured Scan Rate |
The logic solver has set the actual scan rate longer than the configured scan rate based on the estimate of execution time at download. |
Change the logic solver scan rate to match ACT_SCAN_TIME diagnostic parameter value. Re-download. |
|
Non-Volatile Memory Battery or Chip Failure |
NVM battery or chip failure has been detected during periodic test, or not able to restore saved parameter records after powerup or reset, or a CRC error occurred when writing a parameter record. |
Check the value of DIAG_STATUS and CONTROL_STATUS. If the condition is in DIAG_STATUS, the logic solver card should be returned to Emerson. If the condition is in CONTROL_STATUS and the card is in an unconfigured state after powerup, download the logic solver. |
|
Channel Error |
OINTEG is Bad on one or more channels. |
Check the values of channel STATUS parameters for more information. Problem can be in the card or in the field. |
|
SISNet Error |
Any condition other than High Error Rate is active in P2P_STATUS. |
Check value of P2P_STATUS. Transmit errors indicate a problem with this card. Receive and Synchronization errors may be associated with another card. Contact technical support if the condition is persistent or repeats. |
|
Partner Not Available |
Partner card is not responding to heartbeat messages or is responding but is not configured. |
This condition can be due to a temporary situation such as a proof test being underway. If the condition persists longer than two minutes, the partner may have a fatal error. Check the value of PAST_ERROR on the partner card. This condition is active if the Partner Not Present condition is active. |
|
Partner Not Present |
Partner card is not responding to heartbeat messages. |
This condition is due to the partner card not being in the slot, in the slot but in a failed or unpowered state, in the process of powerup testing, or having a problem with the redundancy link. |
|
Card Not Communicating |
One card of a redundant pair is not communicating with the controller. Not applicable to a simplex logic solver. |
Condition can be expected if one card is in a failed or unpowered state, or is having a problem communicating with the controller. If the latter occurs on an Active logic solver, an uncommanded switchover will occur and will be indicated in PAST_ERROR. |
|
Card Not Fully Operational |
The same PAST_ERROR condition was present on back-to-back resets. |
Check the value of PAST_ERROR and refer to the action for it. |