STM32 TIMERS #3. ENCODER MODE || F103C8

Timer counter increasing/decreasing by 4 because it counting each edges from both channels, if you change config for this timer then you should see increasing/decreasing by 2

how can i make it track the distance traveled

Thanks for sharing this video that is useful for me. I am wondering what software you used to code and to compile on this video. Can you share this software name to me, thanks in advance.

Hi @ControllersTech I've watched many videos of yours and I have to tell that you are amazing. Very understandable and interesting videos.
I have one question about the encoder: why sometimes I see, between one step and another of the encoder, the timer reads 3 or 5 steps, instead of 4?

Hello, my live expressions value change 0 and 1. How can I solve it ? Do you have any ideas ?

It posible to used incremental encorder ABI?? 600 until 2500ppr?? But i want to used CPR

Does this work for optical encoders too?

can you explain how frequency can be measured of encoder signal using input capture mode..?

My project is not work. Can y send me your project, please!

How to connect logic analyser

could you please make a video on encoder with DMA. thanks

for increasing/decreasing by 4 problem, try Prescalar(PSC) value as 4 🤗

Thank You so much man

Good work !

Please make a video on PID control.

It start counting clicks only after second click, after rotation start. If I do only one click, it is not counts it. STM32F413VG.
P.S. Sorry, it was no name chinese encoder. Encoder from Bourns do it well, from the first click.

Master, how may i get the direction of the encoder? Has some hal function that returns the encoder direction? Many thanks!

how would we write the same program for 2 encoders. Especially the capture function for two different timers? Can someone please paste the solution

How to use another timer to periodically trigger DMA to capture the value of the rotary encoder ？

I don't know why it not works on my board. I have to change to TIM1 and everything works as expected. Probably hardware problems.