You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The leapmotion/data topic is throwing an error
ERROR: Cannot load message class for [leap_motion/leapros]. Are your messages built?
Hi sir, I've tried to reinstall leapmotion and it ROS driver. But I still recieve the same error. Can you please kindly take a look at the following scrits that I used? Much appreciated. Thank you so much for you constant support.
ROS indigo in Ubuntu 14.04 machine
1.Install Leapmotion
V2 Tracking Downloads
https://developer.leapmotion.com/sdk/v2
I install it in the directory of LeapDeveloperKit_2.3.1+31549_linux, which is /home/ysu66/Downloads/LeapDeveloperKit_2.3.1+31549_linux.
After installation, I get the following info in the terminal.
Check Leap Motion daemon with:
service leapd status
Open the Leap Motion GUI with:
LeapControlPanel
2.Install leapmotion driver(I follow this site http://wiki.ros.org/leap_motion)
ysu66@mech1331:~$ cd ~/catkin_ws/src
ysu66@mech1331:~$ git clone https://github.com/qqfly/leap_motion.git
ysu66@mech1331:~$ cd ~/catkin_ws && catkin_make
3.Start the Leap Motion driver
ysu66@mech1331:~$ leapd
[Critical] Unhandled exception: boost::filesystem::status: Permission denied: "/var//.Leap Motion/config.json"
[Critical] Secure WebSocket server failed to start
[Critical] WebSocket server failed to start
[Critical] Have you tried running as root/Administrator?
ysu66@mech1331:~$
Then I run the follwoing
ysu66@mech1331:~$ sudo leapd
[sudo] password for ysu66:
[Critical] Secure WebSocket server failed to start
[Critical] Have you tried running as root/Administrator?
[Critical] WebSocket server failed to start
[Info] Leap Motion Controller detected: LP59556685952
[Info] Firmware is up to date.
It is not seting up properly, I run sudo service leapd stop and sudo leapd. Then it works well.
ysu66@mech1331:~$ sudo service leapd stop
leapd stop/waiting
ysu66@mech1331:~$ sudo leapd
[Info] WebSocket server started
[Info] Secure WebSocket server started
[Info] Leap Motion Controller detected: LP59556685952
[Info] Firmware is up to date.
3.sudo LeapControlPanel (I can visualize my hands in the GUI)
4.Configure PYTHONPATH
ysu66@mech1331:~$ echo "export PYTHONPATH=$PYTHONPATH:$HOME/LeapSDK/lib:$HOME/LeapSDK/lib/x64" >> ~/.bashrc
ysu66@mech1331:~$ source ~/.bashrc
ysu66@mech1331:~$ gedit ~/.bashrc
The following is what it shows in the end of ~/.bashrc
source /opt/ros/indigo/setup.bash
source ~/catkin_ws/devel/setup.bash
export PYTHONPATH=/opt/ros/indigo/lib/python2.7/dist-packages:/home/ysu66/LeapSDK/lib:/home/ysu66/LeapSDK/lib/x64:/home/ysu66/LeapSDK/lib:/home/ysu66/LeapSDK/lib/x64:/home/ysu66/LeapSDK/lib:/home/ysu66/LeapSDK/lib/x64
4.rostopic echo /leapmotion/data (It throws errors)
After that, I firstly run
ysu66@mech1331:~$ source ~/catkin_ws/devel/setup.bash && roslaunch leap_motion sensor_sender.launch(another terminal)
But when run rostopic echo /leapmotion/data, I get the following error:
ysu66@mech1331:~$ rostopic echo /leapmotion/data(another terminal)
ERROR: Cannot load message class for [leap_motion/leapros]. Are your messages built?
ysu66@mech1331:~$
Also, I secondly run ysu66@mech1331:~$ source ~/catkin_ws/devel/setup.bash && rosrun leap_motion sender.py after I stop last command by CTRL+C.
ysu66@mech1331:~$ source ~/catkin_ws/devel/setup.bash && rosrun leap_motion sender.py(another terminal)
ysu66@mech1331:~$ rostopic echo /leapmotion/data(another terminal)
ERROR: Cannot load message class for [leap_motion/leapros]. Are your messages built?
ysu66@mech1331:~$
The text was updated successfully, but these errors were encountered:
The leapmotion/data topic is throwing an error
ERROR: Cannot load message class for [leap_motion/leapros]. Are your messages built?
Hi sir, I've tried to reinstall leapmotion and it ROS driver. But I still recieve the same error. Can you please kindly take a look at the following scrits that I used? Much appreciated. Thank you so much for you constant support.
The text was updated successfully, but these errors were encountered: