Hi Geoffrey:<br>Thank you for detailed explanation. <br>It's very much appreciated!! <br><br>I couldn't wait, I read the Japanese OpenRTM website with Google translate and found some explanation <br>on these components. <br>
But your explanation still helps alot!<br><br>I have the win32 version OpenRTM source code, but I couldn't find <br>other samples that you mentioned. (such as an image acquisition component and an image display component,<br>
using OpenCV.). <br>However I got image acq and display units from the tutorial you did in April this year. <br><br>I am really looking forward to the new OpenRTM website !! <br><br>Thanks<br>Tony<br><br><br><div class="gmail_quote">
On 8 September 2010 13:02, Geoffrey Biggs <span dir="ltr"><<a href="mailto:geoffrey.biggs@aist.go.jp">geoffrey.biggs@aist.go.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Tony,<br>
<br>
There is documentation about the examples on our new website, but that<br>
isn't live yet. The examples are roughly as follows:<br>
<br>
SimpleIO: Demonstrates basic component and data port operations, as well<br>
as more complex functionality such as data port callbacks. One component<br>
reads a number from the terminal and sends it over a data port; the<br>
other receives a number on its data port and prints it to the console.<br>
<br>
SeqIO: Similar to SimpleIO, but demonstrates the use of sequence data types.<br>
<br>
SimpleService: Demonstrates using a service port. Unlike a data port, a<br>
service port is a two-way RPC-based communication. Use it to provide<br>
services requiring a synchronised response.<br>
<br>
ConfigSample: Demonstrates the use of configuration parameters and<br>
configuration sets. While running, this component will constantly print<br>
out its current configuration. You can alter individual parameters of<br>
this configuration or change the active set at run time using<br>
RTSystemEditor or the rtconf command from rtcshell.<br>
<br>
Composite: Demonstrates a composite component. A composite component is<br>
one component who's behaviour is made up of multiple child components.<br>
This example also demonstrates several features of the manager, such as<br>
pre-loading component implementation libraries and automatically<br>
creating components when the manager is started.<br>
<br>
If you are using the Windows version, you will also have other samples<br>
such as an image acquisition component and an image display component,<br>
using OpenCV.<br>
<br>
Don't forget that you can also find other components on our website in<br>
the "Components" section. The new website will have a much larger<br>
number. Many of these components use more complex data types such as<br>
those defined in the ExtendedDataTypes.idl and InterfaceDataTypes.idl files.<br>
<br>
Geoff<br>
<div class="im"><br>
<br>
On 30/08/10 13:24, Tony Kuo wrote:<br>
> Dear. Dr. Ando<br>
> Thank you for your reply.<br>
> I am still learning some of the concepts in Openrtm framework.<br>
> so, I was also wondering is there any documentation that help me<br>
> understand some of the examples that comes with OpenRTM?<br>
><br>
> For example, I don't quite see the advantage of using components such as<br>
> MyServiceConsumer and provider and the difference between ConsoleIn/Out<br>
> and SeqIn/Out ...etc<br>
><br>
><br>
> Thanks<br>
> Tony<br>
><br>
><br>
> On 29 August 2010 20:26, Ando Noriaki <<a href="mailto:n-ando@aist.go.jp">n-ando@aist.go.jp</a><br>
</div><div><div></div><div class="h5">> <mailto:<a href="mailto:n-ando@aist.go.jp">n-ando@aist.go.jp</a>>> wrote:<br>
><br>
> Dear Tony-san<br>
><br>
> OMG RTC specification defines FSM component, but currently<br>
> OpenRTM-aist does not support FSM component. We have plan to<br>
> support FMS component, but I cannot say expressly when the<br>
> feature will be supported on the OpenRTM-aist. I'm sorry.<br>
><br>
> Best regards,<br>
> Noriaki Ando<br>
><br>
><br>
> > Hi OpenRTM-ML:<br>
> > I have been learning to use OpenRTM for a robotic project i am doing.<br>
> > I learnt a bit about creating periodic dataflow component from<br>
> the workshop<br>
> > the OpenRTM group gave in April in Auckland, NZ.<br>
> ><br>
> > Now I am looking into other features available with OpenRTM.<br>
> > I would like to create a FSM component through OpenRTM.<br>
> > I saw it in RTC builder, but not sure if it's really available or not.<br>
> > Does anyone have any experience in creating FSM component or have<br>
> any good<br>
> > example for me to start with?<br>
> > I am also interested in knowing more about the examples that came with<br>
> > OpenRTM source.<br>
> > Where can I find more information about them and what OpenRTM<br>
> feature and<br>
> > capabilities do they demonstrate respectively?<br>
> > Any help is appreciated!<br>
> > Tony<br>
> > PhD candidate<br>
> > University of Auckland,<br>
> ><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Noriaki Ando, Ph.D.<br>
> Senior Research Scientist, RT-Synthesis R.G., ISRI, AIST<br>
> AIST Tsukuba Central 2, Tsukuba, Ibaraki 305-8568 JAPAN<br>
</div></div>> e-mail: <a href="mailto:n-ando@aist.go.jp">n-ando@aist.go.jp</a> <mailto:<a href="mailto:n-ando@aist.go.jp">n-ando@aist.go.jp</a>>, web:<br>
<div><div></div><div class="h5">> <a href="http://staff.aist.go.jp/n-ando" target="_blank">http://staff.aist.go.jp/n-ando</a><br>
> OpenRTM-aist: <a href="http://www.openrtm.org" target="_blank">http://www.openrtm.org</a><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br>