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

Increase endpoint range #161

Open
batata004 opened this issue Jul 21, 2023 · 3 comments
Open

Increase endpoint range #161

batata004 opened this issue Jul 21, 2023 · 3 comments

Comments

@batata004
Copy link

Hi,

This firmware is awesome but there is only one thing I cant do: is it possible for you to increase the ENDPOINT range? So far I can go up to +120% and -120%. I would like to use something like 500% or even 600%. There reason is valid: I want to control a MOSFET with PWM but the duty cycle of most radios is around 10% (pulses goes from 0.5ms to 2.5ms every 20ms). If you allowed to increase the ENDPOINT to larger values, then many people could use their own MOSFETs to control anything using Flyskyi6 radio. I know I could use brushed ESCs but I will be stuck with the ESCs MOSFET and I would like to use my own MOSFETs for specific loads/voltages/currents...

Thank you and congratulations for the work you put into this firmware, it's awesome!!!

@batata004
Copy link
Author

Is there any other place where I should post this?

@Yenya
Copy link
Collaborator

Yenya commented Sep 1, 2023

@batata004: I don't think it is possible at all. FS-i6 transmits digital AFHDS2A signal, which is transformed to PPM only at the RX side. The only PPM signal generated by the TX itself is the one comming from the mini-DIN connector on the back side of the TX.

Also, bear in mind that our firmware is not a complete firmware rewrite, but instead a binary patch to the partly reverse-engineered original FlySky firmware, with several functions and menus replaced and new features implemented only by using several memory regions we consider unused. So I doubt something like this would be possible without reverse-engineering and rewriting more parts of the firmware.

@ghost
Copy link

ghost commented Sep 8, 2024

The easiest way to do this, is to use a secondary microcontroller, reading the iBus and converting the channel value to PWM using onboard timers. I've done this successfully for another project.

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

No branches or pull requests

2 participants