ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

q8wwe's profile - activity

2023-02-08 07:47:14 -0500 received badge  Nice Question (source)
2021-02-14 03:10:44 -0500 received badge  Necromancer (source)
2021-02-14 03:10:44 -0500 received badge  Teacher (source)
2021-01-19 01:00:09 -0500 received badge  Good Question (source)
2020-08-11 07:32:57 -0500 received badge  Famous Question (source)
2020-07-21 14:52:07 -0500 received badge  Taxonomist
2020-06-15 21:59:08 -0500 received badge  Notable Question (source)
2020-05-11 11:47:31 -0500 received badge  Famous Question (source)
2020-04-03 11:33:21 -0500 received badge  Famous Question (source)
2020-04-03 05:33:59 -0500 received badge  Notable Question (source)
2020-04-03 05:32:17 -0500 received badge  Famous Question (source)
2020-03-23 08:54:31 -0500 commented question Handle Nan values from depthimag_to_laser

I added my camera URDF file and depth to lase launch file .

2020-03-23 08:53:55 -0500 edited question Handle Nan values from depthimag_to_laser

Handle Nan values from depthimag_to_laser Ros: kinetic I'm using depthimage_to laser package and facing problem with ob

2020-03-23 08:11:34 -0500 commented question Handle Nan values from depthimag_to_laser

I tried to change the values for range_min and range_mix but i always get Nan values . did you ever get -/+inf when wor

2020-03-23 05:20:32 -0500 received badge  Popular Question (source)
2020-03-21 12:38:28 -0500 marked best answer No link elements found in urdf file

I'm trying to simulate intel realsense in Gazebo and for that i run into error :No link elements found in urdf file.

My urdf.xacro file: d435.urdf.xacro:

<?xml version="1.0"?>

<!--
License: Apache 2.0. See LICENSE file in root directory.
Copyright(c) 2017 Intel Corporation. All Rights Reserved

This is the URDF model for the Intel RealSense 430 camera, in it's
aluminum peripherial evaluation case.
-->

<robot name= "intel" xmlns:xacro="http://ros.org/wiki/xacro">

  <xacro:include filename="$(find realsense_gazebo_plugin)/urdf/d435.gazebo.xacro"/> 

  <xacro:macro name="sensor_d435" params="parent *origin">
    <xacro:property name="M_PI" value="3.1415926535897931" />

    <!-- The following values are approximate, and the camera node
     publishing TF values with actual calibrated camera extrinsic values -->
    <xacro:property name="d435_cam_depth_to_left_ir_offset" value="0.0"/>
    <xacro:property name="d435_cam_depth_to_right_ir_offset" value="-0.050"/>
    <xacro:property name="d435_cam_depth_to_color_offset" value="0.015"/>

    <!-- The following values model the aluminum peripherial case for the
    D435 camera, with the camera joint represented by the actual 
    peripherial camera tripod mount -->
    <xacro:property name="d435_cam_width" value="0.090"/>
    <xacro:property name="d435_cam_height" value="0.025"/>
    <xacro:property name="d435_cam_depth" value="0.02505"/>
    <xacro:property name="d435_cam_mount_from_center_offset" value="0.0149"/>

    <!-- The following offset is relative the the physical D435 camera peripherial
    camera tripod mount -->
    <xacro:property name="d435_cam_depth_px" value="${d435_cam_mount_from_center_offset}"/>
    <xacro:property name="d435_cam_depth_py" value="0.0175"/>
    <xacro:property name="d435_cam_depth_pz" value="${d435_cam_height/2}"/>

    <material name="aluminum">
      <color rgba="0.5 0.5 0.5 1"/>
    </material>


    <!-- camera body, with origin at bottom screw mount -->
    <joint name="camera_joint" type="fixed">
      <xacro:insert_block name="origin" />
      <parent link="${parent}"/>
      <child link="camera_link" />
    </joint>

    <link name="camera_link">
      <visual>
      <origin xyz="${d435_cam_mount_from_center_offset} 0.0 ${d435_cam_height/2}" rpy="${M_PI/2} 0 ${M_PI/2}"/>
    <geometry>
        <mesh filename="package://realsense_gazebo_plugin/meshes/d435.dae" />
    </geometry>
    <material name="aluminum"/>
      </visual>
      <collision>
    <origin xyz="0.0 0.0 ${d435_cam_height/2}" rpy="0 0 0"/>
    <geometry>
    <box size="${d435_cam_depth} ${d435_cam_width} ${d435_cam_height}"/>
    </geometry>
      </collision>
      <inertial>
    <!-- The following are not reliable values, and should not be used for modeling -->
    <mass value="0.564" />
    <origin xyz="0 0 0" />
    <inertia ixx="0.003881243" ixy="0.0" ixz="0.0" iyy="0.000498940" iyz="0.0" izz="0.003879257" />
      </inertial>
    </link>

    <!-- camera depth joints and links -->
    <joint name="camera_depth_joint" type="fixed">
      <origin xyz="${d435_cam_depth_px} ${d435_cam_depth_py} ${d435_cam_depth_pz}" rpy="0 0 0"/>
      <parent link="camera_link"/>
      <child link="camera_depth_frame" />
    </joint>
    <link name="camera_depth_frame"/>

    <joint name="camera_depth_optical_joint" type="fixed">
      <origin xyz="0 0 0" rpy="${-M_PI/2} 0 ${-M_PI/2}" />
      <parent link="camera_depth_frame" />
      <child link="camera_depth_optical_frame" />
    </joint>
    <link name="camera_depth_optical_frame"/>

    <!-- camera left IR joints and links -->
    <joint name="camera_left_ir_joint" type="fixed">
      <origin xyz="0 ${d435_cam_depth_to_left_ir_offset} 0" rpy ...
(more)
2020-03-21 12:38:28 -0500 received badge  Scholar (source)
2020-03-21 10:57:07 -0500 edited question Handle Nan values from depthimag_to_laser

Handle Nan value from depthimag_to_laser Ros: kinetic I'm using depthimage_to laser package and facing problem with obs

2020-03-21 10:56:13 -0500 commented question Intel Realsense D400 in Gazebo simulation

Thank you for the support , after many attempt I was able to make the simulation work with following the link :https://g

2020-03-21 10:38:01 -0500 edited question Handle Nan values from depthimag_to_laser

Handle Nan value from depthimag_to_laser Ros: kinetic I'm using depthimage_to laser package and facing problem with obs

2020-03-21 10:37:01 -0500 asked a question Handle Nan values from depthimag_to_laser

Handle Nan value from depthimag_to_laser Ros: kinetic I'm using depthimage_to laser package and facing problem with obs

2020-03-21 10:26:05 -0500 commented answer No link elements found in urdf file

thanks, it worked after I instantiate it as marguedas mentioned

2020-03-21 10:24:42 -0500 received badge  Notable Question (source)
2020-03-21 10:24:42 -0500 received badge  Popular Question (source)
2020-03-15 11:36:38 -0500 received badge  Famous Question (source)
2020-03-04 04:44:11 -0500 received badge  Notable Question (source)
2020-03-03 16:05:11 -0500 received badge  Popular Question (source)
2020-03-02 16:38:31 -0500 commented answer No link elements found in urdf file

where shall I instantiate sensor_d435 , shall I instantiate it in the same file or create new file and what parameter sh

2020-03-02 15:15:11 -0500 edited question No link elements found in urdf file

No link elements found in urdf file I'm trying to simulate intel realsense in Gazebo and for that i run into error :No l

2020-03-02 15:13:07 -0500 asked a question No link elements found in urdf file

No link elements found in urdf file I'm trying to simulate intel realsense in Gazebo and for that i run into error :No l

2020-03-02 06:46:28 -0500 asked a question Intel Realsense D400 in Gazebo simulation

Intel Realsense D400 in Gazebo simulation Ros kinetic Ubuntu 16.04 Im trying to use intel D400 with gazebo simulation s

2020-03-02 06:08:28 -0500 commented answer Adding Intel D415 in ROS urdf

im trying to do the same to use intel camera with gazebo , but it seem i can't find a Urdf source on how to use Realsen

2020-03-02 06:07:57 -0500 commented answer Adding Intel D415 in ROS urdf

im trying to do the same to use intel camera with gazebo , but it seem i can find a Urdf source on how to use Realsense

2020-02-20 07:32:48 -0500 received badge  Popular Question (source)
2020-02-19 10:35:49 -0500 commented answer RVIZ No transform from [/links to [odom]

I tried to add : odom_trans.header.stamp = ros::Time::now(); , but it didn't work it gave same error . is there any oth

2020-02-18 15:08:08 -0500 commented answer joint_state_publisher: UnicodeEncodeError: 'ascii' codec can't encode character u'\u0130' in position 28396: ordinal not in range(128)

changing the letter removed that problem . thank you , many thanks to your precious help.

2020-02-18 15:06:52 -0500 received badge  Notable Question (source)
2020-02-18 12:14:51 -0500 commented answer RVIZ No transform from [/links to [odom]

I tried to add the robot description tag to joint_state_publisher but didn't work, it gave same errors .

2020-02-18 08:44:51 -0500 commented answer joint_state_publisher: UnicodeEncodeError: 'ascii' codec can't encode character u'\u0130' in position 28396: ordinal not in range(128)

Thank you for the clarification . I made new question on this link and attached : rqt,urdf, Rviz ,reastate launch file

2020-02-18 08:44:42 -0500 commented answer joint_state_publisher: UnicodeEncodeError: 'ascii' codec can't encode character u'\u0130' in position 28396: ordinal not in range(128)

Thank you for the clarification . I made new question on this link and attached : rqt,urdf, Rviz ,reastate launch file

2020-02-18 08:41:03 -0500 commented answer joint_state_publisher: UnicodeEncodeError: 'ascii' codec can't encode character u'\u0130' in position 28396: ordinal not in range(128)

Thank you for the clarification . I made new question on this link and attached : rqt,urdf, Rviz ,reastate launch file

2020-02-18 08:38:13 -0500 edited question RVIZ No transform from [/links to [odom]

RVIZ No transform from [/links to [odom] ubuntu : 16.04 os: kinetic robot : evarobot I'm trying to work on real robot

2020-02-18 08:26:29 -0500 asked a question RVIZ No transform from [/links to [odom]

RVIZ No transform from [/links to [odom] ubuntu : 16.04 os: kinetic robot : evarobot I'm trying to work on real robot

2020-02-17 15:23:02 -0500 commented answer joint_state_publisher: UnicodeEncodeError: 'ascii' codec can't encode character u'\u0130' in position 28396: ordinal not in range(128)

I created new URDf by removing all parts ,I only kept tags related to base link and wheels . then i relaunched the previ

2020-02-17 14:55:25 -0500 commented question updateConfig() called on a dynamic_reconfigure::Server that provides its own mutex

no solution , still unsolved

2020-02-17 13:24:45 -0500 commented answer joint_state_publisher: UnicodeEncodeError: 'ascii' codec can't encode character u'\u0130' in position 28396: ordinal not in range(128)

I tried to change the letter with dot , but that didn't solve joint_state_publisher issue

2020-02-17 13:24:27 -0500 commented answer joint_state_publisher: UnicodeEncodeError: 'ascii' codec can't encode character u'\u0130' in position 28396: ordinal not in range(128)

I tried to change the letter with dot , but that didn't solve joint_stste_publisher issue

2020-02-17 08:58:42 -0500 commented answer joint_state_publisher: UnicodeEncodeError: 'ascii' codec can't encode character u'\u0130' in position 28396: ordinal not in range(128)

that's just a comment the compiler will ignore it .

2020-02-17 04:42:19 -0500 received badge  Popular Question (source)