Its always the smallest youtubers who have the best tutorials.

Thank you for making small videos on a single subject, it's alot easier to digest. Good Job!

I'm doing the opposite as I wait for money or objects in the mail and it's a bit mind blowing. I already have a Pico W running code for PWM out like a throttle and the ESC/Brushless motor with BEC connectors. On an oscilloscope I get a square wave from the Pico pin. In stage 2 I want to hook in to "something" for auto throttle control which can be a heat sensor or the other servo. An RC car with a propeller is the original idea. Also removing the need for 2 hand controllers.

Banger of a tutorial !

Much appreciated - Needed something like this for a lil project of mine :) Very helpful

Thank you so much, now I can FINALLY read pwm signals from my reciever. Thank you, thank you, thank you!!!!!! I used your code from your blog/website.

Thank you so much. It's really great to see these videos in such quality!

Thanks, nice video! Keep up the good work! FYI, "baud" rhymes with "clawed," not "cloud." It might be nice if you occasionally dipped into the "why" behind some of your decisions. For example, why 9600 baud? As far as I can tell, it just controls the maximum rate at which you can write new values to the serial output port, and just needs to be fast enough keep up with the 50Hz input rate -- but that's not obvious, and it would be good if you said so (and perhaps even showed what happens if you pick a different value). I'm not sure how big an int is in Arduino land; guessing 32 bits. So that's 50 * 32 = 1600 bits per second, which means that any rate higher than that would be sufficient here, and anything faster would make no difference (except, I suppose, the _tiny_ change in latency between input and output). Google says the Arduino can go up to 115,200 baud (12x faster than 9600), so you'd be looking at a potential latency change from ~100µs down to ~8µs. At first I thought that the _input_ was 9600 baud, but I did the math on that and determined that it would only give you enough resolution to differentiate about ten levels of pulse width. Your output graph clearly shows at least an order of magnitude more resolution than that!

Fantastic tutorial Informative and concise

This is a great video -- very well-done and educational about interrupts. But ... the way this is constructed, won't this have the interrupt handler routine called with each pulse of the PWM signal? Even if the duty cycle hasn't changed? Won't this swamp the processor? ALSO, what is the point of a PWM port if it doesn't convert the PWM duty cycle into some value for us? Aren't you treating the PWM port like any other digital port?

thanks code works

thank you so much, excatly what i needed!

Saved my day, thank you so much!

Could you show how to do this with (multiple) switches on your transmitter?

Thx bro

Ok

I playing around with this stuff for a fuew weeks. I have the problem thatt at the 0 position, the arduino reports values between 1505 and 1490, it ist'nt stable. At a stable position with an switch at the radio, defined 40% , isn't stable too. Is woobling around 20 digits. Is this an issue on arduinohardware or the used library?

how can I find out the same thing but from a Bluetooth remote controller app?

Thank you for this nice video, very instructive. It is a nice start for a RC project. I am however experiencing soms troubles. When using this sketch on a Nano, it stalls after about 35 minutes. Do you have any idea what might cause this?

i didn't understand why just using the pulseIn command wasn't enough. (im new to this stuff)

Avrei bisogno di leggere 6 canali da un ricevitore RC, come devo modificare la Sketch?

I want to do the same but with an Raspberry Pi Pico. Should I wire Servo Anode to ADC Ground and Servo Signal to ADC0? The Servo Signal and Servo Anode Pin give a low Voltage between 0.2V and 0.5V which is fine for the Pico's max Voltage of 3.3V

how would you do it fot a switch on the transmitter? Im trying to use arduino to control lights on an RC plane.

Nice tutorial

Excellent and succinct video! If I used a receiver with a 2.4 GHz signal, would it still work with the pwm stuff?

I can only read up to 50% of the duty cycle and then the readings begin to invert, not entirely sure why. Thank you

@TheBoredRobot how can I control a mosfet using this technique to drive coreless motors? Thanks For Your Help.

Thanks for the tutorial! Could one use a brushed ESC plugged into the RC receiver, and just measure the analog voltage it delivers? Would that work?

I have a question, I am currently using this technique to try and controll a servo, but everytime when i pull on the elevator, the servo starts twitching

how can i use this to control a stepper motor like a dc motor

produces an overflow after 35mins cause youre using long instead of unsinged long... will be 70mins with unsigned

Hi do you have any contact platform for pm. Email?

oops! friend to control the position of the stepper motor and the speed

When could CurrentTime be less or equal than StartTime? I think never. CurrentTime will be greather than StartTime always.

volatile long StartTime = 0; volatile long CurrentTime = 0; volatile long Pulses = 0; int PulseWidth void setup() { Serial.begin(9600); pinMode(RCPin, INPUT_PULLUP); attachInterrupt(digtalPinToInterrupt(RCPin),PulseTimer,CHANGE); } void loop() { if (Pulses < 2000){ PulseWidth = Pulses; } Serial.println(PulseWidth); } void PulseTimer(){ CurrentTime = micros(); if (CurrentTime > StartTime){ Pulses = CurrentTime - StartTime; StartTime = CurrentTime; } }

Like 660, great, awesome project, 🇧🇷😊👍 subscribed, @arduinomaquinas thank you bro, 😉👍👍