Little different behavior here:
it makes no difference whether integration cable is connected or not.
Starting Lua before powering up Spirit makes scripts work and LED continues flashing, but powering Spirit without activating scrips before results in Spirit LED off after init procedure is completed (jumping swash plate).
Regards,
Toni
OpenTx integation does not work
Just checked mine again and it acts exactly like yours. I have the latest OpenTx 2.2.3 installed in my Taranis Qx7s and I am using a Rx8r pro rx. I am uploading the video now!Carthago wrote:Little different behavior here:
it makes no difference whether integration cable is connected or not.
Starting Lua before powering up Spirit makes scripts work and LED continues flashing, but powering Spirit without activating scrips before results in Spirit LED off after init procedure is completed (jumping swash plate).
Regards,
Toni
Sent from my SM-G950F using Tapatalk
Tomas, does the integration in the Frsky video, that they sent you, behave differently from the one I posted? If yes, then perhaps they maybe have a new different firmware for the reciever with a fix?
Regards,
Denis
Sent from my SM-G950F using Tapatalk
Regards,
Denis
Sent from my SM-G950F using Tapatalk
-
duckforeman
- Posts: 12
- Joined: Tue 18. Dec 2018 15:55:06
I have now re-tried it with an RX8R pro, with Open TX 2.2.3 on a Horus X10. Before doing so I downloaded and flashed the receiver with the latest firmware. This was EU LBT - I wonder if that is significant?
I can confirm that the behaviour is consistant with what others are seeing, i.e. powering up first, then running the LUA does not work, whereas running the LUA then powering up the receiver does work. Non redundancy receivers working properly.
Chris
I can confirm that the behaviour is consistant with what others are seeing, i.e. powering up first, then running the LUA does not work, whereas running the LUA then powering up the receiver does work. Non redundancy receivers working properly.
Chris
-
duckforeman
- Posts: 12
- Joined: Tue 18. Dec 2018 15:55:06
A further thought, when downloading OpenTX firmware there are several switches that need to be selected to determine exactly which features are compiled. Could the problem lie in that area? I've not looked to see what the possibilities are yet, there may not be anything that could make a difference.
I think there is something different in the way FrSky handles the S-port communications in the recievers that are having this weird behaviour cause how come the other recievers like the non redundancy receivers work (integrate) properly and the ones like the Rx8r pro don't?
Or do the redundancy receivers need a different lua script perhaps? Just a thought! Though the LED light on the Spirit unit turns off completely after initialization if the lua script isn't called first which is strange so the problem might be something else.
Sent from my SM-G950F using Tapatalk
Or do the redundancy receivers need a different lua script perhaps? Just a thought! Though the LED light on the Spirit unit turns off completely after initialization if the lua script isn't called first which is strange so the problem might be something else.
Sent from my SM-G950F using Tapatalk
-
duckforeman
- Posts: 12
- Joined: Tue 18. Dec 2018 15:55:06
Denis 747,
I think that there has to be something different. with two receivers you are only allowed to enable telemetry in one. I've not looked to see how you connect the sensors as I've only set up a redundancy system using an RB10 not any of the receivers with the redundancy bus, but presumably they must have to determine at start up whether they should activate the S-port and I'm guessing that there is a bug in that process that throws the S-port out of sync with the spirit. I'd be tempted to get a 'scope on it but that would be too much like my day job! (Electronic designer)
I think that there has to be something different. with two receivers you are only allowed to enable telemetry in one. I've not looked to see how you connect the sensors as I've only set up a redundancy system using an RB10 not any of the receivers with the redundancy bus, but presumably they must have to determine at start up whether they should activate the S-port and I'm guessing that there is a bug in that process that throws the S-port out of sync with the spirit. I'd be tempted to get a 'scope on it but that would be too much like my day job! (Electronic designer)
Yes I think that is the case too.duckforeman wrote:Denis 747,
I think that there has to be something different. with two receivers you are only allowed to enable telemetry in one. I've not looked to see how you connect the sensors as I've only set up a redundancy system using an RB10 not any of the receivers with the redundancy bus, but presumably they must have to determine at start up whether they should activate the S-port and I'm guessing that there is a bug in that process that throws the S-port out of sync with the spirit. I'd be tempted to get a 'scope on it but that would be too much like my day job! (Electronic designer)
I am using a Frsky XM+ Rx as the slave receiver connected to the RX8R Pro's redundancy bus on my Trex 550X.
Sent from my SM-G950F using Tapatalk