IMDHMIControls LibraryShop main store

Troubleshooting

Sizing a Generic Ethernet Module connection for WAGO 750 I/O

Controllers and I/O Published 7 min read

Short answer

Enter the Generic Ethernet Module connection from the coupler's process image: input assembly instance 107 sized to input-image bytes plus one, output assembly instance 101 sized to the output-image bytes exactly, configuration assembly instance 1 at size 0, Comm Format SINT, and the remaining settings at their defaults. The 750-352 orders analog data before digital, so build both byte maps from the coupler's image view and round the totals once, never slot by slot.

On this page
  1. What sizes and assembly instances does the connection need?
  2. Why is the yellow warning gone but the I/O data still wrong?
  3. Why can't I count connection bytes from the physical module order?
  4. How do I build the input and output byte maps?
  5. What goes in the RSLogix 5000 Generic Ethernet Module dialog?
  6. What does a worked sizing calculation look like?
  7. How do I verify offsets before trusting the tags?
  8. Questions asked

The connection sizes for a WAGO 750 rack behind a ControlLogix come from the coupler's process image, not from the physical slot order. The trap in a mixed rack is ordering: the 750-352 puts analog data ahead of digital data even when the analog modules mount later, so a left-to-right slot count puts tags on the wrong bytes. This article gives the dialog entries, a worked sizing example, and the offset checks that prove each tag before the rack runs.

What sizes and assembly instances does the connection need? #

Enter input assembly instance 107 sized to the input-image byte count plus one, output assembly instance 101 sized to the output-image byte count exactly, configuration assembly instance 1 with size 0, and Comm Format SINT.

The 750-352 setup document defines those three assemblies for a ControlLogix connection and both size rules with them. In CIP terms the assemblies are the connection's data end points: the input assembly produces data toward the controller, the output assembly consumes it, and the configuration assembly is written at connection setup — size 0 here because the generic module passes no configuration data. Give the coupler its IP address first — WAGO's Ethernet Settings utility handles that along with the coupler's basic settings — and enter the same address in the module. A coupler rack like this is also the clean way to add analog channels when the local chassis has no slots left; the sizing habit is the same one you use when you add 4-20 mA analog inputs to a full CompactLogix rack.

Why is the yellow warning gone but the I/O data still wrong? #

Bumping connection sizes until the yellow triangle disappears proves only that the byte counts agree, not that each tag points at its own channel: a correct total with a wrong offset still reads and writes another module's bytes.

The warning triangle reports one thing: the sizes the controller requests and the coupler's connection definition disagree. Once they agree it clears, and nothing in that check says where a channel actually sits. The mismatches a cleared warning leaves behind:

  • Digital input bits at unexpected positions, or a tag that never changes while the field device toggles: the input offsets are shifted.
  • A 4–20 mA value in the wrong word, or one that will not track the channel you drive: analog data sits where a digital-only count assumed it did not.
  • An output command that moves a different field point, or none: the output map writes into another module's byte.
  • RTD or encoder data absent or misread: those image lengths follow each module's configured data representation, which no channel count reveals.

Treat a changed size as a diagnostic step, never as the verification.

Why can't I count connection bytes from the physical module order? #

Analog process data precedes digital data in the 750-352 image even when the analog modules mount later in the rack, so a left-to-right slot count produces offsets that do not match the bytes the coupler actually produces.

In the mixed rack this article sizes — the 750-352 coupler plus 750-508, 750-537, 750-1415, 750-473, 750-464, 750-555 and 750-634 — the analog fields still come ahead of the digital ones in the image. Two more rules move bytes as well: digital allocations can be fractional, with a small module occupying half a byte, and RTD and encoder data occupy whatever length their configured data representation gives. This fault class is not an EtherNet/IP specialty either; a DP/DP coupler communication fix built around its process-image area is the same mistake on a PROFIBUS link.

How do I build the input and output byte maps? #

Build two independent maps — one for the data the coupler produces toward the controller, one for the data it consumes — and take each module's direction and byte length from the coupler's online image or its documented process data, analog before digital.

  1. List every module with the direction it feeds and its process-data length. A module can feed the input side, the output side, both, or neither, and the image view or the module documentation decides which.
  2. Order each direction the way the image orders it — analog fields first, then digital — never by slot position.
  3. Record each module's start offset in bytes as you lay the map out.
  4. Sum the lengths per direction. Combine fractional allocations first — three half-byte modules total 1.5 bytes — then round the image total up to the next whole byte once, not module by module.
  5. Add one byte to the input total only; the plus-one belongs to assembly 107.
  6. Check the finished sizes and offsets against the coupler's online image before any tag is mapped.

What goes in the RSLogix 5000 Generic Ethernet Module dialog? #

Add a Generic Ethernet Module under the controller's Ethernet port, enter the coupler's IP address, set Comm Format to SINT, then enter assemblies 107, 101 and 1 with the calculated sizes and leave every other value at its default.

RSLogix 5000 offers no byte comm format for this module type, which is why the setup guidance calls for SINT. The entries:

  • Comm Format: SINT.
  • Input assembly instance 107, size = input-image bytes + 1.
  • Output assembly instance 101, size = output-image bytes, nothing added.
  • Configuration assembly instance 1, size 0.
  • Everything else at defaults, which gives a 10 ms RPI; move it only when the project's connection requirements call for another value.

Two habits to avoid: entering a different connection size to make the warning disappear, and mixing this generic-module setup with WAGO's EDS-based profile for the 750-352, which brings its own assembly definitions and add-on instructions for specialty modules — run one method, not both.

What does a worked sizing calculation look like? #

Illustrative numbers, read from an image view rather than this rack's actual configuration: a 9-byte input image and a 10-byte output image give input assembly 107 a size of 10, from 9 + 1, and output assembly 101 a size of 10.

Suppose the image view reports, analog first: 4 bytes for the 750-473, 4 bytes for the 750-464, 1 byte for the 750-1415. The input map:

  • 750-473, 2-channel 4–20 mA input: bytes 0–3
  • 750-464, RTD input: bytes 4–7
  • 750-1415, 8-channel digital input: byte 8
  • Input image = 4 + 4 + 1 = 9 bytes, so assembly 107 size = 9 + 1 = 10

Suppose the output view reports 8 bytes for the 750-555, 1 byte for the 750-537 and 1 byte for the 750-508. The output map:

  • 750-555, 4-channel analog output: bytes 0–7
  • 750-537, 8-channel digital output: byte 8
  • 750-508, 2-channel digital output: byte 9
  • Output image = 8 + 1 + 1 = 10 bytes, so assembly 101 size = 10, nothing added

The example leaves the 750-634 out on purpose: its image length follows its configuration and comes from the image view or its documentation, never from a channel count. If the digital allocations in a map summed to 1.5 bytes instead of whole ones, the total would round to 2 before any plus-one.

How do I verify offsets before trusting the tags? #

Go online with the coupler, read back its actual image lengths and offsets, then toggle one input at a time and watch the matching tag: a bit that moves in the wrong word is an offset error no connection size can fix.

Add modules incrementally when a fresh project will not come up clean: prove one module's data, then attach the next. A warning triangle means the connection definition and the coupler image disagree; a cleared triangle means the counts agree, and the channel tests remain yours. Driving an analog channel and watching the one word you expect is the fastest offset proof there is. When you toggle outputs for these tests, every point is live: a mis-mapped bit can start a drive or actuator nobody expects to move.

The commissioning sequence lines up with the remote I/O commissioning checklist for a modular station, and the online work needs a computer at the cabinet; where that station is permanent, an engineering or maintenance seat in the cabinet door is an industrial panel PC. The decision in both cases: with the image in hand, enter assembly 107 at image-plus-one and assembly 101 at image-exact, SINT, defaults otherwise; without the image, build it incrementally from the coupler online — and only then map tags.

Questions asked

Why does RSLogix 5000 only offer SINT for this connection?

RSLogix 5000 has no byte-sized comm format for a Generic Ethernet Module, and SINT is an 8-bit integer, so each element of the SINT array lines up with one byte of the coupler's process image. That is why the setup guidance sets Comm Format to SINT and why the element count equals the byte count.

How do I read each module's byte length before I size the connection?

Take the length from the coupler's online process-image view or from the module's documented process data. The setup document for the 750-352 notes that coupler firmware older than 1.06 does not offer some of those online features, so update the coupler first if the view is missing. Channel counts alone are never enough for analog, RTD or encoder modules.

Does the plus-one byte go on the output assembly too?

No. Assembly 101 is sized to the output-image byte count exactly; only input assembly 107 carries the extra byte in the documented connection definition. Adding one to the output size requests a byte the coupler's output assembly does not produce, and the connection fails or the yellow warning returns.

What changes when I swap one WAGO module for another?

Rebuild both byte maps from the coupler's image before reconnecting. A different module can change the image length, the offsets of every module after it, or both, so re-enter the connection sizes in the Generic Ethernet Module dialog and re-run the channel tests. Only a like-for-like replacement with a confirmed unchanged image lets the sizes stand.

Keep reading

  • Troubleshooting

    Fixing a TwinCAT EtherNet/IP slave connection from an Omron PLC

    The CIP1 fault is a Forward Open mismatch: each Omron direction must carry the full serialized TwinCAT assembly, not the process variables alone. With 2 bytes in and 2 bytes out, the 4-byte ConnCtrl on outputs and ConnState on inputs make each direction 6 bytes, and the instances must follow producer and consumer roles. If a capture shows the request and a rejection, read the sizes and instances the originator actually serialized.

    Industrial networks

  • How-to

    Remote I/O commissioning checklist for a modular station

    Commission a modular remote I/O station in this order: match the coupler's protocol and addressing to the controller interface, budget and verify station power, seat modules and connectors against the drawing, then prove cyclic data exchange and every field signal before enabling outputs. A loading web page and lit status LEDs prove the coupler is alive; only a value that changes at the controller proves valid I/O data.

    Controllers and I/O

  • Selection guide

    Selecting remote I/O architecture for a safety upgrade

    Sort every field signal into ordinary, safety or motion first, then buy the fewest network interfaces your crew can support. The safety controller fixes the safety network — CIP Safety runs over EtherNet/IP or DeviceNet — and ordinary hubs and gateways never carry safety data. Count channels, not functions: 16 stations at 20 inputs and 10 outputs is 480 planning signals, and every dual-channel safety device takes two safety channels.

    Controllers and I/O