Still have an issue with FBus (maybe? Really no clue)

Happy Monday and happy 2023!

Thank you for the report and the files.

We are sorry for the problem you are experiencing with your configuration with ESC YGE and all three dials active and that thanks to the files you sent us we should be able to solve.

From the Flight Log we see that there were two very short Throttle Cuts but without any loss of signals and model control.

Thanks to the Autorotation Bailout on, we see that the ThrottleOut signal is back to the correct value in a few moments.
The unidirectional bearing and flywheel effect of the main rotor should have caused the rotor RPMs to drop very little and the phenomenon was hardly felt during flight and if necessary, easily compensated with a very small change in the collective pitch.

For now, we suggest you use the F.Port protocol (although you use OTX and therefore have no problems, we point out for other users reading that the latest version of the LUA app for Ethos now also works with the F.Port protocol and the Smart.Port + S.Bus protocol).

If you do not use any other external FrSky sensors connected to the bus besides the ESC telemetry, you should not have any limitation or problem (the old FrSky sensors work only if connected to the Smart.Port bus and the new FrSky ADV sensors work only if connected to the F.Bus. There are no working external FrSky sensors connected to the F.Port bus).

PS: The incoming Throttle signal from your transmitter goes to -5%. We suggest you correct it in your transmitter by bringing the signal to 0% to avoid unnecessary delays in starting the motor caused by the fact that the spoolup ramp must gradually raise the signal from -5% to zero before starting to turn the motor.

Regarding your comment "flight count increased while I'm happily flying along," the Event is normal because, as explained in the instructions the flight count is increased after ten seconds from when the throttle has exceeded the value of 10%. The Events of "Governor disengaged" and "Governor engaged" are also normal when the Throttle goes to zero and then immediately returns to the previous value.

@customercare 

Yeah I'm using f.port now since I'm using the GPS on the R9M & whatever was going on causing integration to hang on me seems to have resolved itself.

To be 100% clear, the ONLY issue I saw/felt/heard was at ~336 seconds on the screenshot I've attached where the RxThrottle has remained constant but the throttle dropped on its own.

And I'm still a tail in guy working on orientations so it did freak me out! LOL 

But at ~506 seconds I actually commanded the drop in throttle as I was testing out the autorotation bailout feature.

Which is what I've been trying to tune between the ESC & iKon2 to get a quick but smooth bailout.

Edit: For the events I mentioned it was all about where they were as the throttle drop wasn't commanded by me/radio. But it makes sense that they'd show up regardless of whether not the throttle cut/gov disengaged was commanded or not.  Not sure why I've associated the flight count with a spool down. So yeah, that really doesn't point to anything but I THOUGHT it would be a clue for you guys. Sorry about that. End edit.

VERY good catch on the throttle travel though! Not sure how that happened & correcting it will probably make it easier to tune soft start/gov/bailout. So THANK YOU for that!!!

But again, this was all about the iKon2 acting like I had dropped the throttle at ~336 seconds when I had not.

Sorry for the late reply, I guess I forgot to subscribe to the thread.

Thanks again for catching the throttle travel issue!