You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I verified the behavior described below as well. 10kHz output works properly on ESP32 based receivers, but not on ESP8266 based receivers. Output initializes properly at zero, but once changed never goes below about 1% or above 99%.
Original report:
I can now confirm that my Channel goes from 988-1884. Tested different elrs Versions and differed RX pins.
The very strange thing is that the pwm signal on the receiver Pin is 0 (without any spikes) when the receiver is powered up and bound with the TX while the TX channel signal is low. As soon as the channel signal was above 1000µs once, the receiver output pwm will never go back to o again, it will always keep small positive spikes making to motor to spin slowly and never stop.
For me this looks like a bug in the pwm generation, anyone can confirm this? maybe @Ncerzzk ?
As i read that you were using a BetaFPV Lite RX as well, i just crosschecked with an other Happymodel EP1 and the behavior is exactly the same. Seems to be on all ESP8285 RX.
0% PWM until you rise it once, than it only goes back to ~1% and leaves the motor running.
I verified the behavior described below as well. 10kHz output works properly on ESP32 based receivers, but not on ESP8266 based receivers. Output initializes properly at zero, but once changed never goes below about 1% or above 99%.
Original report:
I can now confirm that my Channel goes from 988-1884. Tested different elrs Versions and differed RX pins.
The very strange thing is that the pwm signal on the receiver Pin is 0 (without any spikes) when the receiver is powered up and bound with the TX while the TX channel signal is low. As soon as the channel signal was above 1000µs once, the receiver output pwm will never go back to o again, it will always keep small positive spikes making to motor to spin slowly and never stop.
For me this looks like a bug in the pwm generation, anyone can confirm this? maybe @Ncerzzk ?
Feel free to contact me in Discord: https://discord.com/channels/596350022191415318/798006228450017290/1168851700002590751
Originally posted by @derFrickler in #1850 (comment)
The text was updated successfully, but these errors were encountered: