140-001A

Identify the missing object

Record the exact object name from the alarm message placeholders '%1' and '%2'. Press the alarm softkey to view full details if truncated.

Use MOD → Diagnose → Log File Viewer to see the complete alarm text if the display truncates long object names.

Access system configuration directory

Press MOD key, select 'System Files', navigate to TNC:\system\ directory. You need access authorization level for viewing system files.

Changes to system configuration files require proper authorization and can render the machine inoperable if done incorrectly. Document original settings before making changes.

Check axis key assignment file

Open CfgAxisKeysAssignment.sys and search for the object name from the alarm. Verify that this name matches exactly (case-sensitive) with an object defined in the SIK file.

Use the TNC editor's search function (FIND SOFTKEY) to quickly locate object references in large configuration files.

Verify SIK object definition

Open SYS.SIK or the machine-specific .SIK file (e.g., machineXXXXX.SIK). Search for the object definition section corresponding to the alarm (e.g., [AXIS], [SPINDLE]). Either add the missing object with proper configuration or correct the name to match the reference.

Each object type has required parameters. For axes, minimum requirements include driveConfig, positionEncoder, and referenceSwitch assignments.

Restart control and verify

After correcting the configuration, perform a full control restart (power cycle recommended). Monitor the startup sequence for the alarm. Check MOD → Diagnose → Log Files for any remaining configuration warnings.

Identify PLC object type

Examine the alarm message to determine if '%1' indicates a PLC-related object type (marker 'M', timer 'T', counter 'C', or I/O module). Check the startup log in MOD → Diagnose for PLC initialization messages.

PLC-related configuration alarms typically appear during the PLC initialization phase of control startup, before axis initialization.

Review PLC configuration file

Navigate to TNC:\system\CfgPLC.sys and verify the referenced object is properly defined in the appropriate section ([MARKER], [TIMER], [COUNTER], or [IO_MODULE]).

Each PLC object must have a unique name and proper range definition. Markers typically use format 'M100-M199' with assigned symbolic names.

Check PLC program references

Open the PLC program (typically in TNC:\plc\ directory, file extension .PLC or .PLCH). Search for symbolic references to the missing object name and either add the definition to CfgPLC.sys or correct the reference in the PLC program.

Modifying PLC programs affects machine safety interlocks and operational logic. Only qualified personnel should modify PLC code, and all changes must be thoroughly tested.

Validate and compile PLC

After configuration correction, use MOD → PLC → Compile to check for syntax errors and verify all references are resolved. Clear any remaining PLC compiler errors before restarting.

The PLC compiler will identify line numbers of unresolved references, making it easier to locate all instances of missing objects.

Check configuration file integrity

In MOD mode, navigate to TNC:\system\ and check file dates/sizes of all Cfg*.sys files. Compare with the SIK file date. All configuration files should be consistent in timestamp if from the same configuration set.

Use MOD → System Info → Software Versions to verify the control software version matches the configuration file compatibility.