Omron C200H-MC221 Motion Board: Resolver, Encoder & Drive Wiring

James Nishida16 min read
Motion ControlOmronTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Overview

The Omron C200H-MC221 is a motion control board for the C200H-series modular PLC rack (C200H, C200HS, C200HE, C200HG, C200HX). It adds closed-loop point-to-point positioning for two servo axes in a single slot, replacing fast pulse-counter input modules and pulse-train output modules while exposing axis status, current position, and motion commands to the host CPU via the standard C200H backplane I/O area. The card is documented by two canonical manuals: I06E-EN-01 (C200H-MC221 / MC421 Motion Control Board Operation Manual) and W359-E1 (Motion Control Board Programming Manual). Always cross-check the manual revision against the board nameplate before applying parameter tables.

A typical 2-axis gantry deployment (X and Z) drives third-party brushless servo amplifiers with resolver-equipped motors. In that topology the MC221 does not read the resolver directly. The resolver cable terminates on the drive; the drive returns a simulated incremental encoder (A/B/Z, typically RS-422) for the MC221 outer position loop. The MC221 is the controller side of that loop; all resolver-side wiring belongs to the drive.

Design origin. The MC221 predates Omron's Mechatrolink motion bus. For 2-axis systems it remains a valid choice, but the cable-management and signal-conversion load it imposes (resolver inside the drive, simulated encoder back to the MC221, separate handshakes for run / alarm / limit) is precisely the engineering pain Mechatrolink eliminates for higher axis counts. Studying the MC221 architecture is a useful baseline for any resolver-to-drive-to-PLC arrangement.

System Architecture and Signal Flow

The MC221 occupies one slot in the C200H rack. Two physical connectors exit the module faceplate; both pre-wired harnesses route to external terminal blocks in the control cabinet. The MC221 also exchanges data with the CPU over the backplane, so axis positions, status flags, and motion profiles flow through allocated I/O words.

The full signal chain for a brushless resolver axis is:

Resolver on brushless motor Resolver cable Sin/Cos feedback to drive Servo Drive e.g. third-party brushless Inner current/velocity loop resolver receiver + sim-encoder Simulated encoder A / B / Z (RS-422) from drive SYS-ENC01 Level adapter (optional) Required if drive output ≠ MC221 encoder spec Quadrature + limits C200H MC221 Outer position loop

Five rules follow directly from the architecture and from the field-tested wiring practice for this product:

  1. The resolver cable between motor and drive is a drive-side cable only; it does not enter the MC221 slot or the C200H rack area.
  2. The simulated encoder is what the MC221 reads. Treat it like any high-speed quadrature signal: shielded twisted pair, 26 AWG minimum, RS-422 receivers at the MC221 end.
  3. If the drive's encoder output stage does not match the MC221 electrical specification (open-collector vs differential, voltage level, common-mode range), plan for an adapter card. On the C200H family this is the SYS-ENC01.
  4. Limit switches, drive-run, and drive-alarm contacts ride on discrete inputs to the MC221 via its terminal block; they do not flow through the encoder signal.
  5. Cable length between the MC221 faceplate and the XW2B-20J6-6 terminal block cannot exceed 1 m because the pre-wired harness XW2Z-100J-F1 ships at that fixed length.

Pre-Wired Harness and Terminal Block Specifications

Two Omron catalog numbers define the cable path from the MC221 faceplate to the field wiring:

Catalog # Function Length Notes
XW2Z-100J-F1 Pre-wired harness, MC221 connector 1 ↔ terminal block 1.0 m Fixed by design; do not splice or extend.
XW2B-20J6-6 20-point screw terminal block, M3.5 n/a Hosts the limit, run, alarm, and power supply wiring.
Why 1 m? The XW2Z-100J-F1 cable carries the analog and high-speed discrete signals between the MC221 and the field wiring. Extending it with intermediate connectors defeats the shielding and introduces ground loops. Plan the cabinet layout so the terminal block sits within that 1 m radius of the rack.

Connector 2 on the MC221 accepts the simulated-encoder input. The cable set for connector 2 typically follows the same XW2Z family at a corresponding length; consult W359-E1 appendix B for the exact catalog number, because wrong cable orientation (keyed vs non-keyed) is a common field bug. Encoder shield termination must land within 50 mm of the terminal block ground bar.

Resolver-to-Drive Wiring (and What Not to Run to the PLC)

Brushless motors with integral resolvers terminate at the drive with a resolver cable carrying the resolver rotor excitation return (R1 / R2) and the two stator windings (S1 / S3, S2 / S4). Shield drain terminates at the drive end only; do not bond the shield at the motor end. Resolver commons must be referenced to the drive side to avoid ground loops caused by long motor-to-drive cable runs.

Confirm the following before energizing:

Wire Drive terminal (typical) Signal Verify
R1 / R2 REF / REF- (resolver excitation input) Excitation reference Continuity to resolver rotor per motor datasheet.
S1 / S3 SIN / SIN- Sine winding Open-circuit resistance matches datasheet.
S2 / S4 COS / COS- Cosine winding Open-circuit resistance matches datasheet.
Drain Drive PE / shield bar Shield One-sided ground only; no continuity at motor end.

Common resolver-side mistakes encountered during commissioning:

  • Routing the resolver cable parallel to VFD power cables in the same tray. Move to a dedicated tray or separate by at least 200 mm.
  • Reversing SIN and COS pairs at the drive terminal: produces a stable but rotated feedback, leading to a permanent position offset that no software origin-search can correct because every position is wrong by the same electrical angle.
  • Terminating the resolver shield at both ends: drives the resolver carrier through ground and adds common-mode noise that the drive's resolver receiver cannot reject.
  • Routing the resolver cable back to the PLC instead of the drive. The PLC has no resolver inputs on this family; any such wiring simply does not get used.

Simulated Encoder Routing and the SYS-ENC01 Converter

The drive synthesizes the simulated encoder from its internal resolver-derived position. Common output formats include:

  • Incremental A/B/Z quadrature, differential line driver, RS-422 levels, 5 V supply typically.
  • Pulse + direction (CW / CCW), differential.
  • SSI / EnDat - some MC221 hardware revisions can be strapped for SSI absolute reading; check I06E-EN-01 hardware configuration.

Bring the simulated encoder from the drive output connector to MC221 connector 2 on its own shielded twisted-pair cable. If the drive delivers 5 V RS-422 and the MC221 encoder inputs are 5 V RS-422, the cable can land directly. When the drive output is open-collector, 24 V, or a non-standard differential level, insert the SYS-ENC01 adapter card between the drive and the MC221 encoder input.

Scenario Drive Output MC221 Encoder Input Adapter Required
Standard 5 V RS-422 incremental 26LS31 / equivalent 5 V RS-422 None - direct connection OK.
Open-collector 24 V Pull-up to 24 V 5 V RS-422 SYS-ENC01 (level-shift to 5 V differential).
Open-collector 24 V on legacy CPM2A Pull-up to 24 V High-speed DC inputs, 24 V Interposing high-speed input card / routing board.
Different line-driver supply (3.3 V) 3.3 V LVDS 5 V RS-422 SYS-ENC01 with verified DC specification.

SYS-ENC01 list-price reference (per piece, two pieces typically required for a 2-axis system):

Card List Price (EUR, 2004-era reference) Quantity for 2 axes
SYS-ENC01 81 2

Quote the adapter inside the bill of materials even if the project initially appears to use direct-coupled drives: late-surfacing open-collector outputs are the most common source of position-loop instabilities in retrofit work. Where the drive manual describes the simulated encoder as "current-sinking" but the MC221 calls for "current-sourcing differential," the SYS-ENC01 is mandatory. Verify against the drive's output-stage description rather than the drive family name.

Cross-platform note. On smaller Omron platforms such as the CPM2A, high-speed counter inputs cannot accept 24 V open-collector encoder signals directly; engineers historically added an interposing high-speed input module or a wiring adapter board for the same effect. The SYS-ENC01 is the analogous interposing card for the C200H / MC221 family - it addresses the same root cause (input-stage voltage and topology mismatch), not a different function.

Limit-Switch, Run, and Alarm Handshakes

The MC221 expects three classes of discrete signal that participate in motion safety and sequencing. All three land on connector 1 via the XW2B-20J6-6 terminal block.

Signal Class Source MC221 Reaction Recommended Wiring
Hardware positive limit (POT) Axis physical limit switch, NC contact to MC221 DI Decelerate to zero using preset deceleration; drive is de-energised via the enable contact. Dedicated shielded pair, NC; dual-channel if safety-rated (ISO 13849).
Hardware negative limit (NOT) Opposite-side limit switch, NC contact to MC221 DI Symmetric behaviour to POT. Dedicated shielded pair, NC.
Drive run / servo-on MC221 DO ↔ drive ENABLE / SON input Closed when an axis is started, opened on stop or fault. Use the MC221 DO; do not rely on CPU scan to drop the enable.
Drive alarm Drive ALM output contact ↔ MC221 DI Triggers fault handling, aborts current move, latches until reset. NC or NO per drive manual; bring back to MC221 DI for separate handling.
Origin / home sensor Proximity or photo sensor ↔ MC221 DI Used by the origin-return sequence and Z-pulse capture. Short-circuit proof signal pair.

Supervisory logic for one axis in IEC 61131-3 structured text:

IF bAlarm THEN
    bRunEnable := FALSE;            (* drop servo-on immediately *)
    eState    := STATE_FAULT;
ELSIF bPosLimit OR bNegLimit THEN
    bRunEnable := FALSE;
    eState    := STATE_LIMIT_HIT;
ELSIF bStart AND bReady THEN
    bRunEnable := TRUE;
    eState    := STATE_MOVING;
ELSE
    bRunEnable := FALSE;
    eState    := STATE_IDLE;
END_IF;

The state machine for one axis:

IDLE READY Servo-on asserted MOVING Profile in execution LIMIT_HIT Hardware limit reached FAULT Latched until reset Start=true Move issued Limit hit Move done / stop cmd Alarm Fault reset

Two rules for the handshake:

  • Decisions on servo-on / fault must originate on the MC221, not on the CPU ladder scan. The MC221's hardware response time is faster than the C200H scan and protects the machine during a CPU halt condition.
  • Hold the alarm input as NC by default; many drives assert alarms as NC contacts for fail-safe detection (broken wire = treated as alarm).

Backplane I/O Mapping Quick Reference

The MC221 occupies one I/O slot and is treated as a 4-word block in the C200H I/O table. The exact allocation is firmware-revision dependent; confirm against the cross-reference in I06E-EN-01 before any ladder bring-up. The summary below is a navigation aid, not a final pinout.

Word Offset (slot base + n) Direction Function
+0 MC221 → CPU Axis 1 status, current position low word, in-position flag.
+1 MC221 → CPU Axis 1 current position high word / Axis 2 status.
+2 MC221 → CPU Axis 2 position, alarms, error code.
+3 MC221 → CPU General status / sequence step / error flags.
+4 CPU → MC221 Start / stop / jog commands, axis select, override.
+5 CPU → MC221 Target position low word / parameters.
+6 CPU → MC221 Target position high word / sequence select.
+7 CPU → MC221 Speed, acceleration, deceleration setpoints.

The error-code field in word +3 contains numerical motion errors (range and interpretation per manual revision); read it first when a move aborts unexpectedly. Standard ladder diagnostics:

(* Read MC221 word +3, isolate error nibble *)
wStatus  := nSlotBase + 3;
bErrFlag := (wStatus AND 16#8000) <> 0;
wError   := wStatus AND 16#0FFF;
IF bErrFlag THEN
    eLastError := WORD_TO_INT(wError);
    nErrorLog[0] := eLastError;
END_IF;

Mechatrolink Alternative for Higher Axis Counts

The MC221 is a 2-axis board. When the application grows to 3 or more axes, stacking additional MC221 modules eventually becomes unwieldy; the engineering path typically shifts to a Mechatrolink-capable master that controls servo drives over a single daisy-chained serial cable. Two configurations recur on brownfield sites:

Configuration Max Axes Cabling When to Prefer
C200H-MC221 (×N) 2 per board Per-axis resolver cable + per-axis simulated encoder cable + per-axis terminal block 2-axis systems with simple wiring constraints and existing C200H base.
Mechatrolink master with W-series servo drives Up to 30 in a single daisy chain (master-dependent) Single daisy-chained serial cable + 24 V node power 3+ axes, multiple stations, mixed brushless and stepper, retrofit headroom.
Field-proven observation. C200HG + MC221 × N was a common building block in late-1990s packaging and labelling lines for 2-axis interpolated motion. For a greenfield 2-axis machine, the MC221 is still a viable economical choice; for greenfield with growth headroom, the Mechatrolink route avoids the next retrofit cycle.

Alternative Vendor Comparison

Other motion-control vendors were evaluated in parallel for this kind of application. Engineering choices that recur across similar deployments:

Vendor / Family Positioning Typical Strengths Typical Caveats
Omron (MC221 - this article) Slot-in board for the existing C200H PLC family. PLC platform synergy, established service and spare channels. 2-axis ceiling; per-axis cabling.
ELAU Application-engineered motion controllers, often pre-sized to a packaging line. Strong application libraries, specialist support. Smaller regional footprint; specialist training required.
Indramat (now Bosch Rexroth) General-purpose high-end motion + PLC. Highest-spec performance and resolver/drive integration. Premium price; resolver-loop tuning required.
Qem (with third-party brushless) Indexer + standalone controller with photo-cell alignment. Single-axis alignment features baked in. Multi-axis coordination requires additional programming.

Selection criteria when Omron is on the shortlist:

  • PLC platform already in use at the site - if the line already runs C200H, MC221 is a one-slot upgrade with no new programming environment to qualify.
  • Axis count - 2 axes: MC221; 3-30 axes: Mechatrolink master.
  • Service lifetime - C200H family is mature and the spare-parts channel is established; Mechatrolink II / III is the modern path.
  • Field-service training - existing Omron-certified technicians on-site reduces support overhead during commissioning and emergency callouts.

Commissioning and Verification Checklist

Use this matrix when bringing up a new MC221 system or a retrofit with new drives. Each row is a discrete step with a defined expected result.

Step Test Expected Result
1. Inspection Card seated, terminal block torqued, XW2Z-100J-F1 fully latched in. No exposed conductors; READY LED on MC221 within 5 s of rack power-on.
2. Resolver continuity Resistance R1↔R2, S1↔S3, S2↔S4 against motor datasheet at drive terminals. Values within ±5 % of datasheet; no shorts to PE.
3. Resolver shield Insulation resistance, shield to PE at drive end only. > 1 MΩ; not connected at motor end.
4. Encoder supply Measure +5 V across SYS-ENC01 input if used, or at MC221 encoder connector. 4.85 - 5.15 V DC, ripple < 50 mV.
5. Quadrature rotation Jog axis positive; verify MC221 position counter increments. Positive command = increasing counter; A leads B by 90° electrical.
6. Limit switch wiring Manually actuate limit; verify MC221 DI state. DI goes FALSE within 5 ms of switch trip.
7. Drive enable Issue MC221 servo-on from the CPU. Drive reads RUN input TRUE; motor current rises; holding torque present.
8. Alarm path Force drive fault (e.g. UV) and observe MC221 alarm input + drive response. Alarm input asserted, MC221 latches FAULT state, drive de-energises.
9. Profile verification Issue point-to-point; trace trapezoidal / S-curve profile on scope if available. Acceleration, constant velocity, deceleration phases match parameter table.
10. Two-axis interpolation Issue line / arc move via MC221 sequence. Both axes arrive within MC221-defined tracking tolerance.

Troubleshooting Matrix

Common failure modes encountered during commissioning and how to triage them.

Symptom Likely Cause First Check
Position counter drifts or reads garbage Encoder wiring mismatch (RS-422 polarity, A/B swap, missing shield). Compare SYS-ENC01 wiring diagram to actual wiring; swap A and A-not if polarity reversed; verify shield on one end only.
Position offset proportional to load Mechanical backlash in reducer/coupler, not encoder error. Move axis unloaded vs loaded; log position error at MC221.
Drive alarms at start of every move Limit switch wired to wrong MC221 DI; signal bouncing. Read raw DI state; add debounce per W359-E1 specification.
Both axes move unevenly in interpolation One axis sees a different cable delay or different encoder resolution set. Verify simulated-encoder pulses-per-rev on both axes match the MC221 parameter.
Move starts, encoder feedback valid, position aborts mid-move Drive dropping enable due to overcurrent / thermal / I²t. Read drive fault code; verify I²t setpoint matches motor datasheet.
MC221 LED flashes at power-on, never goes RUN Slot not configured in CPU I/O table or wrong slot base address. Re-assign slot per I06E-EN-01; write configuration to CPU.
Field wiring appears correct, axis still does not move Servo-on DO is open - either not driven by ladder or wrong DO address. Force the DO ON in monitor mode and verify drive enable input.
Sporadic following error at high speed Encoder cable in same tray as VFD output, or shield grounded at both ends. Re-route the encoder cable; re-verify shield termination.
Origin return completes but machine-coordinate offset persists SIN and COS swapped at drive terminal - rotated electrical zero. Compare drive resolver wiring against motor datasheet; correct and re-run origin.
MC221 reports "no encoder" after move started Open encoder wire or SYS-ENC01 absent where required. Verify drive-simulated-encoder wiring; install SYS-ENC01 if drive output is open-collector.

Spare-Parts and Lifecycle

The C200H-MC221 board, the XW2Z-100J-F1 harness, and the XW2B-20J6-6 terminal block are mature parts with long-running stock channels. The SYS-ENC01 was an established accessory used across many third-party drive retrofits of this era.

  • SYS-ENC01 list pricing published at 81 EUR per card; for a 2-axis system plan 2 × SYS-ENC01 plus spares.
  • Manual codes I06E-EN-01 and W359-E1 remain the canonical references; verify the manual version number against the board's nameplate revision before applying parameters.
  • For current Omron motion-controller alternatives covering higher axis counts with a more compact wiring footprint, evaluate current-generation Mechatrolink-capable controllers (CJ / NJ / NX families) on the manufacturer's industrial automation site.
  • Spare XW2Z family harnesses are interchangeable between connector 1 and connector 2 only when keyed identically; never substitute a different-keying harness.

Frequently Asked Questions

Does the resolver cable from the brushless motor go to the MC221 or to the servo drive?

The resolver cable terminates on the servo drive only. The MC221 is an encoder board; it never sees resolver signals. The drive returns a simulated incremental encoder (typically A / B / Z RS-422) that the MC221 reads to close the outer position loop.

When is the SYS-ENC01 converter card required?

Whenever the drive's simulated-encoder output electrical format does not match the MC221 encoder-input specification - typically when the drive is open-collector 24 V, 3.3 V LVDS, or otherwise non-compliant with 5 V RS-422 differential. Quote two SYS-ENC01 cards for a 2-axis system.

What is the maximum length of the cable between the MC221 and the XW2B-20J6-6 terminal block?

The pre-wired harness XW2Z-100J-F1 is 1.0 m and is not designed to be extended. Place the terminal block within that radius of the rack and route the field cables from the terminal block onward.

Can the MC221 control more than two axes?

The MC221 itself controls two axes. For 3 + axes, a Mechatrolink master with W-series servo drives handles up to 30 axes on a single daisy-chain with one cable - replacing the per-axis cable harness that the MC221 would otherwise require.

Which Omron manuals document the C200H-MC221?

I06E-EN-01 (Motion Control Board Operation Manual) and W359-E1 (Motion Control Board Programming Manual). Verify the manual revision against the board's nameplate revision before applying parameter tables.

How do I decide between C200H-MC221 and a standalone indexer?

Pick the C200H-MC221 when the machine already uses a C200H-family PLC and only needs 2 axes. Pick a standalone indexer (such as those offered by specialist motion vendors) when axis count, interpolation complexity, or cabling footprint dominates the design and the existing PLC platform is not a constraint.

Back to blog