231-95B0

Access system configuration files

Press MOD key, navigate to System Files, and open TNC:\system\cfg\CfgAxisCoupling.cfg to view the coupling configuration.

Identify the faulty coupling group

Note the %1 parameter from the alarm message which identifies the specific coupling name (e.g., GANTRY_Y1_Y2). Locate this section in the configuration file.

The alarm info field %4 may contain keywords like 'axis not found' or 'unknown axis' that directly indicate the problematic axis reference.

Cross-reference with CfgAxes configuration

Open TNC:\system\cfg\CfgAxes.cfg and verify that all axis names used in the coupling definition (master, slave, or gantry axes) exist exactly as spelled including case sensitivity.

Correct axis name references

Edit CfgAxisCoupling.cfg to match the exact axis names from CfgAxes.cfg. Save the file and perform a control reboot to validate the changes.

Always create a backup of configuration files before editing. Incorrect syntax can prevent control startup.

Review coupling type definition

In CfgAxisCoupling.cfg, verify the CouplingType parameter is set to a valid value: GANTRY, TANDEM, or PMASTER_PSLAVE. Check spelling and capitalization.

GANTRY type requires two axes controlling one mechanical axis. TANDEM is for synchronized parallel axes. PMASTER_PSLAVE is for dependent positioning.

Validate synchronization parameters

Check that SyncTolerance, SyncWindow, and related timing parameters are within valid ranges specified in the Technical Manual for your control version. Typical SyncTolerance values are 0.001 to 1.0 mm.

Verify axis role assignments

Ensure each axis in the coupling has a unique role (Master, Slave1, Slave2) and that no axis is assigned conflicting roles within the same coupling group.

Check for mandatory parameter completeness

Verify all required parameters for the specific coupling type are present. For GANTRY: Master, Slave, SyncTolerance minimum. Consult the configuration manual for complete parameter lists.

Use a known-good configuration file as a template. Missing mandatory parameters often cause this specific alarm code.

Search for duplicate coupling names

In CfgAxisCoupling.cfg, search for the coupling identifier shown in %1. Verify this coupling name appears only once in the configuration file.

Check for axis reuse across couplings

Create a list of all axes referenced in all coupling groups. Ensure no single axis appears in more than one coupling definition throughout the entire file.

Common error: defining Y1-Y2 gantry and then also trying to use Y1 in a separate tandem configuration. Each axis can only be in one coupling group.

Verify section delimiters

Check that each coupling definition has proper [COUPLING_x] section headers and that sections are not nested or improperly structured.

Remove or consolidate duplicate entries

Delete duplicate coupling definitions or consolidate overlapping configurations into a single proper coupling group. Save and reboot the control to apply changes.

Check file structure and syntax

Open CfgAxisCoupling.cfg and verify proper INI file syntax: section headers in [brackets], parameter=value pairs, no special characters or extra spaces around equals signs.