Re: More precise timing for record processing

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

Hi Alex,

I think you could do it with a seq record something like this:

record(seq,"BL0:mytimer")

{

        field(DLY1,"2.7")

        field(DOL1,"1")

        field(LNK1,"BL0:mytrigger.PROC")

        field(FLNK,"BL0:mytimer")

}

I have not tested it.

Mark

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Sobhani, Alex via Tech-talk <tech-talk at aps.anl.gov>
Sent: Sunday, May 28, 2023 8:35 PM
To: tech-talk at aps.anl.gov <tech-talk at aps.anl.gov>
Subject: More precise timing for record processing

 

The SCAN field lets you choose from .1, .2, .5, 1, 2, 5, or 10 seconds. In cases where this is not enough, is there a simple way to make a record process at other intervals such as 2.7 seconds or 5.4 seconds, specified at runtime? I know you can add options for more periods of the SCAN field by editing dbd files, but you cannot change your mind at runtime.

 

I envision something like this:

 

record(timer, “BL0:mytimer”){

                field(PERI, 2.7)

                field(FLNK, “BL0:mytrigger”)

}

 

And then subfields to enable/disable it.  

 

Does anything like this exist? I would imagine that something like this would be very generally useful.

 

Alex