Experimental Physics and
Industrial Control System

"Kalantari Babak" <[email protected]> · Sat, 5 May 2007 16:47:35 +0200

> -----Original Message-----
> From: Denison, PN (Peter) [mailto:[email protected]]
> Sent: Freitag, 4. Mai 2007 13:10

> Of particular
> importance is the period during startup that may be before the time
> provider has been fully initialised, but after you've registered it.

Right! The EventTime driver takes care of this. The first thing is that
it does its registration at the end of iocInit (InitHookAtEnd) to let
the required hardware be initialized. Secondly the EventTime becomes
valid when the first sync event occurs. During this the actual time
provider is normally NTP time provider of generalTime.     

> We've just seen a couple of instances where an IOC deadlocked during
> iocInit, because a streamDevice protocol @init handler was waiting for
an
> asyn input timeout, but for some reason the EVR had not been properly
> configured and time wasn't ticking. I'm looking forward to being able
to
> try out generalTime.

I have seen similar effect with drvTS but not with generalTime.

> Although it's not very elegant, the EventTime driver could just use
the
> "first-configured" EVG/EVR in the system. 

It does exactly so. In the drvTS it was even less elegant as it only
could work with card number zero. The current version of EventTime takes
the first configured card irrespective of the card number. 

Babak

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System