An SSI encoder is an absolute rotary encoder that reports shaft position through the Synchronous Serial Interface protocol using two differential signal pairs — clock and data — instead of parallel pulse or fieldbus output. Reliable operation depends on matching the encoder and controller on frame length, Gray or binary code format, maximum clock frequency at the installed cable length, and synchronous or asynchronous timing mode; a mismatch on any one of these produces no valid position reading, not a partially correct one. Typical SSI signal faults trace back to a short list of root causes: data-format mismatch, frame-length mismatch, clock/data polarity reversal, cable length exceeding the frequency limit, shield grounding at both ends, or an asynchronous encoder running in a synchronous-timing system. This guide covers how the SSI protocol moves data, what the wiring and grounding requirements are, and how to trace each fault pattern back to its root cause.
How the SSI Protocol Works
SSI is a master/slave, point-to-point serial protocol. The controller, drive, or PLC card acts as the master and generates the clock signal; the encoder acts as the slave and shifts out one bit of position data for every clock pulse it receives. Both signals — clock and data — run as differential pairs based on RS-422 electrical characteristics, which gives the interface good noise immunity and allows longer cable runs than single-ended signaling would support.
When the line is idle, both the clock and data lines sit high. A transmission cycle begins when the master starts pulsing the clock. On the first falling edge of the clock, the encoder latches its current position value internally so that the number being transmitted cannot change mid-frame even if the shaft keeps rotating. The encoder then shifts out the position word one bit at a time, most significant bit first, synchronized to each subsequent clock edge. Once the full word has been sent, the data line returns high and the interface resets, ready for the next request.
Because SSI has no addressing scheme, only one encoder can sit on a single SSI channel — it is a strictly one-to-one link between a single master port and a single slave device. Systems that need to read multiple absolute encoders need one dedicated SSI channel per encoder, not a shared bus.
Data Format: Binary vs. Gray Code, and Frame Length
The position word an SSI encoder sends is not a fixed universal size — the total frame length depends on the encoder's resolution, and the controller must be configured to expect exactly that many bits, or the reading will be garbage even though the wiring is correct. A typical multiturn SSI encoder frame combines two fields: a block of bits representing single-turn angular position within one revolution, and a block of bits representing the revolution count for multiturn tracking. Common combinations run in the range of 24 to 25 total bits, but this varies by model, and the split between singleturn and multiturn bit count must match the controller's parameter settings exactly.
Position data can be encoded as either straight binary or Gray code, and this is a frequent source of misconfiguration. In Gray code, only one bit changes between any two adjacent position values; in binary, multiple bits can change simultaneously at certain transitions. That difference matters because binary counting has a physical race condition — if one bit line turns off a fraction of a microsecond before the next bit turns on, the transmitted value can transiently jump to a completely wrong number before settling. Gray code avoids this by design, which is why most SSI absolute encoders default to Gray code output. If a controller is configured for binary but the encoder is set to Gray (or vice versa), the position value will read as a nonsensical, jumping number even though every wire is connected correctly — this is one of the most common "encoder acts crazy" complaints traced back to a data-format mismatch rather than a hardware fault.
Some encoders also append an error status bit, commonly placed after the resolution bits, that flags an internal fault condition. If the controller isn't configured to mask out or interpret that bit, it can silently corrupt the apparent position value by one bit position.
Wiring and Interface Requirements
An SSI interface uses four active conductors: Clock+, Clock-, Data+, and Data-, plus a shield and power supply lines. Because both clock and data are differential, correct polarity matters — reversing a + and - pair on either signal typically produces no communication at all rather than a partially working link, which makes polarity one of the first things to check on a dead interface.
Cable length and maximum clock frequency trade off directly against each other: the higher the clock rate, the shorter the cable run that can reliably carry a clean signal, since propagation delay and cable capacitance both degrade the edges the encoder needs to see clearly. As a general engineering guide for twisted-pair RS-422 cabling, clock frequency should be derated as cable length increases — roughly 400 kHz for runs under 50 m, 300 kHz for runs under 100 m, 200 kHz for runs under 200 m, and 100 kHz for runs approaching 400 m. Installations that run a clock frequency too high for the actual cable length typically show intermittent or corrupted readings that look electrical in nature but are actually a timing-margin problem, not a wiring defect.
Twisted-pair cable meeting RS-422 characteristics is the standard requirement, and shield continuity back to a single reference point (not looped or double-grounded) is important for keeping electrical noise off the clock and data lines, particularly in installations near VFDs or switching power equipment. After the last bit of a frame is shifted out, the encoder holds the data line low for a brief pause period — commonly a minimum of around 20 microseconds — before it will accept a new clock burst; a master that starts a new request before this pause completes will simply receive the same value again rather than an updated one, which can look like a stuck or frozen position reading during high-speed polling. Some encoders also support a multiple-transmission (ring-shift) mode, where the master continues clocking past the end of one frame to receive the same position value a second time for comparison — a useful integrity check in applications where a single corrupted read could cause a control fault, though not every model supports it.
There are two SSI timing modes worth distinguishing during installation: synchronous mode, where the position is only sampled in direct response to the master's clock burst, and asynchronous mode, where the encoder continuously recalculates its position internally on a fixed cycle independent of when the master requests data. Non-programmable encoders are typically fixed to asynchronous mode by default. If a system depends on tight synchronous timing and the connected encoder is running asynchronous, position values can lag by up to one internal update cycle, which shows up as small but real position error under fast motion.
SSI vs. Other Absolute Encoder Interfaces
SSI's advantage over fieldbus-based absolute encoders (CANopen, Profibus, Profinet) is simplicity: no addressing, no bus configuration, minimal protocol overhead, and very low latency because the master controls timing directly rather than waiting on a shared network cycle. That simplicity is also its limitation — SSI carries no diagnostic handshake, no automatic device identification, and no ability to share a single controller port across multiple encoders. A system that needs several absolute encoders on one network segment, remote diagnostics, or hot-swappable device identification is generally better served by a fieldbus or industrial Ethernet interface. A system that needs one encoder, one controller, minimal wiring, and the fastest possible raw position readout is generally better served by SSI.
Common SSI Signal Faults and What Causes Them
Across installed SSI links, the recurring fault pattern is narrow: no data with clock present, unstable or jumping position readings, a fixed repeatable offset, intermittent dropout under motion, slow position drift at high speed, or total failure after a nominally identical replacement — and each of these maps to a specific, checkable root cause rather than a random hardware defect.
No data returned, clock present: usually a Data+/Data- polarity reversal, an unpowered encoder, or a cable run exceeding the maximum length supported at the configured clock frequency.
Position value jumps or reads unstable at rest: almost always a Gray code / binary code mismatch between encoder output and controller configuration, rather than a wiring fault — check the data format setting before touching any cable.
Position value off by a fixed, repeatable offset: typically a frame length mismatch — the controller is reading more or fewer bits than the encoder is actually sending, often because the singleturn/multiturn bit split wasn't configured to match the installed encoder's resolution.
Intermittent dropouts under motion, stable at standstill: usually electrical noise coupling into the clock or data pair from nearby motor, VFD, or switching cabling, often worsened by shield grounded at both ends instead of one, or by cable routed in the same conduit as power wiring.
Position drifts slightly under fast motion but reads correctly at low speed: consistent with an asynchronous-mode encoder running in a system that expects tight synchronous timing — the internal update cycle can't keep pace with the sampling rate the controller assumes.
No communication after replacing a failed encoder with a nominally identical model: check clock frequency limits, resolution/bit count, and Gray/binary output setting on the replacement — these parameters can differ between production runs or supplier revisions of an otherwise compatible part, and a mismatch on any one of them produces the same "no valid data" symptom as a wiring fault.
Selecting an SSI Encoder Replacement
When an installed SSI encoder needs to be matched or replaced, the parameters that must be preserved — in order of how often they cause failures if missed — are: total frame length (singleturn + multiturn bit count), data format (Gray or binary), maximum clock frequency the encoder supports at the required cable length, synchronous versus asynchronous timing behavior, and mechanical shaft/flange interface. Voltage supply range and connector type matter for installation but rarely cause the kind of silent, hard-to-diagnose faults that a resolution or code-format mismatch produces. Confirming these parameters against the original nameplate before specifying a replacement avoids the majority of post-installation troubleshooting calls.
For installed SSI encoders that are obsolete, discontinued, or otherwise unavailable from the original source, a custom compatible replacement can be engineered around the confirmed frame length, code format, clock/timing behavior, and mechanical interface of the original unit, preserving the existing control-system configuration without requiring controller-side reprogramming.
