Re: No monitor refresh

[Ralph Lange <Ralph.Lange@bessy.de>]

Hello Hinko,

hm ..... it's an I/O scanned mbbi connected to asyn, and I have no asyn 
experience. (So I'm sort of out-of-the-game at this point.)

Nevertheless - some thoughts:
Your NOBT is zero, but your mask is correct, probably something that 
asyn does for you.
Looked at the record code: An mbbi should definitely send VAL updates 
when it processes and the value changed.
Are you sure asyn gets the value you expect it to into the record? 
(Check by enabling asyn debug.)
Are you sure the record gets processed by asyn when you expect it to? 
(Check by setting the trace field.)
When you set up multiple camonitor clients - do they all behave the same?
When you do intermediate cagets while your camonitor is not getting 
updates, what timestamps are these showing?
(BTW: You only have two states with raw values 0 and 1 defined - any 
particular reason for using mbbi as opposed to bi?)

Someone with more asyn background could probably say more....

Good luck!
Ralph


On Tue 11 May 2010 10:07:12 Hinko Kocevar wrote:
> Hello Ralph,
>
> On 05/11/10 15:21, Ralph Lange wrote:
>   
> > Hello Hinko,
> >
> > what EPICS versions are you using for client and IOC?
> >     
>
> IOC and client use 3.14.10 EPICS base version.
>
>   
> > Can you show a dump (dbpr <name>, 4) of the record that you are
> > connecting to?
> >     
>
> Sure, here it is:
> epics> dbpr LIBERA01:ENV:ENV_AGC_MONITOR 4
> ACKS: NO_ALARM      ACKT: YES           ASG:                ASP:
> 0x00000000
> BKPT: 0x00          COSV: NO_ALARM      DESC: AGC           DISA: 0
>
> DISP: 0             DISS: NO_ALARM      DISV: 1             DPVT:
> 0x50c72c00
> DSET: 0x7c620840    DTYP: asynInt32     EIST:               EISV:
> NO_ALARM
> EIVL: 0x0           ELST:               ELSV: NO_ALARM      ELVL: 0x0
>
> EVNT: 0             FFST:               FFSV: NO_ALARM      FFVL: 0x0
>
> FLNK:CONSTANT 0     FRST:               FRSV: NO_ALARM      FRVL: 0x0
>
> FTST:               FTSV: NO_ALARM      FTVL: 0x0           FVST:
>
> FVSV: NO_ALARM      FVVL: 0x0           INP:INST_IO @asyn(ENV, 725, 1.0)
>
> LALM: 1             LCNT: 0             LSET: 0xe8752e00    MASK:
> 4294967295
> MLIS: 0x38d0320060d0320003000000        MLOK: 0x28700b00    MLST: 1
>
> NAME: LIBERA01:ENV:ENV_AGC_MONITOR      NIST:               NISV:
> NO_ALARM
> NIVL: 0x0           NOBT: 0             NSEV: NO_ALARM      NSTA:
> NO_ALARM
> ONST: AUTO          ONSV: NO_ALARM      ONVL: 0x1           ORAW: 1
>
> PACT: 0             PHAS: 0             PINI: YES           PPN:
> 0x00000000
> PPNR: 0x00000000    PRIO: LOW           PROC: 0             PUTF: 0
>
> RDES: 0xa8a10300    RPRO: 0             RSET: 0x34b70a40    RVAL: 1
>
> SCAN: I/O Intr      SDEF: 1             SDIS:CONSTANT       SEVR:
> NO_ALARM
> SHFT: 0             SIML:CONSTANT       SIMM: NO            SIMS:
> NO_ALARM
> SIOL:CONSTANT       SPVT: 0x388a2f00    STAT: NO_ALARM      SVAL: 0
>
> SVST:               SVSV: NO_ALARM      SVVL: 0x0           SXST:
>
> SXSV: NO_ALARM      SXVL: 0x0           TEST:               TESV:
> NO_ALARM
> TEVL: 0x0           THST:               THSV: NO_ALARM      THVL: 0x0
>
> TIME: 2010-05-11 11:18:40.100440000     TPRO: 0             TSE: 0
>
> TSEL:CONSTANT       TTST:               TTSV: NO_ALARM      TTVL: 0x0
>
> TVST:               TVSV: NO_ALARM      TVVL: 0x0           TWST:
>
> TWSV: NO_ALARM      TWVL: 0x0           UDF: 0              UNSV:
> NO_ALARM
> VAL: 1              ZRST: MANUAL        ZRSV: NO_ALARM      ZRVL: 0x0
>
>
>   
> > What field of that record are you connecting to?
> >     
>
> I did no specify any field - so it is VAL, I guess by default.
>
> Thank you!
>
> Regards,
> Hinko
>
>   
> > Regards,
> > Ralph
> >
> >
> > On Tue 11 May 2010 6:26:48 Hinko Kocevar wrote:
> >     
> > > Hi all,
> > >
> > > I'm experiencing some strange behavior when using camonitor against an
> > > EPICS IOC.
> > >
> > > For some reason a CA_PROTO_EVENT_ADD response from IOC to CA client does
> > > not arrive, or arrives several minutes later after the PV value has
> > > changed. Note that first CA_PROTO_EVENT_ADD response is seen always,
> > > only latter CA_PROTO_EVENT_ADD responses do not arrive (or arrive late)?!
> > > This behavior is not seen always - sometimes the IOC would promptly
> > > respond with CA_PROTO_EVENT_ADD response when needed.
> > >
> > > I can see the CA_PROTO_ECHO requests/responses fine on the same
> > > camonitor channel link, only CA_PROTO_EVENT_ADD response is not seen.
> > >
> > > Inspecting the IOC I can see that the value did change (on lower levels)
> > > and caput response is also valid - updated with new value.
> > >
> > > I've ruled out the network problems, since the issue is raised even when
> > > using cross-over cable to communicate with the IOC. Actually even I
> > > update the value in the IOC shell, the camonitor is not refreshed!!
> > >
> > >
> > >
> > > Has someone experienced something similar?
> > > Are there some conditions that need to fulfilled in order for IOC to
> > > send a subsequent CA_PROTO_EVENT_ADD response(s)?
> > >
> > >
> > >
> > > TIA & HAND,
> > > Hinko
> > >       
>
>
>