130-0199

Access PLC Programming Mode

Press MOD function, select 'PLC Programming' or 'Service' menu (password may be required). Navigate to the PLC marker display to view current PLC states.

On iTNC 530 and newer, use the integrated PLC monitor (DIAG->PLC) to filter markers by recent changes to quickly identify which marker triggered the alarm.

Modifying PLC code without proper authorization may void machine warranty and create safety hazards.

Identify Alarm Trigger Marker

Search PLC program for alarm number 130 or 0199. Look for NC-PLC marker commands like 'M_ALARM' or error flag assignments (typically M4xxx or M5xxx range markers) that reference this alarm code.

OEM alarm triggers often use structured marker naming like M4199 for alarm 199. Check markers in the 4000-5000 range first.

Trace PLC Condition Logic

Once the alarm-triggering marker is identified, trace backward through the PLC logic to find the input condition, timer, or sequence that sets this marker. Document the sensor inputs or NC states involved.

Use the PLC cross-reference function to find all locations where the alarm marker is written or modified.

Resolve Underlying Machine Condition

Based on the PLC logic analysis, check the physical machine condition (limit switches, pressure sensors, temperature monitors, etc.) or NC state that is causing the error flag to be set.

Common OEM triggers include hydraulic pressure low, chip conveyor faults, coolant level, or tool changer position errors.

Check OEM Directory Structure

Navigate to Programming and Editing mode, select 'File Management' (PGM MGT key). Browse to SYS:\ drive and look for OEM\ or MACHINE\ subdirectory containing alarm text files.

OEM alarm files are typically named ALARM_OEM.TXT, ERRORS.H, or language-specific files like ALARM_OEM.ENG or ALARM_OEM.DEU.

Verify Alarm Text File Content

Open the OEM alarm text file with the TNC editor. Search for alarm number 130-0199 or 199 to verify if descriptive text exists. Format should follow Heidenhain alarm text syntax (alarm number followed by text string).

If file exists but alarm text is missing, contact machine builder for updated alarm text file version.

Restore or Update OEM Files

If OEM alarm files are missing or corrupted, restore from machine builder's USB backup or request updated files from OEM technical support. Copy files to correct SYS:\OEM\ location.

Always backup existing SYS directory contents before copying new OEM files. Incorrect file versions may cause control instability.

Reload Control Software

After replacing OEM files, perform a soft restart (CTRL+ALT+DEL on TNC keyboard or controlled power cycle) to ensure new alarm text definitions are loaded into active memory.

On TNC 640 and newer, check MOD->System Settings->OEM Integration to verify OEM package version and last load date.

Perform Visual Machine Inspection

Check all safety doors, guards, enclosures, and access panels are fully closed and latched. Verify no physical obstructions in axis travel paths or tool change areas.

Do not bypass safety interlocks. Address the actual safety condition before attempting to clear the alarm.

Review PLC Input Status

Access PLC input display via MOD function or diagnostic screens (DIAG key -> PLC -> Inputs). Compare current input states against machine electrical schematics to identify which safety input has changed state.

Toggle or cycle suspected safety switches while monitoring PLC inputs in real-time to confirm which input is associated with the alarm condition.