ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

Tutorials / Using the SpaceNav Node doesn't work.

asked 2015-07-24 19:06:07 -0500

John Nagle gravatar image


Ubuntu 14.04 LTS 64 bit, ROS Jade.

First, installed the suggested Ubuntu libraries with Ubuntu software install:

libspnav-dev (0.2.2-1ubuntu, automatic)
ros-jade-spacenav-node (1.10.1-0trusty2015052509793-+0000)
spacenavd (0.5-1)

Then, per the tutorial:

rosdep install spacenav_node
#All required rosdeps installed successfully

Then, again per the tutorial:

rosmake spacenav_node
[ rosmake ] rosmake starting...                                                 
[ rosmake ] Packages requested are: ['spacenav_node']                           
[ rosmake ] Logging to directory /home/john/.ros/rosmake/rosmake_output-20150724-164251
[ rosmake ] Expanded args ['spacenav_node'] to:
[rosmake-0] Starting >>> catkin [ make ]                                        
[rosmake-0] Finished <<< catkin ROS_NOBUILD in package catkin
No Makefile in package catkin
[rosmake-0] Starting >>> genmsg [ make ]                                        
[rosmake-0] Finished <<< genmsg ROS_NOBUILD in package genmsg
 No Makefile in package genmsg
[rosmake-0] Starting >>> genlisp [ make ]                                       
[rosmake-0] Finished <<< genlisp ROS_NOBUILD in package genlisp
No Makefile in package genlisp
[rosmake-0] Starting >>> genpy [ make ]                                         
[rosmake-2] Starting >>> gencpp [ make ]                                        
[rosmake-0] Finished <<< genpy ROS_NOBUILD in package genpy
No Makefile in package genpy
[rosmake-3] Starting >>> geneus [ make ]                                        
[rosmake-0] Starting >>> cpp_common [ make ]                                    
[rosmake-1] Starting >>> cmake_modules [ make ]                                 
[rosmake-2] Finished <<< gencpp ROS_NOBUILD in package gencpp
No Makefile in package gencpp
[rosmake-3] Finished <<< geneus ROS_NOBUILD in package geneus
No Makefile in package geneus
[rosmake-1] Finished <<< cmake_modules ROS_NOBUILD in package cmake_modules
No Makefile in package cmake_modules
[rosmake-3] Starting >>> roslang [ make ]                                       
[rosmake-0] Finished <<< cpp_common ROS_NOBUILD in package cpp_common
 No Makefile in package cpp_common
[rosmake-1] Starting >>> message_generation [ make ]                            
[rosmake-2] Starting >>> rostime [ make ]                                       
[rosmake-0] Starting >>> rospack [ make ]                                       
[rosmake-2] Finished <<< rostime ROS_NOBUILD in package rostime
No Makefile in package rostime
[rosmake-3] Finished <<< roslang ROS_NOBUILD in package roslang
No Makefile in package roslang
[rosmake-2] Starting >>> roscpp_traits [ make ]                                 
[rosmake-3] Starting >>> xmlrpcpp [ make ]                                      
[rosmake-1] Finished <<< message_generation ROS_NOBUILD in package message_generation
No Makefile in package message_generation
[rosmake-0] Finished <<< rospack ROS_NOBUILD in package rospack
No Makefile in package rospack
[rosmake-0] Starting >>> roslib [ make ]                                        
[rosmake-3] Finished <<< xmlrpcpp ROS_NOBUILD in package xmlrpcpp
No Makefile in package xmlrpcpp
[rosmake-2] Finished <<< roscpp_traits ROS_NOBUILD in package roscpp_traits
No Makefile in package roscpp_traits
[rosmake-2] Starting >>> roscpp_serialization [ make ]                          
[rosmake-0] Finished <<< roslib ROS_NOBUILD in package roslib
No Makefile in package roslib
[rosmake-0] Starting >>> rosunit [ make ]                                       
[rosmake-0] Finished <<< rosunit ROS_NOBUILD in package rosunit
No Makefile in package rosunit
[rosmake-2] Finished <<< roscpp_serialization ROS_NOBUILD in package roscpp_serialization
No Makefile in package roscpp_serialization
[rosmake-2] Starting >>> message_runtime [ make ]                               
[rosmake-2] Finished <<< message_runtime ROS_NOBUILD in package message_runtime]
No Makefile in package message_runtime
[rosmake-2] Starting >>> std_msgs [ make ]                                      
[rosmake-2] Finished <<< std_msgs ROS_NOBUILD in package std_msgs
No Makefile in package std_msgs
[rosmake-2] Starting >>> geometry_msgs [ make ]                                 
[rosmake-0] Starting >>> rosgraph_msgs [ make ]                                 
[rosmake-3] Starting >>> rosbuild [ make ]                                      
[rosmake-2] Finished <<< geometry_msgs ROS_NOBUILD in package geometry_msgs
No Makefile in package geometry_msgs
[rosmake-0] Finished <<< rosgraph_msgs ROS_NOBUILD in package rosgraph_msgs
No Makefile in package rosgraph_msgs
[rosmake-2] Starting >>> sensor_msgs [ make ]                                   
[rosmake-3] Finished <<< rosbuild ROS_NOBUILD in package rosbuild
No Makefile in package rosbuild
[rosmake-3] Starting >>> rosconsole [ make ]                                    
[rosmake-2] Finished <<< sensor_msgs ROS_NOBUILD in package sensor_msgs
No Makefile in package sensor_msgs
[rosmake-3] Finished <<< rosconsole ROS_NOBUILD in package rosconsole
No Makefile in package rosconsole
[rosmake-3] Starting >>> roscpp [ make ]                                        
[rosmake-3] Finished <<< roscpp ROS_NOBUILD in package roscpp
No Makefile in package roscpp
[rosmake-3] Starting >>> spacenav_node [ make ]                                 
[rosmake-3] Finished <<< spacenav_node ROS_NOBUILD in package spacenav_node
No Makefile in package spacenav_node
[ rosmake ] Results:                                                            
[ rosmake ] Built ...
edit retag flag offensive close merge delete


I've ticketed the out-of-date tutorials on the ros-drivers/joystick_drivers issue tracker. It would be really nice if you could update them (or at least the installation section(s)) with what worked for you.

gvdhoorn gravatar image gvdhoorn  ( 2015-07-25 02:13:10 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2015-07-25 02:03:36 -0500

gvdhoorn gravatar image

updated 2015-07-25 02:05:02 -0500

tl;dr: yes, that tutorial is a bit outdated.

In general: if you can install ROS package using sudo apt-get ros-.. (or using synaptic, the Ubuntu Software Center or any other package manager) you don't need to build it. So

sudo apt-get install ros-jade-spacenav-node

should have installed the spacenav_node package itself, and should have taken care of all its dependencies.


roscd spacenav/spacenav_svn/spacenavd
roscd: No such package/stack 'spacenav/spacenav_svn/spacenavd'

No such package.

roscd spacenav
roscd: No such package/stack 'spacenav'

is to be expected: a debian pkg doesn't install any sources, and the Jade packages follow the Catkin pkg layout rules (which means the node will not be where you'd expect it based on the tutorial).

You should though be able to rosrun spacenav_node spacenav_node after having installed the package and sourced /opt/ros/jade/setup.bash.

Note also that the spacenav_node package provides a couple of launch files that you can use with roslaunch, instead of starting it with rosrun.

PS: re: rosbuild doesn't seem to have done anything: as spacenav_node is a catkin package, that is to be expected as well (but again: no need to try and build a pkg installed from debians).

edit flag offensive delete link more


That's very helpful, and I now have the 3D mouse talking to ROS. The Ubuntu install apparently installs the device driver as well, and that's always running. It doesn't need to be started.

John Nagle gravatar image John Nagle  ( 2015-07-25 14:31:14 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2015-07-24 19:06:07 -0500

Seen: 415 times

Last updated: Jul 25 '15