Re: Get timestamp from another IOC

[Adrian Martinez via Tech-talk <tech-talk at aps.anl.gov>]

Hello, 

Thanks for all!! Finally, I've solved the problem using any other PV which was being updated. 

Like you said, if the VAL field doesn't update, timestamp value will not update.

Regards, Adrián.

El mié, 16 jun 2021 a las 17:39, Johnson, Andrew N. (<anj at anl.gov>) escribió:

Hi Adrian,

On Jun 16, 2021, at 9:49 AM, Adrian Martinez via Tech-talk <tech-talk at aps.anl.gov> wrote:

I've used 'dbr' command on IOC1 and this is the out for Timestamp_from_IOC1:

ioc > dbpr MBT-RBN:TMG-EVR-01:Timestamp_from_IOC1 10

ACKS: NO_ALARM      ACKT: YES           APST: On Change     ASG:                
ASP: (nil)          BKPT: 00            DESC:               DISA: 0            
DISP: 0             DISS: NO_ALARM      DISV: 1             DPVT: 0x153cf30    
DSET: 0x7f5fc4122160                    DTYP: Obj Prop string                  
EVNT:               FLNK:DB_LINK MBT-RBN:TMG-EVR-01:TimeErr-I                  
INP:INST_IO @OBJ=EVR-MTCA, PROP=NextSecond                  LCNT: 0            
LSET: 0x1410530    
MLIS: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00              
MLOK: f0 85 50 01 00 00 00 00           MPST: On Change    
NAME: MBT-RBN:TMG-EVR-01:Timestamp_from_IOC1   NSEV: NO_ALARM      NSTA: NO_ALARM      
OVAL: Sun, 07 Feb 2106 06:28:16         PACT: 0             PHAS: 0            
PINI: NO            PPN: (nil)          PPNR: (nil)         PRIO: LOW          
PROC: 0             PUTF: 0             RDES: 0x1242bc0     RPRO: 0            
RSET: 0x7f5fc3ca6560                    SCAN: 1 second      SDIS:CONSTANT      
SEVR: NO_ALARM      SIML:CONSTANT       SIMM: NO            SIMS: NO_ALARM      
SIOL:CONSTANT       SPVT: 0x1558ce0     STAT: NO_ALARM      SVAL:              
TIME: 2021-06-16 14:47:16.997443401     TPRO: 0             TSE: 0              
TSEL:CONSTANT       UDF: 1              UDFS: INVALID      
VAL: Sun, 07 Feb 2106 06:28:16  

The SCAN field is 1s, VAL field never changes but the TIME field of the PV does.

That explains why your source record isn’t getting a new timestamp then; the TSEL link actually sets up a CA monitor on the VAL field, so if that monitor never updates it will never get a new timestamp value.

If you set the MPST field of the above record to “Always” it will cause every process to generate a monitor update, which will update your other records.

- Andrew

-- 

Complexity comes for free, simplicity you have to work for.

--

Adrián Martínez Embedded Software Engineer	Seven Solutions
Mail: adrian.martinez at sevensols.com www.sevensols.com

 This e-mail and any materials attached hereto, including, without limitation, all content hereof and thereof are confidential and proprietary to Seven Solutions,S.L and/or its affiliates, and are *confidential*. Without the prior written consent of Seven Solutions, this content may not (i) be disclosed to any third party, (ii) be reproduced, modified or otherwise used by anyone other than current employees of Seven Solutions or its affiliates. If you are not the intended recipient or if this message has been received in error, please notify us immediately via e-mail and delete it.