[Rock-dev] [Rock-users] Problems to get ROS-Rock working in all branches (Ubuntu 12.04)
Essen von Mathias
mathias.vonessen at tut.fi
Thu Aug 28 14:39:57 CEST 2014
Hi Steffen,
> -----Original Message-----
> From: Steffen Planthaber [mailto:Steffen.Planthaber at dfki.de]
> Sent: 27. elokuuta 2014 10:44
> To: Essen von Mathias; rock-users at dfki.de; rock-dev at dfki.de
> Subject: Re: [Rock-users] Problems to get ROS-Rock working in all branches
> (Ubuntu 12.04)
>
> Hi Mathias,
> > In master, rock.ros goes now through autoproj, but ROS doesn't get
> "identified" at runtime. E.g. TRANSPORT_ROS variable remains undefined
> when calling rock-display.
> >
> > In Orocos::ROS::available?
> > defined? TRANSPORT_ROS # not defined when coming here (line
> > 4 of tools/orocos.rb/lib/orocos/ros.rb)
> >
>
> Actually, I never used rock-display to see the ros part, I tested that stuff
> using the ros tooling. Also I used an extra ruby script to get (not start) running
> task contexts and connected them there (or called publish_to_ros on the
> ports I wanted to have in ROS)
>
> It could be possible that the issue is not the bridge itself, but rock-display
> support for ros datatypes.
>
> Can you test whether publish_to_ros works? (in a script and use ross tooling
> to see the data)
>
Unfortunately publishing to ROS doesn't work for me. I get
tools/orocos.rb/lib/orocos/ros/ports.rb:14:in `publish_on_ros' uninitialized constant Orocos::TRANSPORT_ROS (NameError)
I tried to same code on stable and that worked without problems.
>
> > Installing of ROS packages with aup works, but user needs to make the
> directory /rock/ros first. Otherwise you get :
> > "ros has no VCS, but is not checked out in /opt/rock/ros". Apparently I was
> mislead by the error message. I should've read it "directory missing".
> >
> > I was wondering if this was the problem in the first place? Perhaps I
> should've just created directory rock/ros prior to installation of rock.ros.
> >
>
> I think so, but the error was my mistake but the rock/ros directory was
> never meant to be used in first place when writing rock.ros in the
> autoproj/manifest file.
>
> The ros package support may be considered late alpha phase, not more. It
> was just convenient in a project where we used the bridge, but there are
> sill some things that can be done better.
Understood. I used the bridge during last winter and I was hoping that I could use it again.
I'm willing to help if there's anything I can help with to fix the bridge in master.
In stable I just noticed that publishing of ro_ptr<Frame> doesn't work for me. Publishing of ro_ptr<Frame> makes the program to die with SIGSEGV (11). Standard data types get published ok.
BR,
Mathias
>
>
>
> Kind regards,
>
> Steffen
>
>
>
> > BR,
> > Mathias
> > ________________________________________
> > From: rock-users-bounces at dfki.de [rock-users-bounces at dfki.de] on
> behalf of Steffen Planthaber [Steffen.Planthaber at dfki.de]
> > Sent: Tuesday, August 26, 2014 15:23
> > To: rock-users at dfki.de; rock-dev at dfki.de
> > Subject: Re: [Rock-users] Problems to get ROS-Rock working in all branches
> (Ubuntu 12.04)
> >
> > Hi Mathias,
> >
> > This should be fixed now (do an autoproj update)
> >
> > There is support for catkin packages to be build by autoproj, they all
> > got selected by the -rock.ros line.
> >
> > Recently autoproj seems to check if a repo that is "none" has some code
> > in the package folder (or at least a folder). But no ros folder existed
> > and autoproj raised the error.
> >
> > I removed these packages from the default install now. Should fine now.
> >
> > You can load/build ros packages defined in
> > autoproj/remotes/rock.ros/catkin.autobuild by aup and amake (i.e. aup
> > moveit/core) or autoproj in general.
> >
> > All it does is downloading the source package and invoking catkin in the
> > main folder AUTOPROJ_CURRENT_ROOT/ros
> >
> > BUT the dependencies for installing packages there are not properly set
> > there.
> >
> >
> > Best, Steffen
> >
> >
> > Am 26.08.2014 um 13:46 schrieb Essen von Mathias:
> >> Hi Jakob,
> >>
> >> Thanks for the quick response!
> >>
> >> From: Jakob Schwendner [jakob.schwendner at dfki.de]
> >> Sent: Tuesday, August 26, 2014 14:39
> >> To: Essen von Mathias; rock-users at dfki.de; rock-dev at dfki.de
> >> Subject: RE: [Rock-users] Problems to get ROS-Rock working in all
> branches (Ubuntu 12.04)
> >>
> >> Hi Mathias,
> >>
> >>> 2. stable & next : autoproj works fine, everything compiles, but
> >> rock-display
> >>> says:
> >>>
> >>> I get (to my eyes) strange warning during autoproj:
> >>> "WARN: tools/orogen_ros from
> autoproj/remotes/rock.ros/ros.autobuild is
> >>> overridden by the definition in
> >>> autoproj/remotes/rock.core/05deprecated.autobuild"
> >>>
> >>> When running rock-display, or a Ruby file with require 'orocos' line I
> >> get:
> >>> "ROS transport is available, but I cannot load the orogen_ros library,
> >>> disabling" (comes from line 41 of ./tools/orocos.rb/lib/orocos/ros.rb).
> >>>
> >>> This got solved by adding the following to autoproj/manifest under
> >> "layout"
> >>> - tools/orogen_ros
> >> Does this mean you got the ROS bridge running in stable and next?
> Master
> >> seems to be broken. We'll look into it.
> >>
> >> Yes, stable and next work when tools/orogen_ros is added to Manifest.
> >>
> >>> p.s. is there any way or ongoing effort to get ROS Indigo to work with
> >> Rock in
> >>> Ubuntu 14.04?
> >> I don't know if anyone is currently working on getting ROS Indigo working
> (I
> >> include the rock-dev ml here).
> >> Rock master is running in 14.04, tough.
> >>
> >> I've been using master in 14.04 and it's seems to work really well. The
> reason for reverting to 12.04 is that only ROS Indigo is supported in 14.04.
> >>
> >> Cheers,
> >>
> >> Jakob
> >>
> >> BR,
> >> Mathias
> >> _______________________________________________
> >> Rock-users mailing list
> >> Rock-users at dfki.de
> >> http://www.dfki.de/mailman/cgi-bin/listinfo/rock-users
> >>
> >
> >
> > --
> > Steffen Planthaber
> > Weltraumrobotik
> >
> > Besuchsadresse der Nebengeschäftstelle:
> > DFKI GmbH
> > Robotics Innovation Center
> > Robert-Hooke-Straße 5
> > 28359 Bremen, Germany
> >
> > Postadresse der Hauptgeschäftsstelle Standort Bremen:
> > DFKI GmbH
> > Robotics Innovation Center
> > Robert-Hooke-Straße 1
> > 28359 Bremen, Germany
> >
> > Tel.: +49 421 178 45-4125
> > Zentrale: +49 421 178 45-0
> > Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
> > E-Mail: Steffen.Planthaber at dfki.de
> >
> > Weitere Informationen: http://www.dfki.de/robotik
> > -----------------------------------------------------------------------
> > Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
> > Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
> > Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
> > (Vorsitzender) Dr. Walter Olthoff
> > Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
> > Amtsgericht Kaiserslautern, HRB 2313
> > Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
> > USt-Id.Nr.: DE 148646973
> > Steuernummer: 19/673/0060/3
> > -----------------------------------------------------------------------
> >
> > _______________________________________________
> > Rock-users mailing list
> > Rock-users at dfki.de
> > http://www.dfki.de/mailman/cgi-bin/listinfo/rock-users
> > _______________________________________________
> > Rock-users mailing list
> > Rock-users at dfki.de
> > http://www.dfki.de/mailman/cgi-bin/listinfo/rock-users
> >
>
>
> --
> Steffen Planthaber
> Weltraumrobotik
>
> Besuchsadresse der Nebengeschäftstelle:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
>
> Postadresse der Hauptgeschäftsstelle Standort Bremen:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 1
> 28359 Bremen, Germany
>
> Tel.: +49 421 178 45-4125
> Zentrale: +49 421 178 45-0
> Fax: +49 421 178 45-4150 (Faxe bitte namentlich kennzeichnen)
> E-Mail: Steffen.Planthaber at dfki.de
>
> Weitere Informationen: http://www.dfki.de/robotik
> -----------------------------------------------------------------------
> Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
> Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
> Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
> (Vorsitzender) Dr. Walter Olthoff
> Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
> Amtsgericht Kaiserslautern, HRB 2313
> Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
> USt-Id.Nr.: DE 148646973
> Steuernummer: 19/673/0060/3
> -----------------------------------------------------------------------
More information about the Rock-dev
mailing list