• Not Answered

Operator Entered Values

I am using Data Entry Expert to allow operators to enter lab values into the deltav system. After a value is entered, I have several actions that I want to perform. Currently I am using a simple comparison block to compare the old value to the new value, if they are different, the actions take place and then I set the new value to the old value. The problem is that sometimes the old value and new value are the same but I still want the actions to take place. Is there some function within the data entry expert that I can use to determine if the OK button has been clicked?

3 Replies

  • The DeltaV Data Entry Expert writes a script, which you can change to
    extend.
    So write also to an extra boolean parameter which you connect to an ACT
    block. This ACT block can do the required actions, and reset the boolean
    parameter.

    -----Oorspronkelijk bericht-----
    Van: tklatt [mailto:bounce-tklatt@community.emerson.com]
    Verzonden: dinsdag 19 november 2013 17:31
    Aan: DeltaV@community.emerson.com
    Onderwerp: [EE365 DeltaV Track] Operator Entered Values

    I am using Data Entry Expert to allow operators to enter lab values into the
    deltav system. After a value is entered, I have several actions that I want
    to perform. Currently I am using a simple comparison block to compare the
    old value to the new value, if they are different, the actions take place
    and then I set the new value to the old value. The problem is that sometimes
    the old value and new value are the same but I still want the actions to
    take place. Is there some function within the data entry expert that I can
    use to determine if the OK button has been clicked?

  • In reply to Maarten van der Waal:

    I have put a boolean parameter in the subscript of the data entry expert and linked it to an action block. The only trouble is that every time the data entry expert script runs, the actions occur even if the operator presses cancel or x's out of the expert. I am interested in only having it do the actions when OK is clicked. In other words, the compaison has troubles with a false negative and the script has troubles with a false positive.

    Thank you

  • In reply to tklatt:

    Probably easiest to do while keeping most of the actions in control studio is to:

    • Write to say a parameter "OP_ENTRY" which defaults to say -999.  
    • Have a condition block that looks for this to be not equal to -999.
    • Do a PDE into ACT block.
    • Do whatever you want to do in the an ACT block.  You can write the OP_ENTRY to stored parameters, do an shifts in parameters, etc.  However, at the end of it, write it back to -999.  

    It's just a quick way to see something has written to it while having a built in reset in control studio.