Emerson Exchange 365

Configured values for DCC block not getting passed to controller after download Version 13.3.1

We are experiencing an issue with the I_DELAY_ON parameters in the new DCC block in Version 13 where the values configured in the database are not being passed to the controller. No matter what we change the value to in the database, when downloaded the online value remains at 0. Additionally, we can change the value in online mode and after being downloaded again, the parameters will hold on to the value they were changed to in online mode even while choosing not to upload the parameter values. I checked the download script in the powerup directory to verify that it contains the correct values configured in the database and it does. But it still is not getting passed to the controller. Note this is on a development system and we are using a SVIRTUAL controller.

Has anyone else experienced this problem?

Steven Estes

• 11 May 2017 6:48 PM
• Cancel

6 Replies

• IntuitiveNeil

  

  • 11 May 2017 7:12 PM

  Try checking the parameter download behaviour  for your module.

  One of the settings means it never takes the configured value. Cant recall which it is without looking but this behaviour is what you get

  The smart switch modules have the parameter download behaviour set that way.

  • Cancel
• IntuitiveNeil

  

  • 11 May 2017 7:19 PM

  In reply to IntuitiveNeil:

  Here you are
  
  Possibly those DCC parameters are classified as critical block parameter
  
  
  Below extract from DeltaV BOL:-
  
  "Parameter download behavior
  
  Select the download behavior. The choices are:
  
  Preserve critical block values - The controller copies critical function block values from the executing module to the new module during a download. This selection typically minimizes disruption to the process.
  
  Preserve user-defined and critical block values - The controller copies user-defined parameter values from the executing module to the new module during a download in addition to copying the critical function block values. Make sure to use this value if any parameters reference OPC Mirror data. If this is not selected the parameter values will change to their configured default after download rather than retaining the value from OPC mirror.
  
  Use configured values - The controller does not copy any parameter values from the executing module but uses the values from the configuration database. "

  • Cancel
• Matt Stoner

  

  • 11 May 2017 7:20 PM

  In reply to IntuitiveNeil:

  I was about to type exactly the same when I saw the post pop up....
  
  The setting that will never use configured values is "Preserve user-defined and critical block values", it essentially just downloads new parameters (or probably changes of type - FP,Int, Bool, etc) and logic.
  
  For more info on this, Books Online -> Configuration -> General Configuration -> Downloading data

  • Cancel
• Steven Estes

  

  • 11 May 2017 7:45 PM

  In reply to IntuitiveNeil:

  Thank you both for the response. I checked in BOL and the Delay on and Delay off parameters of the DCC block are critical block parameters. I changed the download behavior to "use configured values" and it worked.

  • Cancel
• Steven Estes

  

  • 11 May 2017 8:10 PM

  In reply to Steven Estes:

  Although I am confused as to why the set points for the on and off delays are considered critical block parameters. It makes sense for the timers to be (I_timer1, etc.) but I am not sure why the time set points are.

  • Cancel
• SBPosey

  

  • 15 May 2017 6:07 PM

  I agree with this. We don't have v13 yet (our next upgrade will probably be to v14), but I hope that when we do our next upgrade, the delay values (not the timers) have been removed from the Critical Parameters list.
  In version 12.3, none of the other DELAY_ON/DELAY_OFF parameters are Critical. The CND block's TIME_DURATION is listed in BOL 12.3 as being critical, but it is not (just tested again, to be sure).
  
  
  
  

  • Cancel