About SlaveActivity syntax

Hi all,
I read on page 11 of the Deployment Component manual that there is the
possibility to have SlaveActivity that "allows a component to be
executed by a master component".

I'm interested in this structure because I would like to have a Master
component, as transparent as possible, that executes the updatehook of
every slave.
In my mind the project has this form:

1)The user can create his own Slave component respecting few basic rules.
2)The user load and configure the Master and the Slaves using the deployer.
3)The updatehook of the Master executes the updatehook of the Slaves
(using the Master's thread) .

Anyway from the information of these pages I haven't understand yet
which is the syntax that I need in myMaster component and in mySlave
component and in their updatehook(). There is a specific way to deploy
these components?

Thank you for any hints,
Best regards

Luca

About SlaveActivity syntax

On Tue, 8 May 2012, Luca Magnabosco wrote:

> Hi all,
> I read on page 11 of the Deployment Component manual that there is the
> possibility to have SlaveActivity that "allows a component to be
> executed by a master component".

Here
<http://www.orocos.org/forum/orocos/orocos-users/ann-fbsched-function-block-scheduling-component>

is a recent post that gives a lot of concrete details about this topic.

Let us know whether this helped.

> I'm interested in this structure because I would like to have a Master
> component, as transparent as possible, that executes the updatehook of
> every slave.
> In my mind the project has this form:
>
> 1)The user can create his own Slave component respecting few basic rules.
> 2)The user load and configure the Master and the Slaves using the deployer.
> 3)The updatehook of the Master executes the updatehook of the Slaves
> (using the Master's thread) .
>
> Anyway from the information of these pages I haven't understand yet
> which is the syntax that I need in myMaster component and in mySlave
> component and in their updatehook(). There is a specific way to deploy
> these components?
>
> Thank you for any hints,
> Best regards
>
> Luca

Herman

About SlaveActivity syntax

Thanks,
It was exactly what I was looking for.

I have another question about slave activities:
is it possible in Orocos have a shared memory filed between the
master's task and the slave's task?
If there is only the master thread running there isn't a problem of
contemporary access but I'm facing something quite strange.

Thanks for any hint

Luca

About SlaveActivity syntax

On Wed, 16 May 2012, Luca Magnabosco wrote:

> Thanks,
> It was exactly what I was looking for.
>
> I have another question about slave activities:
> is it possible in Orocos have a shared memory filed between the
> master's task and the slave's task?

Please, don't start using non-component based "features" in a component
based framework. RTT was designed to make low-level things like shared
memory invisible to users.

If you need shared memory (which you might, for efficiency reasons etc),
then do it _inside_ components, and not _between_ components.

Maybe a component based framework is not what you are after anyway...?
I mean: are you looking for a "multi threaded" library support? Then RTT is
not for you.

> If there is only the master thread running there isn't a problem of
> contemporary access but I'm facing something quite strange.
>
> Thanks for any hint
>
> Luca

Herman

About SlaveActivity syntax

Well.. sorry.
My last question wasn't well done.
I will try to explain my problem in other words in another thread to
explain from the beginning my design problem.
The thread will be called "Design of an EtherCAT master using SOEM with a
Taskcontext for every slave"

B.R.
Luca