-
Notifications
You must be signed in to change notification settings - Fork 206
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
camera.AcquisitionFrameRate.SetValue() is not accurate #748
Comments
it is not clear for me what time you want to measure? it seems to be for me that the measurement is not stable on your PC in highspeed mode. how affect his your application? did you check the timestamp if grab result? also print block ids to see if the system loses images |
As mentioned by @SMA2016a you measure the time when you receive the frame on your host and not when the acquisition took place. As you are not running on a RTOS, the time when your user process wakes up ( RetrieveResult returns ) can jitter quite heavy depending on overall system load. |
Describe what you want to implement and what the issue & the steps to reproduce it are: Framerate issue
I am trying to capture a sequence of still images.
I set two stages as below.
I checked that 500fps is possible from the pylon viewer.
And I set the framerate as below. and started recording.
and below is the time difference between each frame
As you can see, the stage 1 which is fast framerate is not very consistent. It must be near 2ms, but they are in the range of 1~3ms and sometimes it is even 0ms or more than 3ms
Also, the relatively slow stage 2 shows the initial framerate is very fast. and it reaches to the specified framerate.
Is my method of specifying the framerate wrong?
Is your camera operational in Basler pylon viewer on your platform
Yes
Hardware setup & camera model(s) used
acA1920-150uc
USB3 communication with PC.
Runtime information:
The text was updated successfully, but these errors were encountered: