DeviceNet to ProfiNet Gateway for Zero-Downtime Retrofits

Project Background: The Integration Challenge

A major textile machinery manufacturer in East China embarked on a digital upgrade for a high-speed air-jet spinning line. The core controller selected was a Siemens S7-1500 PLC (model 6ES7 515-2AM01-0AB0), which communicates exclusively over ProfiNet IRT with a cycle time of ≤4 ms for servo axes handling yarn traverse and winding. However, the execution layer relied on 18 SMC VQ1000-DN DeviceNet bus valve manifolds, controlling 96 coils for pneumatic functions like splicing, cutting, and waste suction. Since the PLC only supports ProfiNet and the valves only DeviceNet, direct communication was impossible. Replacing all valve manifolds would cost over $30,000 and cause two weeks of downtime, which was rejected by the process team. The solution: deploy an industrial protocol gateway that acts as a ProfiNet slave to the PLC and a DeviceNet master to the valves, enabling transparent data exchange.

Network Topology and Hardware Setup

ProfiNet Side

• PLC: Siemens S7-1500 1515-2PN, firmware V2.9, IP 192.168.0.1, cycle 2 ms
• Switch: Siemens SCALANCE XB208, gigabit uplink to MES
• Gateway ProfiNet port: RJ45, supports IRT, station name “JM_GW”, IP 192.168.0.10

DeviceNet Side

• Gateway built-in configurable master, ODVA compliant, supports 0-63 nodes, 125 kbps to 500 kbps
• Valves: SMC VQ1000-DN, each with 4 dual-coil outputs, node addresses 10-27
• Bus power: 24 VDC 4 A, trunk cable: 5-core shielded (2 power + 2 signal + 1 shield), drop length ≤1 m, 120 Ω terminators at both ends

Control Cabinet Layout

The gateway was mounted on a 35 mm DIN rail in the right side of the control cabinet, with 24 VDC redundant power supply, power consumption <3 W, and 50 mm clearance on each side for heat dissipation. ProfiNet and DeviceNet ports were arranged on separate rows to avoid crosstalk.

Gateway Configuration Steps

1. Import GSDML File

In TIA Portal V17, under “Options – Manage general station description files”, import the GSDML file provided by the gateway vendor (e.g., GSDML-V2.35-jm-pn-dntm-20250607.xml). The device “JM-PN-DNTM” appears in the hardware catalog and can be dragged into the ProfiNet network.

2. Configure Data Lengths

With 96 coils, 12 bytes of output are needed (96/8). Similarly, 12 bytes of input for status feedback. In the PLC, set the gateway module to “12 Byte Output / 12 Byte Input”, mapping to addresses QW100-QW111 and IW100-IW111.

3. DeviceNet Master Parameters

Using the gateway’s configuration software (e.g., GatewayBuilder), connect via USB and select “PN→DeviceNet Master” mode:

• Baud rate: 500 kbps (bus length <50 m)
• Master MAC: 0
• Scan list: Add 18 VQ1000-DN nodes (addresses 10-27), each with 8 Byte IN/8 Byte OUT, automatically mapped to gateway internal registers 0-287

4. Data Mapping

The gateway slices the PLC’s 12-byte output into individual bits for the 96 coils, and packs the 96 valve status bits into 12 bytes of input for the PLC. This achieves a “write to control, read to see” behavior.

PLC Programming

Function Block for Pneumatic Control

Create an FB “PneumaticCtrl” with interface variables:

• Enable: Bool
• ValveMap: Array[0..95] of Bool (coil commands)
• StatusMap: Array[0..95] of Bool (feedback)

Data Transfer

In OB1, use MOVE instructions to write ValveMap to QW100-QW111 and read IW100-IW111 into StatusMap. The cycle is synchronized with ProfiNet refresh, ensuring <4 ms latency.

Fault Diagnostics

If any bit in IW100..IW111 indicates a communication timeout or DeviceNet disconnection, the PLC triggers an emergency stop and the HMI displays a “Node XX fault” message, allowing quick replacement of the valve manifold.

Commissioning and Testing

Single Device Test

Disconnect the load and connect only one VQ1000-DN at node 10. Use the configuration software to scan online. Once “Online” status is confirmed, manually set PLC Q100.0. The corresponding valve coil Y1 actuates, and the pressure gauge rises from 0.2 MPa to 0.6 MPa. Response time measured 18 ms, well within the SMC specification of ≤30 ms.

Full Line Dry Run

All 18 valve manifolds were connected. The PLC ran an idle program. ProfiNet cycle load was about 18%, DeviceNet had no error frames. After 2 hours of continuous operation, the gateway temperature stabilized at 42°C.

Production Trial

With yarn introduced, the line ran at 800 m/min high-speed winding. All 96 coils operated according to the process cycle for splicing, cutting, and waste suction. Compared to the previous setup, pneumatic cycle time improved by 12 ms. Output per shift (8 hours) increased from 1.84 t to 1.96 t, a 6.5% gain.

Key Lessons Learned

• Choose IRT-capable gateways for high-speed control: In textile applications with fast servo cycles, the gateway must support ProfiNet IRT to keep jitter below 1 µs. This ensures compatibility with Siemens 1500’s 2 ms cycle.
• Proper DeviceNet wiring is critical: Separate power and signal cables, and never omit the 120 Ω terminators. With 96 nodes, heavy loading can cause bit errors if wiring is not robust.
• Use byte-aligned data mapping: This simplifies PLC code with MOVE and XOR instructions, making the program easier to maintain.
• Reserve I/O capacity: Leave at least 20% spare I/O for future expansion, avoiding another retrofit later.

Frequently Asked Questions