CC%2 cross comparison failed

What does 231-A081 mean?

This error signifies a discrepancy in input or output data of the safety core software during a cross-comparison between the MC (Machine Control) and CC (Controller). This can affect various safety-related functions, including axis group states, motion requests, axis movement releases, machine control voltage, drive enable permissions, machine key statuses, brake-line test signals, safety-related mode of operation (SOM), read-back outputs, SPLC program activity, and stop requests. It also indicates issues with ascertained safety status of the axis group, axis-dependent braking control, motion status, or operating readiness for functional safety.

• Difference found in input data of the safety core software during cross-comparison between MC and CC (e.g., pp_AxGrpStateReq, pp_AxGrpActivate, pp_AxFeedEnable, pp_GenCVO, pp_AxGrpPermitDrvOn, pp_GenMKG, pp_GenTBRK, pp_GenSOM, readBackOutputs, running, stopReq).
• Difference found in output data of the safety core software during cross-comparison between MC and CC (e.g., NN_AxGrpState, NN_AxBrkReleaseReq, NN_AxGrpInMotion, NN_GenSafe).
• Error in the Safety PLC (SPLC) program causing inconsistent data between MC and CC.
• Communication errors or delays between MC and CC leading to out-of-sync data.
• Incorrect or corrupted safety-related configuration or parameters.

Click steps to track your progress.

1. 1

   Review and meticulously check the Safety PLC (SPLC) program for logical errors, inconsistencies, or timing issues that could lead to data mismatches.

2. 2

   Verify that all safety-related input signals (e.g., pp_GenCVO, pp_GenMKG, pp_GenTBRK, pp_GenSOM) are stable and correctly transmitted between MC and CC.

3. 3

   Inspect communication cables and connections between the MC and CC units for damage, loose contacts, or electromagnetic interference.

4. 4

   Ensure that all parameters related to axis groups, drive enables, and operating modes are correctly configured and consistent across the system.

5. 5

   If the issue persists, consider reloading the SPLC program and safety configuration, or updating software versions to address potential bugs or incompatibilities.