axismd.ai
Heidenhain Controller
System · Intermediate · 30-120 minutes
HEIDENHAIN 231-E01A - E01A CC FS configuration error ERR-ID= ObjId= Param=
This alarm indicates the TNC control cannot establish a valid FSoE safety communication link with the CC module due to configuration data incompatibility or corruption. The ERR-ID and ObjId parameters point to the specific safety object or parameter that failed validation during the FS system initialization sequence. Resolution requires synchronizing the configuration data between TNC and CC module or correcting the specific parameter identified in the alarm.
231-E01A
HEIDENHAIN 231-E01A - E01A CC FS configuration error ERR-ID= ObjId= Param=
E01A CC FS configuration error ERR-ID= ObjId= Param=
The configuration data transferred to the SKERN safety kernel are faulty. The ERR-ID in the error text identifies the specific machine parameter or value at fault, such as an out-of-range axis group, a spindle count that is too high, or an invalid pwmSignalOutput entry.
Root Cause Summary
This alarm indicates the TNC control cannot establish a valid FSoE safety communication link with the CC module due to configuration data incompatibility or corruption. The ERR-ID and ObjId parameters point to the specific safety object or parameter that failed validation during the FS system initialization sequence. Resolution requires synchronizing the configuration data between TNC and CC module or correcting the specific parameter identified in the alarm.
Safety
- Refer to Heidenhain service manual
- Ensure qualified technician performs repairs
Causes and Fixes
- 1
Access Safety Configuration Menu
Press MOD key, navigate to System Configuration > Safety > FS Configuration. Check the status display for CC%2 (second communication controller) - note any red indicators or error messages.
The %2 in the alarm indicates the second CC in a multi-CC system - verify you're checking the correct module if multiple CCs are installed.
- 2
Verify Configuration Status
In the FS Configuration menu, check the 'Configuration Status' field. If it shows 'Invalid' or 'Incomplete', the configuration file is corrupted or doesn't match the hardware.
Do not attempt to operate the machine in any mode if safety configuration shows as invalid.
- 3
Download Configuration to CC Module
Select the CC%2 entry and choose 'Download Configuration' to transfer the TNC's FS configuration to the CC module. This synchronizes the safety parameters and resolves most configuration mismatches.
After download, a control restart is typically required. The CC module will validate the configuration during boot sequence.
- 4
Restore from Backup if Download Fails
If download fails or alarm persists, restore the complete FS configuration from a known-good backup. Navigate to MOD > System Configuration > Safety > Restore Configuration and select a backup file from TNC:\system\fs_backup\.
Only restore configurations that match your exact machine configuration and safety circuit design.
Call a technician if:
- ·SKERN safety configuration changes required
- ·Safety system validation needed
- ·Encoder hardware replacement necessary
Prevention
- Always verify encoder safety capabilities before configuring safety axes
- Document safety system architecture during commissioning
- Regular verification of SKERN configuration integrity
Common Mistakes
- Assuming all EnDat 2.2 encoders support safety bits
- Configuring safety axes without proper encoder validation
- Mixing safety and non-safety configurations without proper SKERN setup
Seeing Multiple Alarms?
Seeing another alarm with this one? Enter the code.
Get machine-aware diagnosis
AxisMD logs alarms against your actual machines, tracks patterns, and gives AI context your manual doesn't have.
Start freeWas this guide helpful?
Always verify with your machine manual or a certified technician before performing service procedures.