SlinkE2 provides a link from Jeti receivers to S.Bus devices, such as servos and flight controllers.
What is SlinkE2 ?
SlinkE2 provides a solution for users who want to use S.Bus devices with their Jeti Duplex transmitters and receivers. It does this by converting a Jeti EX Bus signal (available from all current Duplex EX receivers and REX receivers) to a Futaba S.Bus signal.
Futaba's S.Bus protocol is probably the most widely used single-wire protocol in the RC industry. It can be used to drive multiple S.Bus servos from a single cable (reducing the amount of physical wiring and number of connectors), or drive a flight controller with a single cable (reducing clutter). It also reduces latency, and provides more precise digital data compared to traditional PPM servo data, and can output up to 18 channels of data.
Jeti Duplex receivers are unable to natively output S.Bus signals, but can provide Jeti EX Bus output signals. SlinkE2 converts the high-resolution, high-speed EX Bus data from your Jeti receiver into standard Futaba S.Bus format.
Typical uses for SlinkE2 includes:
- Multicopter or helicopter flight controllers which do not support EX Bus or UDI
- Multicopter or helicopter flight controllers where you need more than 12 channels
- Large scale models where multiple S.Bus servos are used to reduce wiring and connector complexity
- Gliders with multi-servo wings and cramped fuselages, where the use of a single wire and wing connector is beneficial
Very little configuration is required on your Jeti transmitter - using Device Explorer, select your receiver and ensure that the "Serial Link" option is set to "EX Bus".
SlinkE2 itself requires no configuration - simply plug one end of the SlinkE2 into the Ext port on a Jeti receiver, and an S.Bus signal is produced on the output connector.
That's it ! You now have a S.Bus signal from your Jeti receiver !
Input Signal: Jeti EX Bus (16 channels)
Output Signal: Futaba S.Bus (16 channels)
- 3.9 gm (including cables), 2.1 gm (excluding cables)
- 10.0 gm (shipping weight, including packaging)
Size: 37 x 14 x 4 mm (excluding cables). Overall length including cables: 195mm
Operating voltage: 3.2 - 16 V
Note that the S.Bus protocol provides 16 proportional servo channels and 2 "on-off" switched channels. Current Jeti transmitters DS16 and DC16 are limited to a maximum of 16 channels. DS14 and DC14 transmitters only provide between 8 to 14 channels. Future Jeti transmitters (DS24, DC24) may allow use of the full 18 channels of S.Bus data.
Can I use SlinkE2 to power the receiver via its Ext port ?
The older Jeti receiver manuals warn that receivers must not be powered via the Ext port. This is not entirely correct. Jeti have confirmed in writing that:
- receivers produced since August 2014 are able to be powered from the Ext port, the same as any other servo port.
- older receivers are able to be powered by the Ext port, if no servos are connected to the receiver also.
But be warned - the Ext port on Jeti receivers (and Central Boxes) are not always rated to handle significant amounts of currents. Even a single servo may draw too much power and permanently damage your receiver.
So in short, there are no limitations on using SlinkE2 to power Jeti Duplex receivers via the Ext port, but don't attempt to power servos or other high-current devices from the receiver's Ext port.
SlinkE2 vs original SlinkE
The SlinkE2 is an evolved version of the original SlinkE device which has been sold and used by many modellers over the past few years.
The SlinkE2 uses a completely new hardware platform (with a faster 32-bit processor, more memory and more flexible outputs).
One obvious physical difference is that it now comes with a servo cable for the EX Bus input only, with header pins for the output. This was a feature that many customers requested, since they often had to modify the output cable on the original SlinkE (either to change the length, or change the gender of the end connector).
The other key physical difference is that there is now TWO outputs. Currently only the first output port (Port A) is used for S.Bus signals, with Port B available for configuring the SlinkE2 via a traditional standalone Jetibox programmer. But in the future, Port B will be available for alternative functions. Stay tuned...
The core of the firmware retains much of the original SlinkE code, but has a few configurable options that the original SlinkE did not offer:
- configurable failsafe behaviour (off vs hold last known good values)
- either normal speed (14ms interval) or high speed (7ms) S.Bus frame rates
- selectable S.Bus signal polarity: standard Futaba polarity (inverted), or non-inverted
Under the hood there is also a competely new firmware updating mechanism built into the device. This will make firmware updates even simpler and more reliable than they were previously, and opens the door to allowing the SlinkE2 to take on entirely new functionality in the future.