Skip to content
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

ros param device_user_id not working from .launch #172

Closed
TRA55A opened this issue Jul 23, 2023 · 1 comment
Closed

ros param device_user_id not working from .launch #172

TRA55A opened this issue Jul 23, 2023 · 1 comment

Comments

@TRA55A
Copy link

TRA55A commented Jul 23, 2023

Hello,

I'm starting multiple Basler GigE cameras, and my aim is to initiate the pylon node using various camera IDs. However, it appears that when I set it from the launch file, it doesn't affect the driver. I wonder if I'm using it incorrectly?

Upon inspecting the code, I noticed the presence of nh.paramstd::string("device_user_id", device_user_id_, ""); but I couldn't find any corresponding call for nh.getParam("device_user_id", device_user_id_).

Best Regards.

@FrancoisPicardDTI
Copy link
Collaborator

Hello @TRA55A
It is not possible to specify the device user id through the launch file. This id must be specified in the config/default.yaml file.
If you want to specify several .yaml files (you need one per camera in your case), you need to point to the right .yaml file when launching the node by specifying the "config_file" parameter. Let me know if it allows you to solve your issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants