IMDTouchKnowledge BaseShop main store

Troubleshooting

Writing WAGO 750 PLC Digital Outputs From a Weintek HMI

HMI and touchscreens Published 5 min read

Short answer

Your read at 0x 513 is already the right address: in the panel's 0x notation it is decimal bit 512, %QX0.0, inside the WAGO physical output area 512–767 (0x0200–0x02FF). The write fails because the CODESYS program assigns %QX0.0 every scan and overwrites it, so command an internal memory bit and let the logic drive the output.

On this page
  1. What the working read proves
  2. The WAGO 750 Modbus map for physical I/O
  3. Worked example: turning 0x 513 into the write address for %QX0.0
  4. Why the write still has no effect: the PLC scan
  5. Writing an internal command bit instead
  6. Commissioning checklist
  7. Questions asked

The address you are hunting does not exist as a second number. The read at 0x 513 is already the correct address for the first digital output: in the panel's 0x notation it is decimal bit 512, and the WAGO 750-881 maps bit 512 to %QX0.0, inside the physical output area 512–767 (0x0200–0x02FF). Put the same 0x 513 in the toggle's write field. If the contactor still does not move, the address was never the fault: the CODESYS program assigns %QX0.0 every scan, and a Modbus write cannot hold a bit the logic owns. Give the panel an internal command bit and let the program drive the output through its own conditions.

What the working read proves #

  • The bit lamp at 0x 513 tracking the output proves the Ethernet link, the Modbus TCP connection, the panel driver and one valid read-response pair at that address. It proves nothing about writes.
  • Operating the same output from the 750-881 web interface proves the controller, the output module and the field wiring all work.
  • The toggle graphic changing while the contactor stays put is not PLC evidence. With separate read and write addresses, the object animates from the read side.

With the lamp updating, leave the network alone. Your crossover cable is confirmed by the readback, not by cable theory, and a working read with a failing write is never a physical-layer fault. Start at the write address, then at the program.

The WAGO 750 Modbus map for physical I/O #

The 750-881 register mapping table fixes the numbers: physical inputs are read-only, and physical outputs occupy decimal 512–767. The table documents bit-oriented access to the real I/O, outputs through the 0x area and inputs through the 1x area.

Area Decimal Hexadecimal PLC image
Physical digital inputs 0–255 0x0000–0x00FF %IW0–%IW255
Physical digital outputs 512–767 0x0200–0x02FF %QW0–%QW255
Additional physical output data 28672–29436 0x7000–0x72FC %QW512–%QW1275

In the bit-oriented view, output channels take consecutive bit positions from 512 upward: %QX0.0 at 512, %QX0.1 at 513, and so on. What the digits on the panel screen mean still depends on which base the tool counts from and whether it shows decimal or hexadecimal, the same ambiguity behind decoding Modbus holding register 4500001 from PLC to HMI.

Worked example: turning 0x 513 into the write address for %QX0.0 #

Inputs:

  • Register table, WAGO 750-881 documentation: physical outputs decimal 512–767, hexadecimal 0x0200–0x02FF, PLC image %QW0–%QW255.
  • Verified observation from your tests: the lamp entered as 0x 513 shows the first output of the first digital output module, cross-checked against the web interface.
  • Your code: outputs addressed as %QX0.0, %QX0.1 and upward in CODESYS.

Rule in words: read the digits both ways and keep the reading that lands inside the documented range. Literal hexadecimal expands digit by digit; the panel's 0x entry takes decimal digits counted from one, so the entered number equals the Modbus bit position plus one.

Arithmetic:

  • As literal hexadecimal: 0x513 = 5×256 + 1×16 + 3 = 1280 + 16 + 3 = 1299. The output area ends at 767, so 1299 sits in the unmapped gap below the additional output data at 28672. The entry is not hexadecimal.
  • As decimal from one: 513 − 1 = 512. That lands inside 512–767, and 512 = 0x0200, the first output word %QW0. Bit 0 of %QW0 is %QX0.0, the exact output the lamp tracks.

Result: 0x 513 is bit 512, %QX0.0. The second output, %QX0.1, is bit 513, entered as 0x 514.

Decision: enter 0x 513 as the toggle's write address and leave the read address alone. The addressing question ends the moment the mapped bit is seen to change and revert within one scan; past that point the fault is program ownership, and no address will fix it.

Why the write still has no effect: the PLC scan #

A Modbus write to bit 512 lands in the output image between scans. On the next task cycle the CODESYS rungs that assign %QX0.0 execute and write the logic value over it, so the panel's value survives at most one scan. WAGO documents the same limit from the controller side: physical inputs can only be read over Modbus, and a physical output only stays where Modbus put it when the application leaves that output to the interface. A rung and a Modbus write cannot both own one bit; the rung wins every scan.

Watch the bit live in the web interface or the CODESYS online view while pressing:

  • The value never moves: wrong write address, area or bit format. Return to the worked example.
  • The value moves and snaps back inside a scan: the program owns the output. Move the command, next section.
  • A command bit moves and the output follows: the path is complete; check the machine side.

Writing an internal command bit instead #

For a contactor gated by anything, permissives, operating modes, other devices, the panel must not write %QX directly. Declare a command bit in internal memory, point the toggle's write address at it, keep the lamp on 0x 513 so the display shows the real output, and let the program compute the rung condition as command AND permissives. For a plain manual station with no rung on the output, the direct 0x write is the right method and will hold.

The command bit's Modbus address comes from the internal memory area of the same register table, a separate row with its own decimal base. Toggle-switch objects with Set ON and Set OFF commands and separate read and write fields are made for this split: read the real output, write the command.

Commissioning checklist #

  1. Mark the destination row in the register table: physical outputs 512–767, or the internal memory area for a command bit.
  2. Convert before typing: entered number equals decimal bit position plus one, and the position must land inside that row's decimal range. If the panel rejects an entry outright instead of ignoring it, the causes are the ones behind invalid bit address errors when adding HMI tags.
  3. Fill the toggle's read address with the real output, its write address with the destination, and keep the bit lamp on the real output.
  4. Press while watching the mapped bit live in the web interface or the CODESYS online view; the toggle graphic on its own proves nothing.
  5. A change that reverts within a scan means the logic owns the output: move the write to a command bit instead of testing more addresses.
  6. Confirm the machine is in a state where the contactor may close before the first live write, because the first successful write energizes whatever the output feeds.

Questions asked

Is the 0x 513 entry hexadecimal or decimal?

The prefix selects the bit area and the digits after it are decimal, counted from one, so 0x 513 is bit 512, %QX0.0, the output the lamp already tracks. Read as literal hexadecimal, 0x513 would be decimal 1299, outside the 512 to 767 output area, which is why hex cannot be what the panel means. If your driver counts from zero instead, the same bit is entered as 0x 512.

What Modbus address does %MX1000.0 get on the panel?

It does not come from the physical output range. Internal memory bits sit in their own row of the same WAGO register table with its own decimal base; take that base, add the bit offset inside the area, and enter the result in the same 0x style. Never convert %MX1000.0 by borrowing the 512 offset, because 512 belongs to the physical outputs only.

Should the output be written as a bit or as a holding register?

As a bit. The WAGO mapping documents the real I/O areas for bit-oriented access, outputs through the 0x area and inputs through the 1x area, and one contactor output is one bit of %QW0. Word-style access describes the word image and is not the documented path for switching a single channel.

Can I delete the PLC logic and let the panel own the output?

Yes, for a pure manual station with nothing else driving the output: remove every rung that assigns that %QX bit and the direct 0x write will hold. If the program must gate the contactor through permissives, modes or another device, keep the logic and write an internal command bit instead, because the rung wins every scan otherwise.

Keep reading

  • Troubleshooting

    Connecting a Delta DVP 15MC PLC to a Weintek HMI

    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.

    HMI and touchscreens

  • Selection guide

    Choosing a PC-based HMI runtime for a Modbus TCP PLC

    No — C-more projects deploy to C-more panel hardware, so a PC-only interface needs a PC runtime instead. Run AdvancedHMI, a PyQt5 front end with pymodbus, or an Excel VBA socket client as the Modbus TCP client, with the PLC acting as the server on TCP port 502.

    HMI and touchscreens

  • How-to

    Connecting an XBTGT HMI to an M241 PLC over Modbus TCP

    Delete the Generic Modbus TCP slave from the M241 device tree and activate the Modbus server on the controller's Ethernet interface instead — that slave makes the M241 a client, so both devices poll and neither answers. Then map Vijeo Designer driver address 40001 to PLC word %MW0, keep TCP port 502 open between panel and controller, and shift the address map by one word if a test read lands one register off.

    HMI and touchscreens