On Jan 17, 2013, at 11:03 AM, Mirko Daniele Comparetti <mirko [dot] comparetti [..] ...mirko [dot] comparetti [..] ...>> wrote:

I'll revise the deployment XML.
The problem arise because the components require some input in ports from other components and they stop because of lacking data and then the component is not started. If I wait a bit and then I try to start the component again, it works.
One of this 2 ports are a connectionpolicy with a ros topic

So in this case I assume that there is the need for a short time between these two components are started.

Thank you,

- - -
Mirko D. Comparetti

M.Sc., Eng'r, PhD Student
Politecnico di Milano - ICT and Bioengineering Department (DEIB)
Neuro Engineering and medicAl Robotics Lab,
Piazza Leonardo da Vinci, 32
20133 Milan, Italy
www.nearlab.polimi.it<http://www.nearlab.polimi.it />

Email: mirko [dot] comparetti [..] ...<mailto:mirko [dot] comparetti [..] ...>
Phone: +39 02 2399 9013
Fax: +39 02 2399 9003

- .... . / -- .. -. -.. / .. ... / .-.. .. -.- . / .- / .--. .- .-. .- -.-. .... ..- - .
.. - / .-- --- .-. -.- ... / --- -. .-.. -.-- / .-- .... . -. / .. - / .. ... / --- .--. . -.

2013/1/17 Markus Klotzbuecher <markus [dot] klotzbuecher [..] ...markus [dot] klotzbuecher [..] ...>>
On Thu, Jan 17, 2013 at 09:40:34AM +0000, mirko [dot] comparetti [..] ...<mailto:mirko [dot] comparetti [..] ...> wrote:
> Hi all,
> In
> [http://www.orocos.org/stable/documentation/rtt/v2.x/doc-xml/orocos-components-manual.html
> this manual] there is an example of the use of Timer.sleep( 5.0 ) // wait 5s
> in an ops script, in order to wait some seconds.
> I need the deployer to wait some time before executing two commands in an ops
> script, like
>
>
> Component1.start();
> //Sleep here for 5 s
> Component2.start();
>
>
> but I didn't find how to do it actually.
>
> Does anybody have an idea on how to do that?

Adding such timeouts is often an indication of a questionable system
architecture or deployment. If possible, I would recommend getting rid
of such sleeps and instead making the necessary condition for
continuing explicit, e.g. introduce a "ready event" or ready()
operation which you can check in you script.

Markus

--
Orocos-Users mailing list
Orocos-Users [..] ...<mailto:Orocos-Users [..] ...>
http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users

Do you have two components connected to each other through a ROS topic? Why? Why not just connect them using a standard Orocos port, and also publish the OutputPort on a ROS topic for off-board subscribers? This would probably alleviate the need for sleeping all together.

But, this brings up a good question. How do you know when a ROS topic is finished being created/connecting? We have that same issue, and have an arbitrary 1sec sleep to ensure ROS topic-dependent software has a valid connection.

-dustin

On Thu, Jan 17, 2013 at 09:13:44AM -0600, Gooding, Dustin R. (JSC-ER411) wrote:
> On Jan 17, 2013, at 8:33 AM, Markus Klotzbuecher <markus [dot] klotzbuecher [..] ...> wrote:
>
> > On Thu, Jan 17, 2013 at 09:40:34AM +0000, mirko [dot] comparetti [..] ... wrote:
> >> Hi all,
> >> In
> >> [http://www.orocos.org/stable/documentation/rtt/v2.x/doc-xml/orocos-components-manual.html
> >> this manual] there is an example of the use of Timer.sleep( 5.0 ) // wait 5s
> >> in an ops script, in order to wait some seconds.
> >> I need the deployer to wait some time before executing two commands in an ops
> >> script, like
> >>
> >>
> >> Component1.start();
> >> //Sleep here for 5 s
> >> Component2.start();
> >>
> >>
> >> but I didn't find how to do it actually.
> >>
> >> Does anybody have an idea on how to do that?
> >
> > Adding such timeouts is often an indication of a questionable system
> > architecture or deployment. If possible, I would recommend getting rid
> > of such sleeps and instead making the necessary condition for
> > continuing explicit, e.g. introduce a "ready event" or ready()
> > operation which you can check in you script.
> >
> > Markus
> >
> >
> > --
> > Orocos-Users mailing list
> > Orocos-Users [..] ...
> > http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
>
>
> In Mirko's defense,
>
> Sometimes those "ready events" are hard to make. For example, we
> have a logic card that has a status register with a handful of bits
> that indicate whether relays are open or closed. Unfortunately,
> some of those bits trigger almost a full 2 seconds before the actual
> relay has changed its state. Unfortunately, reconfiguring the logic
> card isn't feasible. What we do, instead, is issue a command, check
> that the bits are triggered, and then wait 2 seconds before
> continuing. We're not sure of a better way. Using a one-shot timer
> on the Timer component could work, but we haven't tested it. And it
> would still be for an arbitrary (2 sec) duration.

Yes, buggy hardware is one of the few exceptions :-)

Markus

On Jan 17, 2013, at 10:13 , Gooding, Dustin R. (JSC-ER411) wrote:

> On Jan 17, 2013, at 8:33 AM, Markus Klotzbuecher <markus [dot] klotzbuecher [..] ...> wrote:
>
>> On Thu, Jan 17, 2013 at 09:40:34AM +0000, mirko [dot] comparetti [..] ... wrote:
>>> Hi all,
>>> In
>>> [http://www.orocos.org/stable/documentation/rtt/v2.x/doc-xml/orocos-components-manual.html
>>> this manual] there is an example of the use of Timer.sleep( 5.0 ) // wait 5s
>>> in an ops script, in order to wait some seconds.
>>> I need the deployer to wait some time before executing two commands in an ops
>>> script, like
>>>
>>>
>>> Component1.start();
>>> //Sleep here for 5 s
>>> Component2.start();
>>>
>>>
>>> but I didn't find how to do it actually.
>>>
>>> Does anybody have an idea on how to do that?
>>
>> Adding such timeouts is often an indication of a questionable system
>> architecture or deployment. If possible, I would recommend getting rid
>> of such sleeps and instead making the necessary condition for
>> continuing explicit, e.g. introduce a "ready event" or ready()
>> operation which you can check in you script.
>>
>> Markus
>>
>>