Emerson Exchange 365

DeltaV SIS CSLS Simulation - V13 Limitations

I am working on a project that will include DeltaV SIS CSLS.  I will be using a third part simulation software for testing.  The DeltaV system is currently on Version 13.3.1 and will likely stay that way for the near future.

While working with the simulation software to do the initial setup of the test system I ran into an issue.  Apparently in Version 13, there is an limit that does not allow OPC writes to SIS IO or function blocks.  I did a test on a Version 14 and was able to write with no issues.   This snippet is from the DeltaV SIS Electronic Marshalling product datasheet and appears to confirm what was discovered today: 

I/O Simulation

Once the virtual CSLS is commissioned, you can simulate CSLS inputs by writing to the simulation parameter in the SIS input blocks. Starting DeltaV v14, it is also possible to simulate input signals and read output signals either via an out-of-the box application or OPC. DeltaV SIS only allow I/O simulation on virtual CSLS which reduces cyber security threats. To fully decouple software and hardware design, users could simulate values based on the signal name (Device Signal Tag or DST). It is no longer necessary to wait until the physical design is completed and the physical address of the signal is known. 

This has definitely put a snag in my plans.  I am reaching out to see if there is any known work around or change I could make to allow the simulation software to fully interface with a V13 DeltaV SIS CSLS system.

Thanks for any help you can provide.

Greg Bayne

• 12 Apr 2022 10:05 PM
• Cancel

2 Replies

• Cedric Dawnhawk

  

  • 13 Apr 2022 2:52 PM

  Although you can't write to the I/O simulate fields programmatically you can write to non-secure parameters. On a fairly simple job for a v13.3.1 system I used an LSCALC block inserted in each SIS module.The LSCALC block had non-secure parameters wired to its inputs and the LSCALC expression simply wrote the values of the inputs to the simulate fields.
  
  Not sure if this is of any help.
  
  Andrew

  • Cancel
• Tadeu Batista

  

  • 13 Apr 2022 5:41 PM

  Hi Greg,
  
  OPC Simulation directly at the CSLS IO or TAG (DST) is part of v14.
  
  Cedric already mentioned an option to go around it, which is writing to Non-Secure parameter, and using the LSCALC to transfer the variable from the Non-Secure parameter to the Simulated value on the LS Input Function Block.
  
  Couple of points to consider:
  - The simulation shall be enabled on function block, it can be done from the LSCALC
  - Variable will be transferred from the non-secure parameter to the SIMULATE.SVALUE of the input block
  - At the end of the test, simulation shall be disabled on the input function block
  -The LSCALC and non-secure parameters shall be removed, what will change the CRC.
  
  Rgs,

  • Cancel