Ask Your Question
0

Error when installing velodyne lidar on ROS

asked 2019-10-08 11:05:28 -0500

updated 2019-10-08 11:43:27 -0500

gvdhoorn gravatar image

Hi,

I am freshly new to ROS, so forgive if I ask inappropriate question and also my English.

I am running a Virtual Machine with Ubuntu, ROS and Ubiquity Robotic's workstation software. Below is the link to where I downloaded the image: https://downloads.ubiquityrobotics.co...

After checking the version of my ROS, which is 'kinetic', I typed following command line:

sudo apt-get install ros-kinetic-velodyne

It asked me this:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following additional packages will be installed:
  libpcap0.8-dev ros-kinetic-velodyne-driver ros-kinetic-velodyne-laserscan
  ros-kinetic-velodyne-msgs ros-kinetic-velodyne-pointcloud
The following NEW packages will be installed:
  libpcap0.8-dev ros-kinetic-velodyne ros-kinetic-velodyne-driver
  ros-kinetic-velodyne-laserscan ros-kinetic-velodyne-msgs
  ros-kinetic-velodyne-pointcloud
0 upgraded, 6 newly installed, 0 to remove and 711 not upgraded.
Need to get 666 kB/878 kB of archives.
After this operation, 4,204 kB of additional disk space will be used.
Do you want to continue? [Y/n] ^C

So I put in "Y" and this error happened

Err:1 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-velodyne-msgs amd64 1.3.0-0xenial-20171110-140103-0800
  404  Not Found [IP: 64.50.233.100 80]
Err:2 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-velodyne-driver amd64 1.3.0-0xenial-20171117-060453-0800
  404  Not Found [IP: 64.50.233.100 80]
Err:3 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-velodyne-laserscan amd64 1.3.0-0xenial-20171117-060854-0800
  404  Not Found [IP: 64.50.233.100 80]
Err:4 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-velodyne-pointcloud amd64 1.3.0-0xenial-20171117-061317-0800
  404  Not Found [IP: 64.50.233.100 80]
Err:5 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-velodyne amd64 1.3.0-0xenial-20171117-091257-0800
  404  Not Found [IP: 64.50.233.100 80]
E: Failed to fetch http://packages.ros.org/ros/ubuntu/pool/main/r/ros-kinetic-velodyne-msgs/ros-kinetic-velodyne-msgs_1.3.0-0xenial-20171110-140103-0800_amd64.deb  404  Not Found [IP: 64.50.233.100 80]

E: Failed to fetch http://packages.ros.org/ros/ubuntu/pool/main/r/ros-kinetic-velodyne-driver/ros-kinetic-velodyne-driver_1.3.0-0xenial-20171117-060453-0800_amd64.deb  404  Not Found [IP: 64.50.233.100 80]

E: Failed to fetch http://packages.ros.org/ros/ubuntu/pool/main/r/ros-kinetic-velodyne-laserscan/ros-kinetic-velodyne-laserscan_1.3.0-0xenial-20171117-060854-0800_amd64.deb  404  Not Found [IP: 64.50.233.100 80]

E: Failed to fetch http://packages.ros.org/ros/ubuntu/pool/main/r/ros-kinetic-velodyne-pointcloud/ros-kinetic-velodyne-pointcloud_1.3.0-0xenial-20171117-061317-0800_amd64.deb  404  Not Found [IP: 64.50.233.100 80]

E: Failed to fetch http://packages.ros.org/ros/ubuntu/pool/main/r/ros-kinetic-velodyne/ros-kinetic-velodyne_1.3.0-0xenial-20171117-091257-0800_amd64.deb  404  Not Found [IP: 64.50.233.100 80]

E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Seems like the link is invalid. Is there any solution for this?

Thanks in advance! If there is any info I need to provide to fix this problem, please let me. All recommendation, solution or comment is welcomed.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2019-10-08 11:44:20 -0500

gvdhoorn gravatar image

updated 2019-10-08 12:42:29 -0500

I am running a Virtual Machine with Ubuntu, ROS and Ubiquity Robotic's workstation software. Below is the link to where I downloaded the image: https://downloads.ubiquityrobotics.co...

It is very likely your VM image is old and uses the wrong repository key or has outdated package indices:

Err:4 http://packages.ros.org/ros/ubuntu xenial/main amd64 ros-kinetic-velodyne-pointcloud amd64 1.3.0-0xenial-20171117-061317-0800

Notice the 20171117-061317-0800 timestamp. That would be November the 17th 2017.

First try whether a sudo apt update fixes things.

If not, also check #q325039.

edit flag offensive delete link more

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

Stats

Asked: 2019-10-08 11:05:28 -0500

Seen: 18 times

Last updated: Oct 08