Create Autonomy on Tegra TK1
I am having trouble getting this to install. Latest rosdep is installed. Latest python-catkin-tools is installed. RosLaunch confirmed working
The first alarm bell is when I try to run catkin build and install space comes back as "missing":
ubuntu@tegra-ubuntu:~/create_ws$ catkin build
-----------------------------------------------------------
Profile: default
Extending: [env] /opt/ros/indigo
Workspace: /home/ubuntu/create_ws
Source Space: [exists] /home/ubuntu/create_ws/src
Build Space: [exists] /home/ubuntu/create_ws/build
Devel Space: [exists] /home/ubuntu/create_ws/devel
Install Space: [missing] /home/ubuntu/create_ws/install
DESTDIR: None
-----------------------------------------------------------
Isolate Develspaces: False
Install Packages: False
Isolate Installs: False
-----------------------------------------------------------
Additional CMake Args: None
Additional Make Args: None
Additional catkin Make Args: None
Internal Make Job Server: True
-----------------------------------------------------------
Whitelisted Packages: None
Blacklisted Packages: None
-----------------------------------------------------------
Workspace configuration appears valid.
-----------------------------------------------------------
[build] Runtime: 0.0 seconds
No packages were found in the source space '/home/ubuntu/create_ws/src'
Then when I try to run it, I get an error about "create_2.launch not being a launch file".
ubuntu@tegra-ubuntu:~/create_ws$ roslaunch ca_driver create_2.launch
[create_2.launch] is neither a launch file in package [ca_driver] nor is [ca_driver] a launch file name
The traceback for the exception was written to the log file
And now catkin spaces don't like building properly.
I poked through my .bashrc and didn't see anything odd. Does your package use any code that is dependent on x86/AMD CPUs, or that wouldn't play nice on an ARM CPU?
The more important error here seems to be
No packages were found in the source space '/home/ubuntu/create_ws/src'Yeah, I was tired when I was trouble shooting, and caught that this morning. I was in the wrong directory when I cloned from Github. But I reinstalled it (build went fine), and roslaunch still isn't recognizing it as a launch-able file.
Now that the package built, have you sourced the workspace with
source devel/setup.bash?I am not aware of anything specific to the type of CPU, although to date it has only been tested with x86. I have plans to try running the driver on am ARM processor by the end of this week.
Yeah, it was
source devel/setup.bash. Could've sworn that I did that, guess not. But I can now confirm that it works on 700 series and 800 series RoombasAwesome, thanks for investigating!