<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.beastx.com/index.php?action=history&amp;feed=atom&amp;title=Translations%3ASRXL_-_Serial_Receiver_Link_protocol%2F1%2Fen</id>
	<title>Translations:SRXL - Serial Receiver Link protocol/1/en - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.beastx.com/index.php?action=history&amp;feed=atom&amp;title=Translations%3ASRXL_-_Serial_Receiver_Link_protocol%2F1%2Fen"/>
	<link rel="alternate" type="text/html" href="https://wiki.beastx.com/index.php?title=Translations:SRXL_-_Serial_Receiver_Link_protocol/1/en&amp;action=history"/>
	<updated>2026-05-16T07:03:59Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.42.1</generator>
	<entry>
		<id>https://wiki.beastx.com/index.php?title=Translations:SRXL_-_Serial_Receiver_Link_protocol/1/en&amp;diff=14953&amp;oldid=prev</id>
		<title>FuzzyBot: Importing a new version from external source</title>
		<link rel="alternate" type="text/html" href="https://wiki.beastx.com/index.php?title=Translations:SRXL_-_Serial_Receiver_Link_protocol/1/en&amp;diff=14953&amp;oldid=prev"/>
		<updated>2018-02-14T09:20:32Z</updated>

		<summary type="html">&lt;p&gt;Importing a new version from external source&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 09:20, 14 February 2018&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot; id=&quot;mw-diff-left-l1&quot;&gt;Line 1:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 1:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;−&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;[[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.&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;[[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.&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;&amp;lt;br /&amp;gt;&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;−&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;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 &quot;Plug&amp;amp;Play&quot;, indepent of the specific type of radio system that is used.&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;&amp;lt;br /&amp;gt;&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;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 &quot;Plug&amp;amp;Play&quot;, indepent of the specific type of radio system that is used.&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;&amp;lt;br /&amp;gt;&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-side-deleted&quot;&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;&amp;lt;br /&amp;gt;&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>FuzzyBot</name></author>
	</entry>
	<entry>
		<id>https://wiki.beastx.com/index.php?title=Translations:SRXL_-_Serial_Receiver_Link_protocol/1/en&amp;diff=2062&amp;oldid=prev</id>
		<title>FuzzyBot: Importing a new version from external source</title>
		<link rel="alternate" type="text/html" href="https://wiki.beastx.com/index.php?title=Translations:SRXL_-_Serial_Receiver_Link_protocol/1/en&amp;diff=2062&amp;oldid=prev"/>
		<updated>2014-08-27T15:16:59Z</updated>

		<summary type="html">&lt;p&gt;Importing a new version from external source&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;[[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.&lt;br /&gt;
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 &amp;quot;Plug&amp;amp;Play&amp;quot;, indepent of the specific type of radio system that is used.&lt;/div&gt;</summary>
		<author><name>FuzzyBot</name></author>
	</entry>
</feed>