1. Problem Description & Scope

This troubleshooting guide addresses PLC communication failures in industrial automation systems using fieldbus protocols such as Profinet, EtherNet/IP, and Modbus. These failures can manifest as intermittent connectivity, complete loss of communication, or inconsistent data transfer. Affected equipment includes programmable logic controllers (PLCs), human-machine interfaces (HMIs), motor drives, and remote I/O modules. The severity of these issues is classified as critical when system downtime or safety-critical functions are impacted, major when partial functionality is lost, and minor when communication is degraded but not fully interrupted.

2. Safety Precautions

Lockout/Tagout (LOTO): Ensure all power sources to the PLC and fieldbus network are isolated and tagged before performing any diagnostic work.

PPE: Wear insulated gloves, safety glasses, and a face shield when working with live electrical components. Use a grounded wrist strap when handling sensitive electronics.

Stored Energy: Capacitors in power supplies and fieldbus couplers can retain charge even after power is disconnected. Discharge them before handling.

Hazardous Conditions: Avoid working in environments with flammable gases or vapors. Use explosion-proof tools and equipment where required by NFPA 70 and IEC 60079.

3. Diagnostic Tools Required

4. Initial Assessment Checklist

5. Systematic Diagnosis Flowchart

1. Check for Power and Physical Connectivity
   1. Verify all power supplies are operational and within ±10% of nominal voltage.
   2. Inspect all fieldbus cables for frayed insulation, exposed conductors, or loose terminations.
   3. Ensure all connectors are fully seated and secured with appropriate torque.
2. Check for Communication Errors in PLC/HMI
   1. Review the PLC/HMI event log for communication error codes (e.g., 10001 for Profinet, 121 for EtherNet/IP).
   2. Verify the communication status of each node in the network.
   3. Confirm that the network protocol settings (e.g., IP address, subnet mask, gateway) are correct and consistent.
3. Check for Cable Faults Using Fluke 1792
   1. Measure insulation resistance between conductors and ground. Acceptable value: ≥10 MΩ.
   2. Perform continuity test between each pair of conductors. Resistance should be ≤0.1 Ω.
   3. Test for crosstalk and impedance mismatch. Acceptable range: 100–120 Ω for twisted-pair cables.
4. Check for Signal Integrity Using Fluke 434 II or Keysight N9020B
   1. Measure voltage levels on fieldbus lines. Acceptable range: 24 V DC ±5% for Profinet.
   2. Use a spectrum analyzer to check for noise or interference. Acceptable signal-to-noise ratio: ≥20 dB.
   3. Verify signal timing and synchronization. Acceptable jitter: ≤10 ns for high-speed protocols.
5. Isolate and Test Individual Nodes
   1. Disconnect and power down one node at a time.
   2. Reconnect and test communication to determine if the issue is localized to a single node.
   3. Use a loopback test to verify the node’s ability to transmit and receive data.
6. Check for Network Topology and Configuration Errors
   1. Verify the physical and logical topology of the network matches the configuration.
   2. Ensure all nodes are assigned unique addresses and are properly registered in the network.
   3. Confirm that the network redundancy and failover settings are correctly configured.
7. Check for Environmental Factors
   1. Use a thermal imaging camera to identify overheating components or junctions.
   2. Measure ambient temperature and humidity. Acceptable range: 0–50°C, 20–80% RH.
   3. Verify that the installation meets ANSI/ISA-84.00.01 and IEC 61508 standards for safety-related systems.

6. Fault-Cause Matrix

7. Root Cause Analysis for Each Fault

7.1. Fault: Intermittent Communication

Root Cause: Intermittent communication is typically caused by physical damage to fieldbus cables, power supply fluctuations, or electromagnetic interference (EMI). These issues can lead to signal degradation or complete loss of connectivity.

How to Confirm: Use the Fluke 1792 to test insulation resistance and continuity. Measure power supply output with Fluke 434 II and check for voltage fluctuations. Use the Keysight N9020B to analyze signal noise and interference.

Damage if Unresolved: Continuous signal degradation can lead to data corruption, incorrect control actions, and potential safety failures in critical systems. This can result in production downtime, equipment damage, and safety hazards.

7.2. Fault: Complete Communication Loss

Root Cause: Complete communication loss is often due to a disconnection or open circuit in the fieldbus cable, a power failure, or a failure in a fieldbus coupler or repeater. It can also be caused by a software crash in a node.

How to Confirm: Use the Fluke 1792 to test for open circuits. Verify power supply output with Fluke 434 II. Test the fieldbus coupler with Fluke 434 II. Reboot the node and check its communication status.

Damage if Unresolved: Loss of communication can result in uncontrolled equipment operation, safety system failures, and complete system shutdown. In safety-critical applications, this can lead to hazardous conditions and potential injury.

7.3. Fault: Inconsistent Data Transfer

Root Cause: Inconsistent data transfer is typically caused by impedance mismatch in fieldbus cables, signal degradation due to noise or crosstalk, incorrect baud rate or sampling frequency settings, or software incompatibilities.

How to Confirm: Measure impedance with Fluke 434 II. Use Keysight N9020B to analyze signal integrity and noise. Verify baud rate and sampling frequency settings. Check firmware and software versions.

Damage if Unresolved: Inconsistent data transfer can lead to incorrect control signals, system instability, and potential safety failures. In high-speed fieldbus networks, this can also cause data corruption and loss of critical control functions.

8. Step-by-Step Resolution Procedures

8.1. Resolution for Intermittent Communication

1. Inspect all fieldbus cables for physical damage, loose connections, or exposed conductors.
2. Replace any damaged cables with UNITEC-D fieldbus cables rated for the specified protocol and voltage.
3. Check power supply output and stabilize voltage using a voltage regulator if necessary.
4. Install shielding and grounding to reduce electromagnetic interference (EMI).
5. Verify network configuration and ensure all nodes are properly registered.
6. Monitor communication status using PLC/HMI event logs and perform regular diagnostics.

8.2. Resolution for Complete Communication Loss

1. Isolate and test each node individually to identify the faulty node.
2. Replace any faulty nodes with UNITEC-D PLCs or I/O modules that meet the required specifications.
3. Inspect and replace damaged fieldbus cables and connectors with UNITEC-D fieldbus cables.
4. Verify power supply output and ensure all power sources are stable and within tolerance.
5. Reconfigure fieldbus couplers and repeaters to ensure proper operation.
6. Perform a full network reset and reconfigure all nodes using the appropriate configuration tool.

8.3. Resolution for Inconsistent Data Transfer

1. Measure and adjust fieldbus cable impedance to fall within the acceptable range of 100–120 Ω.
2. Replace cables with UNITEC-D fieldbus cables that have proper shielding and termination.
3. Use a spectrum analyzer to identify and mitigate sources of noise or interference.
4. Verify that baud rate and sampling frequency settings match the protocol specifications.
5. Update firmware and software on all nodes to the latest version.
6. Monitor data transfer integrity using PLC/HMI diagnostics and perform regular maintenance checks.

9. Preventive Measures

10. Spare Parts & Components

For spare parts and components, visit the UNITEC-D e-catalog at https://www.unitecd.com/e-catalog/

11. References

• ANSI/ISA-84.00.01-2004: Safety Instrumented Systems for the Process Industry Sector
• IEC 61508: Functional Safety of Electrical/Electronic/Programmable Electronic Safety-related Systems
• IEC 61131-3: Programmable Controllers
• IEEE 1588: Precision Clock Synchronization for Networked Measurement and Control Systems
• Profinet Technical Specification: Version 2.3
• Modbus Protocol Specification: Version 3.0
• UNITEC-D Maintenance Guide: Fieldbus Troubleshooting and Repair

Problem Description & Scope

This guide addresses critical communication failures affecting Programmable Logic Controllers (PLCs) and their interconnected field devices within industrial automation systems. Specifically, it focuses on diagnosing and resolving issues pertaining to common industrial fieldbus protocols including PROFINET, EtherNet/IP, and Modbus (TCP/RTU). Communication failures can manifest in various ways:

• Intermittent Communication Loss: Sporadic data transfer interruptions, leading to erratic machine behavior or brief process halts.
• Total Communication Loss to a Single Node: Complete isolation of an individual field device (e.g., I/O module, variable frequency drive, HMI) from the PLC.
• System-Wide Communication Failure: Complete loss of network connectivity across multiple PLCs or entire production lines, often resulting in emergency stops and significant downtime.
• Degraded Performance: Increased network latency, jitter, and slow data updates, impacting real-time control and process efficiency.

Affected equipment typically includes PLCs (e.g., Siemens S7, Rockwell ControlLogix/CompactLogix, Schneider Modicon), remote I/O blocks, industrial Ethernet switches, managed and unmanaged field devices, HMIs, VFDs, and servo drives. Communication failures are classified as:

• Critical: Immediate production stoppage, safety system compromise, or significant equipment damage potential.
• Major: Production degradation, intermittent faults requiring operator intervention, or reduced product quality.
• Minor: Warning alarms, non-critical data loss, or slight performance reduction not immediately impacting production.

Safety Precautions

WARNING: Prioritize safety. All diagnostic and resolution procedures involving electrical equipment or energized machinery must adhere to strict safety protocols. Failure to comply can result in severe injury, fatality, or extensive equipment damage.

• LOCKOUT/TAGOUT (LOTO): Always follow established LOTO procedures per NFPA 70E (Standard for Electrical Safety in the Workplace) or local equivalent standards before working on any electrical circuit or moving machinery. Verify zero energy state using appropriate test equipment.
• PERSONAL PROTECTIVE EQUIPMENT (PPE): Utilize appropriate PPE including, but not limited to, arc flash rated clothing (as determined by arc flash analysis), insulated gloves (rated for voltage), safety glasses, and hearing protection.
• STORED ENERGY: Be aware of and safely discharge any stored energy in capacitors, pneumatic accumulators, or hydraulic systems before starting work.
• HAZARDOUS VOLTAGES: Industrial control systems frequently utilize hazardous voltages (e.g., 24VDC, 120VAC, 230VAC, 480VAC). Exercise extreme caution. Never bypass safety interlocks.
• GROUNDING: Ensure all diagnostic equipment is properly grounded. Avoid creating ground loops when connecting test equipment.

Diagnostic Tools Required

Accurate diagnosis relies on specialized tools and their correct application. Ensure all test equipment is calibrated per manufacturer specifications and industry standards.

Initial Assessment Checklist

Before initiating invasive diagnostic procedures, conduct a thorough visual and logical assessment. This minimizes troubleshooting time and helps narrow down potential root causes.

Systematic Diagnosis Flowchart

This flowchart provides a decision-tree approach to isolating communication faults, moving from the most general to the most specific diagnostic steps.

1. Initial PLC Communication Failure Detected
   1. Check PLC/Device Status and Logs
      1. Are PLC/Device error LEDs illuminated or flashing red/amber?
      2. Review PLC diagnostic buffer and HMI/SCADA alarm history for communication faults.
      3. IF error LEDs are red/amber OR logs indicate specific device faults:
         1. Proceed to Fault-Cause Matrix and focus on device-specific probable causes.
      4. ELSE IF error LEDs are normal (green) AND logs show general network errors or intermittent issues:
         1. Proceed to Step 1.b.
   2. Verify Physical Layer Integrity
      1. Perform Initial Assessment Checklist items for physical inspection.
      2. Visually inspect all suspect cables (Ethernet, RS-485, fiber) for damage (cuts, kinks, crushed sections) and proper routing (avoiding sharp bends, exceeding bend radius).
      3. Ensure all connectors are securely seated and latched.
      4. IF physical damage or loose connection is found:
         1. Repair or Replace. Proceed to Step-by-Step Resolution Procedures for Cable Damage.
      5. ELSE IF physical layer appears intact:
         1. Proceed to Step 1.c.
   3. Perform Basic Network Connectivity Test
      1. From a connected laptop, attempt to ping the IP address of the problematic PLC or field device.
      2. IF ping fails:
         1. Proceed to Step 1.d.
      3. ELSE IF ping succeeds, but communication via PLC software or HMI still fails:
         1. Proceed to Step 1.e.
   4. Diagnose Network Configuration & Electrical Issues (No Ping)
      1. Use a Multimeter to verify power supply to the device.
      2. Check IP address, Subnet Mask, and Gateway settings on the device and compare to network documentation.
      3. IF power issue or IP configuration mismatch is found:
         1. Rectify. Proceed to Step-by-Step Resolution Procedures for Incorrect Network Configuration or Device Power Issues.
      4. ELSE IF power and IP configuration appear correct for Ethernet/IP or PROFINET, but still no ping:
         1. Isolate the device by connecting it directly to a known-good switch or laptop (if possible) to rule out network infrastructure issues.
         2. IF device communicates directly: Troubleshoot the upstream network switch or cable.
         3. ELSE IF device fails to communicate directly: Suspect a faulty device. Proceed to Step-by-Step Resolution Procedures for Faulty Network Device.
      5. ELSE IF for Modbus RTU (RS-485):
         1. Use a Multimeter to check termination resistors (should be ~60 Ohm across A and B lines with power off).
         2. Use an Oscilloscope to verify differential signal integrity (look for square waves, absence of severe noise/reflections).
         3. IF termination issue or severe signal degradation:
            1. Proceed to Step-by-Step Resolution Procedures for Modbus RTU Specific Issues.
   5. Deep-Dive Protocol & Performance Diagnostics (Ping Success, but Application Failure)
      1. Connect an Industrial Network Analyzer or a laptop with Wireshark (for basic capture) to the network segment.
      2. Monitor network traffic for:
         1. CRC (Cyclic Redundancy Check) Errors: High numbers indicate signal integrity issues, EMI, or faulty transceivers.
         2. Retransmissions: Indicates dropped packets, often due to noise, collisions, or network congestion.
         3. Jitter & Latency: High values impact real-time control.
         4. Network Load/Bandwidth Utilization: Excessively high load can cause delays. Thresholds vary by protocol, but sustained >70% utilization often indicates congestion.
         5. Duplex Mismatch: Check switch port settings vs. device settings.
         6. Incorrect Device Names/IDs (PROFINET): Verify device names match PLC configuration.
         7. Incorrect Connection Parameters (EtherNet/IP CIP): Check RPI (Requested Packet Interval) settings.
         8. Modbus Function Code Errors: Indicate protocol interpretation issues.
      3. IF specific protocol errors (CRC, retransmissions, name/ID mismatch) are identified:
         1. Proceed to Step-by-Step Resolution Procedures corresponding to the identified root cause (e.g., EMI/RFI, Incorrect Network Configuration, Faulty Network Device).
      4. ELSE IF general performance degradation (high load, jitter) is observed:
         1. Consider network segmentation, adding managed switches, or optimizing PLC scan cycles to reduce network traffic.

Fault-Cause Matrix

This matrix correlates common symptoms with their probable causes, diagnostic tests, and expected results.

Root Cause Analysis for Each Fault

Understanding the underlying reasons for communication failures is paramount for effective prevention and long-term reliability.

Cable Damage/Poor Termination

• Why it happens: Industrial environments expose cables to physical stress (impacts, abrasion), chemical degradation, excessive bending radius beyond manufacturer specifications (e.g., <10x cable diameter for fixed installation), and improper installation techniques (e.g., incorrect crimping, lack of strain relief). Vibration, tension, and temperature fluctuations also contribute to conductor fatigue or insulation breakdown.
• How to confirm it: A cable certifier (e.g., Fluke DSX-8000) provides definitive proof by testing against ANSI/TIA-568-C.2 or IEC 61918 standards. Look for failures in wire map, continuity, insertion loss (>24 dB at 100 MHz for Cat5e), return loss (<17 dB at 100 MHz for Cat5e), or NEXT (<39 dB at 100 MHz for Cat5e). Visual inspection may reveal cuts, kinks, or crushed sections. For fiber optics, an OTDR will show breaks or high attenuation points, and an inspection scope will reveal dirty or damaged end-faces.
• Damage if left unresolved: Intermittent data corruption, total communication loss, increased retransmissions leading to network congestion, and potential damage to connected device communication ports due to electrical shorts or impedance mismatches.

Incorrect Network Configuration

• Why it happens: Human error during initial setup or modification. This includes duplicate IP addresses within the same subnet, incorrect subnet masks preventing proper routing, conflicting PROFINET device names, improper EtherNet/IP RPI (Requested Packet Interval) settings that overload devices, or incorrect Modbus addressing. Firmware incompatibilities between devices or PLC controllers can also manifest as configuration issues.
• How to confirm it: Utilize PLC programming software (e.g., Siemens TIA Portal, Rockwell Studio 5000) to cross-reference device configurations against the PLC project. Use network scanning tools (e.g., Advanced IP Scanner, device-specific discovery tools) to identify active IP addresses and potential conflicts. For PROFINET, ensure device names resolve correctly via the PLC. For Modbus, verify slave IDs and register maps.
• Damage if left unresolved: Persistent communication failures, incorrect data exchange, inability to control devices, and potential for data corruption leading to process errors or safety interlock bypasses.

Electromagnetic Interference (EMI) / Radio Frequency Interference (RFI)

• Why it happens: Unshielded or poorly shielded network cables routed too close to high-power electrical conductors, Variable Frequency Drives (VFDs), motor contactors, welding equipment, or other noise-generating sources. Improper grounding techniques (e.g., ground loops) can also introduce noise. These electrical disturbances induce unwanted signals onto communication lines, corrupting data packets.
• How to confirm it: Network analyzers will report elevated CRC errors and retransmissions. An oscilloscope connected to the data lines can visually display noise spikes or distortion overlaid on the data signal. An EMI field strength meter can help locate the source of interference. Relocating the cable or temporarily shielding it can serve as a diagnostic test.
• Damage if left unresolved: Intermittent data loss, increased network latency due to retransmissions, degraded system performance, and potential for false sensor readings or control commands, leading to process upsets or equipment damage.

Faulty Network Device (Switch, I/O Module, PLC Port)

• Why it happens: Component aging, electrical overstress (e.g., power surges, short circuits), excessive heat, or physical damage. Manufacturing defects, though rare, can also occur.
• How to confirm it: Observe device error LEDs, check diagnostic logs within the PLC or device web interface. Perform loopback tests (if supported) on suspected ports. If feasible and safe, temporarily swap the suspected device with a known-good spare. A network analyzer might show a specific port or device generating malformed packets or failing to respond.
• Damage if left unresolved: Complete isolation of critical production segments, failure of entire I/O subsystems, or unreliable control leading to significant downtime and production losses.

Step-by-Step Resolution Procedures

Execute these procedures only after identifying the specific root cause. Always follow LOTO and PPE guidelines.

Resolution for Cable Damage/Poor Termination

1. WARNING: Perform Lockout/Tagout (LOTO) procedures per NFPA 70E or local equivalent before handling any electrical cabling. Verify zero energy state.
2. Visually inspect the suspected cable along its entire length for any signs of physical damage: cuts, kinks, abrasions, tight bends, or crushed sections. Pay close attention to entry/exit points of conduits and cable trays.
3. Use a calibrated Cable Certifier (e.g., Fluke DSX-8000) to test the suspected cable.
4. For copper Ethernet, perform a Category 6A test. Acceptable thresholds: Wire Map: PASS, Length: within 10% of documented length, Propagation Delay: <555 ns, Delay Skew: <50 ns, Insertion Loss: <24 dB @ 100 MHz, Return Loss: >17 dB @ 100 MHz, NEXT: >39 dB @ 100 MHz, PSNEXT: >37 dB @ 100 MHz.
5. For fiber optic cables, use an OTDR to identify exact break points or high attenuation. Use a Fiber Inspection Scope to examine connector end-faces; clean or re-terminate if contamination/damage is present. Acceptable loss for a single splice: <0.1 dB; for a single connector: <0.75 dB.
6. If the cable fails any critical test or shows visible damage, replace it with a new industrial-grade shielded cable (e.g., Belden DataTuff CAT6A for Ethernet, or suitable industrial fiber optic cable). Ensure the replacement cable meets or exceeds original specifications (e.g., PUR or TPE jacket for oil resistance).
7. Terminate new cables using industrial-grade connectors (e.g., Phoenix Contact M12, Panduit TX6A RJ45) following manufacturer’s instructions. Ensure proper crimping and shielding connection to the connector body.
8. Re-test the newly installed or repaired cable with the Cable Certifier to confirm compliance.
9. Remove LOTO, restore power, and verify communication via PLC programming software (e.g., online diagnostics, I/O status) and HMI.

Resolution for Incorrect Network Configuration

1. Access the configuration interface of the problematic device (e.g., web interface, PLC programming software).
2. Verify the IP address, Subnet Mask, and Gateway settings against the official network documentation.
3. Ensure no duplicate IP addresses exist on the network. Use a network scanner (e.g., Advanced IP Scanner) to identify all active IPs.
4. For PROFINET, verify that the PROFINET device name matches the name configured in the PLC project. Use the PLC software (e.g., Siemens TIA Portal ‘Assign PROFINET device name’) to correct if necessary.
5. For EtherNet/IP, check the RPI (Requested Packet Interval) settings for consumed and produced tags. Ensure RPIs are appropriate for the network load and device capabilities; overly aggressive RPIs can overload a device or network.
6. For Modbus RTU (RS-485), confirm the slave ID, baud rate (e.g., 9600, 19200, 38400, 115200 bps), parity (None, Even, Odd), and stop bits (1 or 2) match the master PLC’s configuration.
7. Save all configuration changes and restart the device if required.
8. Verify communication through PLC software (online mode), HMI, and/or by pinging the device.

Resolution for Electromagnetic Interference (EMI) / Radio Frequency Interference (RFI)

1. Identify potential sources of EMI/RFI (VFDs, motors, power lines) near the communication cable path.
2. Ensure all network cables are shielded (e.g., SF/UTP or F/UTP for industrial Ethernet) and that the shield is properly terminated and grounded at one end (or both ends via common ground for high-frequency noise, ensuring no ground loops are formed).
3. Maintain minimum separation distances between network cables and power cables. As per IEEE standards, maintain at least 150mm (6 inches) for parallel runs; greater separation is required for higher voltage or current power lines.
4. Verify proper grounding of all industrial equipment and network components. Use a ground loop tester or a multimeter (resistance to earth ground <5 Ohms) to check for common-mode noise issues.
5. Consider installing ferrite beads or common-mode chokes on network cables near noise sources to suppress high-frequency noise.
6. If possible, reroute communication cables away from known EMI sources. Use metallic conduit for added shielding if necessary.
7. Use a Network Analyzer to monitor CRC errors. If CRC errors decrease significantly after implementing mitigation steps, EMI/RFI was the probable cause.

Resolution for Faulty Network Device

1. WARNING: Before replacing any electrical device, perform Lockout/Tagout (LOTO) procedures per NFPA 70E or local equivalent. Verify zero energy state.
2. Access the device’s diagnostic information via the PLC software or its web interface. Look for specific fault codes or status messages indicating internal hardware failure.
3. If available, perform a loopback test on the communication port to verify its transmit and receive functionality.
4. If a known-good spare device is available, and it is safe to do so under LOTO, replace the suspected faulty device.
5. After replacement, power up the new device and configure its network parameters (IP address, subnet mask, PROFINET name, Modbus ID) according to network documentation.
6. Verify communication via PLC programming software (online diagnostics), HMI, and basic network tests (ping).
7. If the issue persists after replacing the device with a known-good spare, re-evaluate the previous diagnostic steps; the fault may lie upstream (e.g., cabling, power supply) or with the PLC communication module itself.

Preventive Measures

Proactive maintenance and adherence to industrial standards significantly reduce the likelihood of communication failures, enhancing system reliability and overall ROI.

Spare Parts & Components

Maintaining a critical stock of spare parts minimizes downtime during communication failures. Ensure spares meet or exceed the specifications of installed components and carry relevant certifications (UL, CSA, CE).

For a comprehensive selection of industrial networking components, PLC spares, and related accessories, visit the UNITEC-D e-catalog at UNITEC-D E-Catalog.

References

• ANSI/TIA-568.0-D: Generic Telecommunications Cabling for Customer Premises.
• ANSI/TIA-568.1-D: Commercial Building Telecommunications Infrastructure Standard.
• ANSI/TIA-568.2-D: Balanced Twisted-Pair Telecommunications Cabling and Components Standard.
• NFPA 70E: Standard for Electrical Safety in the Workplace.
• IEC 61784-2: Industrial communication networks – Profiles – Part 2: Additional fieldbus profiles for real-time networks (PROFINET, EtherNet/IP).
• IEC 61918: Industrial communication networks – Installation of communication networks in industrial premises.
• IEEE 802.3: Standard for Ethernet.
• ODVA (Open DeviceNet Vendor Association): EtherNet/IP Specification.
• PI (PROFIBUS & PROFINET International): PROFINET System Description and Guidelines.
• Modbus Organization: Modbus over Serial Line Specification and Implementation Guide; Modbus Messaging on TCP/IP Implementation Guide.
• OEM Troubleshooting Manuals for specific PLC manufacturers (Siemens, Rockwell Automation, Schneider Electric).