IMDHMIControls LibraryShop main store

Troubleshooting

Why Micro850 explicit writes fail to SMC EX600 outputs

Industrial networks Published 6 min read

Short answer

Your read works and the write does not because the Micro850 has no EtherNet/IP I/O scanner: its explicit Class 3 messages never supply the Class 1 output ownership the EX600 waits for, so the module holds every channel fail-safe. Set the EX600 documented output force condition, keep service 16 on class 4, instance 150, attribute 3, member 0, and build the write buffer to the documented output image.

On this page
  1. What the working read proves
  2. Why the module ignores the write
  3. The write path, field by field
  4. Writing one EX600-SEN3 output from a Micro850 CIP Generic block
  5. Commissioning checklist
  6. When the channel still does not move
  7. Questions asked

Your read works because the path is correct; your write fails because the EX600 will not let an explicit message own its outputs. Service 16 on class 4, instance 150, attribute 3, member 0 is the right output write for this module, and the Micro850 can execute it — after you set the output force condition in the EX600 that grants control to explicit messages. Until that condition is set, the module receives your data and holds every channel in its fail-safe state, and the CIP Generic block reports no error because the transaction itself completed. This is not a Micro800-versus-SMC incompatibility: it is output ownership, the gate any EtherNet/IP output device raises against a controller with no Class 1 scanner.

What the working read proves #

A completed read with service 14, class 4, instance 100, attribute 3, member 0 proves four things: the Ethernet link, the IP route, the CIP server inside the EX600-SEN3, and the input assembly mapping. It proves nothing about outputs. Instance 100 is the input assembly; the outputs sit behind a different instance and a different gate.

Path element Working read Failing write What to check
Service code 14 16 Read service versus write service
Class 4 4 Assembly object, unchanged
Instance 100 150 Input assembly versus output assembly
Attribute 3 3 Assembly data, unchanged
Member 0 0 Unchanged

Make the read prove it is live before touching anything else: toggle one known field input and watch the returned data change across several reads. One snapshot can be a retained value; changing data is current data. Once that passes, stop editing the network side. The fault that remains is the module's output-control condition or your write payload.

Why the module ignores the write #

CIP moves I/O data two ways. Implicit Class 1 connections are cyclic: a scanner owns the output image and refreshes it on a fixed interval, and the output module trusts that owner while the connection is valid. Explicit Class 3 messages are one transaction at a time, requested by your logic.

An output module holds its channels fail-safe until an accepted connection or a configured mode takes ownership — that is the behavior that drops valves when a cable breaks instead of leaving them running. The Micro850 has no Class 1 I/O scanner; its EtherNet/IP traffic goes out as explicit messages only. Your service 16 request reaches the assembly object, the block calls the transaction done, and the output logic never applies it. A clean status with a dead channel is the expected symptom, the same lesson as when explicit writes to Omron assemblies fail over EtherNet/IP: a completed transaction and an applied output are two different things.

The EX600 documents the way through the gate: a force condition on the outputs that permits control by explicit message. Set it, and a correctly formed write to the output assembly moves the channel. Leave it unset, and no explicit write moves an output, from any controller.

When a scanner does own the outputs, the cyclic connection carries the whole I/O image every cycle and has to be sized for it — the exercise in sizing a Generic Ethernet Module connection for WAGO 750 I/O. On the Micro850 you stay explicit, so that sizing problem never arises; the ownership problem does.

The write path, field by field #

Service 16 is Set Attribute Single, the CIP write counterpart to the service 14 read, Get Attribute Single. Class 4 is the Assembly object; attribute 3 is its data attribute; the instance selects which assembly — 100 for inputs, 150 for outputs on this module. Attribute and member carry over from your read unchanged.

The payload is an image, not a tag. The assembly data attribute holds the whole output picture in the byte order and channel-to-bit map the SMC documentation states for your configured output units; neither is derivable from the input side. Build a buffer of that documented size, set the one bit for the channel under test, and leave every other bit at its intended state.

Writing one EX600-SEN3 output from a Micro850 CIP Generic block #

Inputs:

  • Proven read path, from your working configuration: service 14, class 4, instance 100, attribute 3, member 0.
  • Intended write path, from your failing configuration: service 16, class 4, instance 150, attribute 3, member 0.
  • EX600 output force condition, current state: unset — which is why the channel does not move.
  • Output image size and channel-to-bit map: from the SMC EX600 EtherNet/IP documentation for your output configuration. The byte count is not repeated here; take it from that document, never from the input image size.

Rule, in words: an explicit write energizes an EX600 output only when the force condition is set, the service is the assembly write, the instance is the output assembly, and the payload is the complete documented output image with the target bit in the state you want.

The arithmetic is the path comparison, field by field:

  • Read: 14 / 4 / 100 / 3 / 0
  • Write: 16 / 4 / 150 / 3 / 0
  • Service 14 → 16: changed.
  • Class 4 → 4: same.
  • Instance 100 → 150: changed.
  • Attribute 3 → 3: same.
  • Member 0 → 0: same.

Two of the five fields change. If your write path differs from 16 / 4 / 150 / 3 / 0 in any field, that field is the fault before you look anywhere else.

Result: with the force condition set and the buffer built to the documented image, one write with the target bit set energizes the channel, and a second write with the bit cleared drops it. Decision: force condition unset → no explicit write moves an output from any controller, regardless of path; force condition set and path correct → the channel follows the bit. If the block completes and the channel still does not move, work the payload in order: buffer length, then bit position and byte order, then the module's output state and diagnostics.

These commissioning writes drive real solenoids: isolate the air or restrain the actuators before the first set and clear.

Commissioning checklist #

  1. Leave the proven read — service 14, class 4, instance 100, attribute 3, member 0 — in the program and running; it is your reference transaction.
  2. Toggle one known field input and confirm the returned data changes.
  3. From the SMC documentation, write down the output image size, byte order, and channel-to-bit map for instance 150 with your output units.
  4. Build the write buffer to that documented size, with only the test channel's bit set.
  5. Set the EX600 output force condition that permits explicit-message control.
  6. Execute one write — service 16, class 4, instance 150, attribute 3, member 0 — then record the CIP Generic block's status before retriggering.
  7. Clear the same bit in the same image and write again; the channel must drop.
  8. Confirm in the EX600 diagnostics that the module reports the configured output-control condition.

Trigger one request at a time. Fire it, wait for completion, read the status, then decide; overlapping requests hide which transaction failed.

When the channel still does not move #

Work this order:

  1. The force condition — an unset condition is the cause whenever the read works and the write completes silently.
  2. Buffer length — more or fewer bytes than the documented output image.
  3. Bit position and byte order against the SMC channel map.
  4. The module's output state and its diagnostics.

Changing the IP address, swapping ports, or rebuilding the route fixes nothing here; the working read has already cleared the network.

Questions asked

Why does the CIP Generic block show no error when the output never moves?

The block reports the outcome of its own transaction: the request reached the module and the service completed. It does not report output ownership or the physical channel state. With the force condition unset, the EX600 accepts the data into the assembly object and still holds the output fail-safe, so a clean status with a dead solenoid is the expected symptom of this fault, not a contradiction.

Does the same fix work from a Micro870 to an EX600-SEN3/4?

The module-side fix is identical, because the force condition and the assembly instances belong to the EX600 SI unit, not to the controller: set the force condition and write service 16 to class 4, instance 150, attribute 3, member 0 with the documented output image. Only the controller side differs, and it must issue the same explicit request one transaction at a time.

Is there an explicit-message timeout parameter instead of the force condition?

Some EtherNet/IP output devices accept explicit control when you set a watchdog timeout parameter, but the route SMC documents for the EX600 is the force condition, so use it. If the manual for your SI unit lists no timeout parameter for explicit output control, the force condition is the whole fix; do not keep hunting for a bypass of the ownership gate.

Can I write the outputs through instance 100, since that path already works?

No. Instance 100 is the input assembly: it carries the image of field inputs back to the controller. Outputs live behind instance 150 on this module, and writing the input assembly cannot energize a solenoid. Keep service 14 against instance 100 for reads and service 16 against instance 150 for writes.

What buffer size does the output write need?

The byte count the SMC documentation gives for the output assembly of your configured output units — not the input image size, and not an assumed one byte per solenoid. Write the complete image every time with unrelated bits held at their intended state, so a single-channel commissioning test never disturbs the valves wired next to it.

Keep reading

  • Troubleshooting

    Why explicit writes to Omron assemblies fail over EtherNet/IP

    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.

    Industrial networks

  • Explainer

    Designing a 1734-AENT Point I/O fiber ring on EtherNet/IP

    Yes — enable IGMP snooping on all seventeen switches: the input data a 1734-AENT adapter produces is multicast, so without it every switch floods the ring and all sixteen adapters reject each other's packets. Full-duplex switching ends collisions but not congestion, each fiber span must meet its own optic's distance limit, and ring recovery must beat four times the RPI.

    Industrial networks

  • 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