130-0099

Identify Active NC Program

Press 'PGM MGT' key and check 'Program Run' status. Note the currently executing program name and line number when message appeared.

The alarm timestamp can be cross-referenced with the NC program runtime to pinpoint exact file operation location.

Search for File Functions

Open the identified NC program and use the search function (soft key 'FIND') to locate FN15, FN16, FN18, or FN20 commands. These are the file manipulation functions in HEIDENHAIN programming.

FN16 with ERROR parameter will generate this success message when ERROR variable returns 0.

Verify File Operation Intent

Review the file path and operation type in the FN function. Confirm the target directory (TNC:\, SYS:\, or network path) exists and the operation aligns with intended function.

Use file manager (PGM MGT key) to navigate to target directory and verify file was created/modified as expected.

Suppress Message if Desired

If this informational message is not needed, add conditional error handling in NC program around FN function or suppress error 130 in MOD > Settings > Alarm Settings > Configure message display.

Best practice is to leave success confirmations enabled during development but suppress in production if they clutter the log.

Access PLC Program

Navigate to MOD > PLC Programming or use special service mode access (depends on control variant). Review active PLC program in TNC:\plc\ directory for file operations.

Modifying PLC programs requires appropriate authorization level and can affect machine safety functions. Document original program before changes.

Check for Cyclic File Operations

Search PLC program for file writing routines that may execute cyclically or event-triggered. Look for marker bits that trigger file saves or data export functions.

Common PLC file operations include tool life logging, production counting, or alarm history exports executed at regular intervals.

Review PLC Log Frequency

If file operations are too frequent, adjust cycle timing in PLC program or modify trigger conditions to reduce message frequency in alarm log.

Use timer markers (T functions) in PLC to space file operations appropriately rather than executing every PLC cycle.

Check Backup Configuration

Navigate to MOD > Settings > General > Backup Settings (path varies by TNC version). Review automatic backup schedule and target directories configured.

On iTNC 530 and TNC 620/640, automatic backups can be scheduled in background and write to network locations or USB drives.

Review Backup Log Files

Check the backup target directory (typically TNC:\backup\ or network path specified in settings) for recently created files. Verify timestamp matches alarm message time.

Backup files are typically named with date/time stamps making correlation with alarm messages straightforward.

Adjust Backup Settings

If automatic backups are generating unwanted messages, either disable the feature, change schedule timing, or configure alarm filtering to suppress code 130 messages in MOD > Settings > Alarm Settings.

Regular automatic backups are recommended for production machines; suppressing the success message is preferable to disabling backups.

Check Network Connection Status

Navigate to MOD > Settings > Network Configuration and verify active connections. Review TNCserver connection log if available for recent file transfer activity.

TNCserver transfers appear in Windows application log with matching timestamps to alarm messages on control.