126-0136

Access MOD function configuration area

Turn the keyswitch to position 2 (MOD). Enter MOD mode and navigate to System Files → Configuration Files to access the UVR configuration area.

Only authorized personnel should modify system configuration files. Make complete backups before any changes.

Review CfgUvr.sys file contents

Open CfgUvr.sys and count the number of UVR device entries defined. Compare this count with the %2 value (permitted count) shown in the alarm message.

Use the TNCopt configuration tool if available for your control version - it provides validation and prevents configuration errors.

Remove or comment out excess UVR entries

Edit CfgUvr.sys to remove UVR device definitions that exceed the permitted count. Start by removing the highest numbered devices or those not physically present in the system.

Comment out entries using semicolon (;) rather than deleting them initially, allowing easy rollback if needed.

Verify sys.xml consistency

Check sys.xml for UVR-related entries and ensure consistency with CfgUvr.sys. Remove any conflicting or duplicate UVR device definitions.

Incorrect sys.xml modifications can prevent control startup. Always maintain original backup copies.

Restart control and verify

Save all changes, exit MOD mode, and perform a complete control restart (power cycle). Monitor the startup sequence to confirm alarm 126-0136 no longer appears.

Verify TNC model and firmware version

Access MOD → System Information and document the exact TNC model (320/530/620/640), variant, and firmware NC software number (xxx xxx-xx) to determine correct UVR limits.

Check the hardware label on the control unit itself - configuration files should match the physical hardware model exactly.

Consult technical documentation

Reference the technical manual for your specific TNC model to identify the maximum permitted UVR devices. For TNC 320 this is typically 2-4, for TNC 530/620/640 it varies by configuration (4-8 typical).

Restore model-appropriate configuration

If incorrect configuration was loaded, restore the factory default configuration files for your specific TNC model using MOD → Restore Default Configuration, then reconfigure only the required UVR devices.

Restoring default configuration will erase custom settings. Document all machine parameters before proceeding.

Rebuild configuration incrementally

Add UVR device definitions one at a time in CfgUvr.sys, restarting after each addition to ensure you stay within the permitted limit and identify the exact maximum for your control.

Audit UVR device addressing

In MOD mode, open CfgUvr.sys and create a list of all UVR device addresses. Check for duplicate address assignments or multiple entries pointing to the same physical hardware location.

UVR addresses are typically sequential starting from 0. Any gaps or duplicates indicate configuration problems.

Cross-reference with physical hardware

Compare the configured UVR addresses with actual physical UVR modules installed in the control cabinet. Verify each configured device has exactly one corresponding physical module with correct DIP switch or rotary switch address setting.

Remove duplicate configuration entries

Delete or comment out any duplicate UVR device definitions in CfgUvr.sys, ensuring each physical UVR module has only one configuration entry with a unique address.

Verify encoder interface assignments

Check that encoder connections are not assigned to multiple UVR devices. Review the axis configuration to ensure clean one-to-one mapping between encoders and UVR assignments.

Use the control's diagnostic display (MOD → Encoder Test) to verify each encoder is detected only once on its assigned UVR device.