I don't belive, that Tomas will program a luascript for the Spirit Log for Ethos...this means effort for a "small number" of Ethos users -
It would be simpler and sufficient to write a csv file for the relevant parameters and then be able to view it in an external viewer - of course an integrated solution would be desirable, but whether it will be implemented is questionable - or someone will program something like Offer Shmuely did it at edgetx -
Regards
FrSky Integration with Ethos, S.Port & F.Port
Log viewer for EthOS will certainly be available along with other settings. But I cant tell you when even if it would be next week. We have so many things to do it is better to not promise anything. We are just sure it will be there, especially when OpenTX have this.
Spirit System developer
Why is the menu structure not the same as in Spirit Settings. Not only the Lua for openTX/EdgeTX , but also this Ethos script forces me to search for the parameters, even if it's closer.
Wouldn't it be better to put everything on one page and distribute it across horizontal pages so that everything (e.g. '<Back' , 'Save Settings' and 'Close Menu' ) always remains visible.
...how many times I got out of the Lua without 'Close Menu' and the GT keeps flashing... (and I have to go back into the Lua and exit it the prescribed way)
And please no additional query, whether the menu should really be closed. It's just so unnecessary.
Apart from the fact that the governor is not available (work is apparently being done on it), I couldn't set the limits except in Bank0 (I hadn't adjusted properly at home) because they are grayed out in Bank 1 and Bank2.
Thought it should also be possible to change these and other values in Bank1 and 2.
'Receiver Type' FBus is also called ??? displayed and is not (yet) in the menu, but you probably know that...
Greetings - you are doing a great job
Wouldn't it be better to put everything on one page and distribute it across horizontal pages so that everything (e.g. '<Back' , 'Save Settings' and 'Close Menu' ) always remains visible.
...how many times I got out of the Lua without 'Close Menu' and the GT keeps flashing... (and I have to go back into the Lua and exit it the prescribed way)
And please no additional query, whether the menu should really be closed. It's just so unnecessary.
Apart from the fact that the governor is not available (work is apparently being done on it), I couldn't set the limits except in Bank0 (I hadn't adjusted properly at home) because they are grayed out in Bank 1 and Bank2.
Thought it should also be possible to change these and other values in Bank1 and 2.
'Receiver Type' FBus is also called ??? displayed and is not (yet) in the menu, but you probably know that...
Greetings - you are doing a great job
Hello,
this all comes from limitations that are defined by Lua interface. We can't do magic there and it all depends on what FrSky allows to implement.
Then there are various memory limitations that we have to bear with. So for this reason it is not ideal.
But there are still things we are improving.
this all comes from limitations that are defined by Lua interface. We can't do magic there and it all depends on what FrSky allows to implement.
Then there are various memory limitations that we have to bear with. So for this reason it is not ideal.
But there are still things we are improving.
Spirit System developer
Guys, for me integration doesn't work at all. X20s + Archer GR8 + Spirit Pro + all latest version on Spirit and LUA script. Telemetry works great. But if I start the script, nothing shows up. Question marks in servo type, basically no data. Is it any known issue?
Ok, now I know the reason why it doesn't work. I do use SBUS + S.Port.ZeXx86 wrote:EthOS integration will not work with SPort/SBUS. This is not allowed by FrSky.
Only FPort and FBus will work with EthOS.
With OpenTX all protocols will work.
Thomas, could you share what makes a problem in Ethos comparing to OpenTX? I think it's worth raising an issue on their FrSky GitHub 'Community Feedback'. They are super responsive and resolve most probems.
I opened the ticket here: https://github.com/FrSkyRC/ETHOS-Feedba ... ssues/2628
Although it would be great to have some more background for Ethos devs. For now I hope they just know about the problem.
Although it would be great to have some more background for Ethos devs. For now I hope they just know about the problem.
azaz44 wrote:Ok, now I know the reason why it doesn't work. I do use SBUS + S.Port.ZeXx86 wrote:EthOS integration will not work with SPort/SBUS. This is not allowed by FrSky.
Only FPort and FBus will work with EthOS.
With OpenTX all protocols will work.
Thomas, could you share what makes a problem in Ethos comparing to OpenTX? I think it's worth raising an issue on their FrSky GitHub 'Community Feedback'. They are super responsive and resolve most probems.
If you have spirit pro you need the intergration cable. It works. I have spirit gt and spirit pro on my helis
