235-003F

Inspect Network Device LEDs

Check all ProfiNet devices in the network for proper LED status. Green LED indicates good link, flashing green shows data exchange, red or no LED indicates failure. Start with devices closest to the TNC control and work outward through the topology.

Heidenhain TNC controls typically use X116 or X126 Ethernet ports for ProfiNet - verify you're checking the correct port on the control cabinet.

Verify Cable Integrity

Inspect all industrial Ethernet cables (must be CAT5e or better, shielded for industrial environments) for pinching, cuts, or damage. Check that all RJ45 connectors are fully seated with audible click and examine for bent pins or contamination.

Only use industrial-grade shielded Ethernet cables rated for the machine environment. Standard office patch cables cause intermittent communication errors.

Test Cable Continuity

If cable damage is suspected, replace suspect cable with known-good industrial Ethernet cable. ProfiNet requires proper pin-out (1-1, 2-2, etc.) and shield continuity for reliable operation.

Keep a 2-meter certified industrial Ethernet patch cable in your service kit for quick substitution testing.

Access ProfiNet Diagnostics

Navigate to MOD function key → Settings → Network Settings → ProfiNet Configuration. Review the device list to identify which specific device shows communication error (typically marked in red or with error icon).

The TNC will show device name and station address - note the exact device showing the fault before proceeding.

Verify Device Address Configuration

Check that the ProfiNet device name and IP address match the configuration in the TNC. Each device must have unique device name set via DIP switches or configuration software. Compare physical device settings with TNC configuration.

Never change ProfiNet device addressing while the control is powered on and communicating - always power down the network first.

Check GSDML File Version

Verify the GSDML device description file loaded in the TNC matches the actual hardware revision and firmware version of the ProfiNet device. Mismatched GSDML files cause data telegram length errors.

After TNC software updates, GSDML files may need updating. Check the Heidenhain software release notes for ProfiNet device compatibility changes.

Validate Network Topology

Confirm the physical arrangement of ProfiNet devices matches the configured topology in the TNC. Linear (daisy-chain) topologies must have proper beginning and end points. If using switches, verify port assignments match configuration.

Draw or photograph the actual ProfiNet cable routing and compare to the TNC's configured network diagram to spot topology mismatches.

Isolate Failed Device

Using the device information from MOD → Network Settings → ProfiNet, identify the specific non-responding device. Temporarily remove this device from the network by disconnecting its Ethernet connection and bypass it to restore communication to downstream devices.

Ensure machine is in safe condition and e-stop is active before disconnecting ProfiNet devices, as this may affect safety circuit monitoring.

Test Device in Isolation

Connect the suspect device directly to the TNC's ProfiNet port (if possible) or to a ProfiNet test setup. Power cycle the device and monitor for proper boot sequence and network activity LEDs.

Many ProfiNet devices have diagnostic web interfaces - connect a laptop to the device's Ethernet port and browse to its IP address to check internal diagnostics.

Verify Device Power Supply

Check that the ProfiNet device has stable 24VDC power supply within specification (typically 20.4-28.8VDC). Measure voltage at device terminals under load. Low or fluctuating power causes communication processor resets.

ProfiNet communication modules draw higher current during startup - verify power supply can handle inrush current of all devices powering up simultaneously.