Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Horus X10S Express and OTX 2.3.12 causes on some receivers huge delay in signals and causes malfunction on S-Bus and slow down in PWM Outputs #8565

Closed
BernhardFe opened this issue Jun 21, 2021 · 11 comments · Fixed by #8568
Assignees
Milestone

Comments

@BernhardFe
Copy link

I updated my FRSky Horus X10S Express form OTX 2.3.11 to 2.3.12.

After the update some models working with FrSky Archer R8 Pro (FW2.1.7)and FrSky RSX-R (FW2.1.0) (both on ACCESS protocol) doesn't work with S-Bus to a Spirit FBL unit any more.
Looking deeper I saw as well that there is a huge delay on signal processing (0,5 >2s) on the Archer R8 Pro to the PWM output with OTX 2.3.12. The PWM's of the Archer R8 Pro have nothing to do with the spirit unit. So it seems to be an issue between Horus and receiver.
This happend not to an Archer RS (FW2.1.8). This unit works fine together with the Spirit

Roll back and forth between 2.3.11 and 2.3.12 let me reproduce the errors.

I expected that the Archer R8 Pro and the RSX-R work after the update to the new OTX version as before.

IMG_1870
IMG_1871

@BernhardFe
Copy link
Author

Update: Others found that the issue happens if 24 channels selected in the protocol to the receiver. If the channels reduced to 16 the issue seems to be fixed in 2.3.12. In 2.3.11. 24 channels are working as expected

@3djc 3djc added this to the OpenTX 2.3.13 milestone Jun 21, 2021
@Fridolin1981
Copy link

Fridolin1981 commented Jun 21, 2021

I had a similar issue:

Horus X10S Express, FW 2.1.6, OTX 2.3.12 together with the Archer SR8Pro FW 2.1.7. With OTX 2.3.12 there seems to be an issue in the PWM transmission. I have flaps using the slow function. There is a delay of about 1.5 seconds before the servos start to move and then they stop in midposition. After another 1.5seconds the movement continues.
After switching back to 2.3.11 there is no problem to be found.

@BernhardFe
Copy link
Author

If you need only 8 or 16 channels you can switch in the Horus at the receiver registration to 8 or 16 channels. Then you can use the OTX 2.3.12 and the signal is faster transmitted as well.

@3djc
Copy link
Contributor

3djc commented Jun 22, 2021

Could you try with this firmware and confirml it does fix it ?

not working

@3djc 3djc linked a pull request Jun 22, 2021 that will close this issue
@BernhardFe
Copy link
Author

First test with Archer RS and Horus X10S Express, 16 CH mode, S-Bus connection to the spirit2 unit fails. Communication doesn't work Spirit2 says. Flashing back the Horus works again.

@3djc
Copy link
Contributor

3djc commented Jun 23, 2021

Very true, another test if you do not mind

x10express.zip

@BernhardFe
Copy link
Author

Test with Archer RS and Horus X10S Express, 16 CH mode and 24 CH mode, S-Bus connection to the spirit2 unit has been successful. No issues found any more.
Not tested: Other Archers and 8CH mode

@3djc
Copy link
Contributor

3djc commented Jun 23, 2021

Thanks for your test and report !

@BernhardFe
Copy link
Author

Is this fix save to fly?

@3djc
Copy link
Contributor

3djc commented Jun 24, 2021

yes

@BernhardFe
Copy link
Author

Thanks! :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants