Delta DVPDT02-H2

Delta DVPDT02-H2 DeviceNet Slave Communication Module

Delta DVPDT02-H2 connects a DVP-EH2 series PLC to a DeviceNet network as a slave communication module. In an industrial communication system, it exchanges EH2 command, status and process data with the network master. Its master–slave role is the slave; it does not act as a DeviceNet scanner or master.

The module can exchange local EH2 station data with a central controller in applications resembling remote I/O stations. DeviceNet uses CAN, but sharing the CAN communication layer does not make a CANopen device directly compatible. Select both the required network protocol and the correct master/slave role.

CPU compatibility and operating features

The manufacturer specifies DVP-EH2 series CPUs only. Install the module on the EH2 right-side expansion interface with power removed. An H2 suffix or a similar housing is insufficient evidence of compatibility with another DVP family. Check the full CPU model, expansion arrangement and applicable documentation before installation.

The module supports Group 2 only server operation, I/O polling and explicit messaging. Network rates are 125, 250 and 500 kbit/s. The default data length is 32 bytes in each direction, configurable to 200 bytes in each direction. The slave settings and master scan-list lengths must match; apply changes using the documented download and power-cycle procedure.

Power supply, DeviceNet cable and connector pins

The CPU expansion interface supplies the module logic, while the DeviceNet network side also requires power. Supply network V+/V− with nominal 24 V DC, within the specified 11–25 V DC range. A running CPU does not prove that network power is present. Measure DC voltage at the module connector and consider voltage drop under load.

The network uses a removable five-position connector with 5.08 mm pitch. Manufacturer pin numbering is 1: V− / black / 0 V; 2: CAN_L / blue; 3: SHIELD / drain-shield; 4: CAN_H / white; 5: V+ / red / 24 V DC. Confirm the viewing direction against the wiring drawing rather than assuming a left-to-right order.

Use DeviceNet-rated cable with data and power pairs plus a shield. Terminate both trunk ends across CAN_H–CAN_L with 121 Ω, 1%, at least 1/4 W resistors; do not fit a resistor at every node. Consider electromagnetic interference, grounding and shield connections together. Select cable type, trunk/drop lengths and network speed according to ODVA installation guidance.

Node address, baud rate and data-hold setting

Valid decimal MAC IDs are 00–63; 64–99 are invalid. For address 26, set the tens switch to 2 and the units switch to 6. Each node needs a unique address. Change rotary and DIP settings with power removed; the changes take effect after power is restored.

In DR1/DR0 order: OFF/OFF = 125 kbit/s; OFF/ON = 250 kbit/s; ON/OFF = 500 kbit/s. ON/ON is invalid, not an automatic baud-rate setting. With IN0 OFF, buffer data is not retained on connection loss; with IN0 ON, it is retained. IN1 is reserved. Buffer retention does not provide an independent safety function for physical machine outputs.

Programming software and programming cable

The EH2 CPU’s PLC program can be developed in WPLSoft. ISPSoft is also an option when the exact EH2 CPU and software release support it; configure COMMGR where required. The ladder program transfers data between CPU registers and module control registers. Configure the EDS definition, scan list and I/O lengths with DeviceNet Builder or the selected master’s compatible DeviceNet configuration tool.

For the CPU’s 8-pin mini-DIN RS-232 programming port, use a UC-PRG020-12A USB-to-RS-232 programming cable. Alternatively, use a UC-MS020-01A serial cable with a suitable USB-to-RS-232 converter when necessary. Check the driver and COM-port selection. These cables connect to the CPU, not to the DVPDT02-H2 DeviceNet port. Network configuration also requires the access path supported by the selected master/interface.

Understanding the differences between RS-232, RS-422 and RS-485 helps identify the programming interface. A CPU’s RS-485/Modbus connection or Modbus RTU capability does not change this module’s protocol: DVPDT02-H2 is a DeviceNet device.

DFROM/DTO instructions and data direction

Access the control registers using DFROM/DTO instructions. CR#3–CR#102 carry data from the EH2/module to the DeviceNet master; CR#103–CR#202 carry data from the master to the EH2/module. Establish the direction before copying “input/output” labels from the master configuration into the PLC project. Distinguish bytes, words and doublewords when setting transfer lengths: 32 bytes = 16 words.

CR#0 identifies the model, CR#1 the firmware, CR#2 the I/O lengths and CR#251 the error information. CR#255 indicates CPU status: 0 = STOP, 1 = RUN. Do not write to system or reserved areas. Published documents differ on the model identification value, so verify CR#0 against the actual device and applicable document instead of using one universal constant.

LED indications and initial troubleshooting

POWER indicates supply status, NS network status and MS module status. Flashing green NS indicates an online device without an established master I/O connection; steady green indicates a connection. For red indications, evaluate duplicate addresses, timeouts, bus-off and supply problems using NS/MS together with CR#251. Check the master RUN state and scan list as well.

Editor’s Note

When buying a used unit, inspect its label and EH2 expansion connector first. Broken catches, oxidised pins, damaged rotary switches and a missing five-position plug can delay commissioning as much as an electronic fault. A lit POWER LED alone is insufficient proof of communication.

Bench-test with a known-good EH2 CPU, a compatible DeviceNet master and a short, correctly terminated network. Send different test values in both directions and watch them change in both the master and CPU registers. A one-way exchange is only a partial test.

With all power removed, approximately 50–60 Ω between CAN_H and CAN_L provides an initial termination check; it does not prove the whole network is healthy. After restoring power, measure V+/V− at the module rather than relying only on the power-supply output reading.

Retaining the last value with IN0 is not suitable for every process. Define motor, valve and output behaviour on communication loss in the project, and address emergency-stop and safety-relay functions within the machine’s safety arrangement.

Before component repair, verify the address, baud rate, EDS and I/O lengths. Then inspect terminal tightness, cracked joints and network-interface damage. Find the cause of any short circuit or incorrect network supply before replacing a CAN transceiver; otherwise the replacement may fail again.

Record the master configuration, MAC ID, DIP positions and firmware information as well as the CPU program before removing a working unit. These records make replacement commissioning much more predictable.

PDF files and technical documents

Use our Delta DVP PLC files page for model and series documentation. The DVPDT02-H2 Operation Manual covers DeviceNet wiring, the CR map and network configuration examples. Consult the cable selection guide for CPU connections and the ODVA cabling guide for network installation.

Related topics and navigation

DVPPF02-H2 serves PROFIBUS applications, while DVPCP02-H2 serves CANopen applications; these protocols are not interchangeable with DVPDT02-H2. Ethernet and the EtherNet/IP protocol also differ from DeviceNet. For a DeviceNet master role, examine DVPDNET-SL; its different CPU/interface architecture means it is not a direct plug-in replacement for an EH2 module.

Delta main page | Delta PLC | DVP PLC series | DVP-EH2 | DVP expansion modules | DVP H2 modules | DVPDT02-H2 models

External references

Delta manufacturer product information | Delta DVPDT02-H2 operation manual | ODVA DeviceNet cable planning and installation manual