Comments (7)
Hi @samibouziri Are you using a URDF, please? If you are then the above image looks unusual for a D435. A D435 URDF should look like the one at #459 (comment)
from realsense-ros.
Yes I am using this urdf I am just enabling the visualization of the mesh and the corresponding collision box in the same picture to demonstrate the offset.
here is the mesh alone:
here is the collision box alone:
and here are the two overlapping:
Sorry for the confusion
from realsense-ros.
It's no problem at all. :)
The mesh image looks correct. base_link corresponds to the tripod screw thread on the base of the camera and camera_link corresponds to the center-line of the left infrared sensor on the front of the camera.
On RealSense cameras with a glass front such as D435, depth is measured from the front glass and not from the sensor inside the casing. The depth measurement is 0 at the glass front. To find the 'ground truth' value (the depth when measured from the sensor's lens) on a D435 camera, -3.2 (mm) is added to the depth measurement.
from realsense-ros.
I am not talking about the frames or the measurements. I am talking about the position of the collision box. The collision box of the camera should encompass the camera mesh which is not the case in the picture above.
The collision box should not be centered around the camera frame (x coordinate of the origin of the collision box 0) as the camera is not positioned in the center of the camera.
In other words when visualizing both the mesh and the collision box I am expecting to see something like this :
and not something like this:
from realsense-ros.
I have not seen this particular problem in past RealSense ROS cases, unfortunately.
Are you using ROS1 or ROS2? You linked to the ROS2 wrapper's D435 URDF. If you are using the ROS1 wrapper then it has a D435 URDF here:
https://github.com/IntelRealSense/realsense-ros/tree/ros1-legacy/realsense2_description/urdf
from realsense-ros.
I am using ROS1 but the problem should be the same for ROS2 since the URDFs are the same and the meshes are the same.
Anyway if you want to align the collision box with the mesh like shown just replace the collision tag which is now:
<collision>
<origin xyz="0 ${-d435_cam_depth_py} 0" rpy="0 0 0"/>
<geometry>
<box size="${d435_cam_depth} ${d435_cam_width} ${d435_cam_height}"/>
</geometry>
</collision>
by:
<collision>
<origin xyz="${-d435_cam_depth / 2 + d435_zero_depth_to_glass + d435_glass_to_front instead} ${-d435_cam_depth_py} 0" rpy="0 0 0"/>
<geometry>
<box size="${d435_cam_depth} ${d435_cam_width} ${d435_cam_height}"/>
</geometry>
</collision>
from realsense-ros.
It's great to hear that you achieved a solution. Thanks so much for sharing it!
from realsense-ros.
Related Issues (20)
- Can't not display compressed RGB/Depth in RViz HOT 6
- `rgb_camera.color_profile` -> `rgb_camera.profile` ? HOT 2
- Announcement: RealSense ROS wrapper 4.55.1 now available HOT 10
- Cannot Publish Pointclouds on ROS Noetic under Ubuntu 20.04 on an RPi 4 HOT 4
- Can D435 or D455 be used in a MOOS environment? HOT 3
- How to calibrate D435 using checkerboard underwater? HOT 3
- Current Options for Visual Odometry with T265
- Prefixing camera frames with namespaces in the tf_static topic HOT 12
- ROS2 Lifecycle node HOT 2
- D455 camera cannot get imu msg from rostopic HOT 6
- The requested device with serial number f0232572 is NOT found. Will Try again. L515 HOT 3
- Error with "roslaunch realsense2_camera opensource_tracking.launch" HOT 31
- Connect to device via physical ID HOT 5
- The ROS wrapper for RealSense D435 does not starts, it gives ERRORS - D435+ROS Noetic+Ubuntu 20.04 HOT 41
- D455 camera cannot get imu msg from rostopic HOT 15
- Unable to build from source since PR #3125 HOT 35
- cant change color profile HOT 10
- When can a version with "rolling" support be released? HOT 3
- Failed to start the depth stream with D415 after updating to RealSense ROS Wrapper Version 4.55.1 HOT 10
- fails to build from sources HOT 23
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from realsense-ros.