String prompt OAR with null entry

Is there a way for the out-out-the-box OAR for the BOI to ask the question again for a prompt that requires a string input and the operator acknowledges the prompt without giving an input? In this case, the logic is stuck.

  • No, you will have to check the answer and re-ask the prompt within your Phase logic.

    Not sure what you are prompting for but sometimes using numbers to interpret might be better (i.e. Enter 1 for RX1, 2 for RX2,) than entering a string because the DeltaV controller can't do string manipulations (i.e. UCase).
  • In reply to Matt Stoner:

    In this case, the operator is entering a serial number for a removable part (and needs to be recorded in the batch event journal), so using a string is the only option that I'm awareof. If the operator acknowledges the prompt without writing a string, the logic gets stuck. Unfortunately there are a lot of string OARs, so I would have to have a separate step for each OAR, right? Instead of having multiple OAR actions in a single step.
     
    Confirm expression:
    /OAR/OAR_STATUS.CV = '_OAR_STATUS:NONE'

    Is there a parameter that captures if the prompt was answered? In that case, I could have something like "prompt was answered and entry is null"


    As a side note, it would be nice to have a drop down menu with a named set values (RX1,RX2) , instead of having an operator type 1 for RX1, 2 for RX2, etc.

  • In reply to rhamlin:

    The native prompt's in the DeltaV batch application are quite simple and do not have the features that you and many other new users are looking for. Most large installations that have been implemented have developed a custom prompt (OAR) functionality that leverages the graphics vb capability of DeltaV to allow for nameset dropdowns, error checking and other custom features that are not part of the basic function of the DeltaV batch engine. The prompting has remained the same since the earliest versions of DeltaV and is what it is for the time being.

    Given that and your suitation that you want to implement a simple solution for a serial number entry with checking you have a few possibilities.
    1. Set REQDATA1 to non zero. This will require that the prompt is verified by username and password. Setting REQDATA2 to non zero will require an additional verification and security can be set so that a supervisor verifies this. This would still allow a null prompt but having two people sign for the answer may drastically reduce input of incorrect answers.
    2. The second possibility that comes to mind would be having a PART_ID parameter in the unit and if it is blank then displaying a message to tell the operator to record the part number in the unit (via a graphic on the unit display) . Once that parameter is not null allow the phase to continue and have a prompt as a boolean to allow the operator to confirm the part number is correct (Part number should be included in the prompt text). You can then use a report parameter to record the value into the Batch event journal.

    Point is here that the native functionality of the application is fixed and you have to work around it to achive what you need.

    Steve Linehan