ydlidar X2 health code: ffffffff

edit

Hi from newbie ROS from Thailand. "Everything was working fine until i wanted to start scanning

$ roslaunch ydlidar lidar_view.launch" I change this line to run X2L Parameter roslaunch ydlidar_ros X2L.launch

that's found result :

process[ydlidar_node-1]: started with pid [10298] __ ______ _ ___ ____ _ ____
\ \ / / _ \| | |_ _| _ \ / \ | _ \ \ V /| | | | | | || | | |/ _ \ | |_) | | | | |_| | |___ | || |_| / ___ \| _ <
|_| |____/|_____|___|____/_/ __| _\

process[base_link_to_laser4-2]: started with pid [10299] [YDLIDAR INFO] Current Sampling Rate : 4K [YDLIDAR INFO] Now YDLIDAR is scanning ...... ^C[base_link_to_laser4-2] killing on exit [ydlidar_node-1] killing on exit 547438477696 thread has been canceled [YDLIDAR INFO] Now YDLIDAR Scanning has stopped ...... shutting down processing monitor... ... shutting down processing monitor complete done

but if i run : $ roslaunch ydlidar_ros lidar_view.launch program run completely but not shown data from lidar!

:ROS_MASTER_URI=http://localhost:11311

process[ydlidar_node-1]: started with pid [10803] process[base_link_to_laser4-2]: started with pid [10804] __ ______ _ ___ ____ _ ____
\ \ / / _ \| | |_ _| _ \ / \ | _ \ \ V /| | | | | | || | | |/ _ \ | |_) | | | | |_| | |___ | || |_| / ___ \| _ <
|_| |____/|_____|___|____/_/ __| _\

process[rviz-3]: started with pid [10814] Finally I can solve the problem ....

this git from https://github.com/YDLIDAR/ydlidar_ro...

launch file lidar_view.launch is support G2A when you copy parameter in X2L.launch and paste in lunch.lunch and run lunch_view.lunch it'WORK!!!!! EUREKA!!!!!

for more parameter info please read: https://github.com/YDLIDAR/ydlidar_ro...

I have an X4 Lidar from the same folks and was trying to use it on a Virtual Machine. I ended up not solving all the issues and simply using a USB drive with Ubuntu 16.04 installed to run my computer off of. This worked after making the serial port executable, adding my user to the DIALOUT group, and restarting.

find the serial port your Lidar is at and change perms chmod 666 /dev/ttyS0

Make sure your user is part of dialout group sudo adduser YOURUSER dialout

On the VM, my theory is when the software passes the serial port on to the guest machine, it doesn't give all the info. I had to change the initenv.sh script to get it to make an alias for the serial port with the incomplete info. Even then I still never got it working on the VM. If anyone does let me know!