Troubleshooting
Connecting a Delta DVP 15MC PLC to a Weintek HMI
Short answer
The DVP 15MC exposes its data to an HMI as a Modbus TCP server on the standard port 502. In EasyBuilder Pro, use a 15MC-specific driver if your editor's driver list has one, otherwise the generic Modbus TCP driver with the controller's register-to-Modbus mapping table. A 64-bit QWORD spans four holding registers, so prove one read-only tag before building screens.
On this page
Yes — over Ethernet. The DVP 15MC serves its data as a Modbus TCP server on the standard port 502, and a Weintek panel reaches it with either a 15MC-specific driver, if your editor's driver list includes one, or the generic Modbus TCP driver plus the controller's register-to-Modbus table. CANopen Builder, the tool you program the 15MC with, plays no part in that link. The trap that bites every migration from DVP SE or 28SV projects is width: the 15MC organizes its variables as 64-bit QWORDs, and each one spans four 16-bit Modbus registers. Pick the driver, map one address correctly, prove it with a single read-only tag, then build the screens.
What the 15MC exposes on the wire #
The 15MC is a motion controller that also runs a Modbus TCP server on its Ethernet port, so the HMI conversation is plain Modbus: holding-register reads and writes against a published map. The DVP15MC11T manual carries a table titled "Table of Registers and Corresponding Modbus Addresses" for the motion-control registers, and that table — not a DVP-SE address list — is the source for every tag you create.
Two conventions in it need translation before you type anything into the HMI. Delta's DVP Modbus documentation prints addresses in hexadecimal while the HMI address field takes decimal, and the holding-register area counts 4x references from 40001 while the protocol itself numbers offsets from zero; decoding Modbus holding register 4500001 from PLC to HMI shows how those numbering styles map onto each other. The 15MC's variables are QWORD-based, 64-bit quantities, which is exactly why its map differs from the WORD-based DVP series you used before.
CANopen Builder does not configure the HMI link #
You programmed the SE and 28SV with ISPSoft and the 15MC with CANopen Builder, and that change is where the confusion starts. The tool that writes the motion program does not select, configure or restrict the protocol an HMI uses: CANopen Builder handles the axes and the CANopen device network, while the panel talks to the controller's Ethernet Modbus TCP service, whose settings are the controller's IP configuration plus whatever the HMI project requests. Decision: when the panel cannot connect, stop searching the motion project. The fault lives in one of three places — the driver selected in the HMI, the network path, or the address map — and the sections below clear them in that order.
Pick the driver before you build a single tag #
Device properties in EasyBuilder Pro list every controller driver that release supports, and Weintek publishes a driver list per protocol for its panels, so this check takes a minute. Open the device list in your installed editor and match what you see:
| What the driver list shows | Decision |
|---|---|
| A driver named for the DVP-15MC | Select it and address variables directly in that driver's documented format; this is the shortest path. |
| A generic Modbus TCP driver | Select it; every address comes from the 15MC register-to-Modbus table, converted as shown below. |
| Only the DVP drivers the old SE/28SV project used | Do not reuse them, and do not reuse that project's addresses; the 15MC is not those series. |
| No usable driver for the panel model | Update the editor to the release whose list you checked; if there is still none, the panel is the limit, not the controller. |
Both a dedicated driver and the generic Modbus route are legitimate when their documentation covers the controller. Prefer the dedicated driver when it exposes the 15MC variables by name; use the generic Modbus TCP driver when you only need the mapped registers.
The width arithmetic that sets every address #
Modbus moves data in 16-bit holding registers, so a variable's declared type decides how many registers it occupies and how far apart consecutive variables sit:
| Variable type | Bits | Holding registers spanned | Stride to the next variable |
|---|---|---|---|
| WORD | 16 | 1 | 1 |
| DWORD | 32 | 2 | 2 |
| QWORD | 64 | 4 | 4 |
Worked example, with an illustrative address. Suppose the manual lists a QWORD variable at Modbus offset 0x30. Convert first: 0x30 = 3 × 16 + 0 = 48 decimal. The 4x read reference is then 40001 + 48 = 40049, and because the payload is 64 bits it occupies registers 40049 through 40052 (64 ÷ 16 = 4). The next QWORD in that block starts at 40049 + 4 = 40053, not at 40050. Enter 40049 in the HMI with the tag format set to 64-bit and the read returns the whole value; enter a 32-bit format and you fetch registers 40049 and 40050 only — half the payload — and the display truncates or jumps.
Values wider than one register also have a word order, and the four words of a QWORD can be arranged more than one way; Weintek's Modbus drivers expose word-order options per tag. When a value is readable but wildly wrong, the fault is width or word order, not the connection — displaying a PLC real value over Modbus on an HMI walks the same diagnosis for a two-register value.
Prove the path with one read-only tag #
Use a variable that cannot command motion or an output — a counter or an elapsed-time accumulator — and keep the test object read-only until the mapping is proven.
- Back up the HMI project, then add one device: the 15MC's actual IP address, port 502, and the station number from the controller's Ethernet configuration.
- Confirm panel and controller share a subnet and that no other device holds the controller's IP.
- Build a single numeric display bound to the test QWORD at its mapped 4x address, format 64-bit, no scaling.
- Download and watch the panel's communication status: a device fault at this point is the driver or the network; a rejected request is the address.
- Compare the display with the controller's online value, then change the test variable in the controller and confirm the display follows within one update period.
That one object proves driver, path, address, width and interpretation together. If it works, a later screen fault is a tag-level fault — wrong address, wrong format or wrong binding — and you fix the tag, not the connection.
When the panel is the limit #
If the installed editor lists no 15MC driver and no Modbus TCP driver for the model, no controller-side change will fix it. Update the editor first, because driver lists grow between releases. If the model genuinely supports nothing usable, the connection cannot be rescued from the controller side: replace the panel, either by the criteria in selecting a Modbus TCP HMI panel for an existing controller or with one that documents 15MC support directly, as Delta's DOP100 series does. The 15MC keeps serving Modbus TCP either way; the decision is made entirely at the screen.
Questions asked
Does the DVP 15MC use CANopen to talk to the HMI?
No. CANopen Builder writes the motion program and the CANopen device network; the HMI link is a separate Ethernet service. The 15MC serves its registers over Modbus TCP, and the panel selects that protocol in its own project. You do not change anything in the motion project to make the screen read data.
Can I copy the tag addresses from my old DVP SE or 28SV project?
No. Those projects were built against the WORD-based addressing of the standard DVP series, while the 15MC organizes its data in 64-bit QWORD structures with their own register-to-Modbus table. Copied addresses silently read the wrong registers. Rebuild each tag from the 15MC table and prove it with one read-only object first.
Why does the HMI show a huge or jumping number for a 64-bit value?
The tag width or the word order is wrong. A QWORD spans four holding registers; a 32-bit tag reads only the first two, and the wrong word-order setting rearranges all of them into a nonsense value. Set the tag format to 64-bit, apply the driver's word-order option, and compare the display with the controller's online value.
What port and station number go into the Weintek device settings?
Enter port 502, the registered Modbus TCP server port. The IP address and station number come from the 15MC's Ethernet configuration — Delta's 15MC HMI connection guide lists the defaults — and the panel's destination must match both. If the IP answers but the request is rejected, the fault is in the address map, not the network.
My Weintek editor lists no 15MC driver. Is the connection impossible?
Not necessarily. Driver lists change between editor releases, so check the latest published driver list for your panel model and update the editor if it is behind. If the model supports no usable driver at all, the connection cannot be rescued from the controller side, and a panel with documented 15MC support becomes the practical alternative.