Delta DVPCP02-H2
Delta DVPCP02-H2 CANopen Slave Communication Module
Delta DVPCP02-H2 connects a compatible DVP-EH2/EH3 PLC to a CANopen network as a slave station. This right-side expansion module exchanges PLC data with a supervisory controller in industrial communication applications. In the master–slave arrangement, DVPCP02-H2 performs the slave role; it does not provide a CANopen master by itself.
Protocol and data exchange
It supports CAN 2.0A and CANopen DS301 V4.02, with 8 TxPDOs, 8 RxPDOs and one SDO server, plus NMT, SYNC and Emergency messages. PDOs carry mapped process data; SDO access addresses supported object-dictionary parameters and data. TxPDO/RxPDO directions are named from the slave device’s perspective.
Status, commands and measured values held in the PLC CPU can be exchanged over the network. Data collected by input and output modules is mapped through the PLC; sensors are not wired directly to this communication port. The PLC program and PDO mapping determine where analog and digital input values appear in the bit/WORD data layout.
CPU compatibility and power
The original manual illustrates connection to DVP-EH2; Delta’s later selection catalogue also lists DVP-EH3. Before ordering, check the exact CPU code, hardware/firmware revision, right-side expansion connection and permitted number of special modules. The H2 suffix does not establish compatibility with every DVP or AS CPU.
24 V DC power is supplied through the CPU expansion connection; do not apply external power through the CAN connector. Check CPU/expansion DC supply capacity, total current budget and connector condition together. Switch off power before installing, removing or wiring the module.
Programming software and cables
Use WPLSoft for the CPU program, or ISPSoft after confirming that the installed release supports the actual CPU. In PLC programming, access module data with DFROM/DTO. Configure the network using CANopen Builder or the selected master’s engineering software, together with a matching EDS file, PDO mapping and NMT settings. Downloading the CPU program and downloading the master network configuration are separate operations.
The DVPACAB2A30 cable provides the PC-to-CPU programming connection through RS-232. A USB-only PC needs a suitable USB-to-RS-232 converter, its driver and the correct COM port. Observe the differences between RS-232, RS-422 and RS-485; do not connect this serial cable to the module’s CAN port. Use shielded twisted-pair CANopen cable with suitable terminations on the network side.
CAN connector and bus termination
The removable five-pole connector has a 5.08 mm pitch. Numbered pins are 1 = GND, 2 = CAN_L, 3 = SHLD, 4 = CAN_H, 5 = reserved. Check physical orientation against the module markings and manual. Do not apply 24 V to pin 5. The power-pin arrangement of a similar-looking DeviceNet connector must not be copied to this module.
Use a linear bus with short stubs and 120 Ω termination between CAN_H and CAN_L at the two physical ends. Arrange shielding and grounding according to the cabinet design. Route communication wiring separately from motor and drive power cables; select the permitted bus length for the chosen bit rate.
Node address and bit rate
Node-ID range is 1–127; the two rotary switches form a hexadecimal number. x16¹ selects the high digit and x16⁰ the low digit. For example, decimal 26 = hexadecimal 1A: set the high switch to 1 and the low switch to A. Hexadecimal 00 and 80–FF are invalid. Every station on the network needs a unique address.
In DR2/DR1/DR0 order: OFF/OFF/OFF = 10 kbit/s; OFF/OFF/ON = 20; OFF/ON/OFF = 50; OFF/ON/ON = 125; ON/OFF/OFF = 250; ON/OFF/ON = 500; ON/ON/OFF = 800; ON/ON/ON = 1000 kbit/s. IN0 is reserved. Set address and rate with power off; the settings take effect on the next power-up. The master and all nodes must use the same bit rate.
Control registers and DFROM/DTO example
CR#0 identifies the model, CR#1 reports firmware and CR#2 reports I/O data length. Input/output buffer names use the master’s perspective: CR#3–#102 carry PLC/module-to-master data; CR#103–#202 carry master-to-module/PLC data. Check these directions against the slave’s TxPDO/RxPDO mapping.
For special module number 0, DTO K0 K3 D100 K1 writes D100–D101 to CR#3–#4 for transfer to the master through the mapped PDO. DFROM K0 K103 D200 K1 reads incoming CR#103–#104 into D200–D201. K1 means one 32-bit transfer: two consecutive 16-bit WORDs. K0 is the CPU-side special-module number, not the CANopen node address; replace it with the actual module position.
The manufacturer specifically requires DFROM/DTO instead of FROM/TO for this model. Allocated CR buffers do not mean that every register is part of the active PDO exchange. Match data length, order and type to the master’s EDS/PDO configuration. Do not write reserved CR areas. Read CR#255 to monitor CPU state: 0 = STOP, 1 = RUN.
LED indicators and commissioning
POWER indicates supply. Green RUN is steady in Operational, blinking in Pre-operational and single-flashing in Stopped. Steady red ERR indicates bus-off; a single flash indicates warning-limit status and a double flash an error-control event. POWER alone does not confirm PDO exchange; inspect NMT state, mapping and master diagnostics together.
Editor’s Note
When buying a used module, a POWER light is not a complete test. Inspect its label, side expansion connector, rotary switches and removable CAN terminal block. Damaged switches or a missing terminal block can delay commissioning.
Use a compatible CPU and a known working CANopen master for a bench test. Send one WORD pattern and verify it at the other end, then test the reverse direction with a different pattern. This helps distinguish direction, byte-order and mapping faults.
With the complete bus powered off, two 120 Ω terminators should give approximately 60 Ω between CAN_H and CAN_L. This is a preliminary check only; address, bit rate and signal quality still require verification.
If RUN blinks but data does not change, start PLC debugging with the NMT Operational command, EDS revision and PDO lengths. Remember that K1 in the DFROM/DTO example transfers two WORDs; do not allocate the adjacent D register to another task.
Test bus disconnection, master shutdown and restart with machine loads isolated from the test setup. Configure heartbeat/node guarding and the PLC’s communication-loss response for the application; do not assume that every output automatically switches off. Back up the CPU program, network project and switch positions.
PDF manuals
Start with our Delta DVP PLC files page. The model-specific 50-page CANopen slave operation manual, document DVP-0205610-01, is in Chinese. It includes wiring, the CR map, DFROM/DTO operation and CANopen Builder examples. Match the EDS file to the device/firmware; a PDF manual is not an EDS file.
Related topics
See DVPCOPM-SL for a CANopen master arrangement belonging to a different CPU/expansion platform. DVPPF02-H2 is for PROFIBUS and DVPDT02-H2 for DeviceNet. Interfaces such as IFD9503 also require checking their role and data direction. Do not treat these devices as interchangeable by connector appearance or register map.
Integration with Modbus RS-485 or Ethernet requires an appropriate master/gateway architecture. Showing both data and network faults in SCADA helps operators distinguish a fresh measurement from a frozen value when designing the PLC–SCADA relationship.
Delta DVP PLC series | DVP expansion modules | DVP-H2 modules | DVPCP02-H2 model page | DVP file archive
External references
Delta DVPCP02-H2 product information | Delta DVP-0205610-01 Chinese operation manual — manufacturer-document archive copy | Delta DVPACAB2A30 programming-cable guidance