235-0070

Access PLC configuration menu

Navigate to MOD > PLC > Configuration > I/O Configuration to check current IOC file version and fieldbus settings.

Check the file header information which displays the IOC format version

Verify PROFINET configuration requirements

Confirm PROFINET is configured in machine parameter MP7600 (fieldbus type) and verify IOC file shows V4 format in file properties.

Changing fieldbus parameters requires machine restart and may affect all I/O operations

Update IOC file to V4 format

Use TNCopt or latest version of IOC configuration software to regenerate the IOC file in V4 format for PROFINET compatibility.

Always backup the working IOC file before making changes

Load updated IOC configuration

Transfer the new V4 IOC file via TNCopt or CF card to TNC:\PLC\IOC\ directory and restart the control.

Ensure all connected PROFINET devices are powered and accessible before restart

Check HSCI configuration status

Navigate to MOD > PLC > Diagnostics > I/O Status to verify HSCI module detection and check MP7600 for HSCI fieldbus selection.

HSCI modules show specific diagnostic information in the I/O status display

Examine current IOC file version

Access file manager and check IOC file properties in TNC:\PLC\IOC\ directory to confirm format version is less than V3.

Do not delete IOC files without proper backup

Generate V3 compatible IOC file

Use HEIDENHAIN IOC configuration tool to create new IOC file with V3 format, ensuring all HSCI module addresses and types match physical installation.

Document all module positions and types before reconfiguration

Validate HSCI communication

After loading new IOC file, verify HSCI communication in PLC diagnostics and confirm all expected I/O points are active.

HSCI timing is critical - ensure proper cable lengths and termination

Identify active fieldbus protocol

Check MP7600 (fieldbus type) and MP7601-MP7610 series parameters to determine which communication protocol is currently configured.

Only one fieldbus type should be active at a time in most TNC configurations

Analyze IOC file contents

Open IOC file with text editor to examine header information and verify it matches the active fieldbus type and required format version.

IOC files are sensitive to format changes - use proper editing tools only

Create protocol-specific IOC file

Generate new IOC file using HEIDENHAIN configuration software, ensuring single fieldbus protocol and correct format version (V2 for PROFIBUS/AS-i, V3 for HSCI, V4 for PROFINET).

Keep separate IOC files for different fieldbus configurations if machine supports multiple protocols

Test fieldbus communication

Load the protocol-specific IOC file and verify communication status in MOD > PLC > Diagnostics > Fieldbus Status.

Ensure all fieldbus devices are properly configured and powered before testing

Verify IOC file integrity

Check file size and compare with original IOC file, examine file properties in TNC file manager for any corruption indicators or unusual file attributes.

Compare file checksums if available from original IOC generation

Re-transfer IOC file

Delete corrupted IOC file from TNC:\PLC\IOC\ directory and transfer fresh copy using TNCopt with verified connection or CF card.

Ensure stable communication link during file transfer to prevent re-corruption

Validate file format after transfer

Open transferred IOC file and verify format version header information is readable and matches required version for configured fieldbus.

Use TNCopt file comparison feature to verify successful transfer

Check TNC software version compatibility

Navigate to MOD > System Info to verify current TNC software version and compare with IOC file creation date and format requirements.

Document software versions when creating IOC files for future reference

Upgrade IOC file format

Use current version of HEIDENHAIN IOC configuration software to import legacy configuration and export in required format version.

Some legacy I/O module types may not be supported in newer IOC formats

Validate upgraded configuration

Test all I/O functions after loading upgraded IOC file to ensure compatibility with existing hardware and PLC program.

Keep legacy IOC file as backup in case rollback is needed