Hello,
I have the following setup:
- SAB 700 competition
- Brain2 FBL version 3.4.0 (tried also the latest version)
- FRSKY Archer RS (F-BUS enabled)
- Castle Phoenix edge 160 HV with 10K resistor
- 2S lipo for electronics
- 12S lipo for ESC
I have configured the brain2 to get telemetry data from the ESC, this all is fine, as long as the motor is not spinning.
As soon as i throttle up, the telemetry data from the ESC is gone missing, and ending up into a sensor lost warning in OpenTX.
Only at very low RPM the telemetry data from the ESC is still working.
Even when i disable the throttle again, the telemetry data is not recovered. The recover this, i need to restart the receiver and FBL.
any idea where i can start looking, or how to debug this?
Hello,
Here an update from my side:
I removed the resistor from the ESC line, and turned off link live in the ESC, and turned of the extra telemetry for Castle in the Brain2.
So, basically back to basics, with only the RPM sensor connected.
I did spool up again, and the same issue happened. Lossing only the telemetry from the Brain2. (telemetry like RSSI and RxBt where still working)
Then i looked at the logging in the brain, and seams that all telemetry logging is there including all ESC data, even from the previous flights. And not missing anything.
Then after a long time i found out that my receiver was set to F-PORT2, but the Brain2 was programmed to F.PORT
Afte chancing the receiver to F.port. All was fine.
Question left: how can i use F.port2 together with the Archer-RS. just connect it to the S.Port (non inverted one?)
And what are the advantaged over standard F.Port?
Then after a long time i found out that my receiver was set to F-PORT2, but the Brain2 was programmed to F.PORT
Afte chancing the receiver to F.port. All was fine.
Great that you found the problem yourself and fixed it.
With this second post where you say you were using the F.Port2 protocol with Archer RS, now the reporting makes more sense.
Unlike all other receivers, Archer RS uses a different firmware than the other receivers which has some issues with the new F.Port2 protocol. For example the LUA app for Integration does not work. We have already reported this problem to FrSky some time ago.
From a practical point of view, you get the same performance using the F.Port or F.Port2 protocol (same radio channels, same telemetry, same LUA Integration). Theoretically the newer F.Port2 protocol offers more options and possibilities but these options are not needed and are not used with our flight controller units.
We recommend and suggest you to use the latest firmware 3.4.045 and the latest version of the LUA Integration app in our FCUs.
You didn't say what you use, but if you haven't already, we recommend that you use the latest version of OpenTX in your transmitter, the latest version of the ISRM firmware and the latest version of the Archer RS receiver firmware.
Aside from the above, when asking for support, to get as many answers as possible, you should always read the Sticky "WHEN YOU ASK FOR SUPPORT:" post first.
