-
Notifications
You must be signed in to change notification settings - Fork 142
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
Low framerate with ace2 cam even with low grabtimeout #81
Comments
Hi @michael1309 |
@michael1309 Hi, you should also check what kind of triggering you are using. That is, when using software trigger, the frame rate may be decreased by 50%. That is why, you should either use free-run (no explicit external triggering), or external hardware trigger. This topic was discussed in different other issues already and there were implementations for that. Regards |
@saif-abdullah I have set the frame rate limit in the ros driver to 50 Hz, so I still only get 7-8 FPS. @m-binev I have just tested hardware triggering.
thank you for your support |
Although I'm just in the process of testing configurations for the Ace2 pro, here are my insights so far: @michael1309 Have you tried setting the parameter enable_current_params_publisher for the node to false? It seems that the publishing of the parameter significantly slows down image publishing (from 33 FPS to 8-9 FPS in my case). I am using the following setting:
In the User Profile I set the following options:
The user profile can be saved on the camera under "UserSetControl". Make sure you select the correct user set. When you use bayer encoding, the standard image_proc/debayer and image_proc/rectify nodelets can be used to get a debayered and undistorted image afterwards because the pylon-camera-node seems not to be able to debayer the image inplace. I hope this setting helps. If you find a configuration that further improves the framerate or image quality, I would be happy if you share your setting. |
This solves my Problem thank you. |
I am closing this issue as it seems the problem is solved. |
Hello all.
We started testing the pylon6-dev branch today with an ace2 a2A1920-51gmBAS.
Since commit e07c886 the software works also with this camera :).
We want to build a stereo system and have therefore configured the two cameras with pylon as master and slave. The camera parameters are stored as usersets and then load them via the services of the driver this also works so far.
Unfortunately, in contrast to the pylon software, we do not achieve 20 FPS with mono12 or mono8, but only 7 FPS.
Changing the "grab_timeout" like mentined here :#21 does not bring any improvement.
The CPU load on our system is low during video aquiastion.
Here is the start log of the software:
thank you in advance
The text was updated successfully, but these errors were encountered: