FrSky Integration with Ethos, S.Port & F.Port
All sensors coming from Spirit have physId = 0x16 so it should not cause any conflicts.
Spirit System developer
I got my FBUS sensor for the temperatures today and connected it. Immediately again sensor conflict messages. These messages came constantly every 30s.
I looked at the appIDs of the new sensor and found that Temp.1 from SPIRIT GT and Temp.1 from FAS100ADV have the same appID.
As far as I know this should not happen because Ethos only evaluates the appID for FBus sensors. But I'm not sure if this is really the case.
I have reconfigured the sensor FAS100ADV Temp. 1. Changing the appID from 400 to 40F.
Important: Now I turned off the receiver and deleted all sensors. Reboot the receiver and search for sensors.
Now I no longer get a message about a sensor conflict.
Thanks again for your work on the firmware Tomas.
I am very happy now and will go flying as soon as the wind dies down.
Ciao
Jörg
I looked at the appIDs of the new sensor and found that Temp.1 from SPIRIT GT and Temp.1 from FAS100ADV have the same appID.
As far as I know this should not happen because Ethos only evaluates the appID for FBus sensors. But I'm not sure if this is really the case.
I have reconfigured the sensor FAS100ADV Temp. 1. Changing the appID from 400 to 40F.
Important: Now I turned off the receiver and deleted all sensors. Reboot the receiver and search for sensors.
Now I no longer get a message about a sensor conflict.
Thanks again for your work on the firmware Tomas.
I am very happy now and will go flying as soon as the wind dies down.
Ciao
Jörg
- Attachments
-
-
Thank you for the report.
It is interesting it is reporting as conflict, since both sensors are running as different PhysID. But likely FrSky wish to run all sensors under different AppID.
It is interesting it is reporting as conflict, since both sensors are running as different PhysID. But likely FrSky wish to run all sensors under different AppID.
Spirit System developer
Hi all
Radio: X10s express
Receiver:Archer RX6R LBT
Spirit:Spirit GT
Radio SW:Ethos 1.4.5
I have installed the Spirit GT via SBUS connection from the molex plug of the RX6R to the Spirit GT Rudder Input. All is working good so far, flies good etc.
Now I wanted to use the Ethos Integration on the radio. So I connected via the FRSKY connection cable for Spirit. Shorter lead to the receiver, longer lead to SYS-Input of the Spirit GT.
I installed the script software under Scripts/Spirit in Ethos, but if I try to call the LUA script all items are greyed out.
What I am doing wrong?
Thanks
Radio: X10s express
Receiver:Archer RX6R LBT
Spirit:Spirit GT
Radio SW:Ethos 1.4.5
I have installed the Spirit GT via SBUS connection from the molex plug of the RX6R to the Spirit GT Rudder Input. All is working good so far, flies good etc.
Now I wanted to use the Ethos Integration on the radio. So I connected via the FRSKY connection cable for Spirit. Shorter lead to the receiver, longer lead to SYS-Input of the Spirit GT.
I installed the script software under Scripts/Spirit in Ethos, but if I try to call the LUA script all items are greyed out.
What I am doing wrong?
Thanks
Hello,
you are using Spirit GT and SBus, then you need connection between SPort and Sys-Port (Spirit GT) - look here in the manual discribed:
see under Spirit GT:
http://manual.spirit-system.com/index.p ... ntegration
Additional hint: update your Ethos to 1.46
Regards
you are using Spirit GT and SBus, then you need connection between SPort and Sys-Port (Spirit GT) - look here in the manual discribed:
see under Spirit GT:
http://manual.spirit-system.com/index.p ... ntegration
Additional hint: update your Ethos to 1.46
Regards
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.
Only FPort and FBus will work with EthOS.
With OpenTX all protocols will work.
Spirit System developer
Hi
Of course the SPort Pin (not SBUS) is connected via Spirit connection cable to the SYS-Port.
So the connection should be ok in my opinion.
Thanks
Of course the SPort Pin (not SBUS) is connected via Spirit connection cable to the SYS-Port.
So the connection should be ok in my opinion.
Thanks
Mattes61 wrote:Hello,
you are using Spirit GT and SBus, then you need connection between SPort and Sys-Port (Spirit GT) - look here in the manual discribed:
see under Spirit GT:
http://manual.spirit-system.com/index.p ... ntegration
Additional hint: update your Ethos to 1.46
Regards
Good Morning
Ok, will try again. In the settings of the receiver I can switch between S-Port, Fport and FBUS. Will try with Fport.
Thanks
Ok, will try again. In the settings of the receiver I can switch between S-Port, Fport and FBUS. Will try with Fport.
Thanks
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.