Changes

Jump to navigation Jump to search
Updating to match new version of source page
Line 6: Line 6:  
<br />
 
<br />
   −
'''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 />
   −
'''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 signal!<!-- The MICROBEAST ULTRA has an inverter built in, so here you can use receivers with the original S.PORT.--><br />
 
<br />
 
<br />
   −
'''F.Port'''
+
{| style = "text-align:center;"
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  
+
| style = "width: 200px;" | [[File:ArcherRSPlus.png|border|x180px]] || style = "padding: 0px 0px 0px 50px; width: 200px;" | [[File:ArcherRSPlus_Res.png|border|x180px]]
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 />
+
|-
 +
| 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 />
 +
 
 +
'''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 can't support F.Port due to it's electrical architecture (bi-directional inverted bus protocol).<br />
 +
<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 />
   Line 33: Line 49:  
| 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 123: Line 139:  
==Setup with StudioX==
 
==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. 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 />
  −
  −
(Picture sys adapter!)<br />
   
<br />
 
<br />
    
<br />
 
<br />
7,241

edits

Navigation menu