SRXL - Serial Receiver Link protocol: Difference between revisions
Shornstein (talk | contribs) No edit summary |
Shornstein (talk | contribs) Marked this version for translation |
||
(4 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
<translate> | <translate> | ||
<!--T:1--> | <!--T:1--> | ||
[[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|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.<br /> | ||
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. | <br /> | ||
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.<br /> | |||
<br /> | |||
<!--T:3--> | <!--T:3--> | ||
The following receiver systems/receiver types support SRXL and work in combination with MICROBEAST and MICROBEAST PLUS: | '''The following receiver systems/receiver types support SRXL and work in combination with MICROBEAST and MICROBEAST PLUS:''' | ||
<!--T:4--> | <!--T:4--> | ||
{| | {|cellpadding="4" cellspacing="2" border="0" style="text-align:left;border:0px solid; padding:0px 0px 0px 10px" | ||
!style="width:200px" | Manufacturer !! style="width:400px" | Receivers | |||
|- | |- | ||
|style="text-align:left; border:1px solid #c3c3c3;" | BEASTX | |||
|style="text-align:left; border:1px solid #c3c3c3;" | All BEASTRX receivers | |||
|- | |- | ||
| | |style="text-align:left; border:1px solid #c3c3c3;" | MULTIPLEX | ||
|style="text-align:left; border:1px solid #c3c3c3;" | Receivers with M-Link data port | |||
|- | |- | ||
| | |style="text-align:left; border:1px solid #c3c3c3;" | GRAUPNER / SJ HOTT | ||
|style="text-align:left; border:1px solid #c3c3c3;" | HOTT receivers with SUMD output | |||
|- | |- | ||
| | |}<br /> | ||
<br /> | |||
<!--T:7--> | |||
'''The following receiver systems/receiver types support SRXL and work in combination with MICROBEAST PLUS:''' | |||
<!--T:8--> | |||
{|cellpadding="4" cellspacing="2" border="0" style="text-align:left;border:0px solid; padding:0px 0px 0px 10px" | |||
!style="width:200px" | Manufacturer !! style="width:400px" | Receivers | |||
|- | |- | ||
| SPEKTRUM | |style="text-align:left; border:1px solid #c3c3c3;" | SPEKTRUM SRXL | ||
|style="text-align:left; border:1px solid #c3c3c3;" | AR7700/9020/8010T/9030T/9320T | |||
|} | |} | ||
<!--T:9--> | |||
<p style="font-size:x-small;">Spektrum SPM4649T receiver will also work in combination with MICROBEAST PLUS but please note this receiver acts like a Spektrum remote satellite.<br /> | |||
It does not send a conventional SRXL control signal. So called "Bi-directional SRXL" is something different and only used for transmitting telemetry data which is not applicable in this case.</p> | |||
<br /> | |||
<!--T:5--> | <!--T:5--> | ||
The following receiver systems are compatible with SRXL as they directly implemented the SRXL protocol as specified for MULTIPLEX | '''The following receiver systems are compatible with SRXL as they directly implemented the SRXL protocol as specified for MULTIPLEX:'''<br /> | ||
<!--T:6--> | <!--T:6--> | ||
{| | {|cellpadding="4" cellspacing="2" border="0" style="text-align:left;border:0px solid; padding:0px 0px 0px 10px" | ||
!style="width:200px" | Manufacturer !! style="width:400px" | Receivers | |||
! Manufacturer | |||
|- | |- | ||
| JR propo | |style="text-align:left; border:1px solid #c3c3c3;" | JR propo | ||
|style="text-align:left; border:1px solid #c3c3c3;" | JR X-Bus (activate "X-Bus Mode B" in the radio) | |||
|- | |- | ||
| Jeti | |style="text-align:left; border:1px solid #c3c3c3;" | Jeti | ||
|style="text-align:left; border:1px solid #c3c3c3;" | Receivers with UDI output (UDI-12 & UDI-16) | |||
|} | |} | ||
<!--T:10--> | |||
<p style="font-size:x-small;">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 performing manual channel assignment is mandatory (see MICROBEAST / MICROBEAST PLUS user manual).</p> | |||
<br /> | |||
</translate> | </translate> |
Latest revision as of 09:20, 14 February 2018
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.
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.
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 |
GRAUPNER / SJ HOTT | HOTT receivers with SUMD output |
The following receiver systems/receiver types support SRXL and work in combination with MICROBEAST PLUS:
Manufacturer | Receivers |
---|---|
SPEKTRUM SRXL | AR7700/9020/8010T/9030T/9320T |
Spektrum SPM4649T receiver will also work in combination with MICROBEAST PLUS but please note this receiver acts like a Spektrum remote satellite.
It does not send a conventional SRXL control signal. So called "Bi-directional SRXL" is something different and only used for transmitting telemetry data which is not applicable in this case.
The following receiver systems are compatible with SRXL as they directly implemented the SRXL protocol as specified for MULTIPLEX:
Manufacturer | Receivers |
---|---|
JR propo | JR X-Bus (activate "X-Bus Mode B" in the radio) |
Jeti | Receivers with UDI output (UDI-12 & UDI-16) |
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 performing manual channel assignment is mandatory (see MICROBEAST / MICROBEAST PLUS user manual).