Re: PV Seq not process everytime

[Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>]

On Wed, 9 Feb 2022 at 09:02, GAGET Alexis via Tech-talk <tech-talk at aps.anl.gov> wrote:

record(ao, "myPV1"){

}

record(seq,"mySequence"){

     field(DLY1,"0")

     field(DOL1,"myPV1 CP")

     field(LNK1,"mySetPoint PP")

     field(DLY2,"0.5")

     field(DOL2,"1")

     field(LNK2,"myCommand PP")

}

myPV1 is the destination i want to reach, each time I change it, it process this sequence to set the destination in mySetPoint, and 0.5s later to activate the command. It works well most of the time. But yesterday sometimes, myPV1 was changed but mySequence was not processed .... it causes the whole sequence (emittance measurement) to get stuck. It can be unstuck by processing "mySequence" but it's a long sequence and we don't stay in front of the computer.

Hi Alexis,

CP input links are using monitors. If you have a myPV1.MDEL setting, it could suppress changes to be sent to mySequence.

Unless you have a specific reason to use a CP inlink, you could also set myPV1.FLNK to point to mySequence. That would make this a very tight coupling, with the sequence being run basically as part of changing myPV1. (Remove the CP in mySequence.DOL1 in that case.)

Cheers,
~Ralph