• v1.12.0 [README] [Installation Manual]
• Example code [README]
• New Tutorial code for RTT 1.12.x [README]</... Click below to read the rest of this post.

This summer, from the 18th of July until the 23th of July, the Real-Time Toolkit developers organize their first developer's meeting in order to align their contributions and set out a path for the future. The topics during this week are code generation tools and user tooling in general, real-time logging infrastructure, RTT 2.0 and run-time interoperability with other software and platforms. The agenda is being crafted at The 1st RTT Developers Workshop. wiki page. Click below to read the rest of this post.

Now located at http://orocos.org/wiki/rtt/examples-and-tutorials

From recent discussion on ML, simply a place to put down ideas before we forget them ...

• Use Wiki for FAQ instead of XML doc

FAQ

• My shared libraries won't load
• The deployer won't load my plugins
• Can I use dynamic memory allocation, and where?
• How do I run in real time? Click below to read the rest of this post.

The Orocos development team announces the fourth bug-fix release of
the Orocos Real-Time Toolkit 1.0. You can download this release from here.
This release addresses the following reported issues:

ID     Vers   TargetM   Summary
378    1.0.3   1.0.4   Loading program in KTaskbrowser reports success upon syntax error
379    1.0.3   1.0.4   'Ghost' attributes appear in TaskContext when state machine loading fails
356    1.0.3   1.0.4   CompletionProcessor is not automatically started
397    1.0.3   1.0.4   -fvisibility-inlines-hidden causes undefined symbols

This is a developer's release and provides a look-ahead on RTT 1.2.0.
It passes all unit tests for the GNU/Linux and Xenomai targets. The
documentation manuals have not yet been updated with the latest changes. The
public API is intended to be fully backwards compatible with Orocos 1.0.x
applications.

Sources:

Docs (in progress):

Changes (in progress):

Build instructions:

We are especially interested in current Orocos 1.0.x users testing this release in order to verify the build system and source compatibility, before RTT 1.2.0 is released.

The Orocos development team announces the third bug-fix release of
the Orocos Real-Time Toolkit 1.0. You can download it here.
This release improved the on-line documentation and addressed the
following reported issues:

   ID    Vers   TargetM   Summary
  338    1.0.2   1.0.3   setScheduler() not working correctly under GNU/Linux
  332    1.0.2   1.0.3   Crash when assigning '0' to Property<T>
  324    oroco   1.0.3   make install broken wrt headers (Ubuntu Edgy)

The Orocos development team announces the second bug-fix release of the Orocos Real-Time Toolkit 1.0. A license change from LGPL to the GPL + linking exception was done. The LGPL did not cover C++ templates correctly, while the new license does and is legally more sound for use in commercial applications. You can get it from the download page.

We announce the release of the Graphical User Interface to Orocos Components, based on KDE 3. This program allows to show a component's status variables, and shows the progress of program scripts and state machines. It connects to networked Orocos components through the CORBA Naming Service and allows to browse the full network of components.

Consult the README to see how to compile this program and how to setup your Orocos application such that it can be found by the KTaskBrowser. Download here.

The Orocos development team announces the first bug-fix release of the Orocos Real-Time Toolkit 1.0. This release improved the online documentation, fixed bindings to Xenomai and RTAI and contains additions to the Corba interface.

The Orocos Components Library version 0.2.1 and the Orocos Kinematics and Dynamics Library version 0.2.1 have been released as well. These releases include mainly documentation updates. The 'Component Template' package v1.0 has been released as well, which allows Orocos Component builders to quickly construct a new component. The template offers a ready to use build system (using cmake), an example component and an example test program.