DeltaV Zone 2 / Zone 1 IO Simulation with the DeltaV Simulate OPC SIO Driver

This application note describes the steps required to use the DeltaV Simulate OPC SIO Driver for DeltaV Zone 2 / Zone 1 Remote IO.

Users of  DeltaV Zone 2 Remote IO as an alternative to the procedure below can use the Virtual IO Module with the DeltaV Railbus SIO Driver, MM3-2101,  for direct IO simulation.  Because the DeltaV Zone 1 Remote IO does not support the VIM , the procedure below is the only solution for simulation of this IO system.  For additional information, please see the application note on MiMiC Simulation for DeltaV Zone 1 and Zone 2 Remote IO.  This procedure describes the use of Option 3 in that application note: using the DeltaV Simulate OPC SIO Driver, MM3-2102.  This solution has some disadvantages including:

• MiMiC Simulated IO are driven to the module level of the DeltaV configuration.  No simulation through IO assignments is possible.
• Each Zone 2 or Zone 1 Remote IO file will exist (and need to be started) in MiMiC as a separate node.  There is a limit of 32 running Nodes in any MiMiC system.
• In order to run direct (DeltaV Railbus) IO and remote IO at the same time, both the DeltaV Simulate OPC SIO Driver, MM3-2102, and the DeltaV Railbus SIO Driver, MM3-2101, must be licensed to the system.
• The DeltaV Input modules (AI, DI) will need to run in Simulate mode.

The advantages of this solution include

• No modification to the DeltaV configuration is required.
• The auto-generation of SIO Tags and low level models (IO and Tiebacks) is handled completely by the DeltaV Database Generator Utility in MiMiC.

Procedure for Setting up the Simulation

1. Do a complete, top level export of the DeltaV system.  Ideally, the DeltaV database will be fully configured, ready for install in the live plant system.
2. Generate the MiMiC Database using the MiMiC 3.x Database Generator, following the procedures found in Using MiMiC, DeltaV FHX Utility Guide, in the MiMiC Online Web Help.  Be sure both the Generate VIM IO Definition and Generate OPC IO Definition options are checked under Database Generation, Options.
3. Open the MiMiC Database generated by the utility in MiMiC Explorer.  Each DeltaV Zone 2 or Zone 1 Remote IO controller will have a Node generated in the Simulation Database Section with a corresponding OPC_IODef in the IO definition section.
4. Start the controller Node in MiMiC Explorer with the VIM_IODEF generated by the utility for that node.  The VIM should be commissioned beforehand following the procedure in the Using MiMiC, DeltaV VIM Setup Guide of the MiMiC Online Web Help.  This should start all simulation of DeltaV controller local IO and the IO models used for the Remote IO nodes.
5. Start the Zone 2 or Zone 1 Remote IO Node in MiMiC Explorer with the OPC_IODef generated by the utility for that node.  Change the name of the SERVER_MACHINE to the DeltaV Simulate PPN or ASN node (or the DeltaV Simulate Standalone workstation)that is being used as the OPC Server of the system.  Once the node starts MiMiC should begin driving Simulated IO values to the DeltaV configuration on the workstation.  The IO models in the MiMiC controller Node will read their SIO tag data from the remote IO Node automatically.  The MiMiC to DeltaV Simulate communications should be setup following the procedure in the Using MiMiC, DeltaV Simulate Setup Guide of the MiMiC Online Web Help. 
6. When the use of the simulation is complete the user can use the DeltaV configuration in the production system without making any changes.