230-04CD

Identify software versions involved

Access MOD function, navigate to System Info and document current NC software version. Compare against the previous version from your service documentation to identify the version jump that triggered conversion.

TNC controls store previous software version info in TNC:\system\changelog.txt - this helps identify exactly which firmware transition caused the issue.

Access machine parameter backup

Navigate to TNC:\system\backup\ directory using PGM MGT key. Locate the automatic backup file created before firmware update (usually named with date/time stamp and .BCK or .BIN extension). Copy this to external media before proceeding.

Do not overwrite current parameters until you've documented all current settings - the backup may not contain your most recent tuning adjustments.

Export current motor parameters manually

Press MOD key > Machine Parameters > activate 'Single Axis Display' for the motor indicated in %1. Document all parameters in groups MP700-MP799 (axis-specific) and MP1000-MP1999 (encoder/motor). Screenshot or write down all non-zero values.

Use MOD > Machine Parameters > Print function to generate a complete parameter list to USB stick - this creates a searchable text file.

Re-enter motor configuration using wizard

In MOD function, select Motor Configuration Wizard. Choose the affected axis, select 'Delete current configuration', then 'New Motor Setup'. Input motor manufacturer, model number from nameplate. Let the wizard populate from Heidenhain motor database rather than converting old parameters.

If your exact motor model isn't in the database, select 'User-defined motor' and manually enter nameplate data - this bypasses the conversion process entirely.

Verify encoder compatibility settings

Check MP1420 (encoder type) matches your actual feedback device. After firmware updates, encoder type enumerations sometimes change. Verify against physical encoder label and update if needed. Cycle power after changing encoder type parameters.

Incorrect encoder type settings can cause position loss or runaway conditions. Ensure amplifier enable is OFF before cycling power with changed encoder parameters.

Check system file integrity

Access TNC:\system\ directory via PGM MGT key. Look for MOT.SYS, MOTOR.CFG, or MOTDB files depending on your TNC model. Check file size is non-zero and date matches your firmware version date. Compare file size with a known-good system if available.

On TNC 640 controls, the motor database is in TNC:\system\motordb\ directory - check for multiple manufacturer files (.XML format) here.

Restore motor database from installation media

Insert the Heidenhain firmware USB stick or access the installation files. Navigate to \system\ folder on the media. Copy MOT.SYS or motordb folder to TNC:\system\ directory, overwriting existing corrupted files. Requires 'System Files' access rights enabled.

This operation requires the control to be in MOD function with PLC stopped. Ensure machine is in a safe state with all axes stationary.

Force motor parameter re-initialization

In MOD function, access Machine Parameters, locate MP700 for the affected axis. Set MP700 to '0' (axis disabled), save parameters, cycle control power. Re-enter MOD, set MP700 back to correct axis type, then reconfigure motor using the wizard.

This forces the control to rebuild motor configuration from scratch using the restored database rather than attempting conversion of potentially corrupted data.

Verify system log for additional errors

Access MOD > System Info > Logbook. Filter for errors occurring at the same timestamp as alarm 230-04CD. Look for file system errors, CRC failures, or database access errors that indicate broader corruption issues.

Export the logbook to USB (SYSLOG.TXT) and search for keywords: 'CRC', 'corrupt', 'database', 'MOT.SYS' to quickly identify related issues.