-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Where to find default Params #1757
Comments
Hi @swiz23 You can find the default profile that is being applied by looking near the bottom of the launch log, under the heading Setting Dynamic reconfig parameters.. For example:
The change was introduced in RealSense ROS wrapper version 2.2.22 and is described in the release notes quote below: "Choose the default profile in case of an invalid request. Notice that the rs_camera.launch file now selects the default profile for each device". Doronhi the RealSense ROS wrapper developer has said about it: "The feature is meant to deal with the fact that not all devices have the same profiles. It also prevents the need to define default profiles in realsense2_camera, as they are already defined in the underlying librealsense2 library". Under the new system, if you define a custom stream height and width in the roslaunch instruction then you must also define the FPS speed for that particular stream and express it as a decimal point value such as 30.0. |
Thanks, @MartyG-RealSense. |
Thanks for the tips! I tried setting the fps using a decimal point value, but I get an error message about the type not being correct. I saw in the nodelet.launch.xml file that the 'type' for the fps parameters are set to 'int'. |
I think that the FPS is an int value when set inside the launch file as an arg, such as Can you confirm that you put the FPS value on the end of the roslaunch instruction please (not inside the file). For example: roslaunch realsense2_camera rs_camera.launch depth_width:=640 depth_height:=480 depth_fps:=30.0 |
Ahh, no. I put it as 30.0 inside my custom launch file that calls the rs_camera.launch file. Is that alright to do? It seems to work just fine. |
I researched the issue @swiz23 and FPS values are written as an int (30) in the launch file in every example that I saw. |
For no good reason, for now, fps values are defined as integer in ROS1 and float in ROS2... |
Hi @swiz23 Do you require further assistance with this case, please? Thanks! |
Nope! Thanks. |
Thanks very much @swiz23 for the update! |
Now that the rs_camera.launch file sets many parameters to -1 (which I assume means 'use the default value on a device basis'), where can I find what the actual defaults are for each device?
The text was updated successfully, but these errors were encountered: