200-0018

Access machine parameter overview

Press MOD key, select 'Machine Parameters', navigate to axis-specific parameters MP1010-MP1070 for the affected axis.

Use Ctrl+F to quickly search for specific parameter numbers

Verify axis basic parameters

Check MP1010 (axis designation), MP1020 (linear/rotary axis type), MP1030 (reference point direction), and MP1040 (measuring system type) for valid entries.

Document original values before making changes

Validate encoder configuration

Verify MP1060 (encoder type) and MP1070 (encoder resolution) match the actual hardware configuration and are within manufacturer specifications.

Cross-reference with encoder nameplate data

Restore from backup or defaults

If parameters are corrupted, restore from machine parameter backup file or contact machine tool builder for default parameter set.

Always create backup before parameter restoration

Check encoder hardware identification

Navigate to MOD > Diagnosis > Encoder to verify encoder ID and compare with MP1060 encoder type setting.

EnDat encoders should show proper ID string in diagnosis screen

Verify encoder resolution settings

Confirm MP1070 encoder resolution matches encoder specifications and MP1080 gear ratio is correctly configured.

Incorrect resolution can cause positioning errors and machine damage

Test encoder communication

Use TNC diagnosis functions to test encoder signal quality and communication integrity through the encoder test screens.

Look for consistent position feedback and absence of communication errors

Reconfigure encoder parameters

Update MP1060, MP1070, and related encoder parameters to match actual hardware configuration and save parameters.

Requires machine restart after parameter changes

Access drive configuration parameters

Navigate to machine parameters MP1100-MP1150 for the affected axis to review drive amplifier settings.

Note the drive amplifier model number for parameter verification

Verify drive type and connection

Check MP1100 (drive type) and MP1110 (drive address/connection) match the physical drive installation and wiring.

Incorrect drive addressing can affect multiple axes

Validate motor parameters

Confirm MP1120 (motor type), MP1130 (motor data), and MP1140 (current limits) are correctly configured for the installed servo motor.

Motor parameters should match motor nameplate exactly

Test drive communication

Use TNC diagnosis screens to verify drive communication status and check for drive-specific error codes.

Drive faults may require drive-level parameter reset

Review software limit parameters

Check MP1200 (negative software limit), MP1210 (positive software limit), and MP1220 (working area limits) for logical consistency.

Negative limit value should always be less than positive limit value

Verify travel range settings

Ensure MP1230 (maximum travel) and MP1240 (reference point position) are within machine physical limits and properly defined.

Excessive travel limits can cause mechanical damage

Test axis movement limits

Use manual axis movement to verify software limits engage properly and don't conflict with hardware limit switches.

Test both directions at slow feed rate initially

Recalibrate reference point

Perform reference point approach sequence and verify MP1240 reference point position is correctly established.

Reference point errors affect all subsequent positioning

Check parameter file integrity

Navigate to MOD > File Management and verify machine parameter file size and date stamp for signs of corruption.

Compare file size with known good backup files

Verify software version compatibility

Check TNC software version against parameter file version to ensure compatibility using MOD > System Info.

Mismatched versions can cause unpredictable behavior

Restore from backup

Load known good machine parameter backup file from TNC internal memory or external storage device.

Always maintain multiple dated parameter backups

Perform parameter validation

After restoration, cycle through all axis parameters to verify proper loading and restart TNC system.

Full system restart required after parameter file restoration