IMDTouchKnowledge BaseShop main store

How-to

Setting Up a Weintek MT6050IP With a Delta DVP28SV PLC

HMI and touchscreens Published 6 min read

Short answer

Use EB8000 for the MT6050IP, because EasyBuilder Pro does not list it. Create the project, select the exact panel model, configure the Delta DVP28SV as the PLC device with serial settings copied value-for-value from the wired port, then bind objects to the device areas the Delta driver already exposes. Model, connection and address are three separate checks.

On this page
  1. Use EB8000 and select the exact panel
  2. Configure the DVP28SV connection before the first object
  3. Bind the first object to the driver's address areas
  4. Worked example: scaling a DVP28SV data register on the MT6050IP
  5. Sort every fault into connection, binding, or presentation
  6. Add inputs, outputs and commands
  7. Questions asked

Program the MT6050IP with EasyBuilder 8000. The panel is absent from EasyBuilder Pro's model list, so in Pro the project never starts, and no PLC setting changes that. In EB8000, create the project, select the exact MT6050IP target, then configure the Delta DVP28SV as the PLC device with serial settings copied value-for-value from the port wired to the panel. Only then bind objects: the Delta driver already exposes the controller's device areas, so you pick an address per object instead of building a memory map. Model selection, the PLC connection and each object's address are three separate checks, and every fault you meet later belongs to exactly one of them.

Use EB8000 and select the exact panel #

A missing model is an engineering-software problem, not a communication problem. The fix belongs in the software, before a cable is touched.

  1. Install EB8000 from Weintek or an authorized distributor, together with its manual. EasyBuilder Pro and EB8000 are separate packages with separate model lists, and the MT6050IP belongs to the EB8000 list.
  2. Create a new project and select MT6050IP as the target, written exactly as the label on the housing prints it.
  3. Check the target in the project's system settings before drawing any screen: the selected target fixes the hardware assumptions of the compiled application and what the download will accept.
  4. Save the project under a name that records the panel and controller pairing.

Do not select a similarly named model to get past the dialog; you would compile for hardware you do not have. If the exact model still does not appear, treat it as the software-list problem covered in when an HMI model is missing from the programming software and resolve it there.

Configure the DVP28SV connection before the first object #

The PLC driver translates object reads and writes into controller transactions. Its settings must match the interface and the configuration of the port actually wired to the panel.

Setting Where it lives What it decides
Delta DVP driver project device settings the protocol and the address areas objects can use
Panel communication port device settings and the panel connector documentation which physical connector carries the requests
Interface and cable both device manuals, checked against the installed cable whether the two ports exchange valid signals
Baud rate, parity, data bits, stop bits PLC port configuration and HMI device settings must agree value-for-value on both ends
Station address, where the link uses one PLC port configuration and HMI device settings that requests reach this controller
  1. Identify the connected ports from the hardware labels, not from the model names.
  2. Select the Delta driver whose documented controller support includes the DVP28SV.
  3. Copy the PLC port's serial settings into the HMI device settings, one value at a time.
  4. Verify the cable pinout against the pin tables in both manuals, with both devices powered down for the wiring work.

Choosing the driver here is independent of how the finished project reaches the panel later, the distinction laid out in separating HMI transfer method from PLC driver selection. The port-matching discipline is the one used when connecting a Delta DVP 15MC PLC to a Weintek HMI: labels first, settings second, objects last.

Bind the first object to the driver's address areas #

The driver exposes the controller's device areas in the object's address selector, the same areas the ladder program uses: X inputs, Y outputs, M internal relays, T timers, C counters and D data registers. You choose a device type and a number per object; there is no memory map to define first.

Object setting Where it lives What it decides
Device address properties of the object routes the object to the PLC, not HMI-local memory
Address area and number the driver's address selector which point or register is read or written
Bit or word access object type and address properties discrete state versus numeric value
Format and decimal places numeric object properties how the raw word is interpreted and displayed

Start with one read-only object: a bit indicator for a discrete state, a numeric display for a word. Take the test address from the ladder program or the PLC's online monitor, never a guessed unused location, because an object can read a wrong location successfully. Mind the numbering convention as well: controller notation and the address entry field can use different bases, so copied digits can select a different location than the one intended.

Worked example: scaling a DVP28SV data register on the MT6050IP #

The inputs, with their sources:

  • The ladder program stores an oven temperature in a D register in tenths of a degree, 0.1 °C per count. This is a typical arrangement for this pairing and the case worked here; the register number comes from your program.
  • The numeric display object is set to word access on that D register, 16-bit format, one decimal place.
  • With the process running, the PLC's online monitor shows the raw word as 1247.

Rule in words: the panel displays the raw word multiplied by ten to the power of minus the number of decimal places, so with one decimal place the scale factor is 10 to the power of -1.

The arithmetic: 1247 counts x 0.1 °C/count = 124.7 °C, so the screen shows 124.7 °C. Check the same format at a second operating point before trusting it: an online-monitor raw word of 850 counts must appear as 850 x 0.1 °C/count = 85.0 °C, and a raw word of 100 counts as 10.0 °C. If the second point disagrees, the format was fitted to one reading instead of proven.

The decision: a screen reading of 1247 means the address is right and the decimal-place setting is wrong, so fix the format and leave the address alone. A reading that should be negative but shows a large positive number is two's-complement at work: -100 appears as 65536 - 100 = 65436, so the format must be signed 16-bit. Move to the next object only after the displayed value matches the online monitor on this one.

Sort every fault into connection, binding, or presentation #

When the panel cannot read the PLC, trace from the symptom back to its layer:

What you see Where the fault lives What to do
Panel missing at project creation software model list build in EB8000; no address change fixes this
Every PLC object warns or freezes the shared device connection check driver, cable, port settings, controller state
One object fails while the rest update that object's address properties compare device and number against a working object
Value changes but reads wrong format and scaling correct signedness or decimals, leave the address alone
Value static with no warning the addressed location watch the online monitor; the word may be constant

A plausible number is not proof of a correct binding, and a constant display can be a correct view of a constant value. Updates that arrive but lag are a polling matter rather than an address matter, and the arithmetic behind that is why Modbus RTU drive polling on one serial port is slow.

Add inputs, outputs and commands #

  1. Add read-only lamps for the X inputs and Y outputs the operator needs. An output lamp reports the addressed coil state, not field voltage or actuator movement.
  2. Add numeric displays for the D registers the process uses, each with the format proven above.
  3. Route every write to a location the ladder reserves for HMI commands and setpoints, never to a coil the logic also drives.
  4. Define in the program how each command is accepted: permissives, momentary versus maintained action, reset behavior and setpoint limits.
  5. Run the first write tests on the bench or with actuators disconnected; a momentary command on a live machine can cycle real outputs.

The pairing is commissioned when all three checks pass: the EB8000 project targets the exact MT6050IP, the driver settings match the DVP28SV port value-for-value, and each object's address is confirmed against the PLC's online monitor.

Questions asked

EasyBuilder Pro is the current software. Can it program the MT6050IP anyway?

No. The MT6050IP belongs to the EasyBuilder 8000 model list, and EasyBuilder Pro does not add it, so Pro cannot build a project that targets this panel. Install EB8000 for this panel and keep its projects there; the two packages maintain separate model lists and separate projects.

Do I have to define the Delta addresses in the HMI before I can use them?

No. The Delta driver lists the controller's device areas, including inputs, outputs, internal relays, timers, counters and data registers, in each object's address selector, so you choose a device type and number per object. What you must supply yourself is which address holds your signal, and that comes from the ladder program, not from the driver.

What is the best first test object on this pairing?

One read-only bit indicator on an input you can change by hand, such as a limit switch on an X point. You see the physical cause and the screen effect at the same time, the comparison needs no writing to the controller, and it exercises the driver, the cable and the address binding in a single check.

Where should EB8000 and its manual come from?

From Weintek or one of its authorized distributors, together with the documentation for the release you install. Use the manufacturer's own manual rather than third-party copies: the model list, device settings and driver address conventions it describes are the ones that match your installed version.

Keep reading

  • How-to

    Connecting a Fuji HMI to a ControlLogix PLC

    Yes, the pairing works. You need Rockwell's Logix package matched to the controller firmware on the PLC side and Fuji V-SFT for the panel; FactoryTalk View programs only Rockwell panels, and RSLinx is not part of the Fuji data path. The gate is the driver list for your exact panel model — V8, V9 and TechnoShot have the Allen-Bradley connection documented.

    HMI and touchscreens

  • Troubleshooting

    Fixing Weintek HMI to Mitsubishi FX PLC Communication

    A Weintek panel that shows communication errors against an FX0N, FX1N, FX2N or FX3 CPU is nearly always wired with the wrong cable pinout for the port pair. Match the HMI COM port and PLC port to the Weintek PLC Connection Guide, set GX Developer parameters only for adapter boards, and keep the 1 m cable.

    HMI and touchscreens

  • How-to

    Editing a Delta DOP HMI project without breaking PLC comms

    Downloading a revised project to a Delta DOP panel replaces only the panel's project; the PLC program and its port configuration are untouched. The link survives because the driver and serial parameters are stored separately in each device and a revision leaves them matching. Record both sides first, then prove read and write after the download.

    HMI and touchscreens