IMDHMIControls LibraryShop main store

Troubleshooting

Why explicit writes to Omron assemblies fail over EtherNet/IP

Industrial networks Published 6 min read

Short answer

Your Set Attribute message carries service code E, which is Get Attribute Single, so it reads, succeeds and writes nothing — and the two codes are transposed, since Set Attribute Single is 10 hex. Even corrected, CS/CJ-series EtherNet/IP units do not accept explicit writes to assembly instances, because that service is optional in the specification. Carry the 240 bytes on a Generic Ethernet Module connection or use CIP Data Table Read and Write messages.

On this page
  1. The service codes are on the wrong messages
  2. Why fixing the code runs into a wall
  3. Working the swap on the CP1H-EIP21 to L16ER link
  4. What each symptom tells you
  5. Two supported ways to move the 240 bytes
  6. Test on the controller that ships
  7. Questions asked

Your write message never sends a write. Service code E hex is Get Attribute Single; Set Attribute Single is 10 hex. On your bench the message labeled Set Attribute carries E and the one labeled Get Attribute carries 10, so each instruction holds the other's service: the "write" is a read that succeeds, which is why the MSG completes clean and instance 101 never moves. Correcting the swap still will not make this write land, because explicit writes to assembly instances are optional in EtherNet/IP and the CS/CJ-series EtherNet/IP units do not implement them — the supported PLC object services table in section 9.2 of the W465 operation manual governs. Move the 240-byte block onto a Generic Ethernet Module connection, or drop the tag sets and use CIP Data Table Read and CIP Data Table Write messages.

The service codes are on the wrong messages #

The CIP common services fix the two codes you are using:

Operation Service, hex Service, decimal What the target does
Get Attribute Single 0E 14 Returns the current value of one attribute
Set Attribute Single 10 16 Accepts replacement data for one attribute

Your configuration attaches 10 to the read and E to the write — the opposite of the table. The service field that accepted E is hexadecimal, because E is not a decimal digit, so the 10 beside it in the same screen means 16 decimal, not ten. The radix trap cuts the other way too: a decimal 10 sent where a hex value is expected is 0x0A, which is neither of these services.

Open both MSG instructions and record the configured service value and the radix the field displays. The instruction label, the tag name and the rung comment say nothing about what goes on the wire; the service byte is the whole truth. A Set Attribute message carrying 0E is a read: the Omron returns the attribute's data, the reply is well formed, the MSG records success, and not one byte of instance 101 changes. That is your symptom exactly.

Why fixing the code runs into a wall #

Swapping the codes makes your diagnostics honest, but it does not open the write path. Explicit Set Attribute Single access to an assembly instance is an optional part of the EtherNet/IP specification, and the CS/CJ-series units described by the W465 operation manual do not offer it: the PLC object services table in section 9.2 is the list of explicit services the unit accepts, and a write to a class 4 assembly is not on it. Expect the corrected write to come back with a CIP error status instead of silent success. That error confirms the finding; it is not a new fault.

The block is deliberate engineering. Instance 101 is the tag set your EIP21 consumes from its connection partner, and its contents are owned by the I/O relationship the Network Configurator tag sets define. A unit that accepted explicit writes to that instance would let any client on the network overwrite data a cyclic connection is already delivering, so the optional service stays off. On these units, any explicit write addressed to class 4 is a dead end — stop tuning message parameters and change the exchange instead.

Inputs, as configured on the bench:

  • Read message: service 10, class 4, instance 111, attribute 3 — returns the Omron's data set.
  • Write message: service E, class 4, instance 101, attribute 3 — completes, destination unchanged.
  • Payload: 240 bytes, carried as DINTs.
  • Service definitions: Get Attribute Single 0E hex (14 decimal), Set Attribute Single 10 hex (16 decimal).

The rule in words: the service byte on the wire decides the operation, not the label on the instruction. Decode each configured value against the service table, in the radix the field uses.

The arithmetic:

  • E hex = 14 decimal = Get Attribute Single, so the write message requests a read of instance 101, attribute 3.
  • 10 hex = 1 x 16 + 0 = 16 decimal = Set Attribute Single, so the read message carries the write service. The pair is transposed.
  • Payload check: 240 bytes / 4 bytes per DINT = 60 DINT elements.

Result: the write path has never transmitted service 16. Every "successful" write was a read of the consumed assembly, replied to in full.

Decision: correct the codes once, so a failure means something. With service 10 on the write, the expected outcome is an unsupported-service error from the unit — and per the wall above, the 240 bytes then leave explicit messaging entirely: a Generic Ethernet Module connection, or CIP Data Table messages.

What each symptom tells you #

  • Read returns data, write completes, destination never changes: decode the transmitted service first. A Get Attribute Single on the write path produces exactly this silent result.
  • Codes correct at 14 and 16 decimal and the write still lands nowhere, no fault shown: the target has declined the optional service. Remote valve manifolds show the same pattern — reads from an input assembly at instance 100 with service 14 succeed while writes to instance 150 with service 16 go nowhere — and the answer is the same: change the access method.
  • The read works while carrying the write's service code: the two values are transposed between messages, or the field radix differs from what you recorded. Read both configurations back before concluding anything about the target.
  • The destination changes and then reverts: a second writer owns it — the I/O connection or the Omron program. Trace every writer to that memory before blaming the message.
  • The write returns a CIP error status: compare the requested service with the target's documented service table. An unsupported-service status ends the discussion.

Two supported ways to move the 240 bytes #

  1. Keep the tag sets and let a connection carry the data. Add a Generic Ethernet Module to the Logix I/O tree with input instance 111 and output instance 101 — the same instances the tag sets already use — and connection sizes matching the tag sets: 240 bytes is 60 DINTs per direction if both sets are that size. Sizing that connection is the same job as sizing a Generic Ethernet Module connection for WAGO 750 I/O: the module has to be configured to carry your byte count.

  2. Drop the tag sets and message controller memory directly. MSG instructions with the CIP Data Table Read and CIP Data Table Write message types address the Omron data area without any Network Configurator tag sets; the Path that routes the message to the target is the field that takes the care.

Decision: for a continuously exchanged block like this one, take the first option — the tag sets are already half of that configuration. Take the second when the exchange is event-driven, or when the final controller cannot originate an I/O connection at all.

Test on the controller that ships #

The L16ER on your bench can own a Generic Ethernet Module connection, so the first option is easy to prove there. The Micro850 that replaces it must originate the same I/O connection for that configuration to survive the swap, and connection origination is a property of the specific controller's embedded port, not of the network and not of the Omron end. A configuration proven on the CompactLogix is not a portable Micro850 configuration.

Commit to this rule: build the acceptance test on the shipping hardware. If the Micro850's port will not originate the I/O connection, the CIP Data Table path is the one that travels, because it asks only for explicit messaging, which the Omron unit documents and supports.

Questions asked

Why does the MSG finish with no error if nothing was written?

The error flags report the transaction, not your intent. A Set Attribute message carrying service 0E transmits Get Attribute Single; the Omron answers with valid attribute data, the reply is well formed, and the instruction records success. No status bit distinguishes a read reply from a write confirmation, so the only proof of a write is the destination actually changing. Watch the destination tag, not the done bit.

Do any EtherNet/IP devices accept explicit writes to assemblies?

Some simple adapters implement explicit writes on their output assemblies, which is why the technique keeps circulating. The specification makes the service optional, so support is decided device by device, and the vendor's supported-services table is the whole answer. The CS and CJ series units described by the W465 operation manual do not offer it, so on those targets the explicit assembly write path is closed.

What are the CIP Data Table Read and CIP Data Table Write messages?

They are Logix MSG message types that address controller memory directly instead of an assembly instance, so the Network Configurator tag sets come out of the design entirely. You configure the message type, the target memory and the route to the Omron; the Path field takes the most care because it carries the whole route to the target. Unlike the assembly write, this explicit path is documented for the Omron units.

My read works while carrying service 10 — does that prove the unit accepts Set Attribute Single?

No. A message that returns data transmitted Get Attribute Single, whatever its label says. Either the service field radix differs from what you recorded, or the two codes are transposed between the read and the write instructions. Capture the service byte actually leaving the controller before drawing any conclusion about what the target accepts.

How should the Generic Ethernet Module be set up for the 240-byte set?

Point the module at the instances the tag sets already use: input instance 111 for the data the Omron produces and output instance 101 for the data it consumes, with connection sizes matching the tag sets. Your 240-byte set is 60 DINTs. An instance number does not change meaning between implicit and explicit access; only the access method changes.

Keep reading

  • How-to

    Read and write Logix tags from CODESYS with CIP GenericService

    Read a Logix tag from CODESYS with CIP service 16#4C against the tag's Symbol Object instance at class 16#6B: send a two-byte element-count body, expect a two-byte type word first (16#C4 is DINT), and take the DINT value from bytes 2-5. Write with service 16#4D, sending type word, element count, then data. Rebuild the name-to-instance table after every download or online edit, because the controller reassigns instance numbers.

    Industrial networks

  • 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

  • Troubleshooting

    How a SCADA client reads a small PLC over EtherNet/IP

    An Ethernet link to a MicroLogix is not a working SCADA read: the controller serves data through PCCC commands carried over EtherNet/IP, and a client without that application service gets every read rejected. Check the driver's documented controller list for PCCC over EtherNet/IP or use the controller's documented Modbus TCP server, then prove one read-only value end to end.

    Industrial networks