Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

2015-09-15 Thread Pierre Letier 
Hello, 

Having still problem with the ROCK-ROS bridge on a new installation, I send you 
the description of my installation and the trace when starting the rock-display 
command.

OS: Ubuntu 14.04
ROS: Indigo (Full Desktop)
ROCK: install from the bootstrap.sh downloaded on the ROCK website

After installation, rock-display is working fine.

ROCK-ROS Bridge: 
1. I create the rock-ros folder in the manifest folder, where I put the 
ROCK-ROS bridge package (taken from a previous install in the .remote folder)
2. I copy orogen_ros (needed as still request by the package) and 
RTT_transports in the tools folder (also take from previous installation)
3. amake
4. acd orocos.rb
5. rake clean
6. rake
7. autoproj envsh
8. source env.sh

Then, after starting roscore on the local machine, when I run the rock-display 
command, I receive the trace in attachment.

Do you have any suggestion ?

Best Regards, 

Pierre


- Original Message -
From: "Sylvain Joyeux" <bir.sylv...@gmail.com>
To: "Sascha Arnold" <sascha.arn...@dfki.de>
Cc: rock-dev@dfki.de
Sent: Friday, 11 September, 2015 4:08:17 PM
Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

On Wed, Aug 26, 2015 at 10:56 AM, Sascha Arnold <sascha.arn...@dfki.de> wrote:
> I'm not familiar with the rock ros integration.
> But my guess is that tools/rtt_transports/ros and tools/orogen_ros are
> obsolete, since they are part of orogen and orocos.rb now.

tools/orogen_ros was never really needed (and is part of orogen now).

tools/rtt_transports/ros is the critical one. Nothing is going to work
if it's not installed.

Sylvain
___
Rock-dev mailing list
Rock-dev@dfki.de
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev
OroGen[WARN]: could not load plugin /home/haco/icarus/rock/stable/tools/orogen_ros/lib/orogen_ros/plugin.rb: uninitialized constant OroGen::Gen::RTT_CPP::Project
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/gen/imports.rb:178:in `'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/gen/imports.rb:3:in `'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/gen/imports.rb:2:in `'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/gen/imports.rb:1:in `'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen_ros/lib/orogen_ros/plugin.rb:2:in `'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/plugins.rb:63:in `block in load_orogen_plugins'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/plugins.rb:17:in `block in each_orogen_plugin_file'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/plugins.rb:3:in `each'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/plugins.rb:3:in `each_orogen_plugin_path'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/plugins.rb:15:in `each_orogen_plugin_file'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen/plugins.rb:60:in `load_orogen_plugins'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orogen/lib/orogen.rb:51:in `'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orocos.rb/lib/orocos.rb:2:in `'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /home/haco/icarus/rock/stable/tools/orocos.rb/lib/orocos/async.rb:1:in `'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /home/haco/icarus/rock/stable/gui/vizkit/lib/vizkit.rb:3:in `'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:53:in `require'
OroGen[WARN]:   /home/haco/icarus/rock/stable/gui/vizkit/bin/rock-display:3:in `'
Bundles[INFO]: Active bundles: rock
/usr/lib/ruby/2.0.0/xmlrpc/client.rb:506:in `do_rpc': Wrong size. Was 1513, should be 265 (RuntimeError)
	from /usr/lib/ruby/2.0.0/xmlrpc/client.rb:281:in `call2'
	from /usr/lib/ruby/2.0.0/xmlrpc/client.rb:262:in `call'
	from /home/haco/icarus/rock/stable/tools/orocos.rb/lib/orocos/ros/rpc.rb:52:in `call'
	from /home/haco/icarus/rock/stable/tools/orocos.rb/lib/orocos/ros/rpc.rb:68:in `system_s

Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

2015-09-11 Thread Sylvain Joyeux 
On Wed, Aug 26, 2015 at 10:56 AM, Sascha Arnold  wrote:
> I'm not familiar with the rock ros integration.
> But my guess is that tools/rtt_transports/ros and tools/orogen_ros are
> obsolete, since they are part of orogen and orocos.rb now.

tools/orogen_ros was never really needed (and is part of orogen now).

tools/rtt_transports/ros is the critical one. Nothing is going to work
if it's not installed.

Sylvain
___
Rock-dev mailing list
Rock-dev@dfki.de
http://www.dfki.de/mailman/cgi-bin/listinfo/rock-dev

Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

2015-08-26 Thread Pierre Letier 
Dear Steffen, 

This last step makes it working. I have still an issue with rock-display that 
crashes after this procedure (not before), although it shows the ROS 
connection

So, the current working procedure is (waiting maybe for a easier solution):

1. install stable branch
2. paste tools/orogen_ros and tools/rtt_transports/ros
3. Add them in the manifest
4. add Autobuild::Orogen.transports  'ros' in init.rb
5. Add file ros.osdeps in autoproj folder 
(https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps)
5. amake rebuild

Thank you,

Pierre

 

- Original Message -
From: Steffen Planthaber steffen.plantha...@dfki.de
To: Pierre Letier pierre.let...@spaceapplications.com
Cc: rock-dev rock-dev@dfki.de
Sent: Wednesday, 26 August, 2015 3:28:49 PM
Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

Hi,

Just guessing but it could be, that a autoproj rebuild is nessecary to 
actually build the new transport for all the packages, but i'm not sure.

Best, Steffen


Am 26.08.2015 um 15:23 schrieb Pierre Letier:
 Hi,

 I continued with my trials and here is the status:

 - on a first install (one I have tested several things), I succeeded to 
 publish on ROS
 - on a new install (stable branch), I have still  a problem. Here is what I 
 have done:

 1. install stable branch
 2. paste tools/orogen_ros and tools/rtt_transports/ros
 3. Add them in the manifest
 4. add Autobuild::Orogen.transports  'ros' in init.rb
 5. amake

 I receive then the following error when starting a simple component that 
 publishes on ROS (a base/Pose type):
 : 'publish_on_ros': uninitialized constant Orocos::TRANSPORT_ROS

 6. acd orocos.rb
 7. rake clean
 8. rake

 I receive then the following error when starting a simple component that 
 publishes on ROS (a base/Pose type):
 'Caught std::exceptio. what(): Requesting to start as ROS node, but the 
 support for 'ros' transport is not available. Recompile with 'ros' transport 
 option!

 9. aup
 10. amake

 same error as after 8.

 I also tested rock-display, that shows now the Orocos::ROS:NameService, but 
 crahses after 1 sec, with the following error: Wrong size, Was 1513, should 
 be 284 (RuntimeError) ?? Not sure it is related to the problem above

 For the ROS bridge, I guess I am missing a step. Do you have any idea ?

 Best,

 Pierre



 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev rock-dev@dfki.de
 Sent: Wednesday, 26 August, 2015 11:50:54 AM
 Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

 Hi,

 can you send me the two packages  (zipped or upload them on github)?

 So we could re-establish rock-ros on github.

 tools/rtt_transports/ros
 and
 tools/orogen_ros

 Where I guess the second is not needed anymore.

 Best, Steffen


 Am 26.08.2015 um 11:41 schrieb Pierre Letier:
 Hi,

 My packages come from a previous installation I have done when gitorious was 
 still accessible. I also found the gitorious package in the .remote 
 folder. Is it possible to avoid to access gitorious and launch the 
 standard installation. With the current process, i never stipulate what 
 flavor of ROS I am using and I don't know if it can have an influence.

 I will test your solution and let you know (i am resinstalling a proper 
 system, after my trials...)

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: rock-dev@dfki.de
 Sent: Wednesday, 26 August, 2015 11:18:07 AM
 Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

 Hi,

 rock.ros is the package_set I created to integrate catkin builds into
 autoproj (as far a i remember).

 There I have a ros.osdeps file which tells autoproj to ignore ros
 dependencies (assume it is installed):

 here is the raw link, you can just drop it into your buildconf(autoproj
 folder):

 https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps


 Two packages are required for the ros bridge:

- tools/rtt_transports/ros:
gitorious: orocos-communication/ros-transport
branch: $ROCK_FLAVOR
- tools/orogen_ros:
gitorious: rock-ros/orogen_ros
branch: $ROCK_FLAVOR

 But I cannot find any of them on github.
 Can you tell me where your tools/rtt_transport/ros comes from?

 Best,

 Steffen

 Am 26.08.2015 um 10:52 schrieb Pierre Letier:


 - Forwarded Message -
 From: Pierre Letier pierre.let...@spaceapplications.com
 To: Steffen Planthaber steffen.plantha...@dfki.de
 Sent: Wednesday, 26 August, 2015 10:52:25 AM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hello,

 When following your description, when building, I receive an error as 
 tools/rtt_transport/ros is excluded from the build: it depends on roslib.

 My ROS is sources. Is this roslib created when compiling rock.ros ?

 Thank you,

 Pierre

 - Original Message -
 From: Steffen Planthaber

Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

2015-08-26 Thread Pierre Letier 
Dear Sacha, 

Once the init.rb has been updated, what has to be done ? I have launched a 
rebuild, but without success.

Pierre

- Original Message -
From: Sascha Arnold sascha.arn...@dfki.de
To: rock-dev@dfki.de
Sent: Wednesday, 26 August, 2015 3:56:32 PM
Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

Hi,
I'm not familiar with the rock ros integration.
But my guess is that tools/rtt_transports/ros and tools/orogen_ros are 
obsolete, since they are part of orogen and orocos.rb now.

Maybe it is enough now to activate the support by adding
 Autoproj.env_set 'USE_ROS', true
to the init.rb

There is also a way to set the path to the ros installation by adding
 Autoproj.env_set 'ROS_ROOT', path/to/ros_root


Best regards
Sascha


Am 26.08.2015 um 15:28 schrieb Steffen Planthaber:
 Hi,

 Just guessing but it could be, that a autoproj rebuild is nessecary to
 actually build the new transport for all the packages, but i'm not sure.

 Best, Steffen


 Am 26.08.2015 um 15:23 schrieb Pierre Letier:
 Hi,

 I continued with my trials and here is the status:

 - on a first install (one I have tested several things), I succeeded to 
 publish on ROS
 - on a new install (stable branch), I have still  a problem. Here is what I 
 have done:

 1. install stable branch
 2. paste tools/orogen_ros and tools/rtt_transports/ros
 3. Add them in the manifest
 4. add Autobuild::Orogen.transports  'ros' in init.rb
 5. amake

 I receive then the following error when starting a simple component that 
 publishes on ROS (a base/Pose type):
 : 'publish_on_ros': uninitialized constant Orocos::TRANSPORT_ROS

 6. acd orocos.rb
 7. rake clean
 8. rake

 I receive then the following error when starting a simple component that 
 publishes on ROS (a base/Pose type):
 'Caught std::exceptio. what(): Requesting to start as ROS node, but the 
 support for 'ros' transport is not available. Recompile with 'ros' transport 
 option!

 9. aup
 10. amake

 same error as after 8.

 I also tested rock-display, that shows now the Orocos::ROS:NameService, but 
 crahses after 1 sec, with the following error: Wrong size, Was 1513, should 
 be 284 (RuntimeError) ?? Not sure it is related to the problem above

 For the ROS bridge, I guess I am missing a step. Do you have any idea ?

 Best,

 Pierre



 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev rock-dev@dfki.de
 Sent: Wednesday, 26 August, 2015 11:50:54 AM
 Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

 Hi,

 can you send me the two packages  (zipped or upload them on github)?

 So we could re-establish rock-ros on github.

 tools/rtt_transports/ros
 and
 tools/orogen_ros

 Where I guess the second is not needed anymore.

 Best, Steffen


 Am 26.08.2015 um 11:41 schrieb Pierre Letier:
 Hi,

 My packages come from a previous installation I have done when gitorious 
 was still accessible. I also found the gitorious package in the .remote 
 folder. Is it possible to avoid to access gitorious and launch the 
 standard installation. With the current process, i never stipulate what 
 flavor of ROS I am using and I don't know if it can have an influence.

 I will test your solution and let you know (i am resinstalling a proper 
 system, after my trials...)

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: rock-dev@dfki.de
 Sent: Wednesday, 26 August, 2015 11:18:07 AM
 Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

 Hi,

 rock.ros is the package_set I created to integrate catkin builds into
 autoproj (as far a i remember).

 There I have a ros.osdeps file which tells autoproj to ignore ros
 dependencies (assume it is installed):

 here is the raw link, you can just drop it into your buildconf(autoproj
 folder):

 https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps


 Two packages are required for the ros bridge:

 - tools/rtt_transports/ros:
 gitorious: orocos-communication/ros-transport
 branch: $ROCK_FLAVOR
 - tools/orogen_ros:
 gitorious: rock-ros/orogen_ros
 branch: $ROCK_FLAVOR

 But I cannot find any of them on github.
 Can you tell me where your tools/rtt_transport/ros comes from?

 Best,

 Steffen

 Am 26.08.2015 um 10:52 schrieb Pierre Letier:

 - Forwarded Message -
 From: Pierre Letier pierre.let...@spaceapplications.com
 To: Steffen Planthaber steffen.plantha...@dfki.de
 Sent: Wednesday, 26 August, 2015 10:52:25 AM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hello,

 When following your description, when building, I receive an error as 
 tools/rtt_transport/ros is excluded from the build: it depends on roslib.

 My ROS is sources. Is this roslib created when compiling rock.ros ?

 Thank you,

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier

Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

2015-08-26 Thread Steffen Planthaber 
Hi,

can you send me the two packages  (zipped or upload them on github)?

So we could re-establish rock-ros on github.

tools/rtt_transports/ros
and
tools/orogen_ros

Where I guess the second is not needed anymore.

Best, Steffen


Am 26.08.2015 um 11:41 schrieb Pierre Letier:
 Hi,

 My packages come from a previous installation I have done when gitorious was 
 still accessible. I also found the gitorious package in the .remote folder. 
 Is it possible to avoid to access gitorious and launch the standard 
 installation. With the current process, i never stipulate what flavor of ROS 
 I am using and I don't know if it can have an influence.

 I will test your solution and let you know (i am resinstalling a proper 
 system, after my trials...)

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: rock-dev@dfki.de
 Sent: Wednesday, 26 August, 2015 11:18:07 AM
 Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

 Hi,

 rock.ros is the package_set I created to integrate catkin builds into
 autoproj (as far a i remember).

 There I have a ros.osdeps file which tells autoproj to ignore ros
 dependencies (assume it is installed):

 here is the raw link, you can just drop it into your buildconf(autoproj
 folder):

 https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps


 Two packages are required for the ros bridge:

   - tools/rtt_transports/ros:
   gitorious: orocos-communication/ros-transport
   branch: $ROCK_FLAVOR
   - tools/orogen_ros:
   gitorious: rock-ros/orogen_ros
   branch: $ROCK_FLAVOR

 But I cannot find any of them on github.
 Can you tell me where your tools/rtt_transport/ros comes from?

 Best,

 Steffen

 Am 26.08.2015 um 10:52 schrieb Pierre Letier:


 - Forwarded Message -
 From: Pierre Letier pierre.let...@spaceapplications.com
 To: Steffen Planthaber steffen.plantha...@dfki.de
 Sent: Wednesday, 26 August, 2015 10:52:25 AM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hello,

 When following your description, when building, I receive an error as 
 tools/rtt_transport/ros is excluded from the build: it depends on roslib.

 My ROS is sources. Is this roslib created when compiling rock.ros ?

 Thank you,

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev@dfki.de
 Sent: Tuesday, 25 August, 2015 4:15:02 PM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hi,

 rock-display is unable to display ros types, it can only connect to
 corba, not roscore.

 You can use rostopic list to see if you can publish your ports to ros
 port.publish_to_ros

 To let orogen build the ros types, you need to specify that you want to
 install the ros transport in your init.rb:

 Autobuild::Orogen.transports  'ros'

 and the package

 'tools/rtt_transports/ros' in should be in your manifest

 I once created a package_set (currently not functional because it is
 based on gitorious packages)
 https://github.com/planthaber/ros-package_set which also included catkin
 into autoproj build.

 But I think the contents of the init.rb there may help with your setup.


 Best,

 Steffen



 Am 25.08.2015 um 16:01 schrieb Pierre Letier:
 Hi,

 At least the rock-display doesn't show the ROS topics. If it is in the 
 codebase, is there a need of configuration ? (like during the installation 
 of the rock-ros bridge).

 Otherwise, I have another installation. Is there a way to take the code 
 (folder) from this installation ?

 Thank you,

 Best Regards,

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev@dfki.de
 Sent: Tuesday, 25 August, 2015 3:42:42 PM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hi,


 Am 25.08.2015 um 15:28 schrieb Pierre Letier:
 Thank you Steffen,

 Does it mean that we can not have access currently to the last code of the 
 ROS-ROCK bridge ?

 No Idea, but the comment says
 orogen_ros functionality is now part of the oroGen codebase, so i
 guess it can work out of the box.

 Best, Steffen





 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: rock-dev@dfki.de
 Sent: Tuesday, 25 August, 2015 9:23:03 AM
 Subject: [Rock-dev] Fwd: Re:  Access to Gitorious

 Accidently replied directly, so here is a forward to the list:


  Weitergeleitete Nachricht 
 Betreff: Re: [Rock-dev] Access to Gitorious
 Datum: Tue, 25 Aug 2015 09:21:49 +0200
 Von: Steffen Planthaber steffen.plantha...@dfki.de
 An: Pierre Letier pierre.let...@spaceapplications.com

 Hi,

 We moved all the rock code to github.

 The package_set for the tutorials is located here:
 https://github.com/rock-tutorials, along with the packages.


 I found an old package belonging to the bridge:
 https://github.com/rock-core/tools

Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

2015-08-26 Thread Pierre Letier 
Hi, 

My packages come from a previous installation I have done when gitorious was 
still accessible. I also found the gitorious package in the .remote folder. 
Is it possible to avoid to access gitorious and launch the standard 
installation. With the current process, i never stipulate what flavor of ROS I 
am using and I don't know if it can have an influence.

I will test your solution and let you know (i am resinstalling a proper system, 
after my trials...)

Pierre 

- Original Message -
From: Steffen Planthaber steffen.plantha...@dfki.de
To: rock-dev@dfki.de
Sent: Wednesday, 26 August, 2015 11:18:07 AM
Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

Hi,

rock.ros is the package_set I created to integrate catkin builds into 
autoproj (as far a i remember).

There I have a ros.osdeps file which tells autoproj to ignore ros 
dependencies (assume it is installed):

here is the raw link, you can just drop it into your buildconf(autoproj 
folder):

https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps


Two packages are required for the ros bridge:

 - tools/rtt_transports/ros:
 gitorious: orocos-communication/ros-transport
 branch: $ROCK_FLAVOR
 - tools/orogen_ros:
 gitorious: rock-ros/orogen_ros
 branch: $ROCK_FLAVOR

But I cannot find any of them on github.
Can you tell me where your tools/rtt_transport/ros comes from?

Best,

Steffen

Am 26.08.2015 um 10:52 schrieb Pierre Letier:


 - Forwarded Message -
 From: Pierre Letier pierre.let...@spaceapplications.com
 To: Steffen Planthaber steffen.plantha...@dfki.de
 Sent: Wednesday, 26 August, 2015 10:52:25 AM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hello,

 When following your description, when building, I receive an error as 
 tools/rtt_transport/ros is excluded from the build: it depends on roslib.

 My ROS is sources. Is this roslib created when compiling rock.ros ?

 Thank you,

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev@dfki.de
 Sent: Tuesday, 25 August, 2015 4:15:02 PM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hi,

 rock-display is unable to display ros types, it can only connect to
 corba, not roscore.

 You can use rostopic list to see if you can publish your ports to ros
 port.publish_to_ros

 To let orogen build the ros types, you need to specify that you want to
 install the ros transport in your init.rb:

 Autobuild::Orogen.transports  'ros'

 and the package

 'tools/rtt_transports/ros' in should be in your manifest

 I once created a package_set (currently not functional because it is
 based on gitorious packages)
 https://github.com/planthaber/ros-package_set which also included catkin
 into autoproj build.

 But I think the contents of the init.rb there may help with your setup.


 Best,

 Steffen



 Am 25.08.2015 um 16:01 schrieb Pierre Letier:
 Hi,

 At least the rock-display doesn't show the ROS topics. If it is in the 
 codebase, is there a need of configuration ? (like during the installation 
 of the rock-ros bridge).

 Otherwise, I have another installation. Is there a way to take the code 
 (folder) from this installation ?

 Thank you,

 Best Regards,

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev@dfki.de
 Sent: Tuesday, 25 August, 2015 3:42:42 PM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hi,


 Am 25.08.2015 um 15:28 schrieb Pierre Letier:
 Thank you Steffen,

 Does it mean that we can not have access currently to the last code of the 
 ROS-ROCK bridge ?

 No Idea, but the comment says
 orogen_ros functionality is now part of the oroGen codebase, so i
 guess it can work out of the box.

 Best, Steffen





 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: rock-dev@dfki.de
 Sent: Tuesday, 25 August, 2015 9:23:03 AM
 Subject: [Rock-dev] Fwd: Re:  Access to Gitorious

 Accidently replied directly, so here is a forward to the list:


  Weitergeleitete Nachricht 
 Betreff: Re: [Rock-dev] Access to Gitorious
 Datum: Tue, 25 Aug 2015 09:21:49 +0200
 Von: Steffen Planthaber steffen.plantha...@dfki.de
 An: Pierre Letier pierre.let...@spaceapplications.com

 Hi,

 We moved all the rock code to github.

 The package_set for the tutorials is located here:
 https://github.com/rock-tutorials, along with the packages.


 I found an old package belonging to the bridge:
 https://github.com/rock-core/tools-orogen_ros

 The description says:
 DEPRECATED PACKAGE. The orogen_ros functionality is now part of the
 oroGen codebase

 I can't find the previously required package
 orocos-communication/ros-transport though.

 But perhaps it works directly...

 Kind Regards,

 Steffen



 Am 25.08.2015 um 07:39 schrieb Pierre

Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

2015-08-26 Thread Sascha Arnold 
Hi,
I'm not familiar with the rock ros integration.
But my guess is that tools/rtt_transports/ros and tools/orogen_ros are 
obsolete, since they are part of orogen and orocos.rb now.

Maybe it is enough now to activate the support by adding
 Autoproj.env_set 'USE_ROS', true
to the init.rb

There is also a way to set the path to the ros installation by adding
 Autoproj.env_set 'ROS_ROOT', path/to/ros_root


Best regards
Sascha


Am 26.08.2015 um 15:28 schrieb Steffen Planthaber:
 Hi,

 Just guessing but it could be, that a autoproj rebuild is nessecary to
 actually build the new transport for all the packages, but i'm not sure.

 Best, Steffen


 Am 26.08.2015 um 15:23 schrieb Pierre Letier:
 Hi,

 I continued with my trials and here is the status:

 - on a first install (one I have tested several things), I succeeded to 
 publish on ROS
 - on a new install (stable branch), I have still  a problem. Here is what I 
 have done:

 1. install stable branch
 2. paste tools/orogen_ros and tools/rtt_transports/ros
 3. Add them in the manifest
 4. add Autobuild::Orogen.transports  'ros' in init.rb
 5. amake

 I receive then the following error when starting a simple component that 
 publishes on ROS (a base/Pose type):
 : 'publish_on_ros': uninitialized constant Orocos::TRANSPORT_ROS

 6. acd orocos.rb
 7. rake clean
 8. rake

 I receive then the following error when starting a simple component that 
 publishes on ROS (a base/Pose type):
 'Caught std::exceptio. what(): Requesting to start as ROS node, but the 
 support for 'ros' transport is not available. Recompile with 'ros' transport 
 option!

 9. aup
 10. amake

 same error as after 8.

 I also tested rock-display, that shows now the Orocos::ROS:NameService, but 
 crahses after 1 sec, with the following error: Wrong size, Was 1513, should 
 be 284 (RuntimeError) ?? Not sure it is related to the problem above

 For the ROS bridge, I guess I am missing a step. Do you have any idea ?

 Best,

 Pierre



 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev rock-dev@dfki.de
 Sent: Wednesday, 26 August, 2015 11:50:54 AM
 Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

 Hi,

 can you send me the two packages  (zipped or upload them on github)?

 So we could re-establish rock-ros on github.

 tools/rtt_transports/ros
 and
 tools/orogen_ros

 Where I guess the second is not needed anymore.

 Best, Steffen


 Am 26.08.2015 um 11:41 schrieb Pierre Letier:
 Hi,

 My packages come from a previous installation I have done when gitorious 
 was still accessible. I also found the gitorious package in the .remote 
 folder. Is it possible to avoid to access gitorious and launch the 
 standard installation. With the current process, i never stipulate what 
 flavor of ROS I am using and I don't know if it can have an influence.

 I will test your solution and let you know (i am resinstalling a proper 
 system, after my trials...)

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: rock-dev@dfki.de
 Sent: Wednesday, 26 August, 2015 11:18:07 AM
 Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

 Hi,

 rock.ros is the package_set I created to integrate catkin builds into
 autoproj (as far a i remember).

 There I have a ros.osdeps file which tells autoproj to ignore ros
 dependencies (assume it is installed):

 here is the raw link, you can just drop it into your buildconf(autoproj
 folder):

 https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps


 Two packages are required for the ros bridge:

 - tools/rtt_transports/ros:
 gitorious: orocos-communication/ros-transport
 branch: $ROCK_FLAVOR
 - tools/orogen_ros:
 gitorious: rock-ros/orogen_ros
 branch: $ROCK_FLAVOR

 But I cannot find any of them on github.
 Can you tell me where your tools/rtt_transport/ros comes from?

 Best,

 Steffen

 Am 26.08.2015 um 10:52 schrieb Pierre Letier:

 - Forwarded Message -
 From: Pierre Letier pierre.let...@spaceapplications.com
 To: Steffen Planthaber steffen.plantha...@dfki.de
 Sent: Wednesday, 26 August, 2015 10:52:25 AM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hello,

 When following your description, when building, I receive an error as 
 tools/rtt_transport/ros is excluded from the build: it depends on roslib.

 My ROS is sources. Is this roslib created when compiling rock.ros ?

 Thank you,

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev@dfki.de
 Sent: Tuesday, 25 August, 2015 4:15:02 PM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hi,

 rock-display is unable to display ros types, it can only connect to
 corba, not roscore.

 You can use rostopic list to see if you can publish your ports

Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

2015-08-26 Thread Pierre Letier 
Hi, 

I continued with my trials and here is the status:

- on a first install (one I have tested several things), I succeeded to publish 
on ROS
- on a new install (stable branch), I have still  a problem. Here is what I 
have done:

1. install stable branch
2. paste tools/orogen_ros and tools/rtt_transports/ros 
3. Add them in the manifest
4. add Autobuild::Orogen.transports  'ros' in init.rb
5. amake

I receive then the following error when starting a simple component that 
publishes on ROS (a base/Pose type):
: 'publish_on_ros': uninitialized constant Orocos::TRANSPORT_ROS

6. acd orocos.rb
7. rake clean
8. rake

I receive then the following error when starting a simple component that 
publishes on ROS (a base/Pose type):
'Caught std::exceptio. what(): Requesting to start as ROS node, but the support 
for 'ros' transport is not available. Recompile with 'ros' transport option!

9. aup
10. amake

same error as after 8.

I also tested rock-display, that shows now the Orocos::ROS:NameService, but 
crahses after 1 sec, with the following error: Wrong size, Was 1513, should be 
284 (RuntimeError) ?? Not sure it is related to the problem above

For the ROS bridge, I guess I am missing a step. Do you have any idea ?

Best, 

Pierre



- Original Message -
From: Steffen Planthaber steffen.plantha...@dfki.de
To: Pierre Letier pierre.let...@spaceapplications.com
Cc: rock-dev rock-dev@dfki.de
Sent: Wednesday, 26 August, 2015 11:50:54 AM
Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

Hi,

can you send me the two packages  (zipped or upload them on github)?

So we could re-establish rock-ros on github.

tools/rtt_transports/ros
and
tools/orogen_ros

Where I guess the second is not needed anymore.

Best, Steffen


Am 26.08.2015 um 11:41 schrieb Pierre Letier:
 Hi,

 My packages come from a previous installation I have done when gitorious was 
 still accessible. I also found the gitorious package in the .remote folder. 
 Is it possible to avoid to access gitorious and launch the standard 
 installation. With the current process, i never stipulate what flavor of ROS 
 I am using and I don't know if it can have an influence.

 I will test your solution and let you know (i am resinstalling a proper 
 system, after my trials...)

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: rock-dev@dfki.de
 Sent: Wednesday, 26 August, 2015 11:18:07 AM
 Subject: Re: [Rock-dev] Fwd: Fwd: Re: Access to Gitorious

 Hi,

 rock.ros is the package_set I created to integrate catkin builds into
 autoproj (as far a i remember).

 There I have a ros.osdeps file which tells autoproj to ignore ros
 dependencies (assume it is installed):

 here is the raw link, you can just drop it into your buildconf(autoproj
 folder):

 https://raw.githubusercontent.com/planthaber/ros-package_set/master/ros.osdeps


 Two packages are required for the ros bridge:

   - tools/rtt_transports/ros:
   gitorious: orocos-communication/ros-transport
   branch: $ROCK_FLAVOR
   - tools/orogen_ros:
   gitorious: rock-ros/orogen_ros
   branch: $ROCK_FLAVOR

 But I cannot find any of them on github.
 Can you tell me where your tools/rtt_transport/ros comes from?

 Best,

 Steffen

 Am 26.08.2015 um 10:52 schrieb Pierre Letier:


 - Forwarded Message -
 From: Pierre Letier pierre.let...@spaceapplications.com
 To: Steffen Planthaber steffen.plantha...@dfki.de
 Sent: Wednesday, 26 August, 2015 10:52:25 AM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hello,

 When following your description, when building, I receive an error as 
 tools/rtt_transport/ros is excluded from the build: it depends on roslib.

 My ROS is sources. Is this roslib created when compiling rock.ros ?

 Thank you,

 Pierre

 - Original Message -
 From: Steffen Planthaber steffen.plantha...@dfki.de
 To: Pierre Letier pierre.let...@spaceapplications.com
 Cc: rock-dev@dfki.de
 Sent: Tuesday, 25 August, 2015 4:15:02 PM
 Subject: Re: [Rock-dev] Fwd: Re:  Access to Gitorious

 Hi,

 rock-display is unable to display ros types, it can only connect to
 corba, not roscore.

 You can use rostopic list to see if you can publish your ports to ros
 port.publish_to_ros

 To let orogen build the ros types, you need to specify that you want to
 install the ros transport in your init.rb:

 Autobuild::Orogen.transports  'ros'

 and the package

 'tools/rtt_transports/ros' in should be in your manifest

 I once created a package_set (currently not functional because it is
 based on gitorious packages)
 https://github.com/planthaber/ros-package_set which also included catkin
 into autoproj build.

 But I think the contents of the init.rb there may help with your setup.


 Best,

 Steffen



 Am 25.08.2015 um 16:01 schrieb Pierre Letier:
 Hi,

 At least the rock-display doesn't show the ROS topics. If it is in the 
 codebase, is there a need of configuration ? (like during the installation