230-04C2

Check IOCP file presence

Navigate to MOD function → System Files → TNC:\system\ directory and verify the IOCP file exists with .ioc extension.

IOCP files are typically named based on your specific drive configuration (e.g., 'drives.ioc')

Verify file integrity

Open the IOCP file in the TNC editor and check for syntax errors, incomplete brake output definitions, or corrupted text characters.

Do not modify IOCP files without proper backup - incorrect syntax can cause multiple system alarms

Restore from backup

If file is corrupted, restore the IOCP file from your machine backup or contact machine builder for original configuration file.

Always keep a verified working copy of your IOCP file on external media

Check machine parameter 7251

Access MOD function → Machine Parameters → CfgIoAccess → MP7251 (path for IOCP file) and verify the correct path is specified.

Default path should be 'TNC:\system\' unless specifically modified by machine builder

Verify directory structure

Navigate through the file system using MOD → System Files to confirm the IOCP file exists at the specified path location.

Case sensitivity matters - ensure exact spelling and capitalization match the parameter setting

Correct path configuration

If path is incorrect, modify MP7251 to point to the correct IOCP file location and perform a control restart (MP7251.x = 'TNC:\system\filename.ioc').

Use relative paths when possible to avoid issues with drive letter changes

Open IOCP file for editing

Access MOD → System Files → navigate to IOCP file and open with TNC editor to examine brake output syntax.

Make a backup copy before editing any IOCP file

Check brake output syntax

Verify brake outputs are defined with correct syntax: [BRAKE_OUTPUT] sections with proper axis assignments (X_BRAKE_OUT = HSC:0.DO.0, etc.).

Each servo axis requiring a brake must have a corresponding BRAKE_OUTPUT definition

Validate and save corrections

Correct any syntax errors, save the file, and restart the control to reload the IOCP configuration.

Use the TNC's built-in syntax checking by attempting to save - errors will be highlighted

Check drive communication status

Navigate to MOD → Diagnosis → Drive Diagnosis and verify all servo drives show 'Ready' status without communication errors.

Look for red status indicators or timeout messages in the drive diagnosis screen

Verify EnDat/resolver connections

Check physical connections between TNC and servo drives, ensuring EnDat cables and power connections are secure.

Power down system before checking physical connections to prevent damage

Reset drive communication

Perform a drive reset through MOD → Diagnosis → Drive Diagnosis → Reset Drives, then restart the control system.

Allow 30 seconds between drive reset and control restart for proper initialization

Check current user access level

Verify login status in MOD function - ensure you have at least 'Service' level access (password level 2 or higher).

IOCP file access typically requires service technician level permissions

Login with appropriate credentials

Access MOD → Login and enter service level password to gain sufficient system access rights.

Only use authorized passwords - contact machine builder if service passwords are unknown

Retry IOCP file access

After proper login, restart the control or manually reload the IOCP configuration through system diagnostics.

Some systems require a full restart after permission level changes to properly reload IOCP files