Manuals:BXFbl:Radio Setup:FRSKY - Revision history

Shornstein: Marked this version for translation

2024-08-10T08:11:57Z

Marked this version for translation

← Older revision		Revision as of 08:11, 10 August 2024
Line 49:		Line 49:
	<br />		<br />

	~~= Connection scheme =~~ <!--T:3-->		<!--T:3-->
			= Connection scheme =
	<br />		<br />
	{\| class="wikitable" style="text-align: center; margin-left: 10px; background-color: #F9DDCC; border: solid #F18308 2px;"		{\| class="wikitable" style="text-align: center; margin-left: 10px; background-color: #F9DDCC; border: solid #F18308 2px;"
Line 95:		Line 96:
	<br />		<br />

	~~=Radio setup=~~ <!--T:7-->		<!--T:7-->
			=Radio setup=
	To enable the S.Port or F.Port output scroll down to the MODEL MENU on your FRSKY radio and select the receiver output accordingly.<br />		To enable the S.Port or F.Port output scroll down to the MODEL MENU on your FRSKY radio and select the receiver output accordingly.<br />
	<br />		<br />
Line 115:		Line 117:
	<br />		<br />

	~~=BEASTX setup=~~ <!--T:9-->		<!--T:9-->
			=BEASTX setup=
	In order to use your FRSKY receiver you have to scan the input type in the RECEIVER MENU of your BEASTX device and set the correct channel ordering		In order to use your FRSKY receiver you have to scan the input type in the RECEIVER MENU of your BEASTX device and set the correct channel ordering
	for your radio system. We use the channel layout that is also used on FUTABA radio: '''AETR'''. You can change the channel layout in the MODEL MENU on your FRSKY radio.<br />		for your radio system. We use the channel layout that is also used on FUTABA radio: '''AETR'''. You can change the channel layout in the MODEL MENU on your FRSKY radio.<br />
Line 149:		Line 152:
	<br />		<br />

	~~==MICROBEAST PLUS / MICROBEAST ULTRA==~~ <!--T:11-->		<!--T:11-->
			==MICROBEAST PLUS / MICROBEAST ULTRA==
	Push and hold the button on your MICROBEAST and power up the device. Menu LED A will flash instantly. Now release the button. Push again to start the scan process. When scan was successful, Menu LED B will show up. Now push and hold the button for 2 seconds and release in order to load the default channel assignments. If needed you can set up telemetry at Menu LEDs L & M, if applicable; push button briefly to skip. Finally teach throttle failsafe position at Menu LED N by bringing the throttle in lowest position on your radio and push the button again. Now your MICROBEAST will start with init sequence. You can perform basic setup procedure in SETUP MENU when init sequence was completed. For further information about RECEIVER MENU setup, see next section. <br />		Push and hold the button on your MICROBEAST and power up the device. Menu LED A will flash instantly. Now release the button. Push again to start the scan process. When scan was successful, Menu LED B will show up. Now push and hold the button for 2 seconds and release in order to load the default channel assignments. If needed you can set up telemetry at Menu LEDs L & M, if applicable; push button briefly to skip. Finally teach throttle failsafe position at Menu LED N by bringing the throttle in lowest position on your radio and push the button again. Now your MICROBEAST will start with init sequence. You can perform basic setup procedure in SETUP MENU when init sequence was completed. For further information about RECEIVER MENU setup, see next section. <br />
	<br />		<br />
	<br />		<br />

	~~==NANOBEAST==~~ <!--T:12-->		<!--T:12-->
			==NANOBEAST==
	Connect the SBUS signal of the receiver to [DI1] port and power up NANOBEAST. Connect the push button to [SYS] port. Push and hold the button for 2 seconds, then release. The Status LED will change color or go off. Push the button again to start the scan process. When scan was successful, the Status LED will flash twice. Now push and hold the button for 2 seconds and release in order to load the default channel assignments. If needed you can set up telemetry at Menus L & M, if applicable (Menu L = Status LED flashes long once and then 5 times, for Menu L 6 times); push button briefly to skip. Finally teach throttle failsafe position at Menu N (Status LED flashes long once and then 7 times) by bringing the throttle in lowest position on your radio and push the button again. Now your NANOBEAST will start with init sequence. For further information about RECEIVER MENU setup, see next section. Then perform basic setup procedure in SETUP MENU.<br />		Connect the SBUS signal of the receiver to [DI1] port and power up NANOBEAST. Connect the push button to [SYS] port. Push and hold the button for 2 seconds, then release. The Status LED will change color or go off. Push the button again to start the scan process. When scan was successful, the Status LED will flash twice. Now push and hold the button for 2 seconds and release in order to load the default channel assignments. If needed you can set up telemetry at Menus L & M, if applicable (Menu L = Status LED flashes long once and then 5 times, for Menu L 6 times); push button briefly to skip. Finally teach throttle failsafe position at Menu N (Status LED flashes long once and then 7 times) by bringing the throttle in lowest position on your radio and push the button again. Now your NANOBEAST will start with init sequence. For further information about RECEIVER MENU setup, see next section. Then perform basic setup procedure in SETUP MENU.<br />
	<br />		<br />
	<br />		<br />

	~~==Setup with StudioX==~~ <!--T:13-->		<!--T:13-->
			==Setup with StudioX==
	You can also use the StudioX app to start receiver scan and perform further setup steps. In this case open the '''Control''' menu in StudioX and click the '''SCAN''' button in this menu's screen. For further informations please refer to the StudioX instruction notes.<br />		You can also use the StudioX app to start receiver scan and perform further setup steps. In this case open the '''Control''' menu in StudioX and click the '''SCAN''' button in this menu's screen. For further informations please refer to the StudioX instruction notes.<br />
	<br />		<br />

Shornstein at 08:11, 10 August 2024

2024-08-10T08:11:43Z

← Older revision		Revision as of 08:11, 10 August 2024
Line 1:		Line 1:
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->
	{{TOC_BXFbl\|Manuals:BXFbl:Radio_Setup:ELRS/en\|Manuals:BXFbl:Radio_Setup:RemoteSat/en\|\|}}		{{TOC_BXFbl\|Manuals:BXFbl:Radio_Setup:ELRS/en\|Manuals:BXFbl:Radio_Setup:RemoteSat/en\|RADIOSETUP\|}}
	{{DISPLAYTITLE:FRSKY S.Port & F.Port\|noerror}}		{{DISPLAYTITLE:FRSKY S.Port & F.Port\|noerror}}
	__TOC__		__TOC__

Shornstein at 13:18, 14 May 2024

2024-05-14T13:18:53Z

← Older revision		Revision as of 13:18, 14 May 2024
Line 1:		Line 1:
	<translate>		<translate>
	<!--T:1-->		<!--T:1-->
	{{TOC_BXFbl\|Manuals:BXFbl:Radio_Setup:ELRS/en\|Manuals:BXFbl:Radio_Setup:~~Standard_PPM~~/en\|\|}}		{{TOC_BXFbl\|Manuals:BXFbl:Radio_Setup:ELRS/en\|Manuals:BXFbl:Radio_Setup:RemoteSat/en\|\|}}
	{{DISPLAYTITLE:FRSKY S.Port & F.Port\|noerror}}		{{DISPLAYTITLE:FRSKY S.Port & F.Port\|noerror}}
	__TOC__		__TOC__

Shornstein at 19:55, 30 April 2024

2024-04-30T19:55:55Z

← Older revision		Revision as of 19:55, 30 April 2024
Line 16:		Line 16:

	<!--T:17-->		<!--T:17-->
	'''S.Port ~~(inv.)~~'''<br />		'''S.Port'''<br />
	When it comes to sending telemetry data back to the radio it get's more complicated. There is an older system called S.PORT that allows to send telemetry data using a second line. This was firstly introduced for RC drones. One problem here is that the signal is electricaly inverted similar as it is done with Futaba SBUS. But as most controllers do not have signal inverters by default, FRSky did add an inverted S.Port signal to some of their receivers. So that protocol can be read as "normal" UART. If you've got one of those receivers you can use it in combination with MICROBEAST PLUS / ULTRA ~~and NANOBEAST~~. Please note that you need to add an additional '''10k resistor''' between signal line and ground/minus in order to stabilize the signal!~~<!-- The MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original S.PORT.--><br />~~		When it comes to sending telemetry data back to the radio it get's more complicated. There is an older system called S.PORT that allows to send telemetry data using a second line. This was firstly introduced for RC drones. One problem here is that the signal is electricaly inverted similar as it is done with Futaba SBUS. But as most controllers do not have signal inverters by default, FRSky did add an inverted S.Port signal to some of their receivers. So that protocol can be read as "normal" UART. If you've got one of those receivers you can use it in combination with MICROBEAST PLUS. MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original (uninverted) S.PORT.<br />
			<br />
			Please note that you need to add an additional '''10k resistor''' between signal line and ground (minus) in order to stabilize the signal!
	<br />		<br />

Line 61:		Line 63:
	\| SBUS \|\| - \|\| - \|\| - \|\| - \|\|		\| SBUS \|\| - \|\| - \|\| - \|\| - \|\|
	\|-		\|-
	\| SBUS \|\| - \|\| S.Port (inv.) \|\| ESC telemetry \|\| - \|\|		\| SBUS \|\| - \|\| S.Port (inv.) \|\| ESC telemetry \|\| - \|\| MB PLUS & NANOBEAST
			\|-
			\| SBUS \|\| - \|\| S.Port \|\| ESC telemetry \|\| - \|\| MB ULTRA
	\|-		\|-
	\| - \|\| ESC telemetry \|\| F.Port \|\| - \|\| - \|\| ~~only~~ MB ULTRA		\| - \|\| ESC telemetry \|\| F.Port \|\| - \|\| - \|\| MB ULTRA
	\|-		\|-
	\| - \|\| ESC telemetry \|\| - \|\| - \|\| F.Port \|\| ~~only~~ MB ULTRA		\| - \|\| ESC telemetry \|\| - \|\| - \|\| F.Port \|\| MB ULTRA
	\|-		\|-
	\|}		\|}
Line 158:		Line 162:
	You can also use the StudioX app to start receiver scan and perform further setup steps. In this case open the '''Control''' menu in StudioX and click the '''SCAN''' button in this menu's screen. For further informations please refer to the StudioX instruction notes.<br />		You can also use the StudioX app to start receiver scan and perform further setup steps. In this case open the '''Control''' menu in StudioX and click the '''SCAN''' button in this menu's screen. For further informations please refer to the StudioX instruction notes.<br />
	<br />		<br />
	Please note that when using S.PORT ~~(inv.)~~ telemetry connected to [SYS], you must disconnect the receiver from [SYS] temporarily, switch off your radio and power cycle your device. It will then enable "normal" [SYS] operation for programming purpose. When using F.Port connected at [SYS] in combination with MICROBEAST ULTRA you can connect your BLE2SYS/USB2SYS at the DI2 port at the side of the device using the [https://www.freakware.de/en/p/adapter-cable-telemetry-adapterkabel-micobeast-beastx-bxa76406-a174871.htm Telemetry adapter cable BXA76406].<br />		Please note that when using S.PORT telemetry connected to [SYS], you must disconnect the receiver from [SYS] temporarily, switch off your radio and power cycle your device. It will then enable "normal" [SYS] operation for programming purpose. When using F.Port connected at [SYS] in combination with MICROBEAST ULTRA you can connect your BLE2SYS/USB2SYS at the DI2 port at the side of the device using the [https://www.freakware.de/en/p/adapter-cable-telemetry-adapterkabel-micobeast-beastx-bxa76406-a174871.htm Telemetry adapter cable BXA76406].<br />
	<br />		<br />

Shornstein at 09:14, 25 April 2024

2024-04-25T09:14:05Z

← Older revision		Revision as of 09:14, 25 April 2024
Line 87:		Line 87:

	<!--T:21-->		<!--T:21-->
	When using [SYS] for the F.Port signal, you must connect the BLE2SYS / USB2SYS adapter at the DI2 port in order to use the StudioX app. Here you need the ~~optional~~ adapter from standard servo connector to 5-pin JST. Alternatively you can simply disconnect the F.PORT signal from SYS temporarily, switch off your radio and power cycle your device. It will then enable "normal" SYS operation for programming purpose. Please note that in this case you will not be able to control the system from the radio during setup with StudioX.<br />		When using [SYS] for the F.Port signal, you must connect the BLE2SYS / USB2SYS adapter at the DI2 port in order to use the StudioX app. Here you need the [https://www.freakware.de/en/p/adapter-cable-telemetry-adapterkabel-micobeast-beastx-bxa76406-a174871.htm Telemetry adapter cable BXA76406] from standard servo connector to 5-pin JST. Alternatively you can simply disconnect the F.PORT signal from SYS temporarily, switch off your radio and power cycle your device. It will then enable "normal" SYS operation for programming purpose. Please note that in this case you will not be able to control the system from the radio during setup with StudioX.<br />
	<br />		<br />
	<br />		<br />
Line 156:		Line 156:

	==Setup with StudioX== <!--T:13-->		==Setup with StudioX== <!--T:13-->
	You can also use the StudioX app to start receiver scan and perform further setup steps. In this case open the '''Control''' menu in StudioX and click the '''SCAN''' button in this menu's screen. Please note that when using S.PORT telemetry connected to [SYS], you must disconnect the receiver from [SYS]temporarily, switch off your radio and power cycle your device. It will then enable "normal" [SYS] operation for programming purpose. ~~For further informations please refer to~~ the ~~StudioX instruction notes~~.<br />		You can also use the StudioX app to start receiver scan and perform further setup steps. In this case open the '''Control''' menu in StudioX and click the '''SCAN''' button in this menu's screen. For further informations please refer to the StudioX instruction notes.<br />
			<br />
			Please note that when using S.PORT (inv.) telemetry connected to [SYS], you must disconnect the receiver from [SYS] temporarily, switch off your radio and power cycle your device. It will then enable "normal" [SYS] operation for programming purpose. When using F.Port connected at [SYS] in combination with MICROBEAST ULTRA you can connect your BLE2SYS/USB2SYS at the DI2 port at the side of the device using the [https://www.freakware.de/en/p/adapter-cable-telemetry-adapterkabel-micobeast-beastx-bxa76406-a174871.htm Telemetry adapter cable BXA76406].<br />
	<br />		<br />

Shornstein at 08:32, 25 April 2024

2024-04-25T08:32:30Z

← Older revision		Revision as of 08:32, 25 April 2024
Line 22:		Line 22:
	<!--T:24-->		<!--T:24-->
	{\| style = "text-align:center;"		{\| style = "text-align:center;"
	\| style = "width: 200px;" \| [[File:ArcherRSPlus.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:~~ArcherRSPlus_Res~~.png\|border\|x180px]]		\| style = "width: 200px;" \| [[File:ArcherRSPlus.png\|border\|x180px]]
			<!-- \| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:ArcherRSPlus_Res.png\|border\|x180px]] -->
			\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Archer RSPlus Res2.png\|border\|x180px]]
	\|-		\|-
	\| Archer RS+ using SBUS and S.Port(inv.) signals \|\| style = "padding: 0px 0px 0px 50px;" \| Add 10k resistor between S.Port(inv.) and minus		\| Archer RS+ using SBUS and S.Port(inv.) signals \|\| style = "padding: 0px 0px 0px 50px;" \| Add 10k resistor between S.Port(inv.) and minus
Line 37:		Line 39:
	<!--T:25-->		<!--T:25-->
	{\| style = "text-align:center;"		{\| style = "text-align:center;"
	\| style = "width: 200px;" \| [[File:PullDown DI2 Signal.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Futaba SBUS2.png\|border\|x180px]]		\| style = "width: 200px;" \| [[File:PullDown DI2 Signal.png\|border\|x180px]]
			\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Futaba SBUS2.png\|border\|x180px]]
	\|-		\|-
	\| Add 4.7k between signal and minus \|\| style = "padding: 0px 0px 0px 50px;" \| Use a small PCB to make soldering easier		\| Add 4.7k between signal and minus \|\| style = "padding: 0px 0px 0px 50px;" \| Use a small PCB to make soldering easier

Shornstein: Marked this version for translation

2024-04-25T08:19:21Z

Marked this version for translation

← Older revision		Revision as of 08:19, 25 April 2024
Line 20:		Line 20:
	<br />		<br />

			<!--T:24-->
	{\| style = "text-align:center;"		{\| style = "text-align:center;"
	\| style = "width: 200px;" \| [[File:ArcherRSPlus.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:ArcherRSPlus_Res.png\|border\|x180px]]		\| style = "width: 200px;" \| [[File:ArcherRSPlus.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:ArcherRSPlus_Res.png\|border\|x180px]]
Line 34:		Line 35:
	<br />		<br />

			<!--T:25-->
	{\| style = "text-align:center;"		{\| style = "text-align:center;"
	\| style = "width: 200px;" \| [[File:PullDown DI2 Signal.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Futaba SBUS2.png\|border\|x180px]]		\| style = "width: 200px;" \| [[File:PullDown DI2 Signal.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Futaba SBUS2.png\|border\|x180px]]

Shornstein at 08:19, 25 April 2024

2024-04-25T08:19:12Z

← Older revision		Revision as of 08:19, 25 April 2024
Line 17:		Line 17:
	<!--T:17-->		<!--T:17-->
	'''S.Port (inv.)'''<br />		'''S.Port (inv.)'''<br />
	When it comes to sending telemetry data back to the radio it get's more complicated. There is an older system called S.PORT that allows to send telemetry data using a second line. This was firstly introduced for RC drones. One problem here is that the signal is electricaly inverted similar as it is done with Futaba SBUS. But as most controllers do not have signal inverters by default, FRSky did add an inverted S.Port signal to some of their receivers. So that protocol can be read as "normal" UART. If you've got one of those receivers you can use it in combination with MICROBEAST PLUS / ULTRA and NANOBEAST. Please note that you need to add an additional '''10k resistor''' between signal line and ground/minus in order to stabilize the ~~singal~~!<!-- The MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original S.PORT.--><br />		When it comes to sending telemetry data back to the radio it get's more complicated. There is an older system called S.PORT that allows to send telemetry data using a second line. This was firstly introduced for RC drones. One problem here is that the signal is electricaly inverted similar as it is done with Futaba SBUS. But as most controllers do not have signal inverters by default, FRSky did add an inverted S.Port signal to some of their receivers. So that protocol can be read as "normal" UART. If you've got one of those receivers you can use it in combination with MICROBEAST PLUS / ULTRA and NANOBEAST. Please note that you need to add an additional '''10k resistor''' between signal line and ground/minus in order to stabilize the signal!<!-- The MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original S.PORT.--><br />
			<br />

			{\| style = "text-align:center;"
			\| style = "width: 200px;" \| [[File:ArcherRSPlus.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:ArcherRSPlus_Res.png\|border\|x180px]]
			\|-
			\| Archer RS+ using SBUS and S.Port(inv.) signals \|\| style = "padding: 0px 0px 0px 50px;" \| Add 10k resistor between S.Port(inv.) and minus
			\|}
	<br />		<br />

Line 24:		Line 31:
	Then there also is F.Port which was introduced in 2020. Here both, telemetry data and control data, are combined using only one data line. This system has been enhanced to F.Port2 and sometimes also is called FBUS. At the moment MICROBEAST ULTRA supports the original F.PORT which seems to be available on any newer FRSky receiver. MICROBEAST PLUS / NANOBEAST can't support F.Port due to it's electrical architecture (bi-directional inverted bus protocol).<br />		Then there also is F.Port which was introduced in 2020. Here both, telemetry data and control data, are combined using only one data line. This system has been enhanced to F.Port2 and sometimes also is called FBUS. At the moment MICROBEAST ULTRA supports the original F.PORT which seems to be available on any newer FRSky receiver. MICROBEAST PLUS / NANOBEAST can't support F.Port due to it's electrical architecture (bi-directional inverted bus protocol).<br />
	<br />		<br />
	Please note that you may add an additional '''resistor of 4~~,5k~~ to 10k''' between signal line and ground/minus in order to stabilize the singal! It can work without but if the telemetry signal is not stable a resistor will help. This is because of the different signal levels that some FRSky receivers have.<br />		Please note that you may add an additional '''resistor of 4.7k to 10k''' between signal line and ground/minus in order to stabilize the singal! It can work without but if the telemetry signal is not stable a resistor will help. This is because of the different signal levels that some FRSky receivers have.<br />
			<br />

			{\| style = "text-align:center;"
			\| style = "width: 200px;" \| [[File:PullDown DI2 Signal.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Futaba SBUS2.png\|border\|x180px]]
			\|-
			\| Add 4.7k between signal and minus \|\| style = "padding: 0px 0px 0px 50px;" \| Use a small PCB to make soldering easier
			\|}
	<br />		<br />
	<br />		<br />

Shornstein at 06:46, 25 April 2024

2024-04-25T06:46:41Z

← Older revision		Revision as of 06:46, 25 April 2024
Line 11:		Line 11:

	<!--T:16-->		<!--T:16-->
	'''SBUS'''		'''SBUS'''<br />
	Usually all receivers can send control data using the Futaba SBUS data protocol. As the BEASTX systems support Futaba SBUS for many years, just connect the SBUS output of your receiver to the DI1/IO1 port on your BEASTX system and you're good to go.<br />		Usually all receivers can send control data using the Futaba SBUS data protocol. As the BEASTX systems support Futaba SBUS for many years, just connect the SBUS output of your receiver to the DI1/IO1 port on your BEASTX system and you're good to go.<br />
	<br />		<br />

	<!--T:17-->		<!--T:17-->
	'''S.Port'''		'''S.Port (inv.)'''<br />
	When it comes to sending telemetry data back to the radio it get's more complicated. There is an older system called S.PORT that allows to send telemetry data using a second line. This was firstly introduced for RC drones. One problem here is that the signal is electricaly inverted similar as it is done with Futaba SBUS. But as most controllers do not have signal inverters by default, FRSky did add an inverted S.Port signal to some of their receivers. So that protocol can be read as "normal" UART. If you've got one of those receivers you can use it in combination with MICROBEAST PLUS and NANOBEAST. The MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original S.PORT.		When it comes to sending telemetry data back to the radio it get's more complicated. There is an older system called S.PORT that allows to send telemetry data using a second line. This was firstly introduced for RC drones. One problem here is that the signal is electricaly inverted similar as it is done with Futaba SBUS. But as most controllers do not have signal inverters by default, FRSky did add an inverted S.Port signal to some of their receivers. So that protocol can be read as "normal" UART. If you've got one of those receivers you can use it in combination with MICROBEAST PLUS / ULTRA and NANOBEAST. Please note that you need to add an additional '''10k resistor''' between signal line and ground/minus in order to stabilize the singal!<!-- The MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original S.PORT.--><br />
	<br />		<br />

	<!--T:18-->		<!--T:18-->
	'''F.Port'''		'''F.Port'''<br />
	Then there also is F.Port which was introduced in 2020. Here both, telemetry data and control data, are combined using only one data line. This system has been enhanced to F.Port2 and sometimes also is called FBUS. At the moment MICROBEAST ULTRA supports the original F.PORT which seems to be available on any newer FRSky receiver. MICROBEAST PLUS / NANOBEAST		Then there also is F.Port which was introduced in 2020. Here both, telemetry data and control data, are combined using only one data line. This system has been enhanced to F.Port2 and sometimes also is called FBUS. At the moment MICROBEAST ULTRA supports the original F.PORT which seems to be available on any newer FRSky receiver. MICROBEAST PLUS / NANOBEAST can't support F.Port due to it's electrical architecture (bi-directional inverted bus protocol).<br />
	can't support F.Port due to it's electrical architecture (bi-directional inverted bus protocol). ~~Anyhow~~, ~~this~~ is not a ~~big issue, as you can use the S~~.~~Port protocol as well. Only drawback~~ is that ~~it requires 2 wires instead of one~~.<br />		<br />
			Please note that you may add an additional '''resistor of 4,5k to 10k''' between signal line and ground/minus in order to stabilize the singal! It can work without but if the telemetry signal is not stable a resistor will help. This is because of the different signal levels that some FRSky receivers have.<br />
			<br />
	<br />		<br />

Line 40:		Line 42:
	\| SBUS \|\| - \|\| - \|\| - \|\| - \|\|		\| SBUS \|\| - \|\| - \|\| - \|\| - \|\|
	\|-		\|-
	\| SBUS \|\| - \|\| S.Port \|\| ESC telemetry \|\| - \|\|		\| SBUS \|\| - \|\| S.Port (inv.) \|\| ESC telemetry \|\| - \|\|
	\|-		\|-
	\| - \|\| ESC telemetry \|\| F.Port \|\| - \|\| - \|\| only MB ULTRA		\| - \|\| ESC telemetry \|\| F.Port \|\| - \|\| - \|\| only MB ULTRA
Line 136:		Line 138:
	==Setup with StudioX== <!--T:13-->		==Setup with StudioX== <!--T:13-->
	You can also use the StudioX app to start receiver scan and perform further setup steps. In this case open the '''Control''' menu in StudioX and click the '''SCAN''' button in this menu's screen. Please note that when using S.PORT telemetry connected to [SYS], you must disconnect the receiver from [SYS]temporarily, switch off your radio and power cycle your device. It will then enable "normal" [SYS] operation for programming purpose. For further informations please refer to the StudioX instruction notes.<br />		You can also use the StudioX app to start receiver scan and perform further setup steps. In this case open the '''Control''' menu in StudioX and click the '''SCAN''' button in this menu's screen. Please note that when using S.PORT telemetry connected to [SYS], you must disconnect the receiver from [SYS]temporarily, switch off your radio and power cycle your device. It will then enable "normal" [SYS] operation for programming purpose. For further informations please refer to the StudioX instruction notes.<br />
	~~<br />~~

	~~<!--T:14-->~~
	~~(Picture sys adapter!)<br />~~
	<br />		<br />

Shornstein: Marked this version for translation

2024-04-23T07:06:20Z

Marked this version for translation

← Older revision		Revision as of 07:06, 23 April 2024
Line 10:		Line 10:
	<br />		<br />

			<!--T:16-->
	'''SBUS'''		'''SBUS'''
	Usually all receivers can send control data using the Futaba SBUS data protocol. As the BEASTX systems support Futaba SBUS for many years, just connect the SBUS output of your receiver to the DI1/IO1 port on your BEASTX system and you're good to go.<br />		Usually all receivers can send control data using the Futaba SBUS data protocol. As the BEASTX systems support Futaba SBUS for many years, just connect the SBUS output of your receiver to the DI1/IO1 port on your BEASTX system and you're good to go.<br />
	<br />		<br />

			<!--T:17-->
	'''S.Port'''		'''S.Port'''
	When it comes to sending telemetry data back to the radio it get's more complicated. There is an older system called S.PORT that allows to send telemetry data using a second line. This was firstly introduced for RC drones. One problem here is that the signal is electricaly inverted similar as it is done with Futaba SBUS. But as most controllers do not have signal inverters by default, FRSky did add an inverted S.Port signal to some of their receivers. So that protocol can be read as "normal" UART. If you've got one of those receivers you can use it in combination with MICROBEAST PLUS and NANOBEAST. The MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original S.PORT.		When it comes to sending telemetry data back to the radio it get's more complicated. There is an older system called S.PORT that allows to send telemetry data using a second line. This was firstly introduced for RC drones. One problem here is that the signal is electricaly inverted similar as it is done with Futaba SBUS. But as most controllers do not have signal inverters by default, FRSky did add an inverted S.Port signal to some of their receivers. So that protocol can be read as "normal" UART. If you've got one of those receivers you can use it in combination with MICROBEAST PLUS and NANOBEAST. The MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original S.PORT.
	<br />		<br />

			<!--T:18-->
	'''F.Port'''		'''F.Port'''
	Then there also is F.Port which was introduced in 2020. Here both, telemetry data and control data, are combined using only one data line. This system has been enhanced to F.Port2 and sometimes also is called FBUS. At the moment MICROBEAST ULTRA supports the original F.PORT which seems to be available on any newer FRSky receiver. MICROBEAST PLUS / NANOBEAST		Then there also is F.Port which was introduced in 2020. Here both, telemetry data and control data, are combined using only one data line. This system has been enhanced to F.Port2 and sometimes also is called FBUS. At the moment MICROBEAST ULTRA supports the original F.PORT which seems to be available on any newer FRSky receiver. MICROBEAST PLUS / NANOBEAST
Line 52:		Line 55:
	<br />		<br />

			<!--T:19-->
	In order to use SYS for connecting the BLE2SYS / USBSYS for using the StudioX app, simply disconnect the receiver's S.PORT from SYS temporarily, switch off your radio and power cycle your device. It will then enable "normal" SYS operation for programming purpose.<br />		In order to use SYS for connecting the BLE2SYS / USBSYS for using the StudioX app, simply disconnect the receiver's S.PORT from SYS temporarily, switch off your radio and power cycle your device. It will then enable "normal" SYS operation for programming purpose.<br />
	<br />		<br />
	<br />		<br />

			<!--T:20-->
	'''F.Port'''<br />		'''F.Port'''<br />
	The wire for ESC control is connected to [IO1] at MICROBEAST ULTRA. The wire for the ESC telemetry signal is connected to [CH5/IO2].<br />		The wire for ESC control is connected to [IO1] at MICROBEAST ULTRA. The wire for the ESC telemetry signal is connected to [CH5/IO2].<br />
	<br />		<br />

			<!--T:21-->
	When using [SYS] for the F.Port signal, you must connect the BLE2SYS / USB2SYS adapter at the DI2 port in order to use the StudioX app. Here you need the optional adapter from standard servo connector to 5-pin JST. Alternatively you can simply disconnect the F.PORT signal from SYS temporarily, switch off your radio and power cycle your device. It will then enable "normal" SYS operation for programming purpose. Please note that in this case you will not be able to control the system from the radio during setup with StudioX.<br />		When using [SYS] for the F.Port signal, you must connect the BLE2SYS / USB2SYS adapter at the DI2 port in order to use the StudioX app. Here you need the optional adapter from standard servo connector to 5-pin JST. Alternatively you can simply disconnect the F.PORT signal from SYS temporarily, switch off your radio and power cycle your device. It will then enable "normal" SYS operation for programming purpose. Please note that in this case you will not be able to control the system from the radio during setup with StudioX.<br />
	<br />		<br />
Line 68:		Line 74:
	<br />		<br />

			<!--T:22-->
	If telemetry data is received you should see all available data when starting the SCAN PROCESS in TELEMETRY MENU of your FRSky radio.<br />		If telemetry data is received you should see all available data when starting the SCAN PROCESS in TELEMETRY MENU of your FRSky radio.<br />
	<br />		<br />
Line 88:		Line 95:
	<br />		<br />

			<!--T:23-->
	{\| class="wikitable" style="text-align: center; margin-left: 70px; background-color: #F9DDCC; border: solid #F18308 2px;"		{\| class="wikitable" style="text-align: center; margin-left: 70px; background-color: #F9DDCC; border: solid #F18308 2px;"
	\|+ style="caption-side:bottom;\|FRSKY default channel order		\|+ style="caption-side:bottom;\|FRSKY default channel order

← Older revision		Revision as of 08:32, 25 April 2024
Line 22:		Line 22:
	<!--T:24-->		<!--T:24-->
	{\| style = "text-align:center;"		{\| style = "text-align:center;"
	\| style = "width: 200px;" \| [[File:ArcherRSPlus.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:~~ArcherRSPlus_Res~~.png\|border\|x180px]]		\| style = "width: 200px;" \| [[File:ArcherRSPlus.png\|border\|x180px]]
			<!-- \| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:ArcherRSPlus_Res.png\|border\|x180px]] -->
			\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Archer RSPlus Res2.png\|border\|x180px]]
	\|-		\|-
	\| Archer RS+ using SBUS and S.Port(inv.) signals \|\| style = "padding: 0px 0px 0px 50px;" \| Add 10k resistor between S.Port(inv.) and minus		\| Archer RS+ using SBUS and S.Port(inv.) signals \|\| style = "padding: 0px 0px 0px 50px;" \| Add 10k resistor between S.Port(inv.) and minus
Line 37:		Line 39:
	<!--T:25-->		<!--T:25-->
	{\| style = "text-align:center;"		{\| style = "text-align:center;"
	\| style = "width: 200px;" \| [[File:PullDown DI2 Signal.png\|border\|x180px]] \|\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Futaba SBUS2.png\|border\|x180px]]		\| style = "width: 200px;" \| [[File:PullDown DI2 Signal.png\|border\|x180px]]
			\| style = "padding: 0px 0px 0px 50px; width: 200px;" \| [[File:Futaba SBUS2.png\|border\|x180px]]
	\|-		\|-
	\| Add 4.7k between signal and minus \|\| style = "padding: 0px 0px 0px 50px;" \| Use a small PCB to make soldering easier		\| Add 4.7k between signal and minus \|\| style = "padding: 0px 0px 0px 50px;" \| Use a small PCB to make soldering easier