Support for Ubuntu 18.04 #63

panshuyrr · 2017-08-18T15:47:43Z

I am working on a project using ROS and Fetch robot - including both working with the real robot as well as the simulation environment.

I am going to install Ubuntu in a new computer. Can I confirm with you whether all the features are fully supported in Ubuntu 16.04.3 LTS? Or Ubuntu 14.04 is the only choice for my new computer?

Thank you very much.

hzyjerry · 2018-01-29T23:50:33Z

Hi, I have the same issue. Wondering if there's an updated answer to this at the moment?

Thanks

rctoris · 2018-01-29T23:56:05Z

Currently the Fetch is only supported on Ubuntu 14.04. We realize we are nearing the end of support for Ubuntu 14.04 and have started initial investigations and plans for upgrading the research robots to a further version of Ubuntu. At this time we don't have an estimate of when this work will be complete but will update the community as we have additional information.

DanielTakeshi · 2018-05-02T16:06:53Z

@rctoris Hi, just wanted to kindly ask if there were any plans to upgrade to Ubuntu 16.04. Thanks!

rctoris · 2018-05-02T16:24:39Z

Our current plan is to start work this summer to jump directly to Ubuntu 18.04. At this time we don't have an estimated completion date but will provide updates as we have them.

moriarty · 2018-07-10T02:20:59Z

Just as an update: @rctoris mentioned “this summer” ... some preliminary work has started on this.

It was possible to upgrade to 18.04 and Melodic, not all dependencies were available in Melodic, so some were cloned into a catchin workspace, patched and built from source.

There are some issues which we’ll work out before officially releasing... e.g. the onboard bluetooth: required for the ps3joypad and latest kernel don’t get along.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764645

But, Fetch was running Melodic, moving & MoveIt! Running today.

I just wanted to update this thread.

DanielTakeshi · 2018-07-10T02:29:29Z

@moriarty Thank you! It would be fantastic to have it upgraded to 18.04, and we would upgrade our software in a heartbeat.

moriarty · 2018-07-10T02:49:36Z

For anyone with a new laptop running 16.04 (myself personal laptop included) it is possible to clone the repositories and build them with Kinetic in a catkin workspace.

This was covered in another issue. #56, Specifically three comments.

A few changes were required but they were straight forward from the compile errors to fix.

C++11 flags were needed in a few places: #56 (comment)

build errors were fixed... on Oct 2016: #56 (comment)
Note: they might be broken again if you take master branches due to some upstream changes. I believe a tf2 back port added a c++11 requirement again.

And @pholthau recently said that running 16.04 locally & connecting to a 14.04 robot was working: #56 (comment)

But the current focus is on 18.04

moriarty · 2018-07-18T18:35:17Z

Progress Report:
I've opened a PR for Navigation: ros-planning/navigation#755

ros-planning/navigation#749 (comment) which once merged we will get a melodic release for ROS navigation, one of our dependencies ✔️
https://github.com/ros-planning/navigation/milestone/4

Once that is released some of our smaller dependencies are also ready but not released.

The PR to Navigation breaks fetch_depth_layer but I have changes ready to port that to tf2.

The PS3Joy pad is a weird. But from @chadrockey & @velveteenrobot & @cjds seemed to know that shaking the joypad (to keep the accelerometer publishing) was a sort-of work around... And that I need to tune some parameters as a proper work around.

warp1337 · 2018-08-09T16:55:46Z

Hi everyone!

first things first ... hi Patrick @pholthau I knew our paths would cross at some point ... again ... :D

However, I just built the packages required for the navigation demo (Gazebo7) from source on 16.04. Seems to work as @moriarty pointed out earlier.

My incentive was pretty much that I just wanted to have a look at the "Fetch stack", thus no hardware involved.

I believe that's also the case for many other ppl who are "still" on 16.04 and therefore on Kinetic. From my perspective it would be great to have "kinetic-experimental" branches and some docs. The docs should clearly state that Kinetic is not supported in production environments but if you want to try some toy examples and get a feeling for the Fetch stuff ... Well why not?

I am willing to document and contribute, if desired.

rctoris · 2018-08-15T16:22:42Z

I think having some support for kinetic in simulation could be worth having if people would like to contribute. For hardware support, at this point it makes the most sense to jump to melodic.

nickswalker · 2018-10-01T22:15:31Z

Is there a preliminary release of fetch-drivers available for folks who want to try Melodic on their robots?

moriarty · 2018-10-30T22:23:33Z

Sorry for the delay, no fetch-drivers and the new upstart->systemd scripts are two remaining packages which need to be made available, if one were to try a DIY upgrade: which we do not recommend or support.

But we will be testing the packages and upgrade process before the official "upgrade" process is announced and made generally available.

We're working towards making the upgrade process as seamless, stable and well supported for all customers.

This is a new package providing the "fetch_drivers" which was previously built internally and distributed as a binary only debian package. We will officially announce when the upgrade from Indigo->Melodic is ready. 18.04 and ROS Melodic on the Fetch Research Platforms is still being tested. The process isn't straight foward as there are calibration files which you will want to back-up before the upgrade. This `fetch_drivers` package also won't start like it use to because of the change from `upstart` to `systemd`. That requires `fetch_system_config` which will be open sourced soon. This `fetch_binary_drivers` package is part of a plan to distribute updates and upgrades to Fetch Research Platform customers faster in the future. This relates to ZebraDevs/fetch_ros#63 1. An officiall announcement will be made when everything is ready. 2. We will update and document the process on: https://docs.fetchrobotics.com/ 3. We will also announce via our mailing list, ros discourse and post on: https://opensource.fetchrobotics.com/

moriarty · 2019-02-13T23:04:28Z

ros/rosdistro#20301

pholthaus · 2019-02-14T09:45:44Z

Is there any documented way of upgrading the robot itself?

erelson · 2019-02-14T17:18:06Z

@pholthau that documentation is ready in a PR, but pending testing once the 18.04 debians are actually created. Soon :)

If you want to take a look (feedback/questions very welcome), see the PR here: fetchrobotics/docs#60

moriarty · 2019-03-12T06:00:51Z

@pholthau fetchrobotics/docs#60 has been merged.

http://docs.fetchrobotics.com/indigo_to_melodic.html

pholthaus · 2019-03-12T16:48:39Z

@moriarty thanks a lot for this. Will try it out as soon as I can get my hands on the robot again!

moriarty · 2019-03-14T20:47:50Z

Warning: 18.04 has been released and works on the physical robot...
But we're having trouble identifying and fixing some bugs with the robot in Gazebo9.

These issues are being tracked here:
ZebraDevs/fetch_gazebo#37

ZebraDevs/fetch_gazebo#36 (comment) from @nickswalker

Yes, navigation has been working fine on the real robot

We'll email everyone who owns a Fetch and announce the 18.04 upgrade after we've solved the Gazebo9 issues.

moriarty · 2019-03-31T06:23:47Z

TL;DR:

We've released fetch_ros v0.8.0 with support for 18.04 on Fetch Robots, the process is currently a DIY for early adopters.
@erelson has published http://docs.fetchrobotics.com/indigo_to_melodic.html
The source code for the site is here: https://github.com/fetchrobotics/docs/ if there are any steps which are unclear please open an issue.
As early adopters move to 18.04 we'll fix any new issues and release patches
I'll prepare v0.8.1 as soon as I have more time to test [IKFast Plugin] Regenerate fetch_ikfast_plugin #107 on hardware

Gazebo9 Issues

There are still some issues with Gazebo9. But it is much better than it first did and we couldn't be blocked by these issues any longer. The main new changes to make things work:

I added "castor wheels" to the gazebo model: fetch_gazebo: add casters to fetch.gazebo.xacro fetch_gazebo#49
@RDaneelOlivav "improved the wheel friction values": Improved pick place frictions fetch_gazebo#59

I've bloomed "0.9.0" of fetch_gazebo as it now is, so that at least the ros build farm would test pull requests. We'll still actively work on improving the situation.

If Gazebo9 issues are a blocker

For simulation only, I've released fetch_ros into 16.04 and Kinetic - this was not originally planned, and we won't support 16.04 and Kinetic on the real robot because we haven't tested the drivers, hardware and firmware on 16.04...

I needed to do a lot of back and forth comparing while looking into the Gazebo9 vs Gazebo7 for debugging an issue. The version of fetch_ros released into kinetic is the same version released into indigo. I did all the testing on an 18.04 machine, using a 16.04 docker image, from this Dockerfile: ZebraDevs/fetch_gazebo#46

I hope, that by releasing simulation only support for 16.04 would help end users, and move everyone forward off of 14.04 which is about to reach EOL towards 18.04

ghost · 2019-04-05T21:55:21Z

Just tried upgrading to 18.04.
The gripper was working fine before the upgrade, but after the upgrade,

ping 10.42.42.43

fails and arp -a yields

? (10.42.42.43) at <incomplete> on eth1

Since the step for pinging 10.42.42.43 was in the update procedure I suspected that this might be an issue related to the upgrade.
I'd appreciate any ideas on fixing the issue.

erelson · 2019-04-06T20:22:47Z

@ryom314 Sorry to hear about the issue. If you can open a support ticket at support.fetchrobotics.com, we can get started troubleshooting the issue. Thanks!

erelson · 2019-05-10T15:49:17Z

@ryom314 I don't believe I've seen any support ticket from you, but I also do not know which robot/research group/university you are working with. Were you able to resolve your issue? Thanks!

ghost · 2019-05-10T23:24:19Z

Thanks for asking. I'm contacting Mark Onaga. A downgrade to 14.04 didn't resolve the issue so it probably wasn't an OS compatibility issue.

…

On Fri, May 10, 2019, 8:49 AM Eric Relson ***@***.***> wrote: @ryom314 <https://github.com/ryom314> I don't believe I've seen any support ticket from you, but I also do not know which robot/research group/university you are working with. Were you able to resolve your issue? Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#63 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALQXLYE6VMOQQY2FSUOKMPTPUWKQBANCNFSM4DXO5MMA> .

nickswalker · 2019-05-31T16:53:44Z

I've just verified that our gripper is unresponsive after the upgrade as well. We'll get a support ticket in soon!

sergeant-wizard · 2019-05-31T18:48:16Z

FYI we ended up replacing the MCB for the gripper

sergeant-wizard · 2019-05-31T20:11:37Z

(Don't know if the issue was triggered by the update to 18.04 or not.)

erelson · 2019-06-01T00:08:11Z

Hi @nickswalker, We'll keep an eye out for the support ticket. Thanks!

@ryom314 @sergeant-wizard glad you guys are back in action. We were able to use your problem board to identify a workaround, should the same thing happen going forward.

moriarty · 2019-06-13T16:40:47Z

Just to update the public, the issue from @nickswalker at University of Washington was fixed without replacing the MCB.

@erelson asked in the support ticket:

Could you report back with the output of systemctl status robot for your Fetch? A good output will include green text indicateing the service is enabled and running.

And then to run:

sudo service roscore stop
sudo service roscore start
sudo service robot start

moriarty · 2019-06-13T16:44:59Z

@erelson should we close this ticket?

I think we can deal with any of the future items under a new issue.

PS3 Joystick
Gazebo behaviours
any other things that come up

moriarty · 2019-06-13T16:48:11Z

Confirmed with @erelson over Slack.

I'm closing this. Please see the upgrade guide:

http://docs.fetchrobotics.com/indigo_to_melodic.html

And open any new issues, or support tickets if you have any problems.

moriarty changed the title ~~Support of Ubuntu 16.04~~ Support of Ubuntu 18.04 Jul 18, 2018

moriarty mentioned this issue Jul 18, 2018

[fetch_depth_layer][tf2] ros-planning/navigation#755 #81

Merged

moriarty changed the title ~~Support of Ubuntu 18.04~~ Support for Ubuntu 18.04 Jul 19, 2018

moriarty mentioned this issue Jul 27, 2018

Support for ROS Kinetic #56

Closed

moriarty added this to the 18.04 & Melodic milestone Jul 27, 2018

This was referenced Jan 27, 2019

Release for -Kinetic- (missed) -> Melodic ZebraDevs/fetch_gazebo#15

Closed

Select teleop part by rosparam for indigo #101

Merged

This was referenced Feb 2, 2019

[fetch_binary_drivers] new [fetch_drivers] package ZebraDevs/fetch_robots#27

Merged

Melodic Release Request ros-perception/graft#29

Closed

moriarty mentioned this issue Feb 27, 2019

TODO: switch to official SICK drivers ZebraDevs/fetch_robots#35

Closed

moriarty closed this as completed Jun 13, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support for Ubuntu 18.04 #63

Support for Ubuntu 18.04 #63

panshuyrr commented Aug 18, 2017

hzyjerry commented Jan 29, 2018

rctoris commented Jan 29, 2018

DanielTakeshi commented May 2, 2018

rctoris commented May 2, 2018

moriarty commented Jul 10, 2018 •

edited

Loading

DanielTakeshi commented Jul 10, 2018

moriarty commented Jul 10, 2018

moriarty commented Jul 18, 2018

warp1337 commented Aug 9, 2018

rctoris commented Aug 15, 2018

nickswalker commented Oct 1, 2018

moriarty commented Oct 30, 2018

moriarty commented Feb 13, 2019

pholthaus commented Feb 14, 2019

erelson commented Feb 14, 2019

moriarty commented Mar 12, 2019

pholthaus commented Mar 12, 2019

moriarty commented Mar 14, 2019

moriarty commented Mar 31, 2019

ghost commented Apr 5, 2019 •

edited by ghost

Loading

erelson commented Apr 6, 2019

erelson commented May 10, 2019

ghost commented May 10, 2019 via email

nickswalker commented May 31, 2019

sergeant-wizard commented May 31, 2019

sergeant-wizard commented May 31, 2019

erelson commented Jun 1, 2019

moriarty commented Jun 13, 2019

moriarty commented Jun 13, 2019

moriarty commented Jun 13, 2019

Support for Ubuntu 18.04 #63

Support for Ubuntu 18.04 #63

Comments

panshuyrr commented Aug 18, 2017

hzyjerry commented Jan 29, 2018

rctoris commented Jan 29, 2018

DanielTakeshi commented May 2, 2018

rctoris commented May 2, 2018

moriarty commented Jul 10, 2018 • edited Loading

DanielTakeshi commented Jul 10, 2018

moriarty commented Jul 10, 2018

moriarty commented Jul 18, 2018

warp1337 commented Aug 9, 2018

rctoris commented Aug 15, 2018

nickswalker commented Oct 1, 2018

moriarty commented Oct 30, 2018

moriarty commented Feb 13, 2019

pholthaus commented Feb 14, 2019

erelson commented Feb 14, 2019

moriarty commented Mar 12, 2019

pholthaus commented Mar 12, 2019

moriarty commented Mar 14, 2019

moriarty commented Mar 31, 2019

TL;DR:

Gazebo9 Issues

If Gazebo9 issues are a blocker

ghost commented Apr 5, 2019 • edited by ghost Loading

erelson commented Apr 6, 2019

erelson commented May 10, 2019

ghost commented May 10, 2019 via email

nickswalker commented May 31, 2019

sergeant-wizard commented May 31, 2019

sergeant-wizard commented May 31, 2019

erelson commented Jun 1, 2019

moriarty commented Jun 13, 2019

moriarty commented Jun 13, 2019

moriarty commented Jun 13, 2019

moriarty commented Jul 10, 2018 •

edited

Loading

ghost commented Apr 5, 2019 •

edited by ghost

Loading