-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Issue with input capture timestamp #10623
Comments
@davids5 FYI |
@DanielePettenuzzo would you please provide a link to the test code and any setup info. |
@DanielePettenuzzo - What HW? What branch? Any special test code? Please provide a link and include the pins you are connected to. |
I ran a quick test. FMUv5 Mini
Params
Code to do diff:
data: at 1119 61166978 | 61183079 | 16101 | -3899
|
@DanielePettenuzzo - I did a test run where I hacked the timer to 100 us with a 257us period.
Please describe what you are using as the source? |
@davids5 Thank you very much for looking at this. I am using an fmu-v5 (pixhawk 4) on the pr branch. I basically added a printf after toggling the trigger pin and one in the camera_capture to print the capture time. There is no special code added and I'm using fmu pin 2 to trigger and fmu pin 6 to capture. I am using the GPIO trigger because I could easily print the time of the rising and falling edge. What is the issue with this configuration? The delay I'm seeing is caused by this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm testing the camera capture driver PR (#10295) and I'm having some issues with the timestamp of the capture. I am generating an active high pulse from my pixhawk and looping it back into the input capture. The capture driver is set to capture falling edges. Sometimes my trigger falling edge and the capture timestamp match and sometimes I get a 20ms delay between the two.
Using a 4ms active high pulse as trigger:
When there is a 20 ms delay
trigger (rising edge): 76723791 us
trigger (falling edge): 76727501 us
capture (falling edge): 76747500 us
When it works
trigger (rising edge): 160397157 us
trigger (falling edge): 160401164 us
capture (falling edge): 160401164 us
Moreover in my final setup I would like to be able to able to capture the falling edge of a 100us active high pulse. Is this possible with the current capture setup?
The text was updated successfully, but these errors were encountered: