235-006A

Inspect PROFINET Cable Connections

Check all PROFINET cable connections at the TNC CC (Communication Controller) X116 port and the PROFINET controller. Verify green link LEDs are illuminated on both ends indicating active connection.

Power off the control before reconnecting any network cables to avoid hot-plug network errors.

Test Cable Integrity

Replace suspected PROFINET cable with a known good CAT5e or CAT6 cable (minimum requirement). Ensure cable length does not exceed 100 meters for copper connections.

PROFINET uses standard Ethernet cables but requires specific color-coded industrial connectors (green) for certification - standard patch cables work but verify shielding is intact.

Verify Network Switch Operation

If using a managed switch between TNC and PROFINET controller, verify switch port LEDs are active and check switch configuration for port mirroring or VLAN settings that may block PROFINET traffic.

PROFINET requires Layer 2 network transparency - disable IGMP snooping and enable QoS/priority tagging on managed switches for optimal performance.

Access PROFINET Configuration

Press MOD key → select 'Communication Settings' → select 'PROFINET' → verify 'Device Name' exactly matches the name assigned in the PROFINET controller configuration (case-sensitive, no spaces unless specified).

PROFINET device names must follow DNS naming conventions - use only alphanumeric characters and hyphens, starting with a letter.

Verify IP Address Settings

In MOD → Communication Settings → PROFINET, check that IP address, subnet mask, and gateway match the network configuration. Typical format: IP 192.168.214.x, Subnet 255.255.255.0. Verify no duplicate IP addresses exist on the network.

Changing IP address requires a TNC reboot to take effect. Ensure machine is in safe state before rebooting.

Confirm PROFINET Controller Settings Match

Cross-reference TNC settings with PROFINET controller project (e.g., TIA Portal for Siemens). Device name, IP address, and GSD station configuration must be identical. Export controller configuration if needed for comparison.

Use the PROFINET controller's topology view to see if the TNC appears as 'not assigned' or 'name mismatch' - this directly indicates configuration discrepancy.

Reset PROFINET Configuration

If settings appear correct but alarm persists, reset PROFINET to defaults via MOD → Communication Settings → PROFINET → 'Reset to Default', then re-enter correct parameters from documented configuration sheet.

Resetting PROFINET configuration will clear all custom settings. Document current settings before reset.

Check PROFINET Controller Status

Inspect the PROFINET controller (PLC communication module) for error LEDs. Check PLC diagnostics for communication module faults. For Siemens controllers, verify BF (Bus Fault) and SF (System Fault) LEDs are off.

Most PROFINET controllers have web-based diagnostics accessible via browser - navigate to controller IP address to view detailed status and connected devices.

Verify Controller Scan Cycle Time

Access PROFINET controller diagnostics and verify scan cycle time is within normal range (typically <10ms). Extended cycle times or watchdog errors indicate controller overload or failure.

PLC program errors can cause PROFINET stack crashes. Review PLC program changes made prior to alarm occurrence.

Power Cycle PROFINET Controller

Perform controlled shutdown of PROFINET controller/PLC, wait 30 seconds, then power on. Allow full boot cycle (typically 30-60 seconds) before powering on TNC control. Monitor controller diagnostics during startup.

Coordinate with production team before power cycling PLC - this may affect other connected machines or processes.