Changes

'''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 />

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 />

<br />