Encoder Protocol Matcher

SAS IntelliLink™ Encoder Bridge

Tell us the encoder signal you have and what the controller expects — including a second output for dual bridges.

IntelliLink SSI to incremental A/B/Z bridge — match the protocol you have to the protocol you need
Match the protocol you have to the protocol the CNC or drive expects.

Configuration Tool Protocol match

Match encoder signal to controller protocol

Example: EnDat 2.22 encoder in, Fanuc Serial to the CNC and HTL (Push-Pull) on the second port. Then open the Encoder Bridge configurator with those ports filled in. Input and output use the same 26-protocol catalog.

Encoder you have

Controller expects (port 1)

Second output (optional)

Leave NONE unless you need a dual bridge (e.g. BiSS-C + HTL).

Configuration Summary

Configuration and your notes are copied into the contact form below. You can still edit the message before submitting.

Send your configuration to SAS

Complete the form with your contact details. The message is pre-filled with your protocol match — add machine and CNC type if available.

← Back to Encoder Bridge product page

Configuration inquiry

Your information is secure and used only to respond to your inquiry.

Submit config

FAQ

Questions plant engineers ask

Practical answers on encoder protocol matching — from Sharjah, for plants in the UAE and GCC.

When should I use the matcher instead of the configurator?

Use the matcher when you only know “I have X, the CNC wants Y”. It then opens the Encoder Bridge configurator, including a second output port for dual bridges.

Can one encoder feed two protocols?

Yes. Set output port 2 — for example BiSS-C to the CNC and HTL to a second drive. SAS builds that as a dual Encoder Bridge.

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 protocol matching 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.