Hokuyo Laser plugin only returns INF value reading.

asked 2020-01-30 19:32:36 -0600

chngdickson gravatar image

image description

Hokuyo laser only prints out inf laser scan values, while the laser is within distance. as stated in the gazebo ros laser reference REP117

image description

Idk what's going on, i've adjusted the inertias to a valid value. My parameters for the laser sensors are as such...


    <gazebo reference="base_laser_${number}_${location}">
        <sensor type="ray" name="laser">
            <pose>0 0 0 0 0 0</pose>
            <visualize>true</visualize>
            <update_rate>100</update_rate>
            <ray>
                <scan>
                    <horizontal>
                        <samples>10</samples>
                        <resolution>1</resolution>
                        <min_angle>-0.0174533</min_angle>
                        <max_angle>0.0174533</max_angle>
                    </horizontal>
                </scan>
                <range>
                    <min>${laser_xyz}</min>
                    <max>1.0</max>
                    <resolution>0.01</resolution>
                </range>
                <noise>
                    <type>gaussian</type>
                    <mean>0.0</mean>
                    <stddev>0.00005</stddev>
                </noise>
            </ray>

The behavior of my laser sensor going inf inf inf only happens when the model started moving. When it's static, the range shows up as such.

image description

Please any help would be appreciated.

edit retag flag offensive close merge delete

Comments

Did you get it to work? Can you see the laser visualization in Gazebo?

robotlab gravatar imagerobotlab ( 2020-10-15 16:53:15 -0600 )edit

I'm having a similar issue. I'm not sure what is going on. I was successfully seeing lidar data when running using a VM but when I brought everything over to a computer where I could run natively, the lidar values switched from .inf when it did see anything and a range when it did to all -.inf values regardless of whether something is present or not. I tried sticking something behind the 'robot' as well in case the rays were projecting backwards. Moving doesn't change the behavior.

raefsel gravatar imageraefsel ( 2022-05-04 14:34:43 -0600 )edit

To piggyback onto my previous comment, I figured out that by switching from "gpu_ray" to "ray" I could get good data again provided that I have my collision geometry set up properly. Apparently there may be an issue with the GPU drivers on this computer? The VM was running on this same computer when I had Windows on it.

raefsel gravatar imageraefsel ( 2022-05-04 15:28:42 -0600 )edit