I am working on switching over my fleet to a Horus X10S but have hit a snag on the first model.
Goblin 380
Spirit Pro (2.4.4)
Spirit FrSky Integration Cable
Spirit Hobbywing
Hobbywing v4 80a (4.0.04)
FrSky X4RSB
FrSky GPS v2
Now, I am coming from Spektrum with this exact model, ESC & Spirit and everything was working before I started making the transition.
The Spirit is all setup now and I get the Integration on the X10S and can browse & change settings, however no matter what I do the Horus will not discover the sensors.
It discovers RSSI, RxBt and all the GPS stuff no problem.
I have also tried without the GPS and all it gets is the RSSI and RxBt.
I ordered several cables since I am swapping everything and I tried another cable to no avail.
Not really understanding how the integration works but the telemetry doesn't, especially since it was working fine on Spektrum.
Horus X10S with OpenTX 2.2.1 Telemetry Issue
Hi,
it is important to plug the FrSky integration cable in the right way, otherwise it will not work.
Please see this page: http://manual.spirit-system.com/index.p ... ntegration
There should be no other issue other than that. Yes, I recommend to not connect GPS and start discovery of the sensors.
it is important to plug the FrSky integration cable in the right way, otherwise it will not work.
Please see this page: http://manual.spirit-system.com/index.p ... ntegration
There should be no other issue other than that. Yes, I recommend to not connect GPS and start discovery of the sensors.
Spirit System developer
If integration is working, then telemetry should as well.
If not, then it mean that the integration menu was not closed properly. If the menu was opened then telemetry values are not sent so can't be discovered either.
Maybe the problem is just there. It is enough to just power up the unit and after initialization all telemetry values should be available (if sensor scanning is enabled).
Yes, longer to the SYS port.
If not, then it mean that the integration menu was not closed properly. If the menu was opened then telemetry values are not sent so can't be discovered either.
Maybe the problem is just there. It is enough to just power up the unit and after initialization all telemetry values should be available (if sensor scanning is enabled).
Yes, longer to the SYS port.
Spirit System developer
Well I figured it out.
Spirit is using the same Sensor ID (4) as the FrSky GPS v2 module. When I was testing the other night I had already discovered the GPS sensors before trying the direct connection, bypassing the GPS, so the Spirit sensor still did not come in.
It would be nice if Spirit had the ability to change the Sensor ID in the software, but for now I guess I need to order the FrSky Servo Channel Changer. I want it all setup for testing this Sunday so I guess I have to get it overnighted.
Spirit is using the same Sensor ID (4) as the FrSky GPS v2 module. When I was testing the other night I had already discovered the GPS sensors before trying the direct connection, bypassing the GPS, so the Spirit sensor still did not come in.
It would be nice if Spirit had the ability to change the Sensor ID in the software, but for now I guess I need to order the FrSky Servo Channel Changer. I want it all setup for testing this Sunday so I guess I have to get it overnighted.