SRXL - Serial Receiver Link protocol/de: Difference between revisions

From BEASTX Wiki
Jump to navigation Jump to search
Created page with "SRXL - Serial Receiver Link protocol"
 
Line 1: Line 1:
<languages />
<languages />
[[File:srxl.png|thumb|300px|Watch out for the SRXL logo! It identifies devices supporting the SRXL framework.]] SRXL is an open data transfer protocol which allows to transport control data from a rc receiver to another device like a flybarless system by only using one single line. This protocol has been established by SRXL.org based on the idea to create a freely available and unified protocol that manufacturers can easily implement to their receivers and devices that process receiver data. The protocol does not describe an exact definition of how the data must be processed. It only describes a framework in which receiver data can be packed. Each manufacturer can have his own ID, which must be attached to the beginning of each data set, so that the device using this data can correctly identify and process the payload of the dataset.
[[File:srxl.png|thumb|300px|Achten Sie auf das SRXL Logo! Es Identifiziert Geräte die SRXL unterstützen.]]
Several manufacturers of RC systems already implemented this protocol to their receivers and MICROBEAST can process the data of these receivers. The advantage is that the data transfer is very fast compared to standard transmission by single wires for each control function. Additionaly you can transfer much more channels at one time and freely distribute the usage of these channels to different control functions. Due to the unique identifier it even is possible to automatically adapt the function allocation specifically to the standard that is used by each radio brand, so that the usage of SRXL is almost "Plug&Play", indepent of the specific type of radio system that is used.


Unfortunately some radio systems manufacturers did not fully implement the SRXL standard but only copied the protocol from a different brand of radio systems to be compatible with already exisiting devices. Although this is not a bad idea at all, it has the disadvantage that these manufacturers loose the additional features and advantages that come with the unique manufacturer's ID.
Unfortunately some radio systems manufacturers did not fully implement the SRXL standard but only copied the protocol from a different brand of radio systems to be compatible with already exisiting devices. Although this is not a bad idea at all, it has the disadvantage that these manufacturers loose the additional features and advantages that come with the unique manufacturer's ID.

Revision as of 12:07, 27 August 2014

Achten Sie auf das SRXL Logo! Es Identifiziert Geräte die SRXL unterstützen.

Unfortunately some radio systems manufacturers did not fully implement the SRXL standard but only copied the protocol from a different brand of radio systems to be compatible with already exisiting devices. Although this is not a bad idea at all, it has the disadvantage that these manufacturers loose the additional features and advantages that come with the unique manufacturer's ID.


The following receiver systems/receiver types support SRXL and work in combination with MICROBEAST and MICROBEAST plus:

Manufacturer Receivers
BEASTX All BEASTRX receivers
MULTIPLEX Receivers with M-Link data port (firmware update may be necessary)
GRAUPNER / SJ HOTT HOTT receivers with SUMD output (firmware update may be necessary)


The following receiver systems are compatible with SRXL as they directly implemented the SRXL protocol as specified for MULTIPLEX. MICROBEAST and MICROBEAST plus will work without issues with these receivers, but be aware that due to the same manufacturer ID they will be identified as MULTIPLEX receivers and therefore the preset channel assignment of MICROBEAST/MICROBEAST plus may not fit to your radio system, so a manual channel assignment is mandatory (see pages 28ff in MICROBEAST manual):

Manufacturer Receivers
JR propo JR X-Bus (select X-Bus Mode_B output in the radio)
Jeti Receivers with Jeti UDI output (firmware update may be necessary)