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
[OpenTX 2.1.6] "No Impulse" on X8R seems to be not working #3099
Comments
"No Pulses" only works for the servo outputs, it's irrelevant for the SBUS output. It's the SBUS to PPM converter that AFAIK has no other option than to hold positions on failsafe. |
OK. Fine. 😄
So according yours explanations, the SBUS protocol doesn't support the No Pulse failsafe mode? |
Correct. An SBUS stream always contains 16 proportional channel positions so you can't jsut omit some channels or send a pseudo-stream with no channel data. |
Thanks for answering. |
Hi folks,
In order to create a wireless buddybox (same goal as the "Linker" sold by Aloft), I have done this setup inside the JR module bay of the master radio:
A X8R binded in D16 & Mode 2 (= no telemetry) → S.Bus to CPPM converter → heartbeat pin
The master/teacher radio is configured as followed:
The slave/student radio is configured as followed:
This setup is working perfectly. FYI, the master RF is not perturbed anymore by the telemetry feedback of the X8R (binded in mode 2). I had some RSSI warnings with the flying model on the master radio when using a X4R/CPPM setup (probably the telemetry feedback of the X4R was too close of the internal RF).
If I switched off the slave radio, I'm expecting the X8R going to no pulses failsafe mode. Thus, the master radio will play the "trainer link lost" voice announcement.
Unfortunately it is not the case. Looks like the X8R is going in receiver failsafe mode. Indeed if I chose receiver in the slave radio, I will get the same result as no pulses.
The XJT and X8R have been flashed with the latest non-EU firmwares.
I'm not sure where the problem is coming from, it can be:
The text was updated successfully, but these errors were encountered: