-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release for -Kinetic- (missed) -> Melodic #15
Comments
@davetcoleman -- i've now driven a fetch around in simulation on 16.04 -- I'll continue with actually moving the arm with moveit in the morning -- the repos listed above are what I've had to check out in source (and I have a pretty severe hack in moveit_python to handle the upstream mess that is pyassimp in 16.04) |
My current setup:
|
I have now successfully run the demo under 16.04 |
If you don't have desktop-full, you can end up with the laser not working, so we are probably missing a depend |
gazebo7 branch has been rebased on top of gazebo2/5 branches, so it can be released as 0.9.x |
I used the script suggested by @mikeferguson and after finish install, using roslaunch stockroom_bot stockroomlaunch, I got no launch error and could get the complete scenario with world, bins and the simple arm robot. Then after couple minutes, I got a "not enough memory" message and got an error in terminal window. So, I closed the session and started a new one. Then I started to get an error regarding to tf and the scenario does not show the robot any more. Then I tried other times and did continue getting the same error and no more robot model in the scenario. So, only in the first time I could get the complete scene. Any hints on this? |
FYI, robot_calibration is now in Kinetic. Also, unassigning myself from this (EDIT: I actually can't do that, don't have the requisite permissions...) |
Hello, I'm using Kinetic in Ubuntu 16.04. I followed the aforementioend installation steps. That said, when I tried to catkin build the workspace, I got the follow tf error and I didn't find a solution. Please let me know if you have any suggestion. Thanks. Errors << fetch_depth_layer:make /home/lishuai/logs/fetch_depth_layer/build.make.001.log |
@mikeferguson any updates on this? ZebraDevs/fetch_ros#52 is already merged and it would be nice to have the gazebo simulation working with Kinetic. FYI, I tried following the procedure outline by you on this issue to get things working and when I run Any idea why this might be the case? |
Because libgazebo9-dev is for 18.04 and Melodic. If you want to try on Kinect you’ll need to checkout the gazebo7 branch. We’re currently preparing to release Melodic ASAP with the simulation environment for “FetchIt!” https://discourse.ros.org/t/announcement-win-a-robot-fetchit-the-fetch-mobile-manipulation-challenge-icra-2019-competition/7569 Currently if you’re on 18.04 and Melodic, from GitHub most of the packages should work. Not all are available as debians, and it is our firmware/drivers which have been holding us back (they’re not public- just distributed as binaries) as a lot has changed and we want to have a smooth process for customers who have physical robots. Our target is the end of this month. But if you’re on 18.04 with Melodic, or checkout the gazebo7 branch most things should work. |
gazebo7 won't work because gazebo doesn't provide the ROS wrapper packages for Kinetic. gazebo8 won't work because to get At this point, your only two releases are either out of LTS or not yet ready to be released. 😕 |
Are you only trying to build the simulation? Or also run on a real robot? 14.04 & Indigo is still LTS. Until April 2019. We aren’t targeting Kinetic. Melodic will be released soon, but will work from source already. For the physical robots, you’ll need to wait a little longer for the drivers/firmware and instructions. That MoveIt! Tutorial you’ve linked to, seems to mention that building it from source will work. If you’re not working on a real robot, then building from source should work. If you’re trying to get this on a real robot, then reach out via our support. |
Please check out: |
@varunagrawal I'm going to close this issue and open new one for Melodic to avoid confusion.
There are a few warnings which we'll clean up but this should work on gazebo. We plan to release to Melodic next week, it will take a little until the next melodic sync and the debians are available. |
@moriarty thanks for being on top of this! I may have been a bit harsh with my words before but I have high expectations of you guys and really appreciate the great work you are doing. |
Just FYI -- I'm not with Fetch since end of 2017, so I'm not the guy to ping on these in the future. |
After having some issues with releasing for Melodic, I ended up doing a bunch of extra testing in Kinetic, and then decided that I should just release to Kinetic too. But, we're only supporting Fetch in Gazebo for Kinetic. The drivers, firmware and actual robot haven't been tested in Kinetic. |
Dependent repositories still to be released into Jade:
upstream blocker: Kinetic: implosion due to pyassimp bug mikeferguson/moveit_python#8)Fixes to fetch_gazebo (gazebo7 branch)
Possible improvements:
The text was updated successfully, but these errors were encountered: