-
Notifications
You must be signed in to change notification settings - Fork 150
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
Question about function PylonInitialize #199
Comments
Hi @Felix00643298, well PylonInitialize() ist loading the complete pylon runtime environment for the given application and should be called ideally only once. |
In my ROS system, there are multiple Basler cameras, and I initialize each camera sequentially using ROS plugins. This is a multi-threaded system, and currently, I call PylonInitialize once in the constructor of each Basler class. However, it seems to make the program very unstable, and I'm unsure if what I'm doing is incorrect. basler::basler()
{
PylonInitialize();
}
basler::~basler()
{
PylonTerminate();
} |
Hello @Felix00643298 |
Thanks for replying me. |
Hello @Felix00643298 Looking at your issue, it should not be a problem to call in several instances PylonInitialize. Can you explain a bit more what you are trying to do ? and eventually provide with code examples so that your issue can be reproduced ? You are writing that your program is very unstable, can you be more specific and provide with error messages ? |
I am closing the issue for now, as there's no activity. |
Hey,
I am wondering if I have 2 basler cameras, can I call
PylonInitialize
twice in each individual basler camera object in 2 seperate threads?Thanks.
The text was updated successfully, but these errors were encountered: