You must run the Simulate Conversion function on the workstation before you run your simulation if your configuration contains: Function Blocks that have been assigned to a fieldbus device
Parameters and function block expressions that directly reference I/O channels
The Simulate Conversion function converts modules in the database so that fieldbus blocks and I/O references can be simulated for operator training and control system checkout. Function blocks that have been assigned to fieldbus devices are replaced with their equivalent DeltaV blocks. The block name, parameter values, and links to other blocks are preserved. If an equivalent block does not exist, as is the case for the FFMAI block, a composite block is substituted to support off-line simulation in Operator Interface and Control Studio. Parameters and function block expressions that perform I/O references are converted to external parameter references. When the Simulate Conversion command is run, a module named M_nodename is automatically created under the workstation's Assigned Modules container. M_nodename is populated with parameters that are referenced by the converted modules' parameter and function block expressions' I/O references.
Modules can be downloaded to the workstation after conversion. Converted function blocks perform just like blocks assigned to fieldbus. For example, the logical and dynamic behavior of converted blocks is the same as assigned blocks. To simulate values that would normally be supplied through the I/O, the user or process simulation application can write to the newly created external parameter references that replaced the original I/O references.
To access the Simulate Conversion command, select the workstation to which modules have been assigned in the DeltaV Explorer and select Simulate Conversion from the context menu.
Simulate Conversion Command in DeltaV Explorer
After the Simulate Conversion command is run, Control Studio can be used to view the changes made in the module. The assigned modules must be downloaded to view the converted module operation in Operator Interface, Control Studio, or SimulatePro.
Note: The Simulate Conversion process modifies the modules in the simulation system database. No utility is provided to reverse this
conversion. The simulation system should be created from a copy of the actual system configuration. The following sections provide more detail on the conversions.
Converting Blocks Assigned to Fieldbus Devices
Modules that contain function blocks such as AI, PID, AO that are assigned to a fieldbus device will not execute in DeltaV SimulatePro. The Simulate Conversion command converts these blocks to the equivalent DeltaV function block so they will execute in SimulatePro. The following example shows the impact of a conversion on blocks assigned to fieldbus devices.
Blocks Assigned to Fieldbus Converted to Equivalent DeltaV Blocks
If a module contains fieldbus blocks for which no equivalent DeltaV block exists, the fieldbus blocks are replaced with composite blocks that support execution in a simulation environment. For example, the fieldbus function blocks FF_MAI, FFMDI, and FFMDO have no equivalent DeltaV blocks. Therefore, the Simulate Conversion command substitutes the composite blocks MAI_SIM, MDI_SIM, and MDO_SIM for the fieldbus function blocks. Modules containing the substituted composite blocks cannot be accessed online using the SimulatePro interface. The composite blocks that support the conversion reside in the Simulation folder in the DeltaV Explorer Library's Composite Templates container.
The simulation composite blocks are designed for use in a simulation environment only and are not meant for use in an online system.
Simulation Composite Blocks
The converted blocks contain SIMULATE_INx parameters that can be used to set the simulated OUTx parameters. The following images shows a module containing fieldbus blocks before and after conversion. Notice the SIMULATE_INx parameters after conversion and also notice that the block names and connections between parameters are not changed by the conversion.
Module After Conversion
After conversion, a process simulation tool can write to the SIMULATE_IN parameters and simulate the value and status that is normally provided by the I/O.
Parameters and function block expressions such as a Calc/Logic block expression that directly references I/O channels will have Bad status when the associated module is assigned to a workstation. Also, the value and status cannot be written. The Simulate Conversion command allows these parameters to be used for training and checkout. The conversion changes the I/O references to parameter references. A module called M_nodename that contains the reference parameters is automatically created on the workstation. Nodename is the name of the workstation on which the conversion command executed.
Note: The name of the module that is created by conversion is limited in length to 16 characters. Make sure that the node names in your
configuration that will be converted will result in unique module names after truncation (if the workstation name is longer than 14 characters). Also, the references must refer to valid existing I/O parameters in the database before you run the conversion
For example, if a module assigned to the node NIGHTENGALE contains the parameter MYREF1, an I/O reference to
CTLR2/IO1/CH05/OVERRANGE_PCT, after conversion this I/O reference parameter is changed to an external parameter reference. For this example, the path to the reference parameter is set to M_NIGHTENGALE/C02CH05OVERRAN1. The name of the parameter referenced in M_NIGHTENGALE is automatically created from the original I/O path definition (slashes are removed and the controller, card, channel, and parameter names are combined and shortened to 16 characters and given a unique name). After the I/O reference is converted, applications can read or write the converted external reference parameter to simulate the values and status normally provided by the I/O. The referenced parameters are automatically defined in the M_NIGHTENGALE module and can be accessed online using the SimulatePro interface.
Module Containing I/O References Before Conversion
The following image shows the impact on the blocks after the Simulate Conversion command is run on the workstation that contains this module.
Module Containing I/O References After Conversion
These converted I/O references can be accessed by examining the M_Nodename module or by selecting the IO Reference tab in the SimulatePro application as shown in the following figure.
SimulatePro View of Converted I/O References
Creating a Training System
To create a training system from a configuration with fieldbus function blocks or parameters or function block expressions that reference I/O, you must run the Simulate Conversion command once on every node. If new modules are added to the node, the Simulate Conversion
command can be re-run and any new parameters created to replace I/O references will automatically be added to the existing M_Nodename module.
Note: The conversion modifies the configuration database on the workstation. SimulatePro does not include a utility to convert training
system files back. The Simulate Conversion is a one way transfer in which the actual system configuration is always the master configuration. The training system configuration can always be easily and quickly created from the actual configuration using the Simulate Conversion utility.