Emerson Exchange 365

• Not Answered

PCSD OAR Composite v13.0.1. Issue with default response after timeout.

Hi

I have a problem with the OAR composite in a phase when I set the ACTION as Continue, with a default response (DEFAULT) after timeout (TIME).

e.g.

TYPE = INT no limits

ACTION = Continue

DEFAULT = 2

VERIFY = None

TIME = 60

This works fine when the phase is run from the unit faceplate but does not work when the phase is run from the BOI.

When the phase is run from the BOI the DEFAULT is not copied to the INPUT and the OAR does not reset.

Is this a known issue with the composite? Has anyone found a work around?

Many thanks

Colm

• DeltaVBatch

Colm Crowley

• 1 Dec 2020 11:45 AM
• Cancel

3 Replies

• vmvmhatre

  

  • 1 Dec 2020 3:15 PM

  What is default value of configurable parameter OAR_OPTION ? it should be 'BOI if available' to work in both cases.
  
  Do phase configured default value correctly displayed on Prompt as default value ?
  Do REQUEST parameter returns 0 (zero) after sending abort request '6000' after timeout ?
  
  Default value gets cleared from PROMPT_INT parameter and only available in OAR/INPUT parameter for phase logic to read.

  • Cancel
• Colm Crowley

  

  • 2 Dec 2020 9:18 AM

  In reply to vmvmhatre:

  Thanks for your response. If you have time please look at screenshots below..

  1. Setup with 30s timer. Default answer = 20.

  

  2. 30s expired. Type not reset to None. Input not equal to default in first screenshot. 

  

  Please let me know what you think.

  I have tracked REQUEST in Watchit. After the 30s the Request value is 6000, 10, 0, 3201.

  

  • Cancel
• vmvmhatre

  

  • 3 Dec 2020 5:29 AM

  In reply to Colm Crowley:

  From Screenshots its looks like a second request (REQUEST = 3201) is incorrectly getting send after abort request (REQUEST = 6000) is served by BE. This may be due to TYPE parameter is not immediately set to None (1) and is set after confirming REQUEST = 0. This may happen due to timing of phase execution and timing of BE serving request.
  
  I am suggesting to contact PCSD to check this issue is replicating at their end and any code update or configuration change is required.

  • Cancel