Experimental Physics and
Industrial Control System

"Szalata, Zenon M." <[email protected]> · Thu, 7 Jul 2011 09:14:32 -0700

Hi John,
I tried readback pv, but it seems to make no difference.
Presently I have a solution, I think.  I am using record A in visibility of button B.  In addition I have superimposed a filled rectangle with visibility based on record A.  This way, when record A is false, the toggle button B is visible and when it is false the rectangle superimposed on toggle B is visible.  This seems enough to enforce control rules for these two records when accessed from the EDM screen.  Record processing is still controlled using DISV and DISA in record B, which is needed to enforce proper processing via CA.
Ned, your reply just came in and I will look at it.

Thank you all,
Zen

> -----Original Message-----
> From: John William Sinclair [mailto:[email protected]]
> Sent: Thursday, July 07, 2011 8:08 AM
> To: Szalata, Zenon M.
> Subject: Re: EDM and record processing
> 
> Zen,
> 
> Try configuring the buttons to use control and readback pvs. The pvs
> will be the same, i.e.
> 
> control pv for button 1 will be BO:A
> readback pv for button 1 will be BO:A
> 
> control pv for button 2 will be BO:B
> readback pv for button 2 will be BO:B
> 
> Best,
> John Sinclair
> 
> Szalata, Zenon M. wrote:
> > This is resend of a previously sent question.  Subject is now added and a
> comment at the end.
> >
> > I have a few pairs of bo records.  For simplicity let's consider only one pair,
> record A and record B.  The requirement is that if A is true, then B is not
> allowed to process.  When A is false, then B can process.  In addition, I also
> have an EDM screen with two toggle buttons; toggle A control record A and
> toggle B controls record B.
> > This is how I attempted implementing this:
> >
> > record( bo, "BO:A"){
> >   field( ZNAM, "off")
> >   field( ONAM, "on")
> >   field( FLNK, "DF:A")
> >   field( PINI, "YES")
> > }
> > record( dfanout, "DF:A"){
> >   field( DOL,  "BO:A")
> >   field( OMSL, "closed_loop")
> >   field( OUTA, "BO:B.DISA")
> > }
> > record( bo, "B"){
> >   field( DISV, "1")
> >   field( ZNAM, "off")
> >   field( ONAM, "on")
> > }
> >
> > This record set seems to works correctly.  The communication between the
> EDM buttons and the records does not work correctly, at least from my point of
> view.  This is what I see:
> >
> > I start the test IOC and an EDM screen.
> > Both A and B records are in false state.
> > I set A to true by clicking on toggle button A.  DISA is set to 1 in record B.  So,
> now both DISV and DISA are 1 and the record now does not process.
> > However, I click on toggle B and button goes to an on visual state, this
> conveys wrong information to the operator.
> > If I click toggle B again, the visual state does not change.
> > This behavior is observed each time toggle A changes from off to on.
> > It is actually worse than that.  Clicking on B to put it in on state while A is off,
> then clicking on A to put it in on state, leads to a badly confused state of record
> B and toggle B, when toggle B is clicked again.  In this case the visual aspect of
> toggle changes to off, record B does not process and still is in true (on) state.
> >
> > My goal is to provide operators with an EDM screen such that when record A
> is in true (on) state, then record B will not process, but also that this denial of
> processing will be reflected in the visual representation of the toggle button
> that controls record B.
> >
> > I first tried this with two bo records, where in record B I put SDIS link to get
> the value from record A.  The results were the same.
> >
> > Any suggestions on how to overcome this difficulty, or some different
> approach which produces correct results, are most welcome.
> > Thanks in advance,
> > Zen
> >

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System