126-0133

Check current license scope

Press MOD key, select 'System Info' → 'Options' or 'License Information'. Document the permitted number of CC/UxC axes shown in the license details.

License information may show 'CC axes: X' or 'UxC modules: X' depending on control generation. Write down the exact permitted quantity.

Compare with detected devices

The alarm message shows 'Current: %1; permitted: %2'. Compare %1 (detected devices) with %2 (licensed devices). If %1 > %2, you have a licensing shortfall.

On iTNC 530 and TNC 620/640 controls, %2 reflects both hardware capability and license restrictions—the lower limit applies.

Obtain license upgrade

Contact the machine tool builder or Heidenhain service with control serial number and required number of CC/UxC axes. Request license upgrade file (typically .LIC or .KEY file).

Never attempt to modify license files manually or use unauthorized license sources—this will corrupt the control software.

Install new license

Load the new license file via MOD → 'System Setup' → 'Load License' or through TNCguide service software. Restart the control to activate the new license scope.

Keep a backup copy of all license files on USB storage—they are tied to control serial number and cannot be regenerated without factory authorization.

Power down and verify physical installation

Shut down the control and disconnect power. Open the electrical cabinet and physically count all CC/UxC modules connected to the HSCI daisy-chain. Document module types and positions.

Ensure complete power isolation and follow lockout-tagout procedures before accessing electrical cabinet.

Check HSCI bus configuration

Power up and enter MOD mode. Navigate to 'System Parameters' → 'Bus Configuration' or 'Drive Configuration'. Review the detected HSCI devices and compare with physical count.

On TNC 640 controls, use the graphical bus topology view to see all detected devices with their node addresses clearly displayed.

Remove excess modules

If physical modules exceed permitted quantity, power down and remove the excess CC/UxC modules from the HSCI chain. Ensure proper bus termination after removal.

Always maintain HSCI termination resistor on the last physical device in the chain—improper termination causes communication errors.

Verify configuration file

Check the PLC configuration file (typically SYS.PLC or machine-specific) for the number of configured CC/UxC modules. Ensure it matches the physical installation after module removal.

Configuration file parameter typically looks like 'CC_MODULES = X' or similar—consult machine documentation for exact parameter names.

Access bus diagnostics

Enter MOD function and navigate to 'Diagnostics' → 'HSCI Bus' or 'Drive Diagnostics'. Review the list of detected node addresses for any duplicates or unexpected entries.

Each CC/UxC module must have a unique node address. Standard addressing starts at node 1 and increments sequentially.

Check module DIP switches or rotary switches

Power down the system. Access each CC/UxC module and verify the physical address setting via DIP switches or rotary address selector. Ensure no two modules share the same address.

Address changes require power cycling the entire system—never adjust addresses with power applied.

Verify sequential addressing

Ensure CC/UxC modules are addressed sequentially without gaps (e.g., 1, 2, 3, 4) as required by most Heidenhain configurations. Gaps or non-sequential addressing can cause detection errors.

Some machine configurations allow non-sequential addressing, but this must match the PLC configuration exactly—consult machine tool builder documentation.