Skip to content

New

Skysat delivers its products throughout the European Union 🇪🇺

commande-proportionnelle

S-Link and eVision: Sleipner's thruster control architecture

The short answer

S-Link is Sleipner's CAN control network: it links compatible devices through a backbone, drops, connectors and terminators designed for that system. eVision designates a generation of thrusters with integrated power electronics and, depending on configuration, proportional control. The two notions are not synonyms. To design the whole, start from the exact references of thruster, panel and interfaces, draw the S-Link topology, add the control power feed and the required terminators, then validate the high-power circuit separately. Do not transpose NMEA 2000 rules or the compatibility of an old Side-Power installation without documentation.

Separate power, control and integration

A thruster system stacks several layers. The power circuit links batteries, protection, battery switch and motor. The control network carries orders and status. Interfaces may finally exchange with a remote, a third-party joystick, a display or an external signal. This separation avoids a frequent mistake: believing a network cable powers the motor, or that connector compatibility proves functional compatibility. The model's installation diagram remains the reference for each layer.

In the Sleipner catalogue, S-Link cables, controls, interfaces and thrusters are presented as distinct families, so you can build a verifiable bill of materials.

Understand the S-Link backbone

S-Link is described by Sleipner as a CAN system providing intelligent communication between compatible devices. The range uses dedicated backbone cables, drop cables, joiners and terminators. The backbone forms the main line; equipment connects per the manual's topology, using the authorised components and lengths. Terminators close the network electrically at the prescribed points. A drop must not become an improvised second backbone.

Before purchase, draw the actual run: bow thruster, possible stern thruster, panel, automatic main switch, interfaces and connection points, with every length noted. That step avoids pointless extensions and connectors hidden in unreachable places.

Do not confuse S-Link and NMEA 2000

Both rely on CAN communication, but they are not interchangeable networks. Connectors, power, messages and integration rules belong to their respective systems. Do not insert an S-Link device on an NMEA 2000 backbone, or the reverse, without an explicitly documented interface. Our NMEA 2000 architecture guide helps compare the topologies without mixing them.

An interface to a display or an external signal has a defined role. For instance, the ESI-1 interface is documented to convert a 4–20 mA analogue signal to S-Link and drive certain specific families. That description does not make every 4–20 mA device automatically suitable: range, logic, power and functions must match the manual.

Place eVision in the architecture

eVision thrusters use a design and electronics enabling, notably, proportional control depending on the range. Sleipner publishes datasheets, manuals, drawings and wiring diagrams for each model. Motor, integrated inverter, voltage, main switch and control form one assembly.

The practical benefit of variable thrust is dosage: a light correction to hold the bow, more thrust against a gust, finer coordination with the stern unit. It does not exempt you from duty cycle, temperature limits or the energy budget. An eVision retrofit claim must be checked model by model: record the full reference of the old thruster, voltage, tunnel, motor, control and accessories. A historic Side-Power badge or an identical diameter does not guarantee a direct conversion.

Choose controls by function

Define the stations needed: main helm, flybridge, outside station or remote. Decide whether proportional control is required or a directional order suffices. Check status feedback, alarms, priority between stations and the intended emergency-stop function. Panels and remotes must appear in the configuration's official compatibility list. Do not mix an old on/off panel, an S-Link interface and an assumed eVision function.

Bow and stern controls must also respect identification and direction of operation. For integration with a joystick or third-party system, use Sleipner's dedicated document — and identify who owns the logic, the safeties and the stop. A successful physical link is not enough to validate failure scenarios.

Power and terminate the network correctly

The S-Link network receives its power per Sleipner's diagrams. Use the recommended cable and protection. Check voltage at the most distant devices and avoid injecting multiple unplanned power feeds. The high-power circuit belongs with the battery and power-generation hubs.

Check the presence and position of terminators. Label both ends of every cable and keep joints accessible and dry per their protection level. Keyed connectors ease assembly but do not fix a bad topology. Physically separate signal cables from high-power conductors and interference sources as far as practicable, per the manual. Support the harnesses and protect them from traction, chafe and standing water.

Commission in stages

Before powering the motor, check network continuity, connectors, terminators and circuit polarity. Power the control side, verify device detection and record any fault code. Then test each direction with a short pulse in safe water. Confirm control stations, remote, stop and alarms. On a proportional system, raise the setpoint gradually and watch voltage, noise and behaviour.

Keep the as-built diagram, references and document versions. At the next evolution, that proof beats a harness whose origin nobody remembers.

Official sources

Sleipner — S-Link interface presentation and network FAQ; ESI-1 interface, 4–20 mA signal and documents; E100 eVision thruster, compatibilities and manuals; eVision range.

Read next

Previous Post Next Post

Leave A Comment

FAQ

Is S-Link directly compatible with NMEA 2000?

No. They are two distinct networks, even though both rely on CAN communication. Any bridge requires an interface and a function explicitly documented by Sleipner.

Does eVision mean the system needs no control cabling?

No. The architecture still uses power feeds and control links per the model's diagrams — integrated power electronics do not remove the control network.

Can I reuse my old Side-Power panel?

Only if Sleipner documents the exact compatibility or the required adapter for the references involved. A shared brand or an identical connector is not enough.

How many terminators does S-Link need?

Follow the system's S-Link diagram. The number and position of terminators cannot be inferred from another network or a neighbouring installation.