Experimental Physics and
Industrial Control System

Hello,

 

Can somebody remind me about timestamp handling with monitors?

Namely, we see the following behaviour:

 

caget  -a <record>  

and

pvget <record>

and

camonitor <record>

 

give the same timestamp, but

pvmonitor <record>

 

gives a different one, rather far in the past.

The record in question is a sequence record. VAL has no other meaning there except causing the record to process, right? VAL of the record in question is always null.

Thus, there are no monitor updates (as far as I have seen).

 

Interestingly enough, when I do pvmonitor <record>.VAL, I get the same timestamp as with the three other methods.

 

I was asked why this happens but I could not figure out the reason. I vaguely remember some discussion on this but could not find any hints.

 

Timo