Square Wave (Incremental)
- TTL (RS-422)
- HTL (Push-Pull)
- Open Collector (NPN/PNP)
SAS IntelliLink® — Encoder / Signal Converter
Universal Encoder Signal Converter — 26 protocols in, 26 protocols out
The SAS IntelliLink™ Encoder Bridge is a point-to-point encoder signal converter: the same 26-protocol catalog on input and output (square wave, analogue, synchronous serial, OEM proprietary serial and fieldbus). EnDat 2.1, 2.2 and 2.22 are separate versions; Fanuc Serial is supported; TTL (RS-422) covers incremental square wave. Not a catalog SKU — SAS custom-builds each unit, including dual-output. Need multi-axis fiber over long or noisy runs instead? That is the Encoder Hub.
Product Snapshot
Encoder Bridge
26 protocols in
Square wave, analogue, synchronous serial, OEM serial and industrial fieldbus
26 protocols out
Same catalog as input — any listed protocol to any listed protocol
676+ combinations
26 × 26 matrix, plus dual-output builds. EnDat 2.1 / 2.2 / 2.22 counted separately
Signal Conversion
Same encoder protocol catalog on input and output.
The Encoder Bridge sits between your existing encoder and your target system. Input and output use the same 26 protocols across five families. EnDat 2.1, 2.2 and 2.22 are separate selectable versions. Fanuc Serial is proprietary serial; TTL (RS-422) is incremental square wave.
Encoder Inputs (26)
- Square Wave (Incremental)
- Analog (Sine/Cosine)
- Synchronous Serial
- Proprietary Serial
- Industrial Fieldbus & Ethernet
Encoder Outputs (26)
- Square Wave (Incremental)
- Analog (Sine/Cosine)
- Synchronous Serial
- Proprietary Serial
- Industrial Fieldbus & Ethernet
Analog (Sine/Cosine)
- 1 Vpp
- 11 µA
Synchronous Serial
- EnDat 2.1
- EnDat 2.2
- EnDat 2.22
- BiSS-C
- SSI
- SPI
Proprietary Serial
- HIPERFACE
- HIPERFACE DSL
- Tamagawa Serial
- Panasonic Serial
- Yaskawa Serial
- Mitsubishi Serial
- Fanuc Serial
Industrial Fieldbus & Ethernet
- EtherCAT
- PROFINET
- EtherNet/IP
- CANopen
- PROFIBUS
- DeviceNet
- Modbus RTU / TCP
- IO-Link
Each hardware version is a custom-built, fixed input–output combination engineered to the client request. Dual-output units add a second protocol from the same catalog. You specify the pair — SAS engineers, builds and tests the unit.
How It Works
Three steps from your encoder to your controller.
You don’t need to write firmware or design the converter. Tell us what goes in and what must come out — SAS custom-builds the hardware and engineers the conversion to your request.
1. Tell us your signals
What encoder do you have? What protocol does your drive, CNC or controller require as input? That’s all we need. We identify the correct conversion and specify the version for you.
2. SAS engineers a custom build
Every Encoder Bridge is custom-built to the client request: input, output, voltages and optional second port. It is assembled, programmed and tested by SAS engineers before dispatch.
3. Install and run
Wire the unit between your encoder and your controller. The Encoder Bridge converts the signal transparently — your target system sees exactly the encoder protocol it expects.
Supported Protocols
Which encoder protocols can we accept and output?
Input and output use the same 26 protocols. EnDat 2.1, 2.2 and 2.22 are listed separately because they are different interfaces. Fanuc Serial is the proprietary serial option; TTL (RS-422) is incremental square wave.
| Family | Protocol | Description | In | Out |
|---|---|---|---|---|
| Square Wave | TTL (RS-422) | Incremental square wave, transistor-transistor logic / RS-422. | Yes | Yes |
| Square Wave | HTL (Push-Pull) | High-threshold logic incremental, typically 10–30 V push-pull. | Yes | Yes |
| Square Wave | Open Collector (NPN/PNP) | Open-collector incremental outputs, NPN or PNP. | Yes | Yes |
| Analog | 1 Vpp | 1 volt peak-to-peak sine/cosine analogue. | Yes | Yes |
| Analog | 11 µA | Current-based sine/cosine analogue. | Yes | Yes |
| Synchronous Serial | EnDat 2.1 | Heidenhain EnDat 2.1 — separate from 2.2 and 2.22. | Yes | Yes |
| Synchronous Serial | EnDat 2.2 | Heidenhain EnDat 2.2 bidirectional serial. | Yes | Yes |
| Synchronous Serial | EnDat 2.22 | Heidenhain EnDat 2.22 high-speed variant. | Yes | Yes |
| Synchronous Serial | BiSS-C | Open-source bidirectional serial for absolute encoders. | Yes | Yes |
| Synchronous Serial | SSI | Synchronous Serial Interface — clocked absolute position. | Yes | Yes |
| Synchronous Serial | SPI | Serial Peripheral Interface encoder link. | Yes | Yes |
| Proprietary Serial | HIPERFACE | SICK HIPERFACE hybrid analogue + digital encoder interface. | Yes | Yes |
| Proprietary Serial | HIPERFACE DSL | SICK HIPERFACE DSL single-cable digital. | Yes | Yes |
| Proprietary Serial | Tamagawa Serial | Tamagawa proprietary serial encoder protocol. | Yes | Yes |
| Proprietary Serial | Panasonic Serial | Panasonic proprietary serial encoder protocol. | Yes | Yes |
| Proprietary Serial | Yaskawa Serial | Yaskawa proprietary serial encoder protocol. | Yes | Yes |
| Proprietary Serial | Mitsubishi Serial | Mitsubishi proprietary serial encoder protocol. | Yes | Yes |
| Proprietary Serial | Fanuc Serial | Fanuc proprietary serial encoder protocol. Incremental square wave uses TTL (RS-422). | Yes | Yes |
| Fieldbus | EtherCAT | Encoder position on EtherCAT. | Yes | Yes |
| Fieldbus | PROFINET | Encoder position on PROFINET. | Yes | Yes |
| Fieldbus | EtherNet/IP | Encoder position on EtherNet/IP. | Yes | Yes |
| Fieldbus | CANopen | Encoder position on CANopen. | Yes | Yes |
| Fieldbus | PROFIBUS | Encoder position on PROFIBUS. | Yes | Yes |
| Fieldbus | DeviceNet | Encoder position on DeviceNet. | Yes | Yes |
| Fieldbus | Modbus RTU / TCP | Encoder position on Modbus RTU or TCP. | Yes | Yes |
| Fieldbus | IO-Link | Encoder position on IO-Link. | Yes | Yes |
Proprietary Serial
Fanuc Serial, HIPERFACE DSL and other OEM encoder buses.
Fanuc Serial is a proprietary serial encoder protocol, available as input and as output. Incremental square wave for Fanuc-style A/B/Z uses TTL (RS-422). HIPERFACE, HIPERFACE DSL, Tamagawa, Panasonic, Yaskawa and Mitsubishi serial sit in the same family — same catalog on both sides of the bridge.
OEM encoder, standard control
Machine encoder is Fanuc Serial, Tamagawa or HIPERFACE DSL. The Bridge outputs SSI, EnDat 2.2, BiSS-C, TTL (RS-422) or a fieldbus the new drive expects.
Standard encoder, OEM CNC
Existing 1 Vpp, SSI or EnDat encoder can feed Fanuc Serial, Mitsubishi Serial or EtherCAT so the control sees the protocol it was designed for.
Like-for-like plus a second port
Fanuc Serial in and Fanuc Serial out is a valid pair — isolation, dual-output or a second port in another protocol from the same encoder.
How to Choose Your Version
Your version is defined by two things: your input and your output.
Each SAS IntelliLink Encoder Bridge is a custom-built, fixed-input and fixed-output hardware unit. There is no configuration required on your side. You simply specify the encoder signal you have and the protocol your target system requires — and that determines which device version we build for you.
| You have (input) | You need (output) | Typical use case |
|---|---|---|
| 1 Vpp | Fanuc Serial | Analogue encoder feeding a Fanuc control that expects Fanuc Serial |
| 1 Vpp | EnDat 2.22 | Legacy analogue encoder into a high-speed EnDat 2.22 drive chain |
| Fanuc Serial | EnDat 2.2 | Keep the Fanuc serial encoder; feed a Siemens or Bosch drive that expects EnDat 2.2 |
| EnDat 2.1 | EnDat 2.22 | Older EnDat 2.1 encoder adapted to a control that requires EnDat 2.22 |
| 11 µA | TTL (RS-422) | Current-loop sine/cosine encoder driving a CNC that requires incremental square wave |
| HIPERFACE DSL | EnDat 2.2 | SICK single-cable encoder integrated into an EnDat-based drive chain |
| SSI | CANopen | Absolute encoder feeding position data into a CANopen network |
| BiSS-C | Fanuc Serial | Modern BiSS-C encoder adapted to a Fanuc CNC that expects Fanuc Serial |
| TTL (RS-422) | EtherCAT | Incremental encoder integrated into an EtherCAT motion network |
| EnDat 2.22 | SSI | EnDat 2.22 encoder feeding a PLC or controller that only supports SSI absolute input |
Not sure which version you need? Send us your encoder datasheet and your controller specification — our engineers will identify the correct conversion and confirm the version for you.
Applications
Where the Encoder Bridge solves real problems.
Encoder signal incompatibility is one of the most common and costly integration problems in industrial automation, CNC and drive retrofit work. The SAS IntelliLink Encoder Bridge eliminates it.
CNC machine retrofits
Upgrading a CNC control to Fanuc while keeping existing encoders. The Encoder Bridge converts the listed input protocol to Fanuc Serial or TTL (RS-422) — no encoder replacement, and each unit is custom-built for the machine.
Servo drive replacement
Replacing a servo drive with a different brand that requires a different encoder protocol. The Encoder Bridge sits between the existing encoder and the new drive — both sides stay unchanged.
Encoder protocol conversion
Machine encoder outputs a protocol (e.g. BiSS-C or EnDat) that the controller or PLC does not natively support. The Encoder Bridge translates to the required interface format.
Drive and motor integration
Integrating third-party motors with 1 Vpp or 11 µA sine/cosine feedback into drive systems that require digital encoder input. Converts analogue signals to EnDat, BiSS-C, SSI or TTL (RS-422).
Fieldbus integration
Routing encoder position onto EtherCAT, PROFINET, EtherNet/IP, CANopen, PROFIBUS, DeviceNet, Modbus or IO-Link. Converts any listed encoder protocol to the plant bus.
Repair and spare part replacement
Original encoder model is discontinued. A compatible encoder with a different output protocol can be used as a replacement with the Encoder Bridge — no control system changes required.
Why SAS IntelliLink
A custom-built unit — engineered to the client request.
Every SAS IntelliLink Encoder Bridge is custom-built and engineered by SAS Middle East FZC for the client’s input, output, voltages and application. We do not sell a blank evaluation board. If the pair is unusual, we still engineer it. You receive a finished, tested unit ready for installation.
Custom build per request
Each unit is engineered to the client specification — protocol pair, dual output, voltages and connectors. Non-standard requests go through the same SAS engineering path.
26 inputs × 26 outputs
Same protocol catalog on both sides, including EnDat 2.1, 2.2 and 2.22 as separate versions. Dual-output builds add another port from the same list.
Fanuc Serial and TTL (RS-422)
Fanuc Serial is proprietary serial in and out. Incremental square wave uses TTL (RS-422). HIPERFACE DSL, Tamagawa, Panasonic, Yaskawa and Mitsubishi serial are in the same family.
Engineered for industrial use
Designed for the electrical environment of CNC machines, servo drive cabinets and industrial automation panels.
Technical support included
SAS engineering support covers selection, integration questions and any signal-level troubleshooting after delivery.
Retrofit without downtime risk
Adapt existing encoders or replace discontinued models without modifying the control system — minimum machine downtime.
Encoder Bridge FAQ
Common questions about the SAS IntelliLink Encoder Bridge.
These answers help engineers and buyers confirm whether the Encoder Bridge fits their signal conversion requirement.
Which encoder protocols are supported?
The same 26 protocols on input and output across five families: square wave (TTL RS-422, HTL, Open Collector), analogue (1 Vpp, 11 µA), synchronous serial (EnDat 2.1/2.2/2.22, BiSS-C, SSI, SPI), proprietary serial (HIPERFACE, HIPERFACE DSL, Tamagawa, Panasonic, Yaskawa, Mitsubishi, Fanuc Serial) and fieldbus (EtherCAT, PROFINET, EtherNet/IP, CANopen, PROFIBUS, DeviceNet, Modbus RTU/TCP, IO-Link).
Are input and output counts the same?
Yes. 26 in and 26 out — a 26 × 26 matrix. Dual-output builds add a second port from the same catalog (for example BiSS-C on port 1 and HTL on port 2).
Is Fanuc Serial supported?
Yes. Fanuc Serial is a proprietary serial option on input and output. Incremental square wave uses TTL (RS-422).
How do I select the right version?
Identify your encoder’s output signal type and the protocol your controller or drive requires as input. Those two values define your version. If you’re not sure, send us your encoder and controller datasheets and we will confirm.
Can 11 µA or 1 Vpp be converted to a digital output?
Yes. Both analogue sine/cosine options are supported as input and as output. They can be converted to any listed protocol, including EnDat 2.1/2.2/2.22, SSI, BiSS-C or TTL (RS-422).
Do you custom-build for client requests?
Yes. Every Encoder Bridge is a custom hardware build. SAS engineers the conversion to the client’s encoder, controller, voltages and layout. Listed protocols are the starting catalog; non-standard pairs, connectors and dual-output versions are engineered on request.
Encoder BridgePoint-to-point protocol converter — 26 in / 26 out, optional dual output, short copper runs.
Encoder HubMulti-axis fiber link — 2–5 encoders per string, up to 4 strings / 20 axes, up to 500 m, EMI immune.
Use Bridge whenThe encoder protocol does not match the drive, CNC or PLC.
Use Hub whenDistance, noise or many axes make copper encoder cables unreliable.
FAQ
Questions plant engineers ask
Practical answers on encoder conversion — from Sharjah, for plants in the UAE and GCC.
What does the Encoder Bridge do?
It converts encoder signals so a drive, CNC or PLC can read a sensor it was not designed for. The same 26-protocol catalog is available on input and output — EnDat 2.1, 2.2 and 2.22 are separate versions. Every unit is a custom build engineered to the client request, with an optional second output port.
Which inputs and outputs are available?
The same 26 encoder protocols on both sides, in five families: square wave (TTL RS-422, HTL Push-Pull, Open Collector), analogue (1 Vpp, 11 µA), synchronous serial (EnDat 2.1/2.2/2.22, BiSS-C, SSI, SPI), proprietary serial (HIPERFACE, HIPERFACE DSL, Tamagawa, Panasonic, Yaskawa, Mitsubishi, Fanuc Serial) and fieldbus (EtherCAT, PROFINET, EtherNet/IP, CANopen, PROFIBUS, DeviceNet, Modbus RTU/TCP, IO-Link). That is a 26×26 matrix, plus dual-output builds.
Do you custom-build Encoder Bridges for client requests?
Yes. SAS does not sell a generic off-the-shelf module. Each Encoder Bridge is custom-built and engineered to the client’s input, output, voltages, dual-output layout and application. If the combination is not a standard pair, send the encoder and controller details — we engineer the version and test it before dispatch.
Is Fanuc Serial supported?
Yes. Fanuc Serial is a proprietary serial option on input and output. Incremental square wave uses TTL (RS-422). HIPERFACE DSL and other OEM serial buses are in the same family.
Do you build dual-output bridges?
Yes. One encoder input can feed two ports at once — for example BiSS-C in, BiSS-C out on port 1 and HTL on port 2. Configure both ports in the free configurator.
How do I choose the right version?
Tell us the encoder signal you have, the protocol the controller expects, and any dual-output or connector constraints. Use the configurator or send nameplate photos. SAS engineers a custom build to that request.
Is this the same as the fiber Encoder Hub?
No. Choose the Encoder Bridge for one encoder to one or two controller protocols on a short copper run (point-to-point conversion, optional dual output). Choose the Encoder Hub when several axes must travel over duplex fiber up to 500 m with EMI isolation — up to 20 axes via Master Unit strings. Same 26-protocol catalog; different architecture.
When should I use Encoder Bridge vs Encoder Hub?
Use the Bridge when the problem is protocol mismatch (encoder speaks X, CNC wants Y). Use the Hub when the problem is distance, noise or multi-axis copper runs that need fiber. Many plants use both: Hub for field axes, Bridge where a single axis still needs a protocol change.
Do you work on site in the UAE and GCC?
Yes. SAS Middle East FZC is based in Hamriyah Free Zone, Sharjah. We survey, engineer and commission encoder conversion on site across the UAE and GCC.
How do we request a technical proposal?
Use Request a technical proposal and include the machine, protocol or fault, and the site. We typically reply within 24 hours.
Need an answer for your site? Request a technical proposal — we typically reply within 24 hours.
Ready to solve your encoder interface problem?
Tell us your encoder signal type and your target output protocol — or use the Encoder Bridge Configurator to build your specification and submit directly.
Contact Information
Email
info@sas-engineering.net (Technical inquiries)
sales@sas-engineering.net (Sales inquiries)
Location
Hamriyah Free Zone
Sharjah, UAE
SAS IntelliLink™ Encoder Bridge
Custom-built, engineered and tested by SAS Middle East FZC for your specific signal conversion requirement.