250-13BD

Check program execution status

Press STOP key and verify program is fully stopped. Check status display in MOD function for any active cycles or background processes.

Use MOD 99 to view all active system processes that might be blocking the interface

Verify axis and spindle status

Navigate to Manual Operating mode and confirm all axes are stationary and spindle is stopped. Check position display for any drift or movement.

Ensure machine is in safe state before attempting to clear any active processes

Reset PLC module request

Access PLC program via MOD function, locate Module 9216 call, and verify timing parameters. Consider adding delay before pop-up request.

Module 9216 should include status checking before attempting window display

Clear emergency conditions

Check emergency stop status, release if engaged, and verify all safety circuits. Navigate to alarm display using HELP key to view active alarms.

Only release emergency stop after confirming safe machine conditions

Resolve pending alarms

Address all active alarms in sequence. Use HELP key to access alarm list and follow recommended actions for each alarm code.

Some alarms require power cycle or specific parameter reset procedures

Verify PLC status after clearing alarms

Access MOD function PLC status display to confirm PLC is running normally and Module 9216 can execute without conflicts.

Check PLC cycle time in MOD display - excessive cycle times can cause interface blocking

Review Module 9216 call parameters

Access PLC program editor and examine Module 9216 input parameters including window type, message text length, and priority settings.

Window priority must be appropriate for current operating mode - use lower priority for non-critical messages

Verify message buffer allocation

Check that sufficient memory is allocated for pop-up message text and that message format matches TNC requirements for special characters and length.

Message text should not exceed 80 characters per line and avoid special formatting codes

Test module with simplified parameters

Temporarily modify Module 9216 call with basic parameters and short message text to isolate parameter-related issues.

Use standard ASCII characters only during testing to eliminate encoding issues

Check current operating mode

Verify TNC is in appropriate operating mode for PLC interface access. Switch to Manual or Program Run mode if currently in restricted mode.

Some service modes accessible via MOD functions restrict normal PLC interface operations

Review DNC and external communication status

If using DNC operation, verify communication status and consider timing of PLC pop-up requests relative to data transfer operations.

DNC operations may temporarily block PLC interface access during file transfers

Modify PLC logic for mode-dependent operation

Implement operating mode checking in PLC program before calling Module 9216 to ensure appropriate timing and context.

Use system markers to detect operating mode and queue pop-up requests for appropriate timing

Check system resource utilization

Access MOD function system diagnostics to review memory usage, PLC cycle time, and overall system loading.

PLC cycle times over 20ms may indicate resource constraints affecting interface operations

Review PLC program efficiency

Examine PLC program for excessive Module 9216 calls, infinite loops, or resource-intensive operations that could impact system performance.

Backup PLC program before making modifications

Restart control system if necessary

If resource issues persist, perform controlled shutdown and restart of TNC system to clear memory allocation problems.

Ensure all programs and data are saved before system restart