The Rock development team is proud to announce the official public
release of the Robot Construction Kit (Rock).
Rock is a software framework for the development of robotic systems. The
underlying component model is based on Orocos/RTT (Real Time Toolkit).
Rock provides all the tools required to set up and run high-performance
and reliable robotic systems for a wide variety of applications in
research and industry. It contains a rich collection of ready-to-use
drivers and modules for use in your own system, and can easily be
extended by adding new components. The framework was developed to
specifically address the following issues in existing solutions:
sustainable systems.
The architecture and the tools in Rock are designed with
long-running systems in mind. In practice this means that for us,
error detection, reporting and handling are key in any robotic
architecture.
scalability.
Provide the tools to be able to manage big systems with minimum
fuss. But we don't require you to learn about these (complex) tools
right away: as soon as you use Rock's component development tool,
oroGen, you have the guarantee that your components can be
integrated - from simple scenarios using hard-coded C++ behaviors,
to Ruby scripts, up to the complete system monitoring tools.
reusable code-base.
Even though we think that the rock toolchain is one of the best out
there, some other people might feel differently. And they might be
right. That's why in Rock most of the functionality – from control
to data display through to data processing – is implemented in a way
that is totally independent from Rock's integration framework.
That's right: just pick our drivers, localization algorithms and
control loops and add them into your integration framework. You
don't have to do anything on our side, as the code is completely
independent from the integration parts.
Dive in with the
installation
http://rock-robotics.org/documentation/installation.html
tutorials
http://rock-robotics.org/documentation/tutorials/index.html
and have a look at the framework functionality !
http://rock-robotics.org/documentation/
So far, the development of the Robot Construction Kit has been supported
by the DFKI Robotics Innovation Center (http://www.dfki.de/robotics) in
Bremen, Germany. However, it is an open platform, so feel free to join.
Most packages in the Rock distribution are under an LGPL v2 or later
license.
The Rock Development Team
Contact: rock-dev [..] ...
Public release of the Robot Construction Kit
2012/5/9 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> The Rock development team is proud to announce the official public
> release of the Robot Construction Kit (Rock).
>
> http://rock-robotics.org
>
> Rock is a software framework for the development of robotic systems. The
> underlying component model is based on Orocos/RTT (Real Time Toolkit).
> Rock provides all the tools required to set up and run high-performance
> and reliable robotic systems for a wide variety of applications in
> research and industry. It contains a rich collection of ready-to-use
> drivers and modules for use in your own system, and can easily be
> extended by adding new components. The framework was developed to
> specifically address the following issues in existing solutions:
>
> sustainable systems.
> The architecture and the tools in Rock are designed with
> long-running systems in mind. In practice this means that for us,
> error detection, reporting and handling are key in any robotic
> architecture.
>
> scalability.
> Provide the tools to be able to manage big systems with minimum
> fuss. But we don't require you to learn about these (complex) tools
> right away: as soon as you use Rock's component development tool,
> oroGen, you have the guarantee that your components can be
> integrated - from simple scenarios using hard-coded C++ behaviors,
> to Ruby scripts, up to the complete system monitoring tools.
>
> reusable code-base.
> Even though we think that the rock toolchain is one of the best out
> there, some other people might feel differently. And they might be
> right. That's why in Rock most of the functionality – from control
> to data display through to data processing – is implemented in a way
> that is totally independent from Rock's integration framework.
> That's right: just pick our drivers, localization algorithms and
> control loops and add them into your integration framework. You
> don't have to do anything on our side, as the code is completely
> independent from the integration parts.
>
> Dive in with the
> installation
> http://rock-robotics.org/documentation/installation.html
> tutorials
> http://rock-robotics.org/documentation/tutorials/index.html
> and have a look at the framework functionality !
> http://rock-robotics.org/documentation/
>
> So far, the development of the Robot Construction Kit has been supported
> by the DFKI Robotics Innovation Center (http://www.dfki.de/robotics) in
> Bremen, Germany. However, it is an open platform, so feel free to join.
> Most packages in the Rock distribution are under an LGPL v2 or later
> license.
>
> The Rock Development Team
> Contact: rock-dev [..] ...
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
\o/
Great work guys. Can't wait to try this (this summer I think).
Is there a place to propose user custom code pieces for a common code-base
? This is one of the bigger lack in Orocos. Even if you have a strong
code-base to share with the default framework, letting people sharing their
code easily is the key for an easy growth. I mean something like ROS ;p
Public release of the Robot Construction Kit
On 05/09/2012 04:06 PM, Willy Lambert wrote:
> \o/
> Great work guys. Can't wait to try this (this summer I think).
Thanks
> Is there a place to propose user custom code pieces for a common
> code-base ? This is one of the bigger lack in Orocos. Even if you have a
> strong code-base to share with the default framework, letting people
> sharing their code easily is the key for an easy growth. I mean
> something like ROS ;p
There would be two ways:
- create your own autoproj package set and propose it to rock-dev. We
would happily add it to the rock build, making in effect your
packages available on the Rock package directory.
- propose to develop directly in Rock itself. We are definitely
interested in having other institutes be part of the project itself.
Public release of the Robot Construction Kit
On May 9, 2012, at 10:12 , Sylvain Joyeux wrote:
> On 05/09/2012 04:06 PM, Willy Lambert wrote:
>> \o/
>> Great work guys. Can't wait to try this (this summer I think).
> Thanks
>
>> Is there a place to propose user custom code pieces for a common
>> code-base ? This is one of the bigger lack in Orocos. Even if you have a
>> strong code-base to share with the default framework, letting people
>> sharing their code easily is the key for an easy growth. I mean
>> something like ROS ;p
> There would be two ways:
> - create your own autoproj package set and propose it to rock-dev. We
> would happily add it to the rock build, making in effect your
> packages available on the Rock package directory.
> - propose to develop directly in Rock itself. We are definitely
> interested in having other institutes be part of the project itself.
Would intergrating with ROS in some fashion be an option?
S
Public release of the Robot Construction Kit
On 05/09/2012 04:15 PM, S Roderick wrote:
> On May 9, 2012, at 10:12 , Sylvain Joyeux wrote:
>
>> On 05/09/2012 04:06 PM, Willy Lambert wrote:
>>> \o/
>>> Great work guys. Can't wait to try this (this summer I think).
>> Thanks
>>
>>> Is there a place to propose user custom code pieces for a common
>>> code-base ? This is one of the bigger lack in Orocos. Even if you have a
>>> strong code-base to share with the default framework, letting people
>>> sharing their code easily is the key for an easy growth. I mean
>>> something like ROS ;p
>> There would be two ways:
>> - create your own autoproj package set and propose it to rock-dev. We
>> would happily add it to the rock build, making in effect your
>> packages available on the Rock package directory.
>> - propose to develop directly in Rock itself. We are definitely
>> interested in having other institutes be part of the project itself.
>
> Would intergrating with ROS in some fashion be an option?
Depends on what you call "integrating with ROS"
What I am absolutely 100% again is having to add ros-specific code in
the Rock code (apart from a ros transport that is). I am thinking in
particular about that ros-package-finding C++ code.
What *will* happen is that rock's tooling will eventually be able to use
ROS nodes transparently.
Public release of the Robot Construction Kit
2012/5/9 Sylvain Joyeux <sylvain [dot] joyeux [..] ...>
> On 05/09/2012 04:15 PM, S Roderick wrote:
>
>> On May 9, 2012, at 10:12 , Sylvain Joyeux wrote:
>>
>> On 05/09/2012 04:06 PM, Willy Lambert wrote:
>>>
>>>> \o/
>>>> Great work guys. Can't wait to try this (this summer I think).
>>>>
>>> Thanks
>>>
>>> Is there a place to propose user custom code pieces for a common
>>>> code-base ? This is one of the bigger lack in Orocos. Even if you have a
>>>> strong code-base to share with the default framework, letting people
>>>> sharing their code easily is the key for an easy growth. I mean
>>>> something like ROS ;p
>>>>
>>> There would be two ways:
>>> - create your own autoproj package set and propose it to rock-dev. We
>>> would happily add it to the rock build, making in effect your
>>> packages available on the Rock package directory.
>>> - propose to develop directly in Rock itself. We are definitely
>>> interested in having other institutes be part of the project itself.
>>>
>>
>> Would intergrating with ROS in some fashion be an option?
>>
> +1 on the question
> Depends on what you call "integrating with ROS"
>
Being able to integrate ROS at execution time (meaning messages<=>port
service<=>operation)
>
> What I am absolutely 100% again is having to add ros-specific code in the
> Rock code (apart from a ros transport that is). I am thinking in particular
> about that ros-package-finding C++ code.
>
> What *will* happen is that rock's tooling will eventually be able to use
> ROS nodes transparently.
>
> --
> Sylvain Joyeux (Dr.Ing.)
> Space & Security Robotics
>
> !!! Achtung, neue Telefonnummer!!!
>
> Standort Bremen:
> DFKI GmbH
> Robotics Innovation Center
> Robert-Hooke-Straße 5
> 28359 Bremen, Germany
>
> Phone: +49 (0)421 178-454136
> Fax: +49 (0)421 218-454150
> E-Mail: robotik [..] ...
>
> 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
> ------------------------------**------------------------------**
> -----------
>