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

Add launch parameter to disable auto firmware update #61

Merged

Conversation

apartridge
Copy link
Collaborator

No description provided.

By default the Zivid ROS driver always updates the firmware of the
camera. Some have expressed a desire to disable this behavior, so here
we add a launch parameter that can disable this feature. Then the camera
must be updated manually, fex in Zivid Studio or via
ZividFirmwareUpdater.
Comment on lines +201 to +208
Or, if using `roslaunch` specify the parameter using `<param>`:

```xml
<launch>
<node name="zivid_camera" pkg="zivid_camera" type="zivid_camera_node" ns="zivid_camera" output="screen">
<param type="string" name="frame_id" value="camera_1" />
</node>
</launch>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice to add the example of launching the zivid_camera node with parameters.

I think it would be nice to add the available launch parameters to the sample.launch file also, since it's most convenient to run the zivid_camera node (and the application code) from launch files. It would be nice to include the available options to the sample.launch file then.

<node name="zivid_camera" pkg="zivid_camera" type="zivid_camera_node" ns="zivid_camera" output="screen"/>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe something like this:

<arg name="frame_id" default="zivid_optical_frame"/>
<node name="zivid_camera" pkg="zivid_camera" type="zivid_camera_node" ns="zivid_camera" output="screen">
    <param type="string" name="frame_id" value="$(arg frame_id)"/>
</node>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then we can add most/all available options, like serial_number and update_firmware_automatically, to that sample launch file.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively add a new zivid_camera launch file under https://github.com/zivid/zivid-ros/tree/master/zivid_camera/launch, and that launch file in the sample launch file.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, might be a good idea to add a launch file with all the parameters. Here I just wanted to add an example of how to set it for a .launch file yourself. The disadvantage of having all of them in the launch file is that we duplicate the default value, I suppose. We already have an existing request for this: #34, so I think we should not solve it now as part of this PR.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, sorry didn't go through the current list of issues. #34 explains very well what I meant.
Sure, it's fine for me not to update it as part of this PR.

If it's fine by you, I could make a follow-up PR for #34. I missed this when I was using the driver for internal usage.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Feel free to make a PR for this @runenordmo

@runenordmo
Copy link

Looks good, added only one comment/suggestion 👍

@apartridge apartridge merged commit 9670388 into master Nov 10, 2021
@apartridge apartridge deleted the add_launch_parameter_to_disable_auto_firmware_update branch November 10, 2021 09:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants