2A0-000B

Inspect Ethernet cable at X116 connector

Power down the TNC control and inspect the Ethernet cable at connector X116 (or X26 on older iTNC 530 models). Check for physical damage, proper RJ45 clip engagement, and verify industrial-grade shielded Cat5e or Cat6 cabling is used.

Always power down the control before disconnecting network cables to prevent damage to the Ethernet interface circuitry.

Verify cable shielding and routing

Ensure Ethernet cable shielding is properly terminated at both ends with metal RJ45 connectors. Verify cable routing keeps minimum 300mm separation from power cables, servo motor cables, and spindle drive lines to prevent EMI coupling.

Use double-shielded Industrial Ethernet cables (S/FTP) in high-EMI environments. Standard office-grade UTP cables are inadequate for machine tool applications.

Replace cable and retest LSV2 communication

Replace suspect cable with known-good industrial Ethernet cable. Power up TNC and attempt LSV2 connection from TNCremo or TNCserver. Monitor for alarm recurrence during file transfer operations.

Keep spare tested Ethernet cables in your service kit. Cable issues account for approximately 60% of LSV2 transmission errors in field service experience.

Access TNC network configuration

Press MOD key, enter system password, navigate to System -> Network Settings -> Ethernet Configuration. Record current IP address (typically 192.168.x.x), subnet mask (typically 255.255.255.0), and gateway settings.

On TNC 640 controls, you can access quick network info by pressing MOD then selecting 'System Information' without entering configuration mode.

Verify IP address uniqueness

From a PC on the same network, open command prompt and ping the TNC's IP address before the TNC is connected. If you receive replies, another device has the same IP. Use 'arp -a' command to identify the conflicting device MAC address.

Never assign static IPs without coordinating with facility IT department. DHCP conflicts can occur if static IP is within DHCP range.

Reconfigure network parameters

In TNC network settings, assign a unique static IP address outside the DHCP range but within the correct subnet. Verify subnet mask matches network infrastructure (typically 255.255.255.0 for /24 networks). Set gateway to your network router IP if external access is required.

Document the assigned IP address on a label inside the electrical cabinet. Standard practice is to use higher IP ranges (e.g., 192.168.1.200-250) for machine tools to separate from DHCP pools.

Restart network interface and test

After saving network configuration changes, perform a full TNC control restart (not just NC stop/start). Wait for complete boot sequence, then test LSV2 connection from programming station using TNCremo or file transfer operation.

The LSV2 service on some TNC controls can be restarted without full reboot by cycling the 'Network Service' option in MOD -> System -> Network -> Service Control, saving approximately 3-4 minutes.

Identify TNC software version

Press MOD key, select 'System Information' or 'About'. Record the complete software version number (e.g., 340 590-07 for TNC 320, or 817 600-02 for TNC 640). Note both the NC software and PLC software versions.

The LSV2 protocol version is embedded in the NC software version. Major version changes (e.g., 340 49x to 340 5xx) often introduce LSV2 protocol updates.