Virtual DPU Simulation

User’s Guide

278707 Rev. E1
 Refer to this publication for complete and accurate information that helps you better operate and service Valmet.
Your comments and suggestions are welcome

Valmet
2750 Morris Road
Lansdale, PA 19446

Attention: Manager, Technical Publications

Copyright 2020 Valmet, Inc.

This document is the exclusive intellectual property of Valmet, Inc. and/or its subsidiaries (collectively “Valmet”) and is
furnished solely for operating and maintaining the supplied equipment and/or software. Use of the document for any
other project or purpose is prohibited. All copyrights to the document are reserved by Valmet. Accordingly, the
document or the information contained therein shall not (whether partly or entirely) be reproduced, copied or disclosed to
a third party without prior written consent of Valmet.

Printed in the United States of America

All Rights Reserved

Valmet • 278707 •
ii
Contents
Preface ............................................................................................................................................ v

Chapter 1 ..................................................................................................................................... 1-1

Introducing Simulation ............................................................................................................... 1-1

Overview ............................................................................................................................................... 1-1

maxDNA Software Backplane (SBP) ..................................................................................................... 1-1
Buffers in Simulation ............................................................................................................................. 1-2
Multiple Virtual DPUs ........................................................................................................................... 1-2

Chapter 2 ..................................................................................................................................... 2-1

Software Backplane and Virtual DPUs ...................................................................................... 2-1

Software Backplane Interface ............................................................................................................... 2-1

Chapter 3 ..................................................................................................................................... 3-1

I/O Buffers in Simulation ............................................................................................................ 3-1

Analog Input Buffer (AIB) ................................................................................................................... 3-1

Analog Output Buffer (AOB) ............................................................................................................... 3-2
Counter Buffer (CB) ............................................................................................................................. 3-2
Digital Input Buffer (DIB) .................................................................................................................... 3-3
Digital Output Buffer (DOB) ................................................................................................................ 3-3
Pulse I/O Buffer (PLSIO) ..................................................................................................................... 3-4
Output Driver Buffer (OD) ................................................................................................................... 3-5
Positioner Buffer (PB) .......................................................................................................................... 3-6
QUAD PAT Buffer (QUADPAT) ........................................................................................................ 3-6
RTD Buffer (RTD) ............................................................................................................................... 3-7
TC Buffer (TC) ..................................................................................................................................... 3-9

Chapter 4 ..................................................................................................................................... 4-1

Virtual DPUs in Simulation ......................................................................................................... 4-1

Operators Stations Connected to the Simulation Station...................................................................... 4-2

Simulation Station Configuration And Setup ....................................................................................... 4-3
Simulation DPUs Shortcut and Setup ................................................................................................... 4-4
DPMS Attributes of RunStop, Scenario, and Timewarp ...................................................................... 4-4
Version 4 Configuration of Simulation DPUs ...................................................................................... 4-5

Valmet • 278707 •
iii
Virtual DPU Simulation

Version 6 Configuration of Simulation DPUs ...................................................................................... 4-8

Chapter 5 ..................................................................................................................................... 5-1

Example of Setting Up Virtual DPUs in Simulation .................................................................. 5-1

Chapter 6 ..................................................................................................................................... 6-1

Simulating Virtual Link DPUs .................................................................................................... 6-1

Chapter 7 ..................................................................................................................................... 7-1

SimConsole for Virtual DPUs ..................................................................................................... 7-1

Setting up SimConsole Virtual DPUs ................................................................................................... 7-3

Setting up SimConsole .......................................................................................................................... 7-7
Starting SimConsole ............................................................................................................................ 7-10
Simulation Functions........................................................................................................................... 7-11
Maintenance Menu .............................................................................................................................. 7-14
Edit Scenarios......................................................................................................................7-14
Delete Snapshots .................................................................................................................7-15
Backup Simulator ................................................................................................................7-16
Rebuild Controls .................................................................................................................7-16
Sync Database to DPU ........................................................................................................7-19
Tools Menu ......................................................................................................................................... 7-20
Setup Menu.......................................................................................................................................... 7-21
SimConsole Database Files ................................................................................................................. 7-22

Valmet • 278707 •
iv
Preface

Refer to this publication to learn how to use virtual DPU simulation.

The information presented in this publication applies to systems using the

maxDNA hardware.

Valmet • 278707 •
v
Chapter 1

Introducing Simulation

Overview
The maxDNA system supports process and control simulation through the
Ethernet backbone and the use of an interface, which all applications use for
interface to the system. This interface is the Software Backplane (SBP).
The Software Backplane is responsible for managing all data exchanges with
the I/O of the system both real and simulated.

The system supports both physical and virtual DPUs. The physical DPUs
are those real DPUs connected to the Ethernet backbone of the system. The
virtual DPUs are those which exist as an application in a workstation with no
real DPU hardware or physical connection. Virtual DPUs are used for
physically connectionless process and control operation of the system.

maxDNA Software Backplane (SBP)

The Software Backplane (SBP) is the interface to the maxDNA system for
simulation. It supports three types of operations for data exchange with the
simulator system. These transactions are ‘read’, ‘write’, and ‘subscribe’.
The ‘read’ transaction is a one-time get type operation that returns the
current value of the attribute requested. The ‘write’ transaction is a one time
put type operation that writes the value supplied to the attribute specified.
The ‘subscribe’ transaction is a periodic retrieval of the current value of the
attribute requested. Part of the ‘subscribe’ transaction is a minimum and
maximum time for update.

Valmet • 278707 •
1-1
Virtual DPU Simulation

Buffers in Simulation
An attribute of each I/O buffer is SimST. This allows alternate code to run
in the buffer at a normal execution rate. This code transfer data to and from
the Simulation attributes specific to each buffer. This data can be in percent
of span or real counts as received or sent by the DPU to the I/O module.
Also a status attribute (SimStatus) for simulation is provided with each
buffer to simulate bad data from the buffer to the rest of the system.

Multiple Virtual DPUs

More than one Virtual DPU can be run in a maxSTATION. To view and
operate those Virtual DPUs from the same maxSTATION, each DPU must
be listed in the [Link] and not in the [Link]. The DPUs
should always have an even number in the last octet of the IP Address. To
view and operate these Virtual DPUs from a different maxSTATION, the
other maxSTATION must be running SimTransport and the DPUs must be
listed in both its [Link] and [Link] files

Running multiple Virtual DPUs allow simulating an entire system in the

fewest number of workstations and provides normal operation of the
operator position workstations. A single attribute in DPMS (RunStop)
controls the progress of the simulation in any virtual DPU. This attribute
also allows for the control of saving and restoring various scenarios
(situations or states of the system for review and teaching).

For additional information about setting up Virtual DPUs, refer to the

chapter “Configuration of Virtual DPUs” in the 278605 – maxDPU
Auxiliary Functions manual.

Valmet • 278707 •
1-2
Chapter 2

Software Backplane and Virtual DPUs

Software Backplane Interface

To perform any of the software backplane transactions using the
ClientWrapper a SBP data object must be created by performing a
NewSbpDataObj call. This provides a handle to be used for future command
references to this object. There is also a DeleteSbpDataObj call. This is
used to destroy the data object when you are finished with it. Once the data
object is created the ProvideDataIdentifier call is used to identify the
attribute that you wish to access through the data object. This call uses a
pointer to a string containing the ‘[Link] as shown in the
I/O Simulation Buffers listed below. After the object is created the
HandleToObj call is used to return a pointer to the data object.

To write a value through the SBP the value is entered into the data object by
SetValueLong or SetValueFloat depending on the data type. This places the
value into the SBP data object so that WrapperWrite call will send the data
to the DPU via the SBP.

To read a value through the SBP a WrapperRead call is made. When the
WrapperRead is complete the CallBack will be entered. The data returned
can be obtained from the SBP data object by using the appropriate
GetValueLong or GetValueFloat call.

Subscription reads are repeated reads on a time basis. To perform a

subscription to a SBP data object the WrapperSubscribe call is made. The
minimum and maximum time values must be set prior to making the
WrapperSubscribe call. This establishes how often to make the request and
when a timeout occurs. The callback from the WrapperSubscribe will
provide the data from the latest request. The data returned can be obtained
from the SBP data object by using the appropriate GetValueLong or
GetValueFloat call.

Since a WrapperSubscribe call starts the periodic retrieval of data a call to

WrapperUnSubscribe must be made to terminate the subscription when you
are finished with it. This does not destroy the SBP data object, only the
subscription.

Valmet • 278707 •
2-1
Virtual DPU Simulation

The attributes of an I/O buffer are dependent upon the type of I/O input
or output. The simulation attributes are listed below by I/O module type.

The fastest real DPU I/O buffer update occurs at different times based on
the type of I/O involved. The digital input and output buffers are
updated once every millisecond. The analog input and output buffers are
updated once every 100 milliseconds. The TC and RTD buffers are
updated once every second. In an NT workstation with multiple virtual
DPUs this update rate will be less, however, updates more often than the
maximum processing rate will not be processed. The SBP in a DPU can
handle for simulation about 2,000 transactions per second. ‘Writes’
should be on change only and kept to no more than 200 per second to
allow for ‘subscription’ response. Coding samples are included on the
CD with this document. The project ‘ClientWrapper’ is an example of a
‘C’ interface to the software backplane. You can use these functions by
including the Client.h file in your interface program or programs and
linking with [Link] and [Link].

Valmet • 278707 •
2-2
Chapter 3

I/O Buffers in Simulation

Analog Input Buffer (AIB)

The following attributes are used by the virtual simulation DPU for
simulating an analog input module. The inputs (SimAI01-SimAI15) can be
in counts as presented by a module to the buffer or in 0 to 100 as a percent of
span.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

the simulator station to the buffer – LONG – 0 = normal, 1 = in simulation
and input is in counts, 2 = in simulation and input is in 0 to 100 as percent of
span.

SimAI01 – SimAI15 – Write - the value of individual analog inputs written

from the simulator station to the buffer as counts or percent of span – LONG
- 0 = 0%, 32767 = 100%, 4 ma = 5461 decimal, and 20 ma = 27306 decimal.

SimStatus – Write/Read - status indicating the board health written from the
simulator station to the buffer. – LONG – 0 is board OK, 1 is an error. This
will not generate an event or alarm from the buffer.

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack -
LONG

Valmet • 278707 •
3-1
Virtual DPU Simulation

Analog Output Buffer (AOB)

The following attributes are used by the virtual simulation DPU for
simulating an analog output module. The outputs (SimAO01-SimAO08) are
in counts as presented by a buffer to the module.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

the simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

SimAO01 – SimAO08 – Read - the value of individual analog outputs from

the buffer to the simulator station as counts –LONG - 0 = 0% (4 ma), 32767
= 100% (20 ma)

SimStatus – Write/Read - status indicating the board health written from the
simulator station to the buffer – LONG – 0 is board OK, 1 is an error. This
will not generate an event or alarm from the buffer.

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack –
LONG

Counter Buffer (CB)

The following attributes are used by the virtual simulation DPU for
simulating a counter module. The inputs (SimIn01-SimIn08) are in counts as
presented by a module to the buffer depending on the mode. Event
accumulation type functions are SimIn = In and frequency type functions are
scaled by the High and Low counts attributes.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

the simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

SimIn01 – SimIn08 – Write - the value of individual count inputs from the
simulator station to the buffer as counts – LONG – For event count type
inputs 32 bit quantity and for frequency type inputs 0 to 65535.

SimStatus – Write/Read - status indicating the board health written from the
simulator station to the buffer – LONG – 0 is board OK, 1 is an error. This
will not generate an event or alarm from the buffer.

Valmet • 278707 •
3-2
 I/O Buffers in Simulation

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack –
LONG

Digital Input Buffer (DIB)

The following attributes are used by the virtual simulation DPU for
simulating a digital input module. The inputs (SimWord) are in packed bits
as presented by a module to the buffer. The inputs (SimDI01 – SimDI16)
are Boolean values of 0 or 1. Either input style can be used and the results
will be merged as appropriate.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

the simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

Sim Word – Write - 16 bits representing the state of each of 16 digital inputs
the simulator station to the buffer to MAX

SimDI01 – SimDI16 – Write - the value of individual count inputs from the
simulator station to the buffer as boolean – LONG – 0 or 1.

SimStatus – Write - status indicating the board health written from the
simulator station to the buffer – LONG – 0 is board OK, 1 is an error. This
will not generate an event or alarm from the buffer.

Addr – Read - the bus address of this I/O module -LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack -
LONG

Digital Output Buffer (DOB)

The following attributes are used by the virtual simulation DPU for
simulating a digital output module. The outputs (SimWord) are in packed

Valmet • 278707 •
3-3
Virtual DPU Simulation

bits as presented by the buffer to a module. The outputs (SimDO01 –

SimDO16) are Boolean values of 0 or 1. Either output style can be used and
the results are merged as appropriate.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

the simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

SimWord – Write/Read - 16 bits representing the state of each of 16 digital

outputs from the buffer to the simulator station – LONG

SimDO01 – SimDO16 – Write/Read - the value of individual outputs from

the buffer to the simulator station as boolean – LONG – 0 or 1.

SimStatus – Write - status indicating the board health written from simulator
station to the buffer – LONG – 0 is board OK, 1 is an error. This will not
generate an event or alarm from the buffer.

Addr – Read - the bus address of this I/O module – LONG

Cabinet – Read - the name of the cabinet this module is located in – STRING

Rack – Read - the rack number where this module is located in the cabinet –
LONG

Card – Read - the card number where this module is located in the rack –
LONG

Pulse I/O Buffer (PLSIO)

The following attributes are used by the virtual simulation DPU for
simulating a pulse input/output module. The inputs (SimRa01 – SimRa08
and SimRb01 – SimRb08) are in are in counts as presented by a module to
the buffer depending on the mode.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

the simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

SimRa01 – SimRa08 and SimRb01 – SimRb08 – Write - the value of

individual count inputs from the simulator station to the buffer as counts –
LONG - 0 to 65535

SimStatus – Write/Read - status indicating the board health written from the
simulator station to the buffer – LONG – 0 is board OK, 1 is an error. This
will not generate an event or alarm from the buffer.

Valmet • 278707 •
3-4
 I/O Buffers in Simulation

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack –
LONG

Output Driver Buffer (OD)

The following attributes are used by the virtual simulation DPU for
simulating an Output Driver module. The input (ODSimAI) is in counts as
presented by a module to the buffer depending on the mode. If the buffer is
in normal simulation mode then the value is in counts and is converted to 0
to 100 % of span. In the EU mode the value is passed through to the ODOut
without conversion (0 to 100%). The output is accumulated and presented
as 0 to 100% when the buffer is in DIAT mode. If the buffer is in any other
mode the output is presented directly to ODSimOut.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

the simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

SimAI – Write - the value of individual count inputs from the simulator
station to the buffer as counts or 0 to 100% of span – LONG - 0 to 65535

SimOut – Read - the value of individual count output from the buffer to the
simulator station as counts or 0 to 100% of span – LONG - 0 to 65535

SimStatus – Write/Read - status indicating the board health written from the
simulator station to the buffer – LONG – 0 is board OK, 1 is an error. This
will not generate an event or alarm from the buffer.

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack –
LONG

Valmet • 278707 •
3-5
Virtual DPU Simulation

Positioner Buffer (PB)

The following attributes are used by the virtual simulation DPU for
simulating a Positioner module. The inputs and outputs are in EU. The
digital inputs and outputs are in the packed words of SimDIDOWord and the
statuses are in the packed word of SimDStat.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

SimAO01 – SimAO04 – Read – the value of the output written from the
buffer to the simulator station in percent of span (0 to 100%) - LONG

SimAI01 – SimAI04 – Write - the value of individual feedback inputs from

simulator station to the buffer as counts –LONG – 0 to 100%

SimFAStat01 – SimFAStat02 – Write - the value of individual stroke time

inputs from the simulator station to the buffer as seconds –FLOAT

SimDStat – Write - the value of individual stroke time inputs from the
simulator station to the buffer as seconds –FLOAT

SimAStat01 – SimAStat08 – Write - the value of individual stroke time

inputs from the simulator station to the buffer as seconds –FLOAT

SimDIDOWord – Write - the value of individual stroke time inputs from the
simulator station to the buffer as seconds –FLOAT

SimStatus – Write - status indicating the board health written from the
simulator station to the buffer – LONG – 0 is board OK, 1 is an error. This
will not generate an event or alarm from the buffer.

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack –
LONG

QUAD PAT Buffer (QUADPAT)

The following attributes are used by the virtual simulation DPU for
simulating a QUAD PAT output module. The inputs (SimAI01 – SimAI04)
can be in counts as presented by a module to the buffer or in 0 to 100 as a

Valmet • 278707 •
3-6
 I/O Buffers in Simulation

percent of span. The outputs (SimMove01 – SimMove04) are in percent of

rotation (0 to 100 = 0 to 90 degrees) based on the SimStkTim01 –
SimStkTim04). This value is updated by signed time to move and is
cumulative.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write/Read - status indicating board simulation mode written from

simulator station to the buffer – LONG – 0 = normal, 1 = in simulation and
SimAI01 – SimAI04 are in counts from the module, 2 = in simulation and
SimAI01 – SimAI04are in 0 to 100 as percent of rotation.

SimMove01 – SimMove04 – Read – sign (+ RAISE, - LOWER) + 15 bits

representing the time to move in 128 counts per 4 milliseconds - LONG

SimAI01 – SimAI04 – Write - the value of individual slidewire feedback

inputs from simulator station to the buffer as counts –LONG - 0 = 0%,
32767 = 100%

SimSkTim01 – SimSkTim04 – Write - the value of individual stroke time

inputs from the simulator station to the buffer as seconds –FLOAT

SimHiLim01 – SimHiLim04 – Write - the value of individual stroke time

inputs from the simulator station to the buffer as seconds –FLOAT

SimStatus – Write - status indicating the board health written from the
simulator station to the buffer – LONG – 0 is board OK, 1 is an error. This
will not generate an event or alarm from the buffer.

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack –
LONG

RTD Buffer (RTD)

The following attributes are used by the virtual simulation DPU to simulate
an RTD input module. The inputs (SimRTD01 – SimRTD08) can be in
counts as presented by a module to the buffer or in temperature.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write - status indicating board simulation mode written from

simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

Valmet • 278707 •
3-7
Virtual DPU Simulation

SimRTD01 – SimRTD07 – Write - the value of individual RTD inputs from

simulator station to the buffer as counts – in ohms as follows:

((input ohms-lo ohms[category])/(hi ohms[category]–lo ohms[category]))*32767

RTD Type Max Ohms Min Ohms Category

10, Cu @25C 16.413 6.02 0
9.035, Cu, @25C, =.00427 16.413 6.02 0
10, Pt 43.823 6.99 1
25, Pt 88.343 4.44 2
25.5, Pt @0C Lab Std, =.00392 88.343 4.44 2
100, Pt, DIN43760, =.00385 465.37 26.15 3
100, Pt, IPTS-68, =.00392 465.37 26.15 3
98.13, Pt, SAMA-RC21-4, 465.37 26.15 3
=.003923
100, Pt, JISC-1604-’81, =.003916 465.37 26.15 3
100, Cu, =.00427 465.37 26.15 3
100, Ni 465.37 26.15 3
120, Ni @0C, =.00672 465.37 26.15 3
100, Ni @0C, DIN43760, 159.7 80.27 4
=.00618
100, Pt, Burns-Special, =.003902 159.7 80.27 4
50, Cu, =.00427 176.25 9.91 5
1K, Pt, =.00375 3000 0 6
604, Ni/Fe @0C, =.00518 3000 0 6
1K, Ni/Fe @70F, =.00527 3000 0 6

Or as temperature when the RTD buffer is in the EU simulation mode.

SimStatus – Write - status indicating the board health written from simulator
station to the buffer – LONG – 0 is board OK, anything else is an error

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack -
LONG

Valmet • 278707 •
3-8
 I/O Buffers in Simulation

TC Buffer (TC)
The following attributes are used by the virtual simulation DPU to simulate a
TC input module. The inputs (SimTC01 – SimTC16) can be in counts as
presented by a module to the buffer or in temperature.

TagName – Read - the name by which this buffer is referred. - STRING

SimST – Write - status indicating board simulation mode written from

simulator station to the buffer – LONG – 0 = normal, 1 = in simulation.

SimTC01 – SimTC15 – Write - the value of individual thermocouple

millivolt inputs from simulator station to the buffer as counts –

input_mv/span_mv[category] * 32767

Or as temperature when the TC buffer is in the EU simulation mode.

Category Span
0 10 mv
1 25 mv
2 60 mv
3 100 mv
4 250 mv
5 600 mv

TC Type Category Lo MV Hi MV Lo Temp Hi Temp

°C °C
J 2 -8.096 57.942 -210.0 1000.0
K 2 -5.891 54.8069 -200.0 1370.0
T 1 -5.603 20.252 -200.0 390.0
E 3 -8.824 76.358 -200.0 1000.0
S 1 -0.194 18.504 -40.0 1750.0
R 1 -0.188 20.878 -40.0 1750.0
B 1 0.033 13.814 100.0 1820.0
N 3 -0.5748 47.5019 -22.22 1300.0
G 2 -0.006 38.5639 4.44 2315.5
C 2 -0.234 37.066 -17.77 2315.5
D 2 -0.163 39.506 -17.77 2315.5
Plat II 2 0.0 52.25 0.0 1300.0

SimStatus – Write - status indicating the board health written from simulator
station to the buffer – LONG – 0 is board OK, 1 is an error

Valmet • 278707 •
3-9
Virtual DPU Simulation

Addr – Read - the bus address of this I/O module - LONG

Cabinet – Read - the name of the cabinet this module is located in - STRING

Rack – Read - the rack number where this module is located in the cabinet -
LONG

Card – Read - the card number where this module is located in the rack –
LONG

Valmet • 278707 •
3-10
Chapter 4

Virtual DPUs in Simulation

The virtual DPU program accepts command line options for running. These
options include DPU name, IP address, file name and location for the
database, export of tagnames, simulation, engineering units input and output.
When executing in the Simulation Engineers station (MAXStation) the
following command line options must be included for each Virtual DPU to
run on this station.

/exp – This command line option exports the points so they are viewable
outside of the station.

/n “DPUname” – The n option gives the Virtual DPU a name and this should
be the name given in the system. It is limited to 16 characters.

/f “full path name to the saved database” – the f option provides the path of
where the database is to be stored and retrieved from.

/ip “ip1.ip2.ip3.ip4” – The ip option specifies the ip address which this

Virtual DPU will use and respond to. These ip addresses should be the same
as those used in the live system so that the displays and other programs
obtaining or providing information to or from the DPUs will not have to be
changed.

/sim – The sim option sets a global flag, which is checked by all buffers.
This places all buffers in the simulate mode without having to set each one
individually. The sim option also places the DPU in a waiting state so that
all virtual DPUs in a scenario may be started at the same time. The RunStop
attribute of the DPMS atom must be set to zero to run and execute control
atoms.

/eu – The eu option sets a global flag which is checked by all buffers. This
allows the buffers to accept input in percent of scale for easier human input.
Do not use this input if you are going to connect outputs to inputs by
reference.

A command line example would be as follows:

[Link] /exp /sim /eu /n VIRTDPU1 /f C:\custom\configs\[Link] /ip [Link]

Valmet • 278707 •
4-1
 In the case of the version 4 and newer systems this program is setup using
the Startup Config program which is documented in the auxiliary functions
manual.
Operators Stations Connected to the Simulation Station
Operator Workstations connected to the Simulation Workstation must run an
additional program named SimTransport. This program intercepts messages
for the Virtual DPUs and directs them to the Workstation (“name”) running
the Virtual DPUs. The SimTransport program does this by using the DPU
names, IP addresses, and station name configured in the file [Link].
This file is to be placed in the \custom\database subdirectory. Each entry
(one per Virtual DPU) is described in this file by example.

In the case of version 4 the SimTransport program should be started with the
MAXStation software by adding it to the custom startup initialization file .
The entry is as follows:

1, c:\mcs\Sbp\[Link], SimTransport

In the case of version 6 the SimTransort program should be started with

maxSTATION software by selecting the simTRANSPORT option using
Startup Config program

This is added to the [Link] file found under C:\Custom\SBP

subdirectory. In the case of the version 4 and newer systems this program is
setup using the Startup Config program which is documented in the auxiliary
functions manual.

After startup the program will run minimized. In case of version 4 the health
of a Virtual DPU can be observed by maximizing the SimTransport icon on
the Start bar at the bottom of the screen and in case of version 6 Point
Browser should be used to see the health of Virtual DPUs.

Valmet • 278707 •
4-2
Simulation Station Configuration And Setup
The Simulation Workstation for running Virtual DPUs requires two
operations be performed. The first is the station must be given a name and
should have an IP address in the third position, which is not below 16
(Typically 172.16.160.x). The second task is to create a shortcut to each
Virtual DPU to be simulated. This is where the command line options are
specified. Also add the command line for each Simulated DPU to the
[Link] file (in C:\Custom\Sbp) to automatically start and stop each
Simulated DPU with the Station Startup dialog. In addition the event related
programs should not be run in this station. Below is an example of the
[Link] entry.

1, c:\mcs\atoms\[Link], VIRTDPU1 ,/exp /sim /eu /n VIRTDPU1 /f

C:\custom\configs\[Link] /ip [Link]

A subdirectory per DPU by DPUname (VIRTDPU1) should be setup under

the directory structure of c:\custom\configs. This will facilitate storage of
the various scenarios used for training and simulation starts.

Valmet • 278707 •
4-3
Simulation DPUs Shortcut and Setup
A shortcut should be established for each simulated DPU to be run in the
Simulation Workstation in the system. This facilitates individual DPU
operation should it become necessary for the Engineer to individually
control the DPU. This shortcut is usually placed on the desktop in the
Engineers mode. The shortcut should be titled with the DPUs name for ease
of locating. The properties should have the following line in the target entry:

C:\mcs\atoms\[Link] /exp /sim /eu /n VIRTDPU1 /f C:\custom\configs\[Link] /ip [Link]

These are best organized in desktop folders per subsystem.

DPMS Attributes of RunStop, Scenario, and Timewarp

Two attributes of DPMS are used to control the DPU in the simulation
mode. The RunStop attribute has four functions. The first function (state 0)
is to allow the DPU to execute the atoms downloaded to the database. The
second function (state 1) is to stop the execution of the atoms. This allows
for synchronization with an external simulation control computer. The third
function (state 2) is to snapshot the database at a particular point in time.
Writing a 2 to the RunStop attribute will compress the database to a buffer
(memory) and then in the DPU idle loop write this to the disk. During the
idle task “write” the RunStop attribute will show a 5. When complete the
RunStop will become a 1 indicating that it is ready to resume operation. If
the attribute shows a 6 an error has occurred trying to write the database to
the disk. This usually occurs when the subdirectory does not exist or there is
a file lockout. Write a 0 to the RunStop attribute to continue operation. This
snapshot can be directed to a subdirectory of the dpu name by supplying a
text string (up to 16 characters) in the Scenario attribute. The snapshot will
be saved to the file:

C:\custom\configs\”DPUname”\”Scenario”.mxt

The fourth function (state 3) is to load specific saved situations to the DPU.
These are typically those saved using the snapshot save (state 2) above.
Writing the text string for the specific scenario to the Scenario attribute will
declare which database file to load. Writing a 3 to the RunStop attribute will
cause the DPU to delete the current database and load the new database.
The RunStop attribute will show a 4 during the load and a 1 when the load
is complete. The RunStop attribute can then be written to a 0 to start
running the newly loaded database.

The TimeWarp attribute in DPMS allows the psuedo time in the virtual DPU
to advance faster or slower than actual time. This value is limited between 5
times faster and .001 slower than normal time advancement. This is done by
multiplying the time increment by the entered TimeWarp attribute value and
then adding this new increment to the current psuedo time. This action will

Valmet • 278707 •
4-4
 cause the system to appear to be in slow motion (TimeWarp less than 1) or
fast motion (TimeWarp greater than 1). The real time stamps on events are
not effected by this timewarpping and will appear with a stamp of actual
occurrence.

Version 4 Configuration of Simulation DPUs

For Version 4 a new configuration tool has been designed which will
interactively setup the simulation DPUs on the simulation computer.
This tool is the Startup Config program which is accessible from the
MAX Administrative Tools menu. This program must be run when
logged in as the administrator. To add a virtual DPU to run in simulation,
click on the setup button next to the next available line at the bottom of
the display (see picture below).

Valmet • 278707 •
4-5
The setup screen shown below will popup and you can make your
selections and fill in the blanks for each virtual DPU you need to setup.
First click the radio button for virtual DPU in the block for basic type.
Second fill in the DPUname and real DPUs IP address. Third fill in the
entry for the initial database .mxt file. This should be a full pathname.
The fourth thing to select is the Export Symbols and Enable boxes. The
fifth step is to select the operation mode of the buffers for the I/O. The
selection of normal will set the buffers to expect count values as from an
actual module. The mv selection allows input of the millivolt input rather
than counts for TC modules. The EU selection allows input and output in
terms of 0 to 100% for analog values and actual temperatures for TC and
RTDs. As these selections are made and the data filled in you can
observe the Option Switches line filling in for you. It is blanked out so
direct entry is not possible. When all entries have been made click the
OK button and you will be returned to the Startup Config Tool main
screen and your entry will now be the last entry completed. Repeat this
process until all simulated DPUs have been entered and then click the
Save/Exit button to complete.

Valmet • 278707 •
4-6
Valmet • 278707 •
4-7
Version 6 Configuration of Simulation DPUs
For Version 6 the configuration tool has been modified which will look as below:

The setup screen shown below will popup and you can make your selections
and fill in the blanks for each virtual DPU you need to setup. First click the
radio button for virtual DPU in the block for basic type. Second fill in the
DPUname and real DPUs IP address. Third fill in the entry for the initial
database .mxt file. This should be a full pathname. The fourth thing to select
is the Export Symbols and Enable boxes. The fifth step is to select the
operation mode of the buffers for the I/O. The selection of normal will set
the buffers to expect count values as from an actual module. The mv
selection allows input of the millivolt input rather than counts for TC
modules. The EU selection allows input and output in terms of 0 to 100%
for analog values and actual temperatures for TC and RTDs. As these
selections are made and the data filled in you can observe the Option

Valmet • 278707 •
4-8
Switches line filling in for you. It is blanked out so direct entry is not
possible. When all entries have been made click the OK button and you will
be returned to the Startup Config Tool main screen and your entry will now
be the last entry completed. Repeat this process until all simulated DPUs
have been entered and then click the Save/Exit button to complete.

Valmet • 278707 •
4-9
Chapter 5

Example of Setting Up Virtual DPUs in Simulation

The following example proceeds through the steps to set up the simulation
station which will run the simulated DPUs and the additional set up required
of the workstations connected to the simulation station for proper operation.
This example establishes 5 DPUs (2BCS01-2BCS05) which would be
normal DPUs in the system being simulated and a simulator DPU
(simboiler). Also to be discussed, is the considerations when loading
requires two simulator stations and the correct setting of the [Link]
on each of the simulator stations.

The simulator station must be given a unique name and IP address within the
domain constraints of the system. In this example the station is given the
name DPU5DEV3. It has an IP of [Link]. This should be set up in
the domain configurator tool and the resultant file ([Link]) needs to be the
same on all stations in the system.

NOTE: Do not connect the simulator station on the same network as the
real DPUs as it is possible to confuse the system as to the data from a
real DPU with simulated data.

The next step is to establish the [Link] file correctly identifying the
DPUs in the simulation system. This file is located in C:\Custom\Database.
Below is a snapshot of a correct [Link] used in this example. This file
should be the same on all stations in the simulation system.

Valmet • 278707 •
5-1
Virtual DPU Simulation

The next step is to establish the [Link] file correctly identifying the
DPUs in the simulation system. This file is located in C:\Custom\Database.
Below is a snapshot of a correct [Link] used in this example. This
file should be the same on all non simulation stations (Operator or Engineer)
in the simulation system. If multiple simulation stations are required then
the [Link] file should contain the other simulator stations to which
this station needs access.

The [Link] shown below is how another maxSTATION is

configured to access the VDPUs in the simulation maxSTATION.

The next step is to establish the necessary directory structure to support the
virtual DPU database saves. The directory structure should be set up under
C:\Custom\Configs. There needs to be a directory for each simulated DPU
by name. When snapshots are taken during operation the mxt files will be
directed to these subdirectories and be saved as “scenario”.mxt where the
scenario is that text string entered in the DPMS attribute of scenario prior to
the snapshot. If the file already exists it will be overwritten. Below is a
sample of this structure as viewed from Explorer.

Valmet • 278707 •
5-2
 Example of Setting up Virtual DPUs in Simulation

Snapshots of the DPU databases with the scenario attribute blank will result
in the file of “dpuname”.mxt in the root directory of C:\Custom\Configs as
shown above.

The next step on a version 3 system is to configure the [Link] file which
is stored in C:\Custom\Sbp. Below is an example of the entries for the DPUs
in the simulator station. By placing them in this file the virtual DPUs will
automatically start up when the station is started and close when the station
is stopped.

On a version 4 system use the Startup Config Tool to enter the options of
each of the simulated DPUs. The simulated DPUs can be run as an
application for initial debug and then changed to run as a service for normal
operation. The startup should delay for at least 8 seconds after starting a
Virtual DPU. It may be necessary to have at least one Proxy Server running
in the simulation system or the HID references will not be visible.

Valmet • 278707 •
5-3
Virtual DPU Simulation

This [Link] is shown for reference. In a Version 4 system this file is

automatically generated by the Startup Config utility described earlier.

The next step is to establish a shortcut on the desktop to start and stop each
of the DPUs individually as may be needed. The shortcut should start the
executable [Link] from C:\MCS\Atoms. The options should be
set to match the option line above for each DPU and follows the program
name on the target entry. The startup directory should be set to
C:\Custom\Configs. See below for an example. If there are a large number
of DPUs in the simulation it is advisable to place these shortcuts in folders
on the desktop typically by subsystem for ease of locating when individual
operation is needed.

Note: refer to the 278605_maxDPU auxiliary [Link] manual for more

information about configuring the Virtual DPUs.

Valmet • 278707 •
5-4
 Example of Setting up Virtual DPUs in Simulation

The individual shortcuts should be placed at the most convenient place on

the desktop of the simulator station.

The final step is to start the station in engineer mode. On the Windows Task
Bar you should see a minimized program with the DPUname for each
simulated DPU. When these appear proceed to the Engineer/Operator
station and call up the SimTransport program pop up and observe that a
smiley face is next to each simulated DPU. If not trouble shoot why the
DPU is not cooperative. If all the simulated DPUs are present and smiley
download the databases to them from the Engineers/Operators station and
when successful snapshot each of the DPUs to create .mxts for each DPU to
use on start up.

Valmet • 278707 •
5-5
Chapter 6

Simulating Virtual Link DPUs

In some cases it is necessary to include link data transferred between the
control system and other systems in the plant. This can often be
accomplished by reference within the simulation system itself to provide
appropriate feedback. However, with third party simulation boxes it
becomes necessary to provide virtual points in the system for the third party
simulation box to interface with in substitution for the maxLinks programs.
This is facilitated by creating points within LSS. These points are the
tagnames of the points which the virtual DPU would exchange with the
maxLinks programs. With these points established in LSS the third party
simulator can exchange data through these tagged points and the simulation
system sees the points as if coming from the maxLinks software.

A program titled “SimPointCr” reads a series of files similar to the miniConf

files used for establishing points in maxLinks. The files are referenced in
the [Link] file. This file is placed in the C:\custom\database directory
and contains the full path name to each of the simulation link points text files
as shown below by example.

Valmet • 278707 •
6-1
Virtual DPU Simulation

The simulation link points text files contain the commands and data to create
the lss points for links to transfer points. These commands create a point
with a tagname, specify the type of point, and commit the point to start
executing. These points have the attributes of “.out”, “.outpct”, “.tagname”
and can be read from/ written to and subscribed to by SBP transactions.

The program c:\mcs\links\[Link] utility takes the link miniconf file and
creates a point list that is used by [Link] to create the necessary LSS points.
Note that only incoming points of the link need to be added to LSS for the simulation.

Valmet • 278707 •
6-2
Chapter 7

SimConsole for Virtual DPUs

The SimConsole application provides an interface for an Instructor to use to

control and maintain various training exercises called “Scenarios” to
simulate different situations where Plant Operators must react to control a
maxDNA system in the correct manner.

The SimConsole application typically is set up to run in an Instructor’s

Station in the simulator system with Virtual DPUs (VDPUs) to simulate
actual plant scenarios. Depending on the size of the system, the VDPUs run
on the same or multiple different stations. The picture below shows the
main SimConsole application dialog window.

The application is installed to the C:\MCS\Simulation subdirectory. Copy

the folder contents of C:\MCS\Simulation (except for the application itself)
to the C:\Custom\Applications\Simulation subdirectory. Any modifications

Valmet • 278707 •
7-1
Virtual DPU Simulation

to the files should be performed from within the contents of the folder
C:\Custom\Applications\Simulation.

1. Backup – used to save a copy of the Database folder

2. Database – contains the SimConsole and Simulator mdb files.
a. SimConsole is a saved copy of configuration parameters
defined via the Setup Menu of SimConsole
b. Simulator is a saved copy of scenario and snapshot files
created via SimConsole
3. Debug – contains session log files for the current and the previous
SimConsole sessions.
4. maxINIT – contains the file Sim_maxINIT.txt used to initialize
simulated I/O values for the system.

The file [Link] must be completed for each DPU to be

controlled by the SimConsole application. Below is a sample of the file.

Each DPU is a separate entry containing its name, the name of the station
hosting the virtual DPU, and a timeout value for transactions to the virtual
DPU.

Valmet • 278707 •
7-2
 SimConsole for Virtual DPUs

Setting up SimConsole Virtual DPUs

Normally Virtual DPUs running under SimConsole control are run on a
different station from the station running the SimConsole application.

In order for SimConsole to access the Virtual DPU files, the C:\Custom
folder on the stations where the VDPUs run must be set as Shared. Right
click on the 'Custom' Folder and perform Share. This is true even if the
VDPUs are running on the same station as SimConsole.

Click on Advanced Sharing, then Permissions. By default “Everyone” has

Read access to this folder. Assuming your Instructor station is logged in as a
member of the Engineers Group, add the Engineers Group and give it full
access to the Custom Folder:

Valmet • 278707 •
7-3
Virtual DPU Simulation

Create a folder in C:\Custom named Simulation. SimConsole accesses this

folder via the share name path: \\Station\Custom\Simulation. The Station
names are those provided in the [Link].

Include all VDPUs under SimConsole control in the standard DPU definition
file C:\Custom\Database\[Link]:

These VDPU entries should be in every [Link] in every maxSTATION

in the simulation environment.

SimTransport configuration should be done for all maxSTATIONS in the

simulation environment. Please refer to Chapter 5 of this document for
details on SimTransport and [Link] configuration.

Ultimately, the VDPUs will be launched via the StartupConfig utility. To

begin with, it may be useful to run them as applications as shown in this
picture;

Valmet • 278707 •
7-4
 SimConsole for Virtual DPUs

Download the VDPU configurations through maxDPUTOOLS, and press the

Snapshot button to create a copy of the MXT. This MXT is referred to in
this document as the [BOOT] copy for the VDPU.

Initially it may be desirable to create Desktop Icons to start these VDPUs,

for example:

Valmet • 278707 •
7-5
Virtual DPU Simulation

C:\MCS\atoms\[Link] /sim /ip "[Link]" /n VDPU" /exp /f

c:\custom\simulation\[Link]

C:\MCS\atoms\[Link] /sim /ip "[Link]" /n "VDPU1" /exp /f

c:\custom\simulation\[Link]

C:\MCS\atoms\[Link] /sim /ip "[Link]" /n "VDPU2" /exp /f

c:\custom\simulation\[Link]

C:\MCS\atoms\[Link] /sim /ip "[Link]" /n "VDPU3" /exp /f

c:\custom\simulation\[Link]

Once everything is set up, the VDPUs should be run as services:

Valmet • 278707 •
7-6
 SimConsole for Virtual DPUs

Create sub directories for each of the VDPUs in the C:\Custom\Simulation

directory on the maxSTATION where the VDPU is running. For example:

These sub directories are used by SimConsole to save scenario and snapshot
MXT files for the each VDPU.

Setting up SimConsole
Configure one maxSTATION (e.g. hostname is WIN7OPER1) to run
SimConsole. The Sub Directories 'Backup', 'Database', 'Debug', 'maxINIT'
and the [Link] file should be copied from the

Valmet • 278707 •
7-7
Virtual DPU Simulation

‘C:\MCS\Simulation’ directory to the ‘C:\Custom\Applications\Simulation’

directory. Do not copy the [Link] file.

Edit the [Link] file to define all VDPUs under SimConsole

control

In this simple example, there are four VDPUs running under SimConsole
control. All are hosted on maxSTATION WIN7OPER2. The Timeout value
of 10 seconds tells SimConsole to declare a VDPU non-existent if it does not
get a response from it within 10 seconds.

Ultimately, SimConsole will be launched via the StartupConfig utility:

Valmet • 278707 •
7-8
 SimConsole for Virtual DPUs

Valmet • 278707 •
7-9
Virtual DPU Simulation

Starting SimConsole
Launch SimConsole on WIN7OPER1 via StartupConfig or by navigating to
C:\Mcs\Simulation and double clicking [Link]. Login to the
session immediately after launching the SimConsole via the Session menu.
The default password to login to the session is "sim".

The Instructor may change the password after logging into the session by
providing the existing password and new password. The Instructor may
logout of the session at any point in time by clicking on the 'Logout' option.
The Instructor may close the SimConsole application dialog using the 'Exit'
option.

Initially, SimConsole shows the state of the virtual DPUs as red (paused, not
running). Click the Resume button to get the virtual DPUs to running state.

Note that the default security level to interact with VDPUs is

“Configuration” which is typically set to 7 and 8. It may by desirable to set
the default security level for the Instructor station to 7 or 8.

Valmet • 278707 •
7-10
 SimConsole for Virtual DPUs

The animation colors in the SimConsole application represents the state of

the VDPU. Each color and the corresponding state are listed below.

• Green - Run
• Red - Pause / Freeze
• Purple - Snapshot / Save
• Blue - Reload / Reset
• Magenta - Load Database
• Cyan - Save Snapshot
• Yellow - Error while Snapshot / Reload
• Grey - Unknown state
• Black - VDPU Not Found
Simulation Functions
The Functions that are provided by SimConsole are:

Pause – requests the running VDPUs to go to the Frozen state. When a

VDPU is frozen, the color before the corresponding VDPU is red.

Valmet • 278707 •
7-11
Virtual DPU Simulation

Resume – requests Frozen VDPUs to go to the Running state. When a

VDPU is running, the color before the corresponding VDPU is green.

Snapshot – press this button to create a new scenario. The new scenario
name is shown in the box at the bottom of the Select Scenario window. The
Instructor may also select a particular scenario from the list of scenarios and
overwrite that scenario. The current configuration of all VDPUs is saved to
the scenario name. The new mxt files are saved in each sub directory for the
VDPUs. Note that the [Boot] scenario is also selectable for overwrite.

Reset – use this function to reload all VDPUs with the scenario or snapshot
selected from the Select Scenario / Snapshot dialog. This dialog contains the
list of scenarios on the left hand side and the list of snapshots on the right
hand side. Select the desired scenario or snapshot to load into all VDPUs.

Valmet • 278707 •
7-12
 SimConsole for Virtual DPUs

When all VDPUs are reloaded, you will be presented with the dialog that
shows the Reset Wait Time. When the Time expires, you are presented with
a prompt to do the actual Resume of the VDPUs.

To proceed without resuming the VDPUs, press the “Cancel” button.

Session Log – The SimConsole dialog Session Log windows shows a log of
the interface transactions between the application and the VDPUs. This
same information is repeated in the Debug folder file [Link].

Valmet • 278707 •
7-13
Virtual DPU Simulation

Maintenance Menu
There are several options under the Maintenance menu. The Instructor may
edit the scenarios, delete the snapshots, rebuild the controls, backup the
simulator and synchronize the database to DPU.

Each menu selection is described in more detail below.

Edit Scenarios

This selection opens a dialog that shows the list of scenarios and buttons for
associated functions on the left hand side and the list of snapshots and
buttons for associated functions on the right hand side.

The Protect/Unprotect button is used to toggle the protected state of the

scenario. By default, the scenarios are unprotected. Press the Protect button
to change it to the protected state. When protected, the button text changes
to UnProtect and the name changed to a light gray color. When protected,
the Rename and Delete buttons are disabled so that the scenario cannot be
changed unless it is set back to the unprotected state.

Valmet • 278707 •
7-14
 SimConsole for Virtual DPUs

The Rename button is used to rename the selected. The default scenario
name is of the format 'Scenario_YYMMDD_HHMMSS'. The Instructor
may change the default new scenario name and provide a name of his choice.

The Instructor may select a particular scenario and delete it pressing the
Delete button under the list of Scenarios.

The Move button is used to move the selected snapshot from the list of
Snapshots to the list of Scenarios.

The Delete All button deletes all the snapshots.

The Delete button under the Snapshots list is used to delete a particular
Snapshot from the list of snapshots.

Press the Cancel button to close the Edit Scenarios dialog box.

Delete Snapshots

This selection opens a dialog which contains the list of snapshots.

Valmet • 278707 •
7-15
Virtual DPU Simulation

Use the Delete All button to delete all the snapshots in a single shot. The
Delete button deletes only the selected snapshot. The snapshot MXT file for
all VDPUs is removed from the disk and the snapshot no longer appears on
this list.

The Cancel button closes the Delete Snapshots dialog.

Backup Simulator

This dialog provides an interface to copy the SimConsole database files and
all VDPU files to the Backup folder in C:\Custom\Applications\Simulation.

It is a good idea to backup simulator files before doing the “Rebuild

Controls” step.

Rebuild Controls

This interface provides a series of steps to recreate the [BOOT] MXT files
from actual maxDPUTOOLS database files. This step allows a training
scenario to be updated due to changes in plant configuration or other
changes in plant operation.

In Step 1, the Instructor is prompted to (manually) copy the plant database

files to the Simulation station. On the plant engineer station they are usually
kept in C:\Custom\Configs. They may be placed in a parallel location on the
Simulation system, or somewhere else.

Press the Next button to continue with prompts.

Valmet • 278707 •
7-16
 SimConsole for Virtual DPUs

Step 2 copies the [BOOT] MXT files to the VDPU sub directories and
names them according to the date and time of creation of the [BOOT] file.

Step 3 provides time for the Instructor to download the VDPUs with
maxDPUTOOLS configurations. Press the Next button when all VDPUs
have been downloaded.

Valmet • 278707 •
7-17
Virtual DPU Simulation

Step 4 automatically runs maxINIT with the Sim_maxINIT.txt values in the

maxINIT sub directory. Any necessary changes should be made to this file
before pressing the Next button.

Step 5 requests the VDPUs to update the [BOOT] MXT files with their
current configuration when the Finish button is pressed. Pressing Cancel
will abort the process.

Valmet • 278707 •
7-18
 SimConsole for Virtual DPUs

Sync Database to DPU

This interface updates the [Link] file with the files that are actually
in the VDPU sub directories. A comparison of the list of files presented
when you select this function and when you select the Edit Scenarios
function will show a mismatch if the Simulator database is out of date.

Valmet • 278707 •
7-19
Virtual DPU Simulation

Tools Menu
The Tools menu item provides the ability to run several applications that are
of use to the Instructor in the simulation environment.

Update Graphics – launches the File Synchronization interface application.

This application is typically used to distribute displays or other files
modified on a File Sync Master station to other stations in the system. For
more details, please refer to Manual 278724 File Sync User’s Guide.

Health Log – launches the Health Log application. The application

provides a summary status of all DPUs on a system, including VDPUs.

Steam Property Functions – provides different options to set and compute

the Steam Property functions.

A Curve Fit Display provides the details such as the Mean for the X values
and Mean for the Y values, SD for X values and SD for Y values, SE,
Constant, RSQ, Avg Err, Std Dev and Coefficients values.

Valmet • 278707 •
7-20
 SimConsole for Virtual DPUs

Setup Menu
Auto Snapshot – use this to set the periodicity in minutes for the automation
snapshot function. This feature is disabled until the Start button is pressed.
Use the Stop button to disable the Auto Snapshot.

UOM – use this to select the unit of measurement.

Reset Wait Time – use this to set the time (in seconds) to wait before
resuming VDPU execution after Resetting the simulation scenario. The
default time is set to 20 seconds. Any value between 1 – 120 is valid.

The values set by these dialogs are stored in the SimConsole database file.

Valmet • 278707 •
7-21
Virtual DPU Simulation

SimConsole Database Files

The database files that are used by SimConsole are stored in the Database
directory:

• [Link] – this database contains:

o Simulator Password
o Auto Snapshot period
o Units of Measure
o Name of last Scenario or Snapshot used to start the VDPUs
o Reset Wait Time
• [Link] – this database stores the names of Scenarios and
Snapshots

Valmet • 278707 •
7-22