SSI Output: From Frame Structure to Master Implementation

SSI is synchronous serial: the master clocks, the sensor shifts out one bit per clock. Four wires look simple, and almost every failure sits in the timing detail of a single frame — the latch edge, the bit width, the code format, and the monoflop gap between reads. The articles below run from understanding the frame, through commissioning, to reading it on a master.

01Understand the frame first

02Commissioning

03Getting it into a master

  • Germanjet SSI Sensor Master: Modules and Bit-Banged Reads

    SSI saves the protocol, not the implementation: you supply the clock, assemble the bits and keep the frame gap. Covers where the four master-side settings come from, how to fill in a PLC module, a GPIO bit-bang routine with three traps, and the time budget per frame.

  • Turning Raw Position Counts into Millimetres in the PLC

    The comms are up and the number moves, but it is an integer, not a distance. Conversion needs exactly three parameters: how many counts span the range, how far the zero is offset, and which way is positive. The difficulty is that the three live in three places - sensor firmware, program coefficients and the mechanical datum. Analogue, SSI, fieldbus and Start-Stop each hand over a different kind of raw value, so this article separates their conversion entry points and covers how to avoid throwing resolution away in integer arithmetic.

  • Start-Stop Interface: Pulse Interval Converted to Position

    Start-Stop magnetostrictive sensor pulses on the echo, so the controller times interval by wave speed. Simple wiring, but it needs a fast controller.

  • Matching Sensor Output to the Controller's Available Channels

    Analog, SSI or fieldbus? Pick this magnetostrictive displacement sensor by controller channels, axis count and diagnostics—matrix covers 191 to 199.

04Selection and comparison