FrSky Integration with Ethos, S.Port & F.Port

In case you do not know something or you are not sure, here is the right place for your question.
ZeXx86
Site Admin
Posts: 12849
Joined: Mon 29. Apr 2013 16:06:44
Contact:

Then it works correctly. Your model is producing too low vibrations without blades.
Spirit System developer
Storchy
Posts: 107
Joined: Tue 10. Dec 2019 10:46:57

Ok, thanks i will test the value during flight
STC...
Posts: 20
Joined: Sun 28. Mar 2021 10:43:14

Hello,
will there be a new version of the LUA with the missing functions?
Like the parameters of the governor or reading out the event log.
leatherface
Posts: 72
Joined: Wed 08. Oct 2014 11:21:06
Location: sydney,australia

Also interested in the missing pages of the ethos lua scripts(governor,logs ,servo travel correction etc). Is this something that is going to be updated in the near future? Would be very handy to have. Thankyou.
ZeXx86
Site Admin
Posts: 12849
Joined: Mon 29. Apr 2013 16:06:44
Contact:

Certainly there will be update as we are doing for everything else.
Spirit System developer
Bladescraper
Posts: 3
Joined: Thu 05. Jan 2023 17:33:04
Location: Missouri, US

ZeXx86 wrote:Hello,

this is very good. FrSky told us that S.Port is not supported for EthOS and integration.
We know that it works with some receivers but we dont know if this support will still work in the future.
We hope that yes. The list of tested receivers could be great.
Just FYI:
I reached out to my main HQ contact at FrSky and he said that S.Bus/S.Port integration have always been supported on FrSky's side, and it will always be supported. Since to my (and his) knowledge, the Lua/integration script is agnostic to the communication protocol used between RX and FC.

If you find a receiver that does not work with integration, regardless of protocol it uses, let me know - it's likely something in the firmware and can be fixed, assuming it has already been confirmed to not be something on the Spirit firmware/Lua side.

The reason I am just now replying to this is because I had the thread bookmarked on Page11 and failed to notice it had moved on by a couple pages :D
Last edited by Bladescraper on Sun 19. Mar 2023 17:09:37, edited 1 time in total.
Keith
Dudemeister
Posts: 69
Joined: Mon 24. Oct 2022 5:39:06

Bladescraper wrote:
If you find a receiver that does not work with integration, regardless of protocol it uses, let me know - it's likely something in the firmware and can be fixed.
If you're looking for receivers that DON'T work with S-BUS /S.Port, then you don't need to look any further than the first post.

RX4R, RX6R, R-XSR, Archer RS, Radiomaster R161, RadioMaster R168.

I know the Radiomaster receivers are not FrSky, rather they're D16 clones, but by the same token, this should also affect any D16 compatible receivers FrSky included.
tysonfromcanada
Posts: 10
Joined: Sun 27. Sep 2020 19:31:06

I had good luck with the 3.5.0 firmware, X20s, Archer R4, Spirit2 and integration cable using f.port - everything seems to work in lua script on ethos.
Storchy
Posts: 107
Joined: Tue 10. Dec 2019 10:46:57

I have now testet Position Hold and Altitude Hold.
Both function works very well.
Sometimes the helicopter pumps around the set altitude.
I think this is due to the low vertican gain and the wind, because my Goblin Buddy is very sensitive to pitch.
I think the software works very well
ZeXx86
Site Admin
Posts: 12849
Joined: Mon 29. Apr 2013 16:06:44
Contact:

S.PORT integration always worked with FrSky from the beginning, this is true. But not with EthOS. They want to move away from this protocol and use new F.BUS. We also recommend it since it is faster and more reliable protocol. At least in theory. In practise it will show later.
Spirit System developer
Post Reply