Getting Started With Dynsim
Getting Started With Dynsim
®
DYNSIM 5.3.2
Getting Started with
DYNSIM User Guide
December 2016
Development Engineers employ this tool to design their pilot plants. More significantly, these tools are
indispensable in planning and designing experiments.
Batch processing can now be more rigorously modeled with dynamic simulation tools. Kinetic studies, batch
distillation and extraction are executed with ease using these new tools.
Process Control Engineers find this product advantageous in designing control strategies. Actual controllers
can be located within a flowsheet. It provides accurate first principle models of unit operations and allows for
the detection of defects in control strategies before committing capital for the actual instrumentation.
Additionally, one can tune these controllers with the simulator. Process gain (K) and time constants (Ti and Td,
etc.) can be manipulated to find the accurate settings that will extend optimal operational performance. This
exercise saves time and effort (not to mention off-spec product) if one can eliminate the need to do this on-line
with an operating unit. Advanced users can also directly interface their plants’ DCS to the simulation.
Operation Engineers can apply this tool to plan and execute an effective start-up. These scenarios can be
evaluated on the software, before any feed is introduced into operating equipment. A successful plan can be
evolved for transition effects. Dynamic simulation can be used while starting up to aid the engineer and operator
in their decision-making. The operation engineers and control engineers also use dynamic simulation to do a
controls checkout, i.e., to verify the plant controls using the dynamic simulator before bringing the plant controls
on-line.
Operators find this an essential tool in easing their learning curve. This provides the capability to train operators
on both large and small units efficiently. Since a company’s in-house engineering staff can readily construct the
models, the demand for expensive training model consulting services is reduced.
In this tutorial, we will introduce you to the DYNSIM environment and guide you step-by-step on how to use it
to accomplish your goals. After becoming familiar with using DYNSIM application, you can look at the User
Manual or the on-line documentation to obtain detailed information. The core topics that will be covered here
will allow users to get an overview of the Dynamic Simulation Suite of products. In addition, the user will see
how PRO/II interfaces with DYNSIM application, blending the salient feature of these applications. Here, our
discussion will focus on the translation from “Steady State” to “Dynamic” models.
Italic: Used to indicate text you will enter at prompts; file names are also italicized.
Boldface: Used primarily to indicate mouse or pointer actions you will perform; may also be
used to emphasize for normal text.
Information Links
The user is strongly encouraged to explore the links suggested here in order to get accustomed to the
features and the complexities that may surface during the initial exposure to DYNSIM.
Online Documentation
Online documentation is provided in Adobe® Acrobat’s Portable Document Format (.pdf) files that are
viewed using Acrobat Reader 6.0 as well as online help that are accessible through standard help
facilities built into DYNSIM application. Acrobat Reader is a freeware that can be installed from the
DYNSIM distribution CD or from the Adobe Systems website, www.adobe.com.
All associated documentation is stored in the Manuals directory on the CD.
Additional Resources
DYNSIM Documentation:
1. Dynamic Simulation Suite User Guide
2. DYNSIM Reference Manuals
3. DYNSIM Application Briefs Guide
4. Getting Started with DYNSIM(this document)
5. DYNSIM Best Practices Documentation
6. DYNSIM License User Guide
Technical Support
®
SimSci ’s Technical Support Center is committed to providing you with the best overall product
experience. This includes any queries connected with the use of the program or the interpretation of
output data as the case may be. Our time-tested products are designed with superior quality and ease of
use in mind, but we understand that issues do arise from time to time that warrants the backing of our
support resources.
®
If you have any questions, contact the nearest SimSci Technical Support Center from the following
address list, or get in touch with your local SimSci representative.
To expedite your request for assistance, please have the following details available with you when you
call:
• A brief description of the problem encountered.
• The installation CD sent along with this package.
• The configuration of the computer you are using along with the following information:
1. Available free disk space where DYNSIM is installed.
2. Quantity of installed memory.
3. CPU type and frequency.
4. Operating system, version, and any applied patches.
5. List of all Java® virtual machines installed on your computer.
• The corrective actions you were attempting when the problem occurred.
• The list of error messages that appeared on your screen and any other relevant symptoms.
• Access to the installed software.
http://software.schneider-electric.com/support/simsci/
Documentation
A comprehensive online Help system is an integral part of the DYNSIM application. A list of Dynamic
Simulation Suite documents is furnished below.
Release Notes and FlexNet® Security Guide, and all other documents are provided in electronic
form on the installation CD.
• Getting started with DYNSIM (this document)
• Dynamic Simulation Suite User Guide
• DYNSIM Reference Manual- Base Equipment and Process Equipment Library
• DYNSIM Reference Manual – Control’s Library
• DYNSIM Reference Manual – Utilities Library
• DYNSIM Reference Manual - Electrical Library
• Translation Reference Manual(Translation of PRO/II Models)
• SIM4METM Thermo Component and Thermo physical Properties Reference Manual
• Application Briefs
• SIM4ME_LicenseSecurity_UserGuide (SimSci documentation on 3rd party license security)
A complete set of online documentation in PDF format is provided for each product.
If at any stage you have difficulty accessing the documentation, please contact Technical Support
Center.
A list of addresses and contact information can be found in the “Technical Support” section as
mentioned under “Introduction’’ described elsewhere in this document.
Hardware/Software Requirements
Configuration
Server ® ®
• Intel Pentium Processor 2.8 MHz or faster
Hardware
• 2 GB RAM and above
• Minimum: 17” monitor with minimum 800 x 600
resolution
• Recommended: 19” monitor with 1024 x 840
resolution
• Minimum 10 GB of free Hard Disk space
•
®
Windows 7 Enterprise SP1 (complete list of
Operating supported OS provided in next sections)
System
While installing DYNSIM Checkout or utilizing DYNSIM Bulk Configurator for tieback configuration,
user is recommended to install Microsoft® Excel® spreadsheet or Microsoft Office prior to installing DYNSIM
software. Open Microsoft Excel sheet at least once to register the Microsoft Excel product key. This ensures that
DYNSIM software installation installs the appropriate Microsoft Primary Interop Assemblies required for
DYNSIM Checkout and DYNSIM Bulk Configurator.
Lower speed or lesser amounts of RAM will lead to degradation in performance. Windows Classic
desktop theme is preferred over any other theme.
If you are using USB security hardware key, DO NOT INSERT the USB key until after
DYNSIM software installation is complete. The DYNSIM software install includes installation of the
SafeNet driver security services and if you install the USB key before the SafeNet driver security
services you will need to perform a manual install of SafeNet services.
SimSci provides a FNP 11.13 FNP 11.11/11.12 security option in the License Server Application
installation CD. The FLEXNet License Manager is a third-party concurrent-user software licensing tool
from Macrovision Corporation. SimSci has customized this client/server tool.
The FlexNet licensing system has two parts. One is the license server manager, which is OS dependent.
The FlexNet license server works on all current OS's (32-bit and 64-bit). The other part is client that
goes with the licensed application, and this part of 11.13/11.12/11..11 is supposed to work on all OS's.
To install, learn, and troubleshoot FLEXNet security, please refer to the
SIM4ME_LicenseSecurity_UserGuide included in the standard release package. This guide is located
in ..\Program Files(x86)\Common Files\SimSci\SIMSCICFIxx\VC090x32\bin.
If you are using a FlexNet security, you will need the name of the FLEXNet security server name or its
fixed IP address, which will be requested during the install. If you want to use a FNP 11.11/11.12/11.13
servers at your site, choose the FNP 11.13, FNP 11.12, FNP 11.11 option during the installation process.
The install option will set up the version 11.11/11.12 dlls for the application. FLEXNet software
supports borrowing of FlexNet licenses by the software application for a fixed period of time.
To run the application using Token licensing, select the Token licensing option during the DYNSIM
installation.
SimExecutive Licensing
Starting from DYNSIM 5.0, a new licensing mechanism has been implemented. The SimExecutive will
launch only if a valid Dynamic Simulation Suite license (any one of DYNSIM, DYNSIM-P, DYNSIM
Runtime, DYNSIM-P Runtime, CheckOut, OTS Engines, SCP®, TRISIM Plus® ) is found. The
SimExecutive checks for a valid license and returns it after finding one. A separate SimExecutive
license is not needed.
If the SimExecutive finds a valid license, the message window will display a message “SimExecutive
has obtained a runtime license”. If the SimExecutive does not find an appropriate license, it will not
launch the message “License check failed for SimExecutive” will be displayed.
The users should not see any other difference in the existing licensing behavior.
The web distribution package does not include a FLEXNet Server security installation, which
must be downloaded separately if you are setting up FLEXNet security for the first time.
Pre-Install Checklist
This section lists the most common issues that may be encountered by users when installing DYNSIM Software.
DYNSIM 5.3.2 co-exists with previous, released versions of DYNSIM (5.3.1, 5.3, 5.2, 5.1, 5.0, and 4.5x,). It is
not required to uninstall any existing version. Users do not need to un-install and re-install components or pre-
requisite software that were successfully installed as part of previous full installs such as Microsoft SQL 2008,
.NET 3.5 SP1 or Microsoft Windows Installer 4.5
NOTE: To avoid complications with the DYNSIM Software Bulk Configurator startup, Microsoft Excel or
Microsoft Office (2010 or 2013 or 2016) software must be installed prior to installing DYNSIM Software.
Open an Excel spreadsheet at least once to register the Excel product key
NOTE: When the DYNSIM Software installer is used with SCP Software or TRISIM Plus® Software this
DYNSIM Software install is a subset of the total system install. It is very important to plan the system
configuration and perform system installation in the correct order. When using this installer with SCP
Software please review the SCP Installation Guide prior to beginning system configuration and install. The
DYNSIM Software 5.3.1 installation is a subset of the procedures documented in the SCP Installation Guide.
1. You need local machine administrative rights (Microsoft Windows security) for the
machine on which you will install or un-install DYNSIM Software.
2. DYNSIM Software requires Power User or Local Machine Administrator privileges to stop and
restart its services at runtime. Computers with SCP270 Software (CP Image) require Local
Machine Administrator privilege as Power User is not sufficient for this instance.
3. DYNSIM Software does not support Microsoft Windows 2008, Windows XP, Windows 98, and
ME. Do not try installing DYNSIM Software on these operating systems.
5. DYNSIM Software install testing has been performed on the following 32-bit operating
systems:
DYNSIM Software install testing has been performed on the following 64-bit operating
systems:
6. Do not rename a machine with DYNSIM Software or any application with Microsoft SQL
Server installed. Use the following procedure:
back up your work,
un-install DYNSIM Software and (SIM4ME or Dynamic Simulation Suite),
reboot machine,
rename machine,
re-install DYNSIM Software,
restore your work
7. Machine names should only include characters (A to Z) and (0 to 9). Issues have been reported
for machines with special characters in machine names during installs. Consult your IT
administrators to ensure that host names are fully supported by your DNS Servers. Mixed case
or lower case machine names (a to z) will, on certain occasions, cause issues with the MS SQL
server naming. If you have issues with MS SQL server, start with Microsoft Knowledge Base
Q285100 and Q302409.
8. If you are using FlexNet or TOKEN security, you will need the name of the FlexNet security
server or fixed IP address, which will be requested during the install.
9. If you are using USB security hardware key, DO NOT INSERT the USB key until after the
DYNSIM Software installation is complete. The DYNSIM Software install includes installation
of the SafeNet driver security services and if you install the SafeNet USB key before the
SafeNet driver security services you will need to perform a manual install of SafeNet services.
10. If you have a firewall installed, it may interfere with the DSS Activation Manager and other
DYNSIM services. We recommend turning off firewall for installation. If disabling the
firewall is not allowed, you will need to put the firewall in "learning mode" the first time you
start up DYNSIM applications or allow it to start various DYNSIM processes with dynamic
port addresses.
11. Data Execution Prevention may cause DYNSIM services and installer to be unreliable. The
options may be controlled from System Properties (right click on my computer) Select:
Advanced Tab->Performance Options->Settings -> Data Execution Prevention Tab. The
options are:
We recommend using the option “Turn on DEP for essential Windows programs and services
only”. Additional information may be found on Microsoft Knowledge Base Article 875352.
12. DYNSIM Software 4.1 and later versions must be installed on NTFS formatted hard drives.
FAT drives are not supported and may cause issues with Thermo Data Manager.
14. Installing DYNSIM Software with running SCP/TRISIM/DYNSIM processes will cause install
issues. Stop SCP, TRISIM and DYNSIM processes via normal shutdown and reset services via
Host Configuration editor reset. Exit the SCP launcher before installing DYNSIM Software.
15. Install and re-install of DYNSIM Software versions may cause the SIM4ME environment
variable to contain multiple paths. Before installing SCP Software, verify that SIM4ME
environment variable contains a single unique path to the current DYNSIM install root (valid
example is C:\SIMSCI\DSS51) where the proper version of DYNSIM Software resides that will
be used as a prerequisite for the SCPsoftware install.
16. Windows 7 – DYNSIM software startup in Windows 7 requires extra care, especially for multi-
host simulators. Please refer to the DYNSIM Software 5.3.2 Known Issues Document for
Windows 7 specific issues.
17. DYNSIM is not compatible with Windows sleep mode. Ensure that all workstations that host
DYNSIM and any DSS engines have sleep mode turned off.
Software Co-existence
DYNSIM can co-exist with DYNSIM 5.x.x, , 4.5.x, 4.4.x and 4.3.x. Versions prior to DYNSIM 4.3x
and all support software must be uninstalled prior to installing DYNSIM software.
The Host Configuration Editor may not reset services properly when installing DYNSIM in system with
DYNSIM 4.3.x installed causing the 4.3.x AMEditor to fail. The user may resolve the installation issue
by executing the “patchResetSIM4ME.bat” file located in
‘DSS532\Servers\\PatchForDYNSIM4_3\’ directory of the DYNSIM installation kit.
Refer to the SCP 2.0 and TRISIM Plus Release Notes for Operating System and product compatibility.
Prior to installing DYNSIM with other products that utilize Thermo Data Manager (TDM), the user
should take in account the following setup TDM installation rules.
DYNSIM supports co-existence of major releases on the same machine. Ex: DYNSIM 5.2,
DYNSIM 5.1, DYNSIM 5.0, DYNSIM 4.5.x and DYNSIM 4.4.x.. Starting from DYNSIM 5.2.1, co-
existence of patch versions is supported. For installing previous versions of DYNSIM software, refer to
Appendix-1.
1. Install the pre-requisites by executing the Setup.exe in the DYNSIM install package.
3. To install DYNSIM, double-click Setup.exe in the DYNSIM install folder. The installer installs SQL
Express 2008 first and then DYNSIM.
• Typical Install: DYNSIM Typical installation will install typical DYNSIM features.
5. The default path for shared components that include CFI 5.0 installation is C:\Program Files
(x86)\Common Files\SimSci. However, user can modify this path during installation. If the machine
already has a previous or same version of the shared components, then the installation will proceed with
the existing location.
7. During installation of DYNSIM, the user has the option of saving User Data files in a destination folder
of their choice or in the default location, which is C:\SIMSCI\.
10. If issues are found with licensing or services starting correctly, use
11. “Start > Programs > SIMSCI > DSS532> DSS Host Configuration Editor” and click the reset
button. An example of a command window from a successful reset is shown below.
The regular DYNSIM software is a pre-requisite for installing DYNSIM 64-bit engines.
1. Install the DYNSIM 64-bit engines by executing the Setup.exe in the DYNSIM_x64 install package.
2. Click Next, and Read the License Agreement. If you agree, select the checkbox to accept the agreement
and select Next
4. Click Next, and Users can select the required DYNSIM x64 engine for installation.
The latest version of OTS Engines is 1.3.2. OTS Engines 1.3.2 cannot coexist with the earlier version, OTS
Engines 1.3.1/1.3/1.2/1.1/1.0. Uninstall OTS Engines 1.3.1/1.3/1.2/1.1/1.0 before installing OTS Engines 1.3.2.
2. Select the required engines by right-clicking the icon in the Custom Setup window.
4. Wait while the Installation is in progress and click Finish after the installation is complete.
Note: At least one system must include the full DYNSIM infrastructure to manage the simulation engines and to
access the DYNSIM Graphical User Interface (GUI).
The lightweight Activation Manager installer does not include the DYNSIM user interface. If required, the SCP,
FAIM, TRISIM, and SimSync Engine systems can be installed with the full DYNSIM infrastructure, which
includes Activation Manager as well.
Activation Manager 5.x Install Prerequisite install Program for SCP, or TRISIM Plus
software, if the DYNSIM infrastructure is not installed
For the DCS checkout, it is assumed that the actual hardware that will be installed in the plant is used. In such
cases, never install SimSci software on the actual DCS hardware suite, as some components cannot be
completely uninstalled. They will invalidate the Foxboro warranty.
Installation Assumptions:
• The user has administrative privileges
• No firewalls or other port blocking software is installed
• Other DYNSIM software has been uninstalled and the system rebooted
3. Read the License Agreement. If you agree, select the checkbox to accept the agreement and select Next.
6. Wait while the Installation is in progress and click Finish after the installation is complete.
The DSS Host Configuration Editor is a tool to customize simulation infrastructure configuration. Use this
utility to configure Operator Training Simulators (OTS) in a distributed environment where engines or
Graphical User Interface (GUI) instances reside on more than one computer. Refer to the Dynamic Simulation
Suite User Guide for additional details about this utility.
b. Change the Name Service Host and Database Server Host to point to the machine running the
Simulation Executive
c. Select the Set Interface button
It may be necessary to disable the Windows Firewall/Internet Connection Sharing (ICS) service on the
computer. Refer to the Disable Windows Firewall section in this document for details.
d. Choose the appropriate Network Interface (in this example, the secondary network is
164.168.1.1) and click Set
e. Select Reset when finished
f. Verify the services registered
It may be necessary to disable the Windows Firewall/Internet Connection Sharing (ICS) service on the
SCP Station(s). Refer to the Disable Windows Firewall section in this document for details.
When the Activation Manager or DYNSIM infrastructure is installed on computers having multiple NICs or
Microsoft Loopback adaptor configuration, use the DSS Host Configuration Editor’s Set Interface button to
specify an IP Address that will bind to the TAO Name Service. This step optimizes the DYNSIM infrastructure
to look only at the correct network connection which results in faster networking and configuration
performance.
Additional configuration is needed when running DYNSIM software on computers with more than one network
interface card (NIC) or if the simulator is split between several computers. Configuring DYNSIM engines to run
in a distributed environment on multiple machines involves these steps:
• Configure a network with dedicated NICs and a switch
• Establish an account on each machine with identical (case sensitive) user name and password which is part
of the Administrators group
• Disable firewalls or place in learn mode
• Install either the DYNSIM infrastructure or Activation Manager
• Install specific engines
• On each machine, configure the Name Server Host and Database Server Host to point to the correct machine
and use ‘Set Interface’ to specify the IP associated with the simulator network
The security option used is normally chosen during the install procedure. If you want to switch to a different
security method after installation,
1. Click Control Panel > Add or Remove Programs > Change and select the “Change” option from the
SimSci DYNSIM installation program.
2. Click Next.
3. Select the desired security option and click Next. Your security option is now changed.
Starting DYNSIM 4.1, patch install kits will no longer be supported. Each maintenance version of DYNSIM,
such as DYNSIM 4.1.1, when available, will include the full install kit and require a full re-install.
After you install the program, a DYNSIM shortcut is displayed on your desktop. You may use this icon to start
the program or follow the steps given below:
1. Start DYNSIM by clicking on Start/ Programs/SIMSCI/DSS53 and selecting the DYNSIM icon.
2. This brings up the DYNSIM login screen. You’ll be prompted for a “Username” and “Password”. Use
simsci for both the username and password and launch the application by clicking on “Login”.
1. DYNSIM software user can select a previously saved PRO/II flowsheet in a way similar to
selecting a previously saved DYNSIM flowsheet. Within the Open Simulation dialog box, the
user must change the “Files of Type” option from “SIM4ME Files *.s4m” to “PRO/II
Simulation Files *.prz”.
2. On applying the Open command, the flowsheet is processed to generate a DYNSIM flowsheet.
The Open command then proceeds the same way as the native DYNSIM Open command.
Required The user must enter data in order to run the simulation. Without a valid entry, the input for the
simulation is incomplete and an error message will be displayed if the simulation is executed.
The default color for this type is red.
Default The default value is usually a good estimate and a value that is commonly used for that
parameter. The value may be overridden if desired. The default color for this type is green.
Caution Indicates a value that is not realistic and might produce erroneous results. The default color for
this type is yellow.
Optional Data, which is not explicitly required by DYNSIM software for its execution. A Colorless
cell is used for this type of data.
A Colorless cell also means that the required or default data has been modified.
Valid Data Entry of valid data in all the data fields of an individual tab of a DEW. Any default data
(green data field) or optional data (colorless data field) are also considered as valid and the
status is indicated by .
Invalid Data Any required data (red data field) or data, which is not realistic (yellow data field) in any of
the cells of a DEW, is considered invalid and the status is indicated by .
Setting up a Simulation
The DYNSIM interface has been designed to incorporate many of the features that are built in the
PRO/II GUI. Hence, similar to a PRO/II simulation, the user can follow a series of steps to setup a
simulation.
They are detailed as below:
1. Define the Units of Measure (UOM).
2. Select components and define component slates.
3. Specify a thermodynamic method.
4. Configure the flowsheet objects.
5. Connect the objects through relevant streams.
Once the above steps are accomplished the user will run the simulation and monitor the dynamic
behavior of the process under study; specifically on how to model reverse flow through a valve. This
simple example illustrates the fact that DYNSIM software is well equipped with a state of the art
pressure-flow solver, critical for modeling more complex unit operations such as distillation columns
with precision.
1. Click on the UOM icon , which will display the Units of Measure dialog box as indicated below.
1. Bring up the DYNSIM thermodynamic GUI by clicking on the Component icon in the
toolbar. Notice that both components and thermodynamics are displayed in this window.
2. The first tab is titled “Library” and allows the user to add any of the pure or library components.
The user can enter a component by typing the technical name, alias or the chemical formula in
the Add Library Component cell and clicking on Add.
By default, only the most commonly used components are listed. Additional components can
be exhibited by selecting a different Component Family (located above the filter box).
Similar to the PRO/II application, if you wish to define a Petro component, a minimum of two physical
properties among the listed parameters below must be defined:
• Boiling Point
• Density
• Molecular Weight
The next stage is to define the component slates. A component slate can consist of a few select
components (e.g. in the case of a cooling water stream there might only be one - water). The primary
objective is that when DYNSIM software performs property or equilibrium calculations, for instance a
drum or separator, it only needs to consider those components defined in the component slate and not all
the components defined for the entire simulation. This will enable faster computational speed, especially
for simulations containing a large number of components.
1. Click on the Slate tab wherein the New Component Slate box appears at the left-hand corner of the
application. The screen appears as shown below.
4. Users have the flexibility to define as many slates as per their requirements. However, you must
first define a component in the Selected Components list before it can be added to any given slate.
The user may drag and drop multiple components by selecting marginally outside the icon of
one of the selected components.
Step 3: Define a Thermodynamic Method
Once the component slate is defined, the next step is to specify a suitable thermodynamic method. The
sequence of operation is as follows:
1. Click on the Method tab. In the New Method Slate cell, enter SRK and click Add.
2. Now expand the Thermodynamic Data tree against SRK created by you and observe the available
methods for equilibrium, enthalpy, entropy, and density calculations by right-clicking with the
mouse.
Once the above step has been completed in all aspects the user is now faced with a blank canvas. To
start configuring the flowsheet, the user needs to select the appropriate models. You have the option to
choose from one of two methods for adding objects to the flowsheet.
1. The first method is through selecting the Palette icon . This appears on the main toolbar and
can also be accessed by clicking on the View menu and selecting it there. Upon selection, a
floating Icon Palette similar to the “PFD Palette” found in PRO/II appears. You can now select
streams, equipment models, or other configurations to lay down on the flowsheet.
2. Alternatively, the user can select the Types tree on the bottom left hand corner of the screen.
The Types tree contains a complete list of the entire model Libraries in DYNSIM software
including Primitives, Widgets, References, Connectors, Points, Base Equipment, Controls,
Electrical Grid, and Utilities.
The “Icon Palette” contains only a subset of the most common models present in
DYNSIM software. If a particular unit operation is not listed on the icon palette the user is
instructed to locate the same in the “Types” tree.
3. From the Icon Palette, select a Source and fix it on the flowsheet.
The default action on a double-click depends on the state of the flowsheet. For example,
when running a simulation, double-clicking on a valve brings up a slider, which allows you to
manipulate the valve position. All options are always available through the right mouse click menu.
Configuring a Flowsheet
Remember that if you select the Edit option, the Object Editor Viewer (OEV) window pops up. This
window contains a comprehensive set of all the parameters associated with this model.
Until you select the Thermo tab and select the Process slate, the “Boundary Condition” tab will
display all the components selected for the simulation. After you have selected the “PROCESS” slate
and fixed “SRK” as the thermodynamic method, go back to the “Boundary Condition” tab.
Enter the following data: Ethane: 2 kg-mol
Ethylene: 3 kg-mol
iButane: 2 kg-mol
Propane: 4 kg-mol
Now you will observe that the Process slate composition is displayed. Notice that this data is pertaining
to the composition data and that you are entering values, which will be normalized to determine the
stream composition. The flow is a calculated value, which is dependent on the pressure network.
7. Administrator ensures that all DYNSIM software’s options are displayed. Operator, Instructor and
Engineer configures the toolbar to suit a specific user profile. For example, an engineer might need
to edit and modify a simulation. However, it might not be the case for an operator training on a
particular DYNSIM simulation. These options indicate that DYNSIM software is not limited to
engineering studies alone. Apparently, it’s also utilized for Operator Training Applications (OTS) in
which the operator, the instructor, and the engineer use a single integrated modeling environment.
8. Enter the following information as exhibited in the screen below for the Valve model. As in the case
of the Source, the Thermo method is SRK and the component slate is Process. For the Sink model,
the pressure is fixed at 200 kPa.
The next step in building the simulation is to connect the flowsheet objects using the appropriate
streams. For the purpose of simplicity only the process streams are considered for this example.
However, there are other stream types available in DYNSIM software as indicated in the table below.
These include:
In DYNSIM software, as in PRO/II software, valid port locations are highlighted and green (required).
1. Click the Start button, , to initiate the simulation engine. This causes DYNSIM software to
start the simulation and leave it in a frozen state.
2. To run the simulation the user should click on the Run button, .
4. Double-click on the valve flowsheet icon. The “Operate Valve” window will pop up. This allows
the user to adjust the valve position using a Slider. Set the position to 100% open. Notice that
the Flow Rate Initiator indicates a positive flow rate in the direction of flow specified by the user
(green arrow).
Under ideal conditions, you would wish to have the flexibility to modify the boundary condition
of the sink (i.e. it’s pressure) without having to edit the parameter in the tabbed dialog box.
DYNSIM software allows you to drop a Slider on the canvas and link it to flowsheet parameters
such as a sink pressure. Hence, in this mode you have the option to easily alter the sink pressure
and see how it affects the flow though the valve.
6. Before varying this parameter (Sink Pressure Boundary) remotely, the user must first change its
designation from static to dynamic. To do this highlight the Sink, right-click on it and select,
Edit . This exhibits the OEV interface, which allows the user to edit any variable associated
with this model.
7. The user can now alter the pressure of the Sink by varying the pointer on the slider. To track the
exact value of the pressure at the sink at a specific point of time, the user can select a Point from
the References library on the Types tree. Locating the Point on the canvas next to the Sink, the
user is prompted for a name. Now enter the name as SNK1.PB and observe that the sink
9. To complete the demo, select a Rectangle from the Primitives library on the Types tree. Draw a
rectangle around the slider, right-click, select Draw Attributes and choose a fill color. To
summarize, the ultimate step illustrates the flexibility available to the users to customize the
flowsheet graphics according to their requirements.
Summary
This chapter describes the details of setting up DYNSIM® software in a distributed environment for projects.
2. If the system administrator has established Active Directory Control and a group policy that enforces
this, then a workgroup needs to be established, including all users that are allowed Administrative
privileges on each of the machines. The system administrator should apply the new policy.
3. A basic test is to run a \\<remote_machine_name> (see example below) from the windows run
command. If you are queried for user credentials to access \\<remote_machine_name>, then the
DYNSIM services will certainly not be able to start a DYNSIM process on the remote machine. If this
simple test works, also verify that you can create and delete files on the remote machine and manage
user accounts on the remote machine.
1. On each machine use Start Programs SIMSCI DSS532 DSS Host Configuration Editor. Use
the Reset button on this application to reset services for the local machine. Verify the various services
are running OK.
2. If you have Windows 7 Enterprise SP1, verify the Windows Firewall service is stopped and disabled.
See Start Control Panel System and Security.
3. Check the status of these services. Each should be started and automatic mode. If the service is not
started use the Windows services utility to start the service. If the service fails to start, review the
Windows event viewer System Log and Application Log for root cause.
If there is a third party firewall, such as McAfee®, ensure that incoming learning mode is enabled.
SIMSCI Support has an instructions form for McAfee v8 firewall.
4. Verify that DYNSIM application starts up on each machine and a new empty flow sheet can be created.
5. Set up \WINDOWS\system32\drivers\etc\hosts file. The entries should include a standard local host. In
the example below there are four remote machines named d43xp1, d43xp2, d43xp3 and d43xp4. In
order to set up hosts file on another machine, perhaps named d43xp5, include both the simple machine
name and fully qualified machine name separated by tabs. Check every hosts file twice. Spelling errors
and transpositions cause frequent issues. All hosts’ files must be consistent.
127.0.0.1 localhost
10.2.21.178 d43xp1 d43xp1. <DNS suffix>
10.2.21.148 d43xp2 d43xp2. <DNS suffix>
10.2.21.146 d43xp3 d43xp3. <DNS suffix>
10.2.21.144 d43xp4 d43xp4. <DNS suffix>
6. All machines should have a consistent Windows login authentication. Specifically, each Windows user
logged in should have local machine administrator privileges on each of the other machines. If there is
an issue with administrative privileges the user will be able to get most of the way through these steps,
but will not be able to actually launch the engine on a machine where windows authentication is not
correct.
7. Execute a ping test from each machine to another to verify network viability. Ping both the machine
name and the fully qualified machine name. Both should return the same IP.
ping d45xp1
ping d45xp1. <DNS suffix>
If it does not pass the ping and pingns test, check network cables, network configurations, and finally
consult your IT administrator for help.
8. Optional for debugging: Open and modify the Config_file.dat file present under <Install
drive>:\SIMSCI\DSSxx\Servers\System. Set the variable ‘show_windows’ to YES. Save and close the
file. This will launch the engine dos windows (for both Run and Edit) when the application invokes the
engines respectively.
10. All machines must look to a single Name Service Host where the SimExecutive should reside. This is
always the same as the Data Base Server Host. The next step is to change the Host Configuration Editor
settings in the 2nd machine (CIN05409B) to point to the machine on which SimExecutive is hosted
(CIN05409A in this case).
Right-click on Folder Managers and Security Serves and examine IP and port bindings.
The following screenshot illustrates an issue encountered on a system with multiple network cards.
The above IOR table shows one issue that may be encountered if multiple network cards are present. On
the machine running the simexec (fsxp09 in this example), use the Naming Viewer to examine the IOR
table for the remote machine, where engine startup or performance is an issue (fsxp41 in this example).
In this example, the 10.2.x.y network is common to fsxp41 and fsxp09 and the DYNSIM Services must
bind on the 10.2.x.y network, but fsxp41 is returning the 151.128.x.y network. Use the DSS Host
Configuration Editor / Set Interface button and point to a specific IP Address to overcome this issue.
Contact SIMSCI support to obtain a troubleshooting guide if this is encountered.
Modify the Engine configuration for the simulation (on machine CIN05409A)
13. The final step is to modify the logon window parameters for 2nd machine and point to the first machine
(CI054509A in this case)
The GUI on 2nd machine will not launch automatically and will have to be invoked by the user by
clicking on the DYNSIM start icon. However, once launched, the GUI display will get synchronized
automatically.
15. There should be only one SimExecutive (on the SimExec host machine) running for a multi-box setup.
The Naming Service Viewer may be used to confirm this.
16. If the above-mentioned steps are not successful, here are some additional troubleshooting steps.
Check to see if there are multiple network adaptors installed. Ask SIMSCI Support for the DYNSIM
troubleshooting guidelines for multiple networks or private networks. Change the search order for
network adapters and then perform an ipconfig /release and ipconfig /renew to determine if this helps.
Verify naming service port settings are all set correctly. Default port setting should be 10152 and
consistent everywhere. Also verify that there are no collisions from other processes at this port. Use
Host Configuration Editor to change default port settings on each DYNSIM machine if this is necessary.
a. If network settings are modified recently or converted to a new machine with an old network name,
try an ipconfig /flushDNS
b. If step “a” is not successful, perform an ipconfig /all command from a command prompt. Note the
Host Name and the DNS Suffix Search List.
d. Ping the <Host Name>.< DNS Suffix Search List> and verify that the same IP address is resolved.
e. If the IP addresses from steps “c” and “d” are identical then skip to step “h”.
f. If the IP addresses from steps “c” and “d” are different, ask your system administrator to release old
DNS entries in the system DNS table.
g. Then stop and start the DNS client on your local machine (on Windows 2000 and later).
Verify the box is checked for "Use this connection's DNS suffix in DNS registration".
On the system in this example, the DNS servers are supplied by DHCP server and therefore the
"DNS server addresses, in order of use" is blank. The user may need to provide "DNS server
addresses, in order of use" on your system. To obtain DNS server addresses, consult the system
administrator.
Troubleshooting Guidelines
Occasionally users encounter problems during installation. Here are some troubleshooting tips that you
can use that may resolve the problem. If you have further questions, please contact your local SimSci
Technical Support Center (see “Technical Support” detailed under the “Introduction” of this guide).
Following are some typical scenarios you may be facing when installing DYNSIM software, along with
suggested tips to overcome them.
Scenario # 1
One or more files appear to be corrupted based on an unusual file size or run-time message.
Solution:
1. Run CHKDSK to verify the drive
2. Remove the current installation
3. Reinstall the programs from the start
Scenario # 2
Access failures due to invalid path: You received messages that files could not be copied and the
installation has been aborted.
Solution:
1. If you are attempting to install on a network, ensure that you have adequate read/write access
privileges.
2. Ensure that you have adequate disk space in the desired directory.
Prior to DYNSIM 4.1, the DSS Activation Manager and DSS Utility Server were named SIM4ME
Activation Manager and SIM4ME Utility Server.
1. If you have a 3rd party firewall, such as McAfee or similar, ensure that incoming learning mode is
enabled.
2. On some 64-bit machines it may be necessary to stop and restart the SIMSCI_Naming_Service.
Using the Windows Services utility stop the SIMSCI_Naming_Service. You may be prompted to
stop other services (Activation Managers and Utility Servers). Click Yes. Once the
SIMSCI_Naming_Service is stopped, restart it. Now restart the Activation Managers and Utility
Servers that were stopped. Alternatively use reset in the DSS Host Configuration Editor to restart
the services.
We suggest that you use this procedure to verify that McAfee firewall is the root cause of your current issues
and then discuss a permanent remedy with your system administrator.
If a McAfee firewall has been installed (often because of a new VPN setup or new security policy) and your
DYNSIM application services are not starting up despite using the Host Configuration Editor reset feature
several times, then:
This procedure shows you how to get DYNSIM software working with the McAfee firewall. The solution
outlined in the next few lines may be temporary if your system administrator has pushed security policies related
to firewall policies on to your system at regular time intervals or at time of login to his network/domain. If
McAfee Agent is used as your policy orchestrator, you may learn more about your security policies at using a
web browser on local host at port 8081.
Double-click the in your system tray to launch the McAfee firewall policy Manager.
1. If someone has already created a policy that allows DYNSIM software to run (IMPORTANT: It is on
your network), use the import policy to apply it to the same policy that they exported. This should be
cleared with your System Administrator first.
2. If item 1 does not apply, start with the policy that exists on your system (just as you find it) and make
notes of the settings for Protection Level and Learn Modes.
3. Place the enabled firewall in Learn Mode (as shown in the screen below)
• Protection Level must be Custom.
• Incoming Learn Modes is Enabled (checked).
• Outgoing Learn Modes is Enabled (checked).
4. Use the DSS Host Configuration Editor to stop and restart the DYNSIM services. Eventually the
SIMSCI_Naming_Service, Activation, and Utility services will all start successfully and when they do,
go to next step.
6. Open the Ammonia Reactor App lib – It has the Microsoft Excel interface example.
A McAfee firewall policy screen from a machine that has learned to run DYNSIM is listed below.
9. At this point you should place the Firewall back in its original policy mode as you noted in step 2.
The performance of DYNSIM on a Windows 2008 Server R2 operating system is impacted by the O/S
settings and one can adjust these settings to improve the performance and energy efficiency of the Windows
Server 2008 R2 operating system.
1. The Power Options (Control PanelSystem and Security) should be set to High Performance.
2. In the next step, apply the performance setting for the programs running. This can be done by right-
clicking on Computer->Properties
In some cases while installing DYNSIM 5.3.2 on a cleanly built Server 2012 R2 machine, prerequisites
installation might get hung up on Microsoft.VSTO2.0.SE (Visual Studio Tools for Office Second Edition
Runtime). It might return an error code that a prerequisite Microsoft .NET Framework 2.0 is missing.
In such scenarios specific configuration setting need to be done to enable Microsoft .NET Framework 3.5.
Following link shows the procedure.
https://blogs.msdn.microsoft.com/sql_shep/2012/08/01/windows-2012-and-net-3-5-feature-install/
Introduction
This diagnostics framework was developed primarily to help diagnose problems associated with startup of
SimSci applications. It can also be used by these applications to log system or setup problems encountered
during runtime. It is not designed to log diagnostics related to algorithmic failures.
Each application decides where to log the messages. In general, more critical messages are logged to the Event
Viewer along with the database and the rest are logged only to the database log. In the rare case where the
application is unable to create a database log (due to permissions etc.), a message indicating the same will be
logged to the Event Viewer.
These diagnostics are designed to help the SimSci technical support staff in identifying the root cause of a
reported problem. These tools can also be used by the end users to possibly find and eliminate startup or setup
problems.
Within the event viewer, select the ‘SimSci’ folder to view the messages logged by the SimSci products. These
messages will be listed in the right pane. The source column in the right pane will indicate which product logged
the message. The ‘Type’ column indicates whether the message indicates an error, a warning, or is an
informational message.
Double-click on a message to bring up the details, which would be shown in a separate dialog box:
Each message contains three entries. The first entry is the actual message indicating the problem. The second
entry indicates the code location where the error message was initiated and the third entry indicates the
associated error code. The last two entries are written for use by SimSci development personnel and provide no
Database Logs
Database logs are available as files in the folder SimSci\InstallationDiagnostics under MyDocuments. These files
are created using SQLite database. These files are named as: ProductName_LogYear_LogMonth_LogDate e.g.
DYNSIM_2008_02_23. All the logs belonging to a product for an entire day are stored in the same file. To view
the messages in these log files, you can use either a command line tool SQLite3.exe or a graphical tool
SQLiteDatabaseBrowser.exe.
To use a command line tool, open a command prompt, change the working folder to
SimSci\InstallationDiagnostics under MyDocuments, and run the command:
>SQLite3 LogFileName
For example,
>SQLite3 DYNSIM_2008_02_23
Sqlite>
The diagnostics database consists of three tables: errorTable, warningTable, and infoTable. You can run any
SQL compliant queries on these tables, e.g. “Select * from errorTable”. Each query must be terminated by a
semicolon (;). The messages meeting the query specification will be displayed in the command window:
Wed Feb 06 13:30:59 2008 >> Image files not found in the Image
Folder|GUI:ImageHandling:LoadImage.java|80023
The table schema contains three columns: Description, ModuleName, and Code. The description contains an
automatic time stamp generated by the diagnostic framework. ModuleName and Code correspond to Code
Location and Message Code as described in the Event Viewer section above.
Double-click on SQLite Database Browser.exe to bring up this tool. Use the FileOpendatabase menu option
or the corresponding toolbar open button to open the log file of interest.