calculate the time between 2 rising edge

You are aware that a single chronograph can be used to take quite a number of intermediate times when you have a runner doing a 10000m run?

It's just that you don't seem to have considered yet what it means to either start/stop a timer. Or to have a free-running timer and just take multiple snapshots and compute the difference between the snapshots. So start thinking about how you could use a single clock to both measure the total time that runner needs for 10 km running. And how you can manage to figure out each individual lap time. Or maybe each individual 1km section time.

You will fail again and again until you stop playing around and start to think about what the timer actually does. Stop thinking that the timer magically starts being in existence the moment you start to sample values. And by the way - you don't even need to capture values continuously within the loop, since it's enough to capture the value directly after you found the condition change that means you want to exit.

In the end, trial and error really is not a good route since it's so very slow. That's basically what evolution does. So trying millions of small biological changes over hundreds of generations to try to figure out if some changes might lead to an improvement or not. It's just that trial and error (in science also sometimes discussed as Monte Carlo methods) means you need a huge number of dices to be able to test enough random solutions concurrently - just to get some decent progress.

You are aware that a single chronograph can be used to take quite a number of intermediate times when you have a runner doing a 10000m run?

It's just that you don't seem to have considered yet what it means to either start/stop a timer. Or to have a free-running timer and just take multiple snapshots and compute the difference between the snapshots. So start thinking about how you could use a single clock to both measure the total time that runner needs for 10 km running. And how you can manage to figure out each individual lap time. Or maybe each individual 1km section time.

You will fail again and again until you stop playing around and start to think about what the timer actually does. Stop thinking that the timer magically starts being in existence the moment you start to sample values. And by the way - you don't even need to capture values continuously within the loop, since it's enough to capture the value directly after you found the condition change that means you want to exit.

In the end, trial and error really is not a good route since it's so very slow. That's basically what evolution does. So trying millions of small biological changes over hundreds of generations to try to figure out if some changes might lead to an improvement or not. It's just that trial and error (in science also sometimes discussed as Monte Carlo methods) means you need a huge number of dices to be able to test enough random solutions concurrently - just to get some decent progress.

Keil continues to run this forum like fools. I can't use the word "s t o p w a t c h" without getting error 500 when trying to post. Just as this forum constantly fails to accept posts relating to "w a t c h d o g". Who thinks it's clever to filter these words on a forum specifically related to embedded development??? I have also notified their support but they don't seem to be able to figure out why anyone might want to legimitely want to use the word "w a t c h" without intending it as spam.

How old are you?

How many w atches would you need to time your trip between your home and the closest town?

What processor and board are you using?

watch

stopwatch

Just use a little imagination

Imagination? The word "chronograph" in my earlier post was "stopwatch", but without any character in bold.

New posters who come here and get error 500 when they try to post will not be able to use any imagination to modify their post since they will not know that status code 500 is a badly tuned spam filter. All they want is help, and they'll leave when they can't post. And you'll never know because you never see their post. And Keil'll never know because they don't analyze the blocked posts.

All they want is help ...

All anybody wants is that occasional piece of help.

If you are using a STM Board there may be a example available with a name like

TIM_InputCapture that programs a timer to operate in input capture mode. And use

a timer interrupt to capture the time a pulse comes in. The next interrupt that occurs

because of another input pulse will cause a calculation of the time between pulses.

I am looking at STM32F_100E_EVAL board. They calculate but it also says that the frequency

maximum it can resolve is around 330 khz.

The timer can have very high resolution.
But if handling it using interrupts, then there is a limit to how often you can have your interrupts, i.e. how fast you can read out a captured value before you get the next edge.

Notice that in this specific case, the two edges arrives on two different pins, so the same capture function can often not be used unless both pins can be routed as capture pins for the same timer.

Anyway - I expect the OP has already lost interest in this thread.

Many spam in my gmail box is about Rolex. Somehow they didn't block Rolex. Maybe GShock?

Hi. we are working on the project again for now four months. i made many changes to the project and the code is now very good but it is still not working very properly.

uint8_t ch[10000];
double timerValue1,timerValue2 ,delta, delta2;

do { timerValue1 = TIM_GetCounter(TIM2); delta2 = delta1 + timerValue1;
} while(GPIO_ReadInputDataBit(GPIOC, GPIO_Pin_10)!=1) ; do { timerValue2 = TIM_GetCounter(TIM4);

delta2 = delta2 + ch[53];
} while(GPIO_ReadInputDataBit(GPIOC, GPIO_Pin_10)!=1) ;
delta= timerValue2- timerValue1;

} sprintf(ch,"%lf seconds", (double)delta); LCD_SetTextColor(LCD_COLOR_WHITE); LCD_SetBackColor(LCD_COLOR_BLACK); LCD_DisplayStringLine(LINE(9),ch);