-
Notifications
You must be signed in to change notification settings - Fork 782
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
Pr vision cam #180
Pr vision cam #180
Conversation
models/vision_cam/model.sdf
Outdated
<stddev>0.001</stddev> | ||
</noise> | ||
</camera> | ||
<plugin name="svo_plugin" filename="libgazebo_ros_camera.so"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
svo_plugin
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've tested this model with external vision library which is called svo: https://github.com/uzh-rpg/rpg_svo. But it's up to user what name for plugin is preffered. We may call it vision_plugin.
</noise> | ||
</camera> | ||
<plugin name="vision_cam_plugin" filename="libgazebo_ros_camera.so"> | ||
<alwaysOn>true</alwaysOn> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The indentation is 2 whitespaces.
@EliaTarasov can you explain and exemplify why is this required and how can it be used? This should also be documented on the PX4 Devguide. |
@TSC21
So here vision works always ok and we can't do much testing.
So overall, optical flow plugin allows us to test some important math stuff behind. Example: |
I see the point. But then I guess it makes sense to actually generalize this for other models by adding a sdf element to select the src for vision estimation (Gazebo itself or an external estimator). |
Generalization looks better of course. Does it make sense to implement this sdf element on current commit? |
Yes I don't see a problem |
I've added <vision_source> tag into gazebo vision plugin: branch |
That's the point. If the vision source is external, that means that the vision plugin does not have to start, since there is another vision source producing and publishing data to |
That's true. |
- since the airspeed axis is different for tailsitters we need to know if the vehicle is a tailsitter or not Signed-off-by: Roman <bapstroman@gmail.com>
Signed-off-by: Roman <bapstroman@gmail.com>
Signed-off-by: Roman <bapstroman@gmail.com>
Signed-off-by: Roman <bapstroman@gmail.com>
That makes sense to me. Can you implement and commit? Thanks |
This implements the Basic Camera Operations described by the Camera Protocol Documentation: https://mavlink.io/en/protocol/camera.html Only the very basic commands are implemented, providing image capture only (no video capture). Within the basic set of messages, all messages are implemented as well as all behaviors. This "camera" component handles its own UDP "link" with the GCS. It emits its own heartbeats, and handles all the camera related communication between the GCS and the camera.
@TSC21 I did some research regarding last conversation and found that Gazebo vision topic cannot be easily filled by external vision subsystem's output. Basically we have two options:
First option's drawback is that plugin's code become directly dependent on Ros which is not good for users want to use gazebo sim without Ros. I think these two drawback are too much to be handled in master and now i work on integration of vision library directly into sitl_gazebo code (the way Optical Flow now works).
So for now i would suggest to close this pr as it is not completely solve the original task. |
@EliaTarasov additional repos may represent a problem because of the licensing and we actually want to not depend on any kind of other repo. The PR itself should be generic in a way we don't need to rely on any other dependency and, at all. depend on ROS (unless the CMake option |
Signed-off-by: Roman <bapstroman@gmail.com>
- handling of the various actuation joints is handled via channels specified in the sdf file of the model Signed-off-by: Roman <bapstroman@gmail.com>
- this was causing unrealistically high side force when the vehicle was turning and producing sideslip, as a result the vehicle would hardly turn Signed-off-by: Roman <bapstroman@gmail.com>
…azebo into pr-vision_cam
@EliaTarasov you need to rebase this. |
Closed as it was found not suitable for the task. |
This pr adds vision cam model to be able to test external vision without internal vision plugin (for example by using ROS).