For Automation World’s Leadership in Automation program, now in its seventh year, readers have named their preferred suppliers across a variety of automation technologies. MYNAH was awarded as a First Team Honoree in the category of Simulation & Modeling Software.

Subscribe below to receive our monthly e-Newsletter and product announcements.

The previous general released version is v3.6.3. This release, v3.6.3.1, comprises hot fixes of defects discovered or reported in v3.6.3.

To install this version, please uninstall the existing Mimic v3.6.3 and then install v3.6.3.1. Sites with Mimic older than v3.6.3 may proceed directly to install this version. Installation procedures are documented in the QuickStart Guide.

Upgrade to this release is recommended for all Mimic users.

Release Components:

The following defects were corrected

DeltaV Railbus VIM Bridge and Driver:

• A defect was found in handling the Analog Output - 16 Channel, 4-20mA, HART Series 2 Plus card. The defect prevented the communication of HART values to DeltaV and, in some cases, caused a VIM to lockup. This defect impacted both VIM and VIM2. New firmware (included in release) flash is required.

Mimic Explorer:

• Corrected the copy/export of connection information in a SPA SIMIT IO Definition.
• Corrected download operation for IPARAM blocks as well as other locations where system localization could cause floating point data values to be parsed incorrectly.

Mimic Logger:

• Modified the Mimic Logger to prevent potential crash when monitoring another service.

SPA SIMIT* Bridge:

• Corrected SPA SIMIT communications of freeze/resume and snapshot/restore operations when multiple nodes are involved.

* SIEMENS, SIMATIC, SIMIT, STEP 7, S7-300, and S7-400 are trademarks of Siemens AG or its affiliates in the United State and in other countries

Bulk Generation Utility:

• Corrected Bulk Generation Utility to handle nested areas for models and command line arguments when handling IO Definitions.

Simulation Engine:

• Corrected temperature usage of Stream TEE so that the first input is not always the overall temperature especially in the case of no flow through that path.

For any questions about these release notes, please contact us at:

MYNAH Technologies
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017
support@mynah.com
+1.636.728.2000

This tutorial covers auto-sensing the VIM in DeltaV, creating a devices instance, creating a dataset, and viewing real-tim register values.

Part 4 of 4.

Part 1 - Starting VIMNet Explorer and Commissioning VIMs
Part 2 - Flash Upgrading VIMs
Part 3 - Configuring Devices with ModbusTCP

This tutorial covers requirements for flash upgrading VIMs, effects of flash upgrading VIMs, and how to flash upgrade VIMs.

Part 2 of 4.

Part 1 - Starting VIMNet Explorer and Commissioning VIMs
Part 3 - Configuring Devices with ModbusTCP
Part 4 - Configuring Datasets with ModbusTCP

This tutorial covers the basics of launching VIMNet Explorer, setting VIMNet's network properties, detecting decommissioned VIMs, and commissioning simulation VIMs.

Part 1 of 4

Part 2 - Flash Upgrading VIMs
Part 3 - Configuring Devices with ModbusTCP
Part 4 - Configuring Datasets with ModbusTCP

This tutorial covers creating I/O VIM placeholders, commissioning I/O VIMs, and creating device configuration.

Part 3 of 4.

Part 1 - Starting VIMNet Explorer and Commissioning VIMs
Part 2 - Flash Upgrading VIMs
Part 4 - Configuring Datasets with ModbusTCP

These release notes are for Mimic v3.7.0.

Description

The previous general released version is v3.6.2.3. This release, v3.7.0, comprises functionality enhancements and defect corrections discovered or reported in v3.6.2.3 or earlier.

Installation procedures are documented in the QuickStart Guide.

Release Components

Who Should Upgrade?

Upgrade to this release is recommended for all Mimic users.

What's New in This Release?

Mimic v3.7.0 contains addition of the Mimic Advanced Thermo Package as a licensed option. It delivers a step change in rigorous model calculation functionality. Prior to v3.7.0, the Mimic Thermo functionality included the following:

1. Ideal Gas Equation of State (EOS) for the vapor phase with user defined Compressibility Factor for handling non-ideality of the phase;

2. Activity model for the liquid phase with user defined Activity coefficients for handling non-ideality of the vapor-liquid equilibrium (VLE);

3. Enthalpy model for Ideal Gas and Ideal liquid enthalpy calculations that can be modified with user defined corrective terms.

This level of functionality is maintained in Mimic v3.7.0 for backward model compatibility and is called Core Thermo. Aspects of the existing Core Thermo have been enhanced and are available as part of the Advanced Thermo Package option. This enhancement is called Core Thermo Plus and comprises vapor compressibility, enthalpy calculations and/or component activity coefficients dynamically calculated by the Advanced Thermo Package. In essence, Core Thermo Plus is an option to augment of existing Mimic models.

Users with the Advanced Thermo Package license can configure and employ rigorous thermodynamic model methodologies. This expanded modeling capability comprises two broad classes of functionality:

1. Cubic Van der Waals type Equation of State (EOS) Models. The most widely used EOS types are included in the Mimic Advanced Thermo option.

• Peng-Robinson (PR76)
• Peng-Robinson (PR76- Boston Mathias)
• Peng-Robinson (PR78)
• Peng-Robinson (PR78-Boston Mathias)
• Predictive Peng-Robinson (PPR78)
• Soave-Redlich-Kwong (SRK)
• Soave-Redlich-Kwong (SRK- Boston Mathias)
• Predictive Soave-Redlich-Kwong by Jaubert and Privat (PSRK-JP)

The EOS equations utilize one or two empirical binary interaction parameters (BIPs) for each binary pair in a mixture. The parameters characterize the non-ideality of interaction between pair components with a value of zero indicating negligible interaction. The Mimic Thermo package contains two methods for leveraging BIPs in EOS models:

• Constant values of BIPs, defined by approximation of the experimental data for each binary pair in a mixture, are used in PR, PR78 and SRK models;
• Temperature dependent values of BIPs, calculated by a group contribution method for the binary pair in a mixture, are used in the Predictive models PPR78 and PSRK-JP.

2. Activity models based on the Non Random Two Liquid (NRTL) equations for the liquid phase. The vapor phase is based on the Ideal Gas EOS in this Mimic version. The NRTL equation is applied for calculation of liquid phase activity coefficients and excess enthalpy (enthalpy of mixing).

Model Thermo details are configured in the Component Set. Component Sets are used by all Mimic modeling objects which represent Unit Ops. Consequently, thermodynamic consistency is maintained across units. When configuring, users select from a list of options:

• Core Thermo: As described above, this is the default model for new Component Sets. This Thermo method that has been in use prior to v3.7.0.
• Core Thermo Plus: In this mode, the user can select certain facets of the enhanced methodologies to apply to individual blocks in the simulation. This allows for selective accuracy improvements. Note, however, that electing for enthalpy corrections obligates all blocks using the Component Set to use enthalpy corrections.
• Cubic Equations of State: Choosing Cubic Equation of State allows selection from a list of widely used methods. In this mode, the phi/phi method of flash calculations is used.
• NRTL activity model: Choosing this model leads to dynamic calculation of the activity coefficients on the basis of NRTL. In this mode, the gamma/phi approach is used for flash calculations with vapor handled as an ideal gas (phi is equal to 1).

Enhancements/Optimizations:

Mimic Explorer:

Updated the TI5XX IO Definition to display the segment information and configuration dialogs using the actual register instead of a register offset. This clears confusion regarding 0 or 1 based registers in the nomenclature.

Added ability to set the SIOTag Sub-Value for multi selected SIO Tags, exclusively in the Modbus and TI5XX IO Definitions.

Bulk Generation Utility:

Update to TI5XX template text to indicate that the register values entered should be one based instead of zero based.

Simulation Engine:

StreamT object now includes a temperature mixing option to allow the selection of heat capacity mixing, weighted average or, for backwards compatibility in some cases, a legacy mode.

Added access via OPC and as Block References to Overall, Liquid and Vapor Enthalpies for the Vessel (VLE), Separator, Reactor (CST), Jet Condenser and Surface Condenser AMOs.

Added access via OPC and as Block References to calculated Gas compressibility for the Vessel (VLE), Separator, Reactor (CST), Jet Condenser, Surface Condenser and other AMOs.

Simple Compressor, Compressor (AMO) and the compressor in the Air Cooled Heat Exchanger now include a pressure ratio conversion option for polynomial types which will prevent the Pd/Ps curve from converging to zero instead of 1 when the speed is zero.

Simple Compressor, Compressor (AMO) and the compressor in the Air Cooled Heat Exchanger now have heat capacity ratio as a tunable value when online.

Simulation Studio:

Added context menu to change a block’s execution order to the beginning or the end of the list.

Defects Corrected:

Bulk Generation Utility:

Correction to not sanitize nested areas when generating models. Previously, names containing the slash ("/") character were sanitized by replacing the "/" with an "_".

Corrected command line generation for IO Definitions. Previously it was non-functional.

Bulk Generation Utility User Interface has been modified so that read-only fields are properly marked and protected.

DeltaV OPC Communications:

Error logging had become non-functional. This has been corrected and now the communication bridge is logging correctly again.

Mimic Explorer:

Correction to IPARAM downloads and other issues related to floating point localizations. Currently forcing the localization to “culture invariant” in both Mimic Explorer and Mimic Test Bench.(Corrected in hotfix 3.6.3.1). This was an issue in Mimic systems not using the US English localization. Specifically, parsing of strings representing floating point numbers with "," instead of "." for fractions.

Corrected the copy/export of the connection information in a SPA SIMIT IO Definition within Mimic Explorer.(Corrected in hotfix 3.6.3.1)

Sanitize imports of models where the execution group is not defined in the target system. Updated export of models to only bring those execution groups being used.

Added correction to import handling and database conversions for Separator objects from database revision 28 and older.

Mimic Logger:

Corrected the Mimic Logger potential crash when monitoring another service.(Corrected in hotfix 3.6.3.1)

Mimic Properties:

Correction to Columbium Fluoride component which had the symbol, Cb, which has been superseded by Niobium and symbol Nb.

Mimic VIM Bridge:

Simulation VIMs were not rebooting after communications were terminated.(Corrected in hotfix 3.6.3.2)

Corrected the Series 2 Plus AO Hart poll for VIM Bridge. This change also requires a firmware upgrade for both VIM and VIM2.(Corrected in hotfix 3.6.3.2)

OTM Engine:

Report generation now correctly generates all scoring details even if the first item has insufficient data.

Simulation Engine:

Standard Conveyor block now handles the Maximum Speed correctly when a speedup/slowdown time adjustment is applied. Previously it would remain static causing the mass to appear to stack and spill once the transfer due to speedup exceeded the maximum speed defined. Now the Maximum Speed is also scaled with the time factor. (Corrected in hotfix 3.6.3.2)

Corrected the displayed dP value of the PRV Advanced modeling objects to handle gauge pressures. (Corrected in hotfix 3.6.3.1)

Corrected temperature usage of Stream TEE so that the first input is not always the overall temperature especially in the case of no flow through that path.(Corrected in hotfix 3.6.3.1)

Corrected the size distribution and incorrect phase for the Cyclone Advanced Modeling Object.(Corrected in hotfix 3.6.3.2)

Corrected the temperature for the Cyclone Advanced Modeling Object when not executing on a one second basis.(Corrected in hotfix 3.6.3.2)

Correction to Air Cooled Heat Exchanger flow rate displayed value versus units displayed. This display error has been corrected.

Calculation Modulus function, MOD, now correctly identifies a zero value after passing the initial conditions of non-zero floating point data when casting less than 1 values to integer. Previously, an integer value of 0 would pass through causing a Divide by 0 error.

Correction to transfer from vessel to vessel. It would provide unusual totalization during the last steps of complete transfer.

Corrected the Flotation Cell AMO so that (a) it no longer destroys mass in the Overflow category; (b) checks to catch invalid inlet dimensions; and (c) protect against all quality values being set to 0.

Corrected the Dead Time block configured with a variable time value. On start up, the first input value would immediately pass to the output side without the expected time delay.

SPA S71 Communications:

Corrected SPA S7 communications to work with signed integer types instead of unsigned as well as corrections to error handling.(Corrected in hotfix 3.6.3.2)

SPA SIMIT1 Snapshot:

SPA SIMIT OTM handling now only sends restore commands to SPA SIMIT sessions attached to the system ensuring that the restore command is sent only once to a SPA SIMIT system even if it has more than one Mimic node communicating with it.(Corrected in hotfix 3.6.3.1)

*(SIEMENS, SIMATIC, STEP 7, S7-300, and S7-400 are trademarks of Siemens AG or its affiliates in the United State and in other countries)

Simulation Studio:

The Turbine AMO worksheet no longer converts stored data for the worksheet from engine to user units. Previously, this would cause the values to change without the user editing them each time the dialog was opened and the OK button pressed.(Corrected in hotfix 3.6.3.2)

Correction to Calculation expression helper function template for BYTES_TO_VAL function. No longer creates a starter expression called BYTE_TO_VAL.

Modified so that the Delta_Time Parameter for the RnR Tuner block is correctly saved.

Modification to block rename marking system within Simulation Studio to correctly identify freshly added blocks after a save has been performed. This occurred when the model was saved but the application had not been closed. This prevented the global rename operation from activating when that new block had its name changed subsequent to the save operation.

Modified so that the Dead Time block now maintains the values of the block when reverting from online mode.

Contact Us

Please contact us for any questions about these release notes at:

MYNAH Technologies
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017
+1.636.728.2000
support@mynah.com

On Friday, May 19, 2017, MYNAH Technologies LLC changed ownership from Experitec Holdings Inc., to now being owned in entirety by Emerson. Within Emerson, MYNAH fits into the Lifecycle Services of the Process Systems and Solutions business, a group focused on delivering Emerson's vision of Operational Certainty to the process industries. All MYNAH employees continued on in the change of ownership and are very excited to be part of team Emerson.

An Incredible Opportunity for MYNAH

As part of Emerson, MYNAH now has access to the operational reach of the global leader in process automation. While MYNAH was privileged to be Emerson's strategic partner for dynamic simulation and industrial Ethernet for many years, this move cements our relationship and allows MYNAH solutions to be adopted and promoted to a broader range of global customers.

In the months ahead, we will be integrating MYNAH into Emerson's focus on Operational Certainty, helping process companies achieve top quartile performance in safety, reliability, production and energy management. In addition, the excellent business and financial management, that has made Emerson one of the best run companies in the world, brings both resources and capability to grow our reach more than ever before at MYNAH. We are poised for a great future and will be delivering more value to our customers as part of the "OneEmerson" team.

Our Mission Doesn't Change

In spite of our ownership changes on that very big day for MYNAH, our commitment to our customers, partners, and the industry has not changed. As part of Emerson, our goal of reducing the cost, risk and complexity of plant operations through Lifecycle Dynamic Simulation has never been stronger. And our vision to deliver greater operational value and extend the benefits to new users and industries is still our number one priority. With the full backing of our new parent company, we will continue to:

• Support the full Lifecycle of Plant Operations, Automation, Compliance, and Reliability.
  MYNAH will continue to support all users in the process industries, regardless of whether they use Emerson, Rockwell, Siemens, ABB, or any other control system platform.
• Provide the lowest Total Cost of Ownership of using Lifecycle Dynamic Simulation so that the return on our customer's investment continues to grow.
• Deliver solutions that are easy to work with, easy to maintain, and continue to be a partner for the customer and the automation supplier that is easy to work with and supports their business.
  May 19, 2017 was a very big day for MYNAH Technologies. A day that we will remember as a significant first step in our future growth and a day that increased the value of Lifecycle Dynamic Simulation to our users and partners. The MYNAH Team is excited to be part of Emerson, the global leader in process automation, as we continue in our mission to reduce the cost, risk, and complexity of plant operations.

  More Information on Lifecycle Dynamic Simulation from MYNAH

  • MYNAH Technologies Now Owned By Emerson
  • Lifecycle Dynamic Simulation with Mimic
  • Business Case for the Virtual Plant

I look forward to your comments, questions, or suggestions. Hope to hear from you soon.

Mart Berutti, 05/25/17

Maximizing operator and system synergy for best plant performance. It is well known that the operator can make or break a system. A recent research study found that only 2% of process losses and safety issues could be traced to something other than human error. Operator training is recognized as essential.

For the last five years at our annual Holiday Party, we have recognized one special person in the Emerson Simulation business with the Ab Initio Award.

The Emerson Process Simulation Holiday Party this year was held on Friday, December 8, 2017, at Edgewild Restaurant and Winery in Chesterfield, Missouri. As we celebrated another year of blessing at Emerson, I had the honor of introducing new people, acknowledging significant milestones in the lives of our people, and recognizing this very important member of the Emerson Simulation team with the Ab Initio award. It was a very exciting and eventful year since we last met at the MYNAH Technologies 2016 Christmas party. In May 2016, Emerson bought MYNAH, and our team was very busy forming the process simulation center of excellence within Process Systems and Solutions. It was a challenging 6 months, but I have never been more excited about our business or working with this great team of people. The first Emerson Process Simulation Christmas Party was a great opportunity to celebrate the year and thank the associates and their loved ones who joined us that evening.

See more pictures of the party on our Facebook page!

Ab Initio 2017

When we talk about impact, of attitude and integrity, of innovation and excellence, there is one person in particular that comes to my mind. I would like to talk about this person for a moment tonight …

In science something is said to be ab initio (AB INISH EE OH) ", Latin for from first principles" if it relies on basic and established laws of nature. As we grow into Emerson there is even more of a need for focus on core values, integrity and innovation, on the spirit of Ab Initio. This person demonstrates this spirit every day. He started his career with us as a coop. It became clear that he could handle every challenge that we asked him to take on. So, when he graduated, we challenged him to join our simulation engineering team. He excelled as a Simulation Project Engineer, moved up to Lead Simulation Engineer, and we asked him to take step up further as our project and resource manager. He does everything really well....except travel well. For some reason he seems to have a hard time taking a trip without getting robbed, his luggage lost, flights missed or delayed, or stuck in a cell in South Africa for weeks on end. Of course, I am talking about Zach Sample. Zach is patient, perseverant, innovative, and very intelligent. Zach has a BS in Chemical Engineering from Missouri University of Science and Technology and just completed his Masters in Chemical Engineering from North Carolina State University. He demonstrates impeccable integrity, and I have never seem him with a bad attitude … even when working with some very challenging partners and customers. Zach is a leader of our organization. Someone that I depend upon a lot. I am very glad I met Zach Sample in Rolla, Missouri, several years ago and asked him to join our team. Believe me, that is one decision I will never regret.

My friends, the Emerson Process Simulation Center of Excellence would like to recognize Zachary Sample, Ab Initio 2017.

Our wish for all the men, women, and friends of Emerson is for a very blessed and Merry Christmas and a Happy New Year.

Mart Berutti, 12/20/17

The previous general released version is v3.7.0. This release, v3.7.1, comprises functionality enhancements and defect corrections discovered or reported in v3.7.0 or earlier.

Installation procedures are documented in the QuickStart Guide.

Release Components

Who Should Upgrade?

Upgrade to this release is recommended for all Mimic users.

What's New in This Release?

Simulation Studio, the Mimic simulation configuration application, has been enhanced to include a Process Flow Diagram (PFD) style flowsheet to specify AMO based models. This functionality is a user selectable option. Users can continue to use the existing IEC1131 methodology, configure new models using the PFD style, and/or convert existing models from IEC1131 to PFD style. Conversion from IEC1131 to PFD style is done automatically by Simulation Studio; however, the resulting placement of stream connections and layout will require a cleanup effort. All underlying functionality remains the same when using IEC1131 or PFD styles. The benefits of the new PFD style are:

• Space conservation so that a large process area can be condensed into a small flowsheet
• Equipment and UnitOps are represented with easily recognizable graphic symbols
• Reduction of clutter on the screen by allowing users to show only the values they want to see, e.g., stream flows
• Easily see the process flow direction
• Ability to select and position display of Equipment and UnitOp run-time values on the screen
• Drag and drop objects from the pallet onto the flowsheet
• Create stream connections between objects by clicking on a source point and drag the mouse pointer to a destination point

Model execution threads have been enhanced to include 10, 25, and 50 msec model execution. This fast model execution can be applied to Mimic base models as well as advanced models.

A pressure Regulator object has been added. It is designed to maintain a target pressure drop or pressure with VLE balance.

An Orifice Plate object has been added. It is designed to reduce the line pressure with VLE balance.

Future Value Function Block - This block computes the future value of a process variable and rate of change with a good signal to noise ratio. This block also computes the rate of change of the input and the value and time to peak rate of change.

PID Reset Functional Block - This block provides reset action that compensates for a variable measurement update time.

PID Performance Functional Block - This block can be used in conjunction with an ePID block to give the user information about their PID Performance. This block computes the integrated absolute error (IAE) and the peak error when LOAD_METRICS is enabled. If SETPT_METRICS are enabled, this block will compute the rise time, overshoot, undershoot, and settling time for a setpoint change. It will also compute the number of communications and test time to determine wireless battery life. Note that the times are in seconds but the IAE is in eu*minutes, and the peak error, overshoot, and undershoot are in engineering units (EU).

The Joule-Thomson (JT) effect calculation has been added to the outflow from Valves, Pressure Regulators and Orifice Plate objects.

When using component sets with Advanced Thermodynamics enabled, the Compressor object will now internally calculate the Heat Capacity Ratio for the outlet flow. The previous user defined heat capacity ratio functionality is maintained as an option.

New I/O bridge to support the Rockwell Logix Emulate interface API has been added.

Enhancements and Optimizations

Mimic Explorer

Added an easy way to add snapshot files into the Mimic database

Added progress indicator when performing large copy/paste operations

Backup log completion message is reported to the Mimic event log. Backup creation can fail if the disk is full or if the user does not have file permissions. The event message is a record of success or, in case of failure, reason for failure

Added MEMI2 Model Download and Stop menu for the External Model definitions so that all instances can be stopped and started independent of the node

Corrected Discrete Device Template editing. When editing a template from Mimic Explorer, if the number of DI or DO bits was changed quickly by clicking the arrows, the number of bits editable became different from the number specified in the Template definition

Tag Browser

Added new functionality to add/remove SIOTag and Initialization items from L5K files for Logix Emulate API interface

Logix Emulate

Added new bridge to perform I/O Access via DLL API

Bulk Generation Utility

The I/O Definition properties and SIO tag grid had a lot of read-only fields. Almost nothing in the IO definition properties could be modified, and SIO tags could not be added. Editing of these features has been implemented

Added capability to bulk generate and/or modify Unity OFS and Modbus I/O Definitions

Simulation Engine

Added Column/Stripper Tray level as browseable parameter. Tray level has been added to the run-time engine database. Previously, it was calculated and discarded. Now it is stored and exposed as a parameter value.

Added calculation of Heat Capacity Ratio when component set is configured for Advanced Thermodynamics and EOS. The ratio is then used to calculate outlet temperature, e.g., in a Compressor.

Added calculations for Cavett Liquid Enthalpy in NRTL based Thermodynamics with EOS component sets. The user can choose between Ideal + Excess Enthalpy or Cavett Correlation for computing the liquid enthalpy by manipulating the Liquid Enthalpy Model droplist. Ideal + Excess Enthalpy will compute the excess enthalpy based upon NRTL and add it into the ideal enthalpy computed from an Ideal Gas basis. Using Cavett Correlation will compute the Liquid Enthalpy based upon the Cavett liquid enthalpy model (which leverages component critical data). Cavett allows for estimation of enthalpy without relying on ideal gas as a basis.

Added simulation Speedup/Slowdown to the Logix Emulate bridge which uses the new Rockwell interface API. This functionality is now available in the release version of the Rockwell API.

Added functionality to calculate phase in Advanced Source object. The Advanced Source allows the user to put in any data, but this easily leads to specifying data that are not thermodynamically consistent. A new radio button has been added for the phase, i.e., to allow the user to define it or let the object calculate it internally. The default is User Defined. When User Defined is active, the Phase tag reference will be available, and Calculate will disable the tag reference. The configuration dialog also checks the component set to make sure it's not a pure component. If it's a single component, or if it's a pure component in a multi-component set, Calculate is grayed out and only User Defined is available.

Added functionality to externally calculate the phase in Vessel object (non VLE). An array reference in the vessel allows users to define the phase of each component for medium fidelity modeling of separations utilizing core modeling objects. To use this feature, a new mass integration type called "Custom Liquid/Vapor Separation" has been added. The User Interface rules are the same as for "Independent Liquid/Vapor Integration." When set to the new custom mode, the infinite source option is disabled. Two new array tags are enabled, "External Component Phase Array" and "Component Phase Enable Array." Not configuring "Enable Array" will result in all being enabled

Pump: Added a preconditioner to Pump polynomial inline solution. This change adds detection for cubic polynomials which cannot be analytically solved in double precision arithmetic. Consequently, the engine uses a fallback procedure to resolve the pump.

Execution suspended/slippage when running a multi-threaded simulation on a single core machine. If a Mimic database is multi-threaded, but placed on a single core, it does not execute all threads. While this is an expected issue with this setup, there is no indication that anything is wrong, since there is no slipping noted if there is no execution time. Consequently, the user is now notified on startup that the system is limited.

Added steam tables based on the 1997 standard. The previous libraries for the 1967 standard remain available for backward compatibility. Inclusion of the 1997 standard corrects inaccuracies in some functions using the 1967 standard due to interpolation, e.g., KFPT.

Modified so that streams have improved data consistency when using EOS component sets.

Modified how density is calculated in mixed flow streams. It is now implemented based on a global option, "Phase Density Mixing" vs. "Volume Density Mixing." Volume Density Mixing is the default for new databases, and Phase Density Mixing is the default for upgraded databases.

Modified the way the COND block evaluates comparison of double precision numbers. Instead of a straight equality, the comparison is now done with a precision of 1E-15.

Mimic Diagnostics

Moved thread information into its own branch. The addition of multiple user threads to Mimic has caused the number of threads per node to explode. This has led to thread information crowding out everything else in diagnostics. This thread information has been moved to its own branch under the node.

Simulation Studio

Added Power and Mass Flow Units to the Compressor object.

Modified configuration of the Air Cooled Hx to consolidate the way the configuration sheets are called.

Added default values to Advance Source object. The defaults are 20 DegC, 101.325 kPa and Phase of 1, i.e., Liquid water at standard state.

Corrected Valve K-Value editing - When a Valves K value is modified online and then the model goes offline, the user is prompted if changes should be saved. If you select no, everything seems fine, but when you go back online without a download, the Valve will be using the modified K value but the display will show the original K.

Mimic Help

Separator Help - The help files for the initial conditions of the Separator do not indicate that a stream with more than one component needs to be present to select options like Pressure-Level (calculate Temperature). When the stream contains only one component, the initial condition fields are greyed out and the default Temp-Level (calculate pressure) is selected. When a multi-component stream is selected, the options for Pressure-Temp (calc level) and Pressure-Level (calc Temp) become available.

Corrections

Test Bench

Corrected Test Bench crash. This crash occurred when using arrow keys to navigate grid.

Mimic Explorer

Corrected model export defect. If a Calc block used defined global registers and/or constants, subsequent model export did not also export these global parameters. This resulted in Calc block errors. The referenced global registers and constants are now part of the model export.

Corrected XML export defect. If the user exported a graphic or snapshot, they did not get the required file that goes with the database entry. To receive these files required a separate, manual step. The external files have now been added to the XML export.

Mimic's documentation lists 32 VIMs as the running limit, but Explorer only allows 31 VIMs to be commissioned. This has been corrected and the Explorer now allows 32.

Corrected the download difference between Explorer and Simulation Studio which caused PVnRT function block error. The Gain parameter was not downloaded.

Mimic Modbus Bridge

Corrected Modbus Coil configuration. Modbus coils registers must be assigned to byte boundaries (both start and length be byte size) for proper updates to/from field devices. In the configuration dialog for these any register may be set for start (this should be limited to 1, 8, ...). The length may be set to any size, this is now limited to units of 8, 16, ...

Corrected Modbus bridge user interface for Slave mode while communicating with multiple field devices. Previously, it only communicated with a single device with ID=1. The bridge now has a mode which can be set to single device or gateway for multiple devices.

Added functionality to support Modbus Function Code 5. This function code allows users to force single coils on/off. Previous bridge version did not permit this.

Simulation Engine

Corrected error reporting for MEMI2 models. If a MEMI2 model overruns its update time, the engine sets all associated blocks in error. Subsequently, it did not clear this error if the MEMI2 model started to run in the allotted time.

Modified First Order Filter time constant – The filter time constant has been converted from integer to floating point to allow fractional time values. Mathematically, the filter time can be a non-integer positive number but was previously configured as an integer. Frequently, a 1 second filter is too large of a filter time because a 1 second filter takes 4 seconds to get to 90%. This modification also affects the AI, LTB, PID & SOF blocks.

Corrected the PRV function block to properly update the Cg parameter. If the PRV Cg is changed online (e.g., from 1 to 5), the flow and Cv will also change. If the model is taken to configuration mode and the 'Online Changes' window is cancelled, the original (1) value is shown in the configuration view of the PRV Cg. If the model is then taken back online with the play button (not downloaded), the PRV Cg shows the configuration value (1), but the Cv and Flow values are based on the engine Cg (5).

Corrected Compressor issue where high resistance on outlet stops compressor. Once the flow of the compressor stopped, such as by forcing the outlet K-factor to a high value to reach its minimum flow rate or maximum pressure ratio, the compressor never again tried to calculate flow; it stopped flow forever after this point.

Corrected Vessel so that the min/max pressure is maintained. In execution, for a given temperature, the Vessel will retain the correct amount of vapor holdup so that the pressure does not fall below the minimum.

Corrected Advanced Source and Vessel objects to propagate equilibrium values when using the Advanced Thermodynamics functionality. Currently the equilibrium values do not propagate which causes calculation consistency issues.

Corrected handling of 16-bit Signed Integer values coming from VIM Serial, Profibus and Devicenet signals. Mimic stores these 16-bit numbers as Unsigned before passing them to the AO blocks. This produced completely incorrect results for AO OUT or IParams in Mimic.

Corrected elevation handling related to Stream Output parameter. Incorrect handling impacted the PF Solver.

Corrected Heat Exchanger following snapshot restore. Restoring snapshot and downloading supporting standard model caused Heat Exchanger's Heat Transfer Coefficient to change from a referenced tag to a static value.

Corrected Dynamic Hx for proper usage of internally calculated phase. Phase is calculated in mass units, but is being used as moles in the dynamic heat exchanger, which will cause all phases to be slightly wrong if they're not pure vapor or liquid. Warning to existing users - if the DHX involves mixed phase outlet conditions, upgrading to v3.7.1 will not maintain previous results.

Corrected Separator defect - During mass integration the Separator does component by component integration. During this it is possible to end up with a negative amount of mass. Currently it will then create more mass to make a smooth approach to zero. This is nice in some cases as it gives a smooth response, but it is not physically accurate and can result in getting stuck in a feedback loop of mass creation. Instead of trying to be smooth, the functionality has been modified to be more correct (more since it's already in an invalid state by ever getting to a negative value, but no sense in compounding the issue) by just setting the component to 0.

Corrected executing of two vapor valves connected in series.

Corrected sight glass display names for Separator, Reactor, Surface Condenser, Jet Condenser and Vessel VLE objects.

Corrected Valve Hysteresis calculation for Discrete valves. Users could configure the parameters, but they had no impact on valve performance.

Corrected pumps where the downloaded curve has multiple solutions. The solution implemented is to keep the answer closest to the previous solution.

Corrected error message on Positive Displacement Pump. When a pump is configured with a centrifugal pump curve; but has positive displacement pump checked, it can activate false positive centrifugal pump errors such as "the max flow is greater than pump curve" error.

Corrected Vessel (VLE) Jacket energy creation issue. If a Vessel (VLE) is configured without both heat transfer coefficients for either the liquid or vapor phase, the outlet temperature of fluid going through the jacket will be the same as the temperature of the vessel. The jacket will show a Q_Jacket of 0 (as it should since there is no configured U) but the temperature of the fluid will change to whatever the vessel temperature is.

Corrected flow through StreamT where there is no flow when using the PF Solver and the flow is unstable when using the Node Solver.

Corrected Vessel so that it initializes to the correct phase when a component set with EOS is specified.

Corrected the state table logic for the MOV function block. Due to a discrepancy, the OPEN_LS_NO returned TRUE, and the OPEN_LS_NC returned FALSE, when the opposite was expected.

Corrected Valve leakage functionality. It was incorrect when the flow type is based on Velocity Head Loss Coefficients and the Valve is closed.

Corrected Streams so they now return the proper thermodynamically calculated Heat Capacity based on the temperature and composition.

Corrected liquid volume calculation in VH Flash when using Advanced Thermodynamics and EOS.

Corrected pressure drop calculations to eliminate unstable vapor flow through Valves for both Valve Cv and K-Factor resistance methods.

Simulation Studio

Corrected Multiple OParam writes error message - If multiple OParam blocks are writing to the same target, one of them will end up with "Block not present in run-time system or invalid path." which was not exactly helpful. The error message has been updated to reflect that another block is writing.

SPA S7¹ Communications

SPA SIMIT¹ Snapshot

Corrected SPA bridge so that it does not crash when the API DLL is missing. If Siemens.SIMIT.CS.CSAPI.DLL is missing (or the wrong version), the SPA bridge crashed when the first API call was invoked. The bridge now reports that initialization has failed and shuts down.

¹(SIEMENS, SIMATIC, STEP 7, S7-300, and S7-400 are trademarks of Siemens AG or its affiliates in the United State and in other countries)

Please contact us for any questions about these release notes.

This integration guide describes the recommended settings for integrating the CSI6500 Modbus TCP/IP compliant A6824R interface cards to DeltaV utilizing the Emerson Virtual IO Module (VIM) with the MYNAH Modbus TCP/IP driver. The A6824 / A6824RCommunication module is a component of the CSI 6500 Protection machine monitoring system. This module performs cyclical polling of CSI 6500 Protection monitor data. The captured data are output via Modbus RTU or Modbus over TCP/IP.

Introduction

Resources

1. CSI 6500 Machinery Health Monitor – Protection and Prediction in a Single Chassis
2. MYNAH Online VIM Help Files

Hardware Requirements

• DeltaV Virtual I/O Module 2 (VIM2) VE4026: M-Series or SE4026: S-Series
  MYNAH Technologies Modbus TCP/IP Master Driver (IOD-4111)
• DeltaV Controller
• (3) DeltaV 2-Wide
• (3) DeltaV power supply
• CSI 6500 Protection Monitoring System
• (2) A6824R
• Interface cable for connecting a PC to the RS232 configuration port on the A6824R

Software Requirements

• DeltaV System Software (Release 10.3 or later) installed on a hardware-appropriate Windows workstation configured as a ProfessionalPlus Workstation for DeltaV (requires license)
• DeltaV Explorer
• DeltaV Diagnostics
• DeltaV Control Studio
• CSI 6500 Configuration Utility
• VIMNet Explorer

Guide Assumptions

The user has an installed CSI 6500 Modbus TCP compliant Remote I/O System with appropriate I/O Modules connected to the system (A6824R) and is familiar with VIMNet Explorer, DeltaV, and the CSI 6500 configuration software.

Integration

Theory of Operation

The DeltaV VIM provides a native DeltaV I/O interface to the CSI 6500 A6824R communication module via an open plant Ethernet network and Modbus TCP (RTU TCP) protocol. DeltaV controllers can read and write signals to the A6824R residing on this Ethernet network. As such, the VIM exists as a Network Gateway between DeltaV controllers and the external CSI 6500 nodes. This connectivity is illustrated below:

A6824R Configuration

For operation of the communication module, a configuration must be created with the A6910 configuration software and then loaded into the module. The following portion of this manual assumes a configuration has been loaded into the module and briefly highlights strict parameters necessary for successful communications to DeltaV VIM cards. Additionally, the interface cable for connecting the PC to the RS 232 port on the A6824R is required for all configuration changes.

Please reference the OM_A6824_Communication_Module.pdf included with the product for additional setup information.

1. To start the configuration software, navigate to:

All Programs->Emerson Process Management->CSI 6500 Configuration->CSI 6500 Configuration

For the first start of the program, login with ID “first” and Password “user."

2. The communication module is configured and edited under the “CSI Configuration” icon in the configuration tree.

Once configured and selected, parameters are entered / edited by selecting the Configuration – Edit menu item or clicking on the hammer-icon in the symbol bar. A menu with two tabs for the input of parameters will open. Please contact Emerson for specific information regarding the Administration and Configuration tabs.

3. A third Redundancy tab appears when connected to the A6824R module with firmware version of 1.05 or later.

The following steps must be complete for configuration and activation of redundancy mode:

a. Check the "Redundancy active"checkbox.
b. Enter the “wait time” parameter (minimum of 5 seconds). The Secondary Master will wait this amount of time before taking over communications when traffic on the 6 COM lines stop to the Primary Master.
c. Enter the corresponding bus addresses of the Primary Master and Secondary Master.
d. Enter the corresponding TCP/IP addresses of the Primary Master and the Secondary Master.
e. Click "Apply"and/or "OK." br style="line-height: 1.6em; background-color: initial;">f. The configuration must be downloaded to both A6824R communication modules with the “Send configuration” command. Section 4 below describes the download procedure.

4. To download the configuration to the A6824R modules, the communications settings must be adjusted in the configuration software.

On the “Connecting” tab enter the COM “Port no.” being used on the PC. Select "Gateway 6824." Accept the settings by clicking the "Apply" button, then click "OK" to close.

Transmit Parameters:
To activate the connection between computer and module use the “Connect” in menu “Connection” or by clicking the chain symbol.

Receive Parameters:
To receive the parameter file form the module, use the “Receive” in menu “Configuration” or use the “Up Arrow” symbol.

Edited data must be loaded again.

5. The Modbus TCP interface provides 100 main values, plus additional extended address information, as Input Registers for each monitor. The following Modbus TCP parameters can be entered from the "Options" selection on the menu.

DeltaV and VIMNet Configuration

1. Use the VIMNet Explorer utility to configure the VIM card.

Open VIMNet Explorer. Expand VIMNet and Physical Network until I/O Net is displayed, as in the image below. Right-click on I/O Net and select "New Controller."

A prompt will appear asking for a controller name. The name of the controller used in this example is shown below.

Expand I/O Net until the new controller (labeled “NODE1” in this example) is displayed. Right-click on the controller and select "New IO VIM."

A prompt will appear requesting specific configuration information about the new I/O VIM. For configuring the VIM to work with the EBIM node, enter a valid IP address on the device network and select the appropriate parameters based on the VIM type.

Expand the controller and the newly created I/O VIM, then expand C57 to show the two ports attached to Card 57. Right-click on P01 and select "Add Device."

Set the IP Address to the IP Address of the A6824R modules. Click "Add" to define redundant IP addresses for the two A6824R modules. Redundancy with No Switching IP means the field device has two IP addresses, where the active IP address can be either of the IP addresses defined.

After the IP Address is selected, add a description and click "OK."

A new device should now appear under the first port of Card 57. This device is the Modbus TCP CSI 6500. VIMNet Explorer simply configures the VIM to map a DeltaV Device Address to an IP address in the field.

Right-click on the VIM placeholder under the EBIM controller node and select "Commission."

Select the VIM connected to the backplane containing the DeltaV controller and click "OK."

Repeat for the redundant VIM.

A blue arrow will appear next the VIM placeholder after it has been successfully commissioned. The arrow indicates that an upload is required to the VIM due to the difference between the VIMNet Explorer configuration and the running configuration in the VIM. Right-click on the VIM placeholder and select "Upload Configuration to VIM." After the upload is complete VIMNet should indicate a successful upload and the blue arrow should disappear.

VIMNet Explorer is now fully configured and the VIM can now map a DeltaV device to a field IP address.

2. Configuring a DeltaV Controller to Communicate to the CSI 6500

Launch DeltaV Explorer. Expand System Configuration, then expand Physical Network. Right-click on "Control Network" and select "New->Controller."

Give the controller a name, then right-click the controller and select "Commission." Select the controller from the decommissioned nodes list. If the controller does not appear on the decommissioned nodes list, please investigate the DeltaV network.

When prompted Auto-sense the I/O cards. The I/O card may be auto-sensed because we have already configured in the VIM in the previous section. If the DeltaV is configured before VIMNet the cards will need to be manually added or auto-sense later.

Expand C57, then right-click on P01 and select "Properties."

Check the Enable box for the port, then click "OK."

All devices under a port share the same communications mode and timing values.

Mode
Master - all underlying devices in this port will be considered as external slaves to whom the VIM will connect.

Slave - the underlying datasets will be "servers" to which one or more external masters will connect. The VIM only listens for new connections in this mode.

Retry Count
This is the number of times a message will be transmitted, if there are errors, before the VIM gives up on a specific message. This number does not include the original message transmission. For example, setting this value to 5 could potentially result in a message being transmitted 6 times before the VIM gives up and moves on to the next message in the transmit buffer.

This retry count does not include any retry attempts due to underlying protocols, such as TCP. For example, TCP includes a sophisticated retry mechanism based on message round trip time. Retries at the TCP layer do not count against this retry count.

Message Timeout (ms)
This is the amount of time the VIM waits for a response (i.e., the command result) to a message before giving up on it and moving to the next message. This timeout is an application-layer message timeout, it is in addition to the built in TCP message timeout. This timeout value should be set high enough so that there is enough time for the field device to service the request and round-trip message transmission.

The total time the VIMVI may wait before reporting an error is:

Session Timeout = (Retry Count + 1) * Message Timeout

If the field device does not respond within the session timeout, the VIM will close the connection. The VIM will attempt to reconnect to the field device after waiting 15 seconds. The VIM will continue this behavior until it connects with the field device.

This message timeout does not include any timeouts set by the underlying protocols, such as TCP. For example, default TCP timeout mechanisms could wait multiple minutes before disconnecting. The VIM overrides this behavior with the session timeout in the above equation.

Transmit Delay (ms)
For all messages related to field devices on this port, the VIM will insert the specified amount of time between each message it transmits on the network. This is a tuning parameter for slower devices that do not have large message buffers for network messages. This parameter is especially useful for Ethernet-to-serial gateway devices.

Send Outputs on Startup
When this option is checked, the VIM will write all output values to the target field device after one of the following events occurs: Reboot, DeltaV card download, DeltaV controller download, or DeltaV controller power cycle. After this "first pass" the VIM will resume normal output operations (i.e., write outputs on state change).

When this option is unchecked, the VIM will only write output values on state change.

Next, right-click on P01 under C57 and select "New Serial Device."

Ensure that the “Device Address” parameter is set to the same node address assigned to the device in VIMNet Explorer.

Right-click DEV01 under P01 and select "New Dataset." A dataset will be created for each physical IO module in the CSI 6500 chassis.

The following instructions are for configuring each of the datasets:

• FC 01 - Read Coil Status – Device data type = 0, Input
• FC 02 - Read Input Status – Device data type = 1, Input
• FC 03 - Read Holding Registers – Device data type = 3, Input
• FC 04 - Read Input Registers – Device data type = 2, Input
• FC 05 - Force Single Coil – Device data type = 0, Output type = 1
• FC 06 - Preset Single Register – Device data type = 3, Output type = 1
• FC 15 - Force Multiple Coils – Device data type = 0, Output type = 0
• FC 16 - Preset Multiple Registers – Device data type = 3, Output type = 0

For more information on configuring a DeltaV dataset with Modbus TCP mappings, please consult the VIMNet Explorer Help Topics.

In this example, two modules are assigned to the DeltaV controller. The first landing module will read the input module channels, while the second module will write data to the output module channels. Landing modules should be created based on the standards of the DeltaV end-user.

Finally, right-click on the DeltaV controller and select "Download"; choose to download the whole controller.

DeltaV is now ready to communicate to the CSI 6500 in the field. The IO has now been fully migrated from the channels on the modules to the A6824R across the Ethernet network via Modbus TCP to the VIM card and presented to the DeltaV serial dataset channels.

Redundancy Mode

Redundant Field Device with Single Chassis
In this case the field device has a single chassis but uses two network interface cards for communications with the VIMs. Connect each network card to a separate isolated switch corresponding to the VIM. The IP address of these network cards can be consecutive, e.g. 192.168.1.101 and 192.168.1.102.

VIM A opens connections with both IP addresses 192.168.1.101 and 192.168.1.102. VIM B also opens connections with both IP addresses 192.168.1.101 and 192.168.1.102. The Active VIM communicates with the first IP address, while continuing to ping the second IP. The Standby VIM sends a periodic ping to its connected IP addresses. The ping allows the Standby VIM to ensure that the communication paths are valid. If the Standby VIM cannot verify the network path, an error message will be reported in DeltaV. The error message will indicate the Standby problems, and switchover will not be available. If the standby path is valid, you can command VIM switchover using DeltaV Diagnostics.

Note: Both Active and Standby VIM’s use a ping to determine presence of field devices. Note that by default the ping comprises the Modbus Diagnostics command. This command uses Function 8, Sub-Function Hi=0, Sub-Function Lo=0, and 2 bytes of data. The normal response to this command is to loop back the same data. Users can configure the standby VIM’s ping mechanism. The options are as follows: Default Ping, Customer Ping, ICMP Ping.

To better support the integration of the CSI 6500, MYNAH recommends using the custom ping:

This flag allows users to select any input dataset (one that uses Device Data Type of 0, 1, 2 or 3), and use it as the ping. By adding 10 to the Device Data Type of an input dataset indicates to the standby VIM that this dataset should be used as the ping. Instead of sending Function 8 command, the standby VIM will send the read command associated with the dataset. For example, if there is a dataset that reads Input Registers, it will be configured with a Device Data Type of 2. By changing the Device Data Type to 12 allows the standby VIM to use this dataset as a ping.

If the Active VIM loses communications with the first IP address, it starts using the second IP address and does not request a switchover. Only if both IP address connections are lost will the Active VIM request a switchover. The DeltaV controller verifies that the switchover is possible and then commands the currently Active VIM to go Standby, and at the same time commands the currently Standby VIM to go Active. Both VIMs maintain current DeltaV outputs. On switchover, the new Active VIM immediately starts scanning the field inputs to update its internal database.

Scenario 1 Operating Conditions

• VIM A is active
• VIM A is scanning 192.168.1.101 and Pinging 192.168.1.102
• VIM B is pinging 192.168.1.101 and 192.168.1.102

Scenario 2 Operating Conditions

• VIM B is active
• VIM B is scanning 10.22.6.50 and Pinging 10.22.6.51
• VIM A is pinging 10.22.6.50 and 10.22.6.51

Expected Results

For the tests below, the following diagnostics dataset registered are monitored in a DeltaV control module:

R33 Connected Device Mask
A bit set indicates the above reported IP address is connected. A bit clear indicates no connection or a failed connection. Bit 0 corresponds to IP address in register R1, Bit 1 corresponds to IP address in register R2, etc.

R36 Primary Device Status
Bit mask status of primary device connections. A bit value of 1 indicates connected, and a value of 0 indicated a disconnected device.

R37 Secondary Device Status
Bit mask status of secondary device connections. A bit value of 1 indicates connected, and a value of 0 indicated a disconnected device.

R38 Connected Device Mask from Partner
A bit set indicates the above reported IP address is connected. A bit clear indicates no connection or a failed connection. Bit 0 corresponds to IP address in register R1, Bit 1 corresponds to IP address in register R2, etc.

R39 Primary Device Status from Partner
Bit mask status of primary device connections. A bit value of 1 indicates connected, and a value of 0 indicated a disconnected device.

R40 Secondary Device Status from Partner
Bit mask status of secondary device connections. A bit value of 1 indicates connected, and a value of 0 indicated a disconnected device.

When R33 is greater than or equal to R38 the VIMs do not switch as the Active VIM connection integrity identified by R36, and R37 are better or equal to the connection integrity of the Partner VIM identified by R39 and R40.

6824R A: 10.1.98.47

6824R B: 10.1.98.57

1. Stable Normal Operation
Once the system is configured and normal operation is stable (no switchovers on any communication modules), allow the system to operate for 24 hours to verify that there are no intermittent switchovers on any of the communication devices. Follow standard troubleshooting techniques if unusual behavior is noted during this run-in period.

The system ran 24 hours as expected with a standard configuration highlighted in this manual.

2. Simulate Failed CSI 6824R A
With no random switchovers and the CSI 6824R A module as the primary, remove the primary CSI 6824R A module from the chassis to simulate a failed module. This should cause the CSI 6824R modules to switch and the VIMs should not switch.

In DeltaV Diagnostics, the partner VIM will report a failure to ping 6824R A.

The diagnostics registers identify a loss to 6824R A on both the Active and Partner VIM; data is not lost.

3. Simulate Failed CSI 6824R B
Once the 6824R switchover completes, and 6824R B assumes the primary role, re-install the removed 6824R and allow the system to stabilize. Repeat the previous test by removing CSI 6824R B from the backplane. CSI 6824R modules should switch and the VIMs should not switch.

In DeltaV Diagnostics, the partner VIM will report a failure to ping 6824R B.

The diagnostics registers identify a loss to 6824R B on both the Active and Partner VIM; data is not lost.

4. Simulate Failed Network Switch/Ethernet Cable (CSI 6824R A)
Once the 6824R switchover completes, and 6824R A re-assumes the primary role, re-install the removed 6824R and allow the system to stabilize. Unplug the Ethernet cable between the CSI 6824R A and the network switch. Communications on the CSI 6500 should switch and VIMs should not switch.

In DeltaV Diagnostics, the partner VIM will report a failure to ping 6824R A.

The diagnostics registers identify a loss to 6824R A on both the Active and Partner VIM; data is not lost.

5. Simulate Failed Network Switch/Ethernet Cable (CSI 6824R B)
Reconnect the Ethernet between 6824R A and the network. Allow the system to re-stabilize. Unplug the Ethernet cable between the CSI 6824R B and the first network switch. Communications on the CSI 6500 should switch and VIMs should not switch.

In DeltaV Diagnostics, the partner VIM will report a failure to ping 6824R B.

The diagnostics registers identify a loss to 6824R B on both the Active and Partner VIM; data is not lost.

6. Simulate Failed Interconnection Cable between Network Switches
Restore the system to a stable configuration with CSI 6824R A as the primary module. Disconnect the interconnection cable between the switches. This will prevent the CSI 6824R modules from seeing each other, simulating a failed or missing cable. There should be no communication switchover on either system. However, 6824R B should report a “94E10” error in the configuration software.

In DeltaV Diagnostics, the partner VIM will report a failure to ping 6824R A.

The diagnostics registers identify a Primary VIM connection loss to 6824R B and a partner VIM connection loss to 6824R A; data is not lost.

7. Simulate Failed Network Switch/Ethernet Cable (VIM A)
Restore the system to a stable configuration with CSI 6824R A as the primary module. Unplug the Ethernet cable between the VIM A and the switch. Communications on the CSI 6500 should not switch, but the VIM communication should switch.

In DeltaV Diagnostics, the previously Active VIM will report a failure to ping either IP address. The VIMs have switched in DeltaV Diagnostics.

The diagnostics registers identify a complete connection loss of the newly standby VIM; data is not lost.

8. Simulate Failed Network Switch/Ethernet Cable (VIM B)
Restore the system to a stable configuration with CSI 6824R B as the primary module. Unplug the Ethernet cable between the VIM B and the DeltaV Smart Switch. Communications on the CSI 6500 should not switch but the VIM communication should switch back to VIM A.

In DeltaV Diagnostics, the previously Active VIM will report a failure to ping either IP address. The VIMs have switched in DeltaV Diagnostics.

The diagnostics registers identify a complete connection loss of the newly standby VIM; data is not lost.

Contact

Please contact MYNAH for any questions about this integration at:

MYNAH Technologies
390 South Woods Mill, Suite 100
Chesterfield, MO 63017 USA
1.636.728.2000
support@mynah.com

MYNAH Technologies has released a complete set of Dynamic Simulation Application Packages for the Petrochemical Industry.

The New Petrochemical Industry

The shale gas revolution is driving the renaissance of the chemical and process industries in North America. With low cost natural gas comes low cost feedstock for many chemical compounds. Methane, Ethane, Propane, and Butane are trading at record low prices, providing an economic boost for the chemical industry. The American Chemistry Council released a report in May 2013, predicting capital investment of $72 BB, in over 100 new chemical plant projects, through 2020 in North America. This report claims that this investment will result in 500,000 additional jobs, many in plant operations.

But how will these new chemical plants find and train the operations staff to run them? How will they safely automate or modernize their process investments? How will these plants take advantage of new technology safely and mitigate the very real risks of plant operations? The business case has never been stronger for Life Cycle Dynamic Simulation. At MYNAH, we are committed to providing a platform to address the risks of the new Petrochemical industry and help these plants thrive and prosper.

Application Packages for Petrochemical

We began several years ago by delivering a step change in value, reduced life cycle cost, and greater usability for ammonia plant dynamic simulators. This year we extended it to the other petrochemical processes with growing investments. Each of our Dynamic Simulation Application Packages provides accurate, real-time I/O updates to control system simulators. The individual process reactors, separation equipment, pumps, compressor, and piping are rigorously modeled using Mimic’s Advanced Modeling Objects. The dynamic simulation consists of real-time, dynamic, first principles unit operation models configured and tuned to respond closely to the actual operations of the plant.

The application packages available for the petrochemical industry are:

• Mimic Dynamic Simulation for Ammonia Plants
• Mimic Dynamic Simulation for Methanol Plants
• Mimic Dynamic Simulation for Ethylene Plants
• Mimic Dynamic Simulation for Propylene (PDH) Plants
• Mimic Dynamic Simulation for Methanol to Propylene (MTO/MTP) Plants
• Mimic Dynamic Simulation for Polypropylene Plants

In addition, Control Global published a case study in July 2015 , documenting the use of Life Cycle Dynamic Simulation at US Nitrogen in Ammonia plant simulation shortens ramp up, improves training.

These application packages are proven to help petrochemical plant operations optimize their automation platform and address their operator training needs.

Other Resources to Review

• Control Global 2016 Reader's Choice Awards 2016 Reader's Choice Awards
  
• Automation World's 2015 Leadership in Automation
• Process Control Improvement with Mimic v3.6.2
• Life Cycle Dynamic Simulation with Mimic
• Business Case for the Virtual Plant

I look forward to your comments, questions, or suggestions.

Hope to hear from you soon.

Mart Berutti, 02/12/16

Introduction

This article walks through the workflow of using the DeltaV Virtual IO Module (VIM) starting with registering for an account at MYNAH.com to creating DeltaV datasets.

1. Locate the Site ID
2. Register for an Account
3. Download the latest version of VIMNet Explorer and the VIM Firmware
4. Install the VIM Hardware
5. Prepare the VIMNet Explorer Computer
6. Install, Run, and Set Up VIMNet Explorer
7. Commission the Simulation VIM
8. Flash Upgrade the VIM with the VIM Firmware
9. Create the IO VIM Placeholder
10. Commission the IO VIM
11. Create the IO VIM Configuration
12. Upload the Configuration to the VIM
13. Verify Cards are Emulated by the VIM
14. Configure the DeltaV Datasets

1. Locate the Site ID

Every instance of the VIM has an associated Site ID. This is a unique number that allows MYNAH to track, maintain, and support each unique licensed instance of the VIM firmware. This is NOT the same number as, nor is there any direct correlation to, the DeltaV System ID. Every time a copy of any VIM firmware is purchased, the Site ID is emailed with the Order Confirmation to all listed parties on the PO. VIM firmware Site IDs are allocated per purchase order and per type. For example:

• If one Modbus TCP/IP VIM firmware is purchased, one unique Site ID will be provided.
• If two copies of the Modbus TCP/IP VIM firmware are purchased with a single PO, only one Site ID will be provided.
• If one Modbus TCP/IP VIM firmware is purchased and another is purchased later or with a different PO, each firmware will have a unique Site ID.
• If one Modbus TCP/IP VIM firmware and one ODVA EtherNet/IP VIM firmware are purchased, two Site IDs will be provided; one for each type regardless of whether they are all purchased with the same PO.
• If two copies of the Modbus TCP/IP VIM firmware and one ODVA EtherNet/IP VIM firmware are purchased with the same PO, two Site IDs will be provided.

A Site ID will be required to download associated files and receive support. The Site ID can be found in the confirmation email sent to all listed parties on the PO. If the confirmation email cannot be found, register for an account at MYNAH.com, open a support ticket requesting the Site ID, and provide the following information:

• Company Name and location that owns the VIM firmware
• Firmware type
• Date of purchase

2. Register for an Account at MYNAH.com

MYNAH recommends that every person who requires access to downloads and technical support register for a unique user account at MYNAH.com. End customers, Emerson Local Business Partners and integrators may all register for an account, open support tickets, and access downloads associated with a Site ID. To access the registration form, go to http://www.mynah.com, click "MENU," expand Client Login under Resources, and click "Register." New users will have the opportunity to specify Site IDs when registering. Access to the downloads for the Site ID will be granted if the Site ID is provided at registration.

The application for registration will be reviewed by MYNAH staff during normal business hours. The approval process will typically only take a few minutes. Applications submitted after business hours will be reviewed on the next business day. A confirmation email with instructions for logging in will be sent once the account has been approved.

If the Site ID was not specified at the time of registration or the firmware was purchased after registration, Site IDs can still be applied to the user account. Simply open a support ticket and request to add the Site ID to your account.

For more details about an account at MYNAH.com and how to open a support ticket, see the following link: My Account at mynah.com Features and Directions

3. Download the latest version of VIMNet Explorer and the VIM Firmware

The latest versions of the VIM firmware and VIMNet Explorer downloads can be found on the Site ID page that can only be accessed by users that have successfully linked their accounts to the Site ID. To access the Site ID page, log onto your account, click "MENU" at the top-left, and click the "Software Licenses" button. The Software Licenses page will list all of the Site IDs associated with the user account, including overview details about the site such as: the Company Name, Product Family, and Support Expiration. Click the Site ID to access the Site ID page. Note: Any number of users may be attached to and access the Site ID page.

Notice the Support Expiration section. Downloads will not be available for this Site ID if support has expired. Annual support will need to be purchased through the Emerson Local Business Partner to continue access to downloads and technical support.

If support is not expired, attached users can download any of the files listed in the Site ID's Downloads section by following the links. The following files will be available:

• Latest version of VIMNet Explorer
• Latest version of the VIM firmware
• Latest version of the Simulation Firmware (All new VIM2 hardware are pre-flashed with Simulation firmware)

Download these files to the computer which will run VIMNet Explorer.

Virtual IO Module Hardware Installation

5. Prepare the VIMNet Explorer Computer

The following items are requirements for VIMNet Explorer:

• Disable Anti-Virus software
• Turn off Windows Firewall
• VIMNet Explorer must be run with Administrator privileges (right-click the VIMNet Explorer icon and select Run as Administrator).

If these requirements are not met, MYNAH cannot guarantee complete and proper functionality of VIMNet Explorer. Anti-virus software, the Windows Firewall, and the lack of Administrative privileges on the computer can all prevent VIMNet Explorer from properly accessing the computer's network card, resulting in failures that include but are not limited to:

• Failure to detect VIMs on the network
• Failure to commission/flash VIMs or upload the configuration
• Failure to gather diagnostics information from the VIM using VIMNet Diagnostics

If any of these failures are encountered, check that the requirements have been met. These failures very rarely occur when the above requirements have been met. If any of these failures is encountered after ensuring that the above requirements are met, please contact MYNAH Technical support.

6. Install, Run, and Set Up VIMNet Explorer

After the files have been downloaded from the Site ID page, extract all of the .zip files. Run the VIMNet Explorer installer and follow the installer's instructions.

Once installed, locate VIMNet Explorer under the Windows Start Menu, right-click the icon, and select "Run As Administrator." This step is necessary even if logged into the Windows machine as an administrator. If VIMNet Explorer is launched without Administrator privileges, it will open but VIM operations over the network, such as commissioning and flashing, may fail.

If prompted to select a network card (NIC) when VIMNet Explorer is initially launched, select the IP Address of the computer from the "Available NIC" selection and click the "Add" button. The IP Address of the NIC that is connected to the VIM/PLC network must be used. Only the correct IP Address should be listed in the Used Addresses field. If there are multiple IP Addresses listed there, select and delete all IP address that are not connected to the VIM/PLC network. Once the PC IP address on the VIM/PLC network is the only IP in the list, click "OK" to continue to VIMNet Explorer.

Verify that the network settings are correct. Right-click "Physical Network" in the tree on the left side of the VIMNet Explorer window and select "Properties." Again, make sure that only the correct IP Address is listed under the Used IP Address. Delete any other IP Addresses from the list.

VIMNet Explorer Installation

7. Commission the Simulation VIM

All new VIM2 hardware shipped to customers will be pre-loaded with Simulation firmware. This firmware is designed for process simulation use with Mimic Simulation Software and the Mimic Railbus SIO Driver. Simulation Firmware is not a valid Industrial Ethernet Gateway firmware. The VIM must be commissioned and flashed to the desired firmware before it can be used as a gateway VIM. A VIM cannot be commissioned to a placeholder in VIMNet Explorer that does not match the firmware type currently loaded on the VIM. In VIMNet Explorer, there are two classes of VIM placeholders; Simulation VIM placeholders, and I/O Net VIM placeholders. Because new VIM hardware shipped from Emerson comes with Simulation Firmware, they must be commissioned to a Simulation VIM placeholder to be flashed to the appropriate Gateway IO Driver for use in a real process.

To get started, click the Decommissioned VIMs list to see the list of available VIMs on the network. If any of the VIMs are missing from the list, right-click "Decommissioned VIMs" and select "Refresh." Refreshing the list sends a special beacon on the network and all VIMs are designed to respond to this message. VIMNet Explorer will populated the decommissioned VIMs list based on the responses that are received. If no VIMs are listed, VIMNet Explorer was either not able to send the command or no responses were received.

If no VIMs are listed under the Decommissioned VIMs list, verify the following:

• The computer has been prepared correctly based on the steps provided above
• VIMNet Explorer was run as Administrator as instructed previously
• The network connection to the VIM is good; it may be helpful to simplify the network by connecting the VIM directly to the computer

Once all of the VIMs are available in the Decommissioned VIMs list, create a VIM placeholder under "Simulation Net." Right-click the Simulation Net and select "New Simulation VIM." Provide a valid and available IP Address and a valid subnet mask for the VIM. Use the Ping button to verify that no other device on the network has this IP Address. Click "OK" when done.

Right-click the Simulation VIM placeholder and select "Commission." All Simulation VIMs should be listed as available for commissioning. VIMs with different firmware types will not be listed. Select the VIM to commission and click "OK." Once the VIM has been commissioned, the IP Address at the placeholder will be applied to the VIM. Use the VIMNet Explorer computer to ping the VIM's IP Address to verify that the VIM is correctly responding on the network.

[VIDEO DEMO] Starting VIMNet Explorer and Commissioning VIMs

8. Flash Upgrade the VIM with the VIM Firmware

At this point, the VIM should have Simulation firmware flashed and be commissioned with a valid IP Address. The VIM must be flashed to a different firmware to act as an Industrial Ethernet Gateway. At least two .hex files should have been included in the files downloaded from the Site ID page: a Simulation firmware .hex file and an Industrial Ethernet Gateway .hex file. For VIM2 hardware that is currently flashed with Simulation firmware at or below version 2.5.3, a flash to latest Simulation firmware is required. Once the VIM is flashed to the latest Simulation firmware, the VIM can be flashed using the Industrial Ethernet Gateway .hex file downloaded from the Site ID page.

In VIMNet Explorer, right-click the Simulation VIM placeholder again and select "Properties." Click the "Flash Upgrade" button, browse to and select the .hex file, and click "OK." This will start the flash process and it may take several minutes to complete. If the flash fails for any reason, check the following:

• Verify that the system requirements have been met as previously discussed
• Verify that the VIM responds to network pings
• Verify that the correct file (.hex) is being selected for flashing
• Verify that the .hex file is saved on the local computer and is not stored on a thumb drive or network drive

If the VIM firmware type was not changed during the flash upgrade, as would be the case when flash upgrading from an older version of Simulation firmware to the latest, the VIM will remain commissioned. After this initial VIM flash to the latest version of Simulation firmware is complete, the instructions above should be repeated to flash upgrade the VIM to the Industrial Ethernet Gateway firmware.

If the VIM firmware type was changed during the flash upgrade, the VIM should be automatically decommissioned because a VIM cannot be commissioned to a placeholder that does not match its firmware type. Sometimes it may take a moment for VIMNet Explorer to show that the VIM has been decommissioned. If the icon is not updating, press the F5 key to update the display. The VIM should also be listed under the Decommissioned VIMs list with the updated firmware version that matches the version listed in the name of the .hex file. This VIM is now ready to be commissioned to an I/O VIM placeholder.

[VIDEO DEMO] Flash Upgrading VIMs

9. Create the IO VIM Placeholder

An I/O VIM placeholder must now be created, similar to how a Simulation VIM placeholder was created when the VIM was flashed with Simulation firmware. Right-click I/O Net and select "New Controller." Provide a name for the controller to match the name of the controller in DeltaV. Right-click the controller and select "New IO VIM." A new configuration window will appear. Perform the following:

• Select the firmware type
• Check the box “VIM is Redundant” if this is a redundant application
• Check the box “M-Series IO” if this is an M-Series VIM
• Check the box for “VIM 2” if this is a VIM2
• Select the serial card range (57-60 or 61-64) if the VIM is Simplex; all cards will be used if the VIM is redundant
• Provide a name, IP Address, and Subnet for the VIM(s)
• Click the Ping button to verify that the provided IP Address is available

Click "OK" to finish once the VIM placeholder has been configured.

10. Commission the IO VIM

Right-click the newly created I/O VIM Placeholder and select "Commission." Your VIM should appear in the list of available VIMs. Select the VIM and click "OK." Click "OK." to confirm the commission. Verify that the VIM has been properly commissioned by using the VIMNet Explorer computer to ping the VIM.

If the VIM does not appear in the list of available VIMs, check the following:

• Verify that the system requirements have been met as previously discussed
• Verify that the VIM is decommissioned by checking the LED status on the VIM
• Verify that the VIM is listed in the Decommissioned VIMs list with the correct firmware version
• Verify that the VIM firmware type was correctly selected in the VIM placeholder configuration

Commission a Simplex VIM

Commission a Redundant VIM

11. Create the IO VIM Configuration

The next step is to add devices in VIMNet Explorer that correspond to the devices in DeltaV. If a device is configured in DeltaV under Card 57, Port 1, then a device must be added in VIMNet Explorer under Card 57, Port 1. Make sure to create a device in VIMNet Explorer for every device in DeltaV regardless of which firmware is flashed to the VIM.

To add a device, expand the VIM, expand one of the cards, right-click the Port, and select "Add Device." A new windows will pop up for defining the device. Change the Device Address to match the device address in DeltaV Explorer. Click the "Add" button and specify the IP Address of the device and click "OK." Click "OK" again to finish the device configuration.

Modbus TCP: Field Device Configuration, Field Device IP Address

Rockwell PLCs EtherNet/IP: Field Device Configuration, Field Device IP Address

Generic Devices EtherNet/IP: Field Device Configuration, Field Device IP Address

ODVA EtherNet/IP: Field Device Configuration, Field Device IP Address

If using the IOD-4101/4111 or IOD-4102/4112 firmwares, no additional configuration for the device is required. If using IOD-4104/4114 or IOD-4116, at least one connection definition must be created and assigned to the device. The connection definition defines the communication details. When IOD-4101/4111 or IOD-4102/4112 are used, the communication details are defined by the dataset configuration in DeltaV.

Generic EtherNet/IP Connection Definition

ODVA EtherNet/IP Connection Definition

The I/O VIM Configuration will be complete once all of the devices have been added (with connection definitions if necessary).

[VIDEO DEMO] Configuring Devices with ModbusTCP

12. Upload the Configuration to the VIM

Once the configuration is finished, right-click the VIM and select "Upload Configuration to VIM." There is an option to upload the configuration to VIM A, VIM B, or Both if this is a redundant VIM pair. The configuration will need to be uploaded to both VIMs, either individually or all at once. The VIM's serial cards should be visible to the controller across the railbus after uploading the configuration to the VIM.

13. Verify Cards are Emulated by the VIM

The VIM should emulate the DeltaV serial cards after the configuration has been uploaded. The VIM cards can be added to DeltaV automatically or manually. To automatically add the VIM's cards to DeltaV and verify that the VIM is emulating the cards in one step, right-click <Controller> -> I/O and select "Auto-sense I/O Cards." The VIM's configured cards (57- 60 or 61-64) should be auto-sensed by the controller and added to the controller's I/O automatically. Next, download all four cards. After the download, right-click the controller and select "Diagnose" to open DeltaV Diagnostics. Verify that the Serial Cards do not show "Configured but not Present" errors. The VIM is properly emulating the serial cards if there are no errors at this point.

If the cards are added manually, then the emulation will need to be verified through DeltaV Diagnostics. To add the cards manually, right-click lt;Controller> -> I/O and select "New Card." Select the following settings for the card:

• Card Class: Serial Cards
• Card Type: 2 Ports, Programmable, RS232|RS485
• Card Series: M or S Series depending on the series of the controller
• Slot Position: 57-60, or 61-64

All four of the VIM's cards must be added then downloaded. Once the cards have been downloaded, right-click the controller and select "Diagnose" to open DeltaV Diagnostics. Verify that the Serial Cards do not show "Configured but not Present" errors. The VIM is properly emulating the serial cards if there are no errors at this point.

14. Configure the DeltaV Datasets

Instructions for configuring DeltaV datasets for the Rockwell PLC EtherNet/IP driver and Modbus TCP/IP driver can be found in the VIMNet Explorer Help files:

Modbus TCP/IP DeltaV Dataset Configuration

(Rockwell PLCs) EtherNet/IP DeltaV Dataset Configuration

The DeltaV dataset configuration for the Generic EtherNet/IP and ODVA EtherNet/IP drives is defined by the connection definition. In VIMNet Explorer, browse down to "Device→Connection Definition→Dataset." Click on the dataset. The DeltaV dataset configuration for this connection definition will be listed on the right-hand side. Copy the configuration exactly to the dataset in DeltaV.

[VIDEO DEMO] Configuring Datasets with ModbusTCP

Contact

MYNAH Technologies
+1.636.728.2000
support@mynah.com

These release notes are for the Mimic v3.6.2 DeltaV Utility v4.1.46.

Product Description:

These release notes are for the Mimic v3.6.2 DeltaV Utility v4.1.46. The previous released utility version is v4.1.45.

Installation:

The release comprises a 32-bit and 64-bit version of the following two files:

1. DVUtil.exe; and
2. ParserEngine.dll

To install, replace the existing files with the new in the Mimic folder.

Who should upgrade?

The following FHX Grammar Updates were implemented

PLEASE CONTACT US FOR ANY QUESTIONS ABOUT THESE RELEASE NOTES AT:

MYNAH Technologies
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017
+1.636.728.2000
support@mynah.com

One of the larger producers of nitric acid for use in fertilizers in the US had to work through the design, procurement and construction of its new ammonia plant. There was also an immediate need to find skilled workers to operate the facility.

Advanced simulation technology was used before the plant was built and operational to train operators in startup and shutdown, as well as how to handle rare process excursions that they may have not seen with even 10 years of experience.

Todd Jaco explains how using an effective ammonia plant operator training system can greatly reduce startup time. Read more on page 101.

In the last hours of 2017, right before the Holidays, the Mimic Development team gave the process industry a big Christmas present. Mimic v3.7.1 is the first Mimic release from the new Emerson Process Simulation Center of Excellence, formerly MYNAH Technologies. This release is packed with capabilities that make the development and maintenance of Lifecycle Dynamic Simulation much easier while, at the same time, improving process model performance. All Mimic users current on Mimic Software Support can download and start using this new release right away.

Mimic Simulation Studio PFD View in Mimic v3.7.1 is a new way of building and viewing Advanced Models. Completely user selectable, Mimic users can continue to use the existing IEC1131 methodology, configure models using PFD view, or even convert existing models from IEC1131 to PFD style. Model execution and functionality remains the same when using IEC1131 or PFD view. PFD View delivers an intuitive and functional way of building dynamic process models including the following advancements:

• Excellent flowsheet space conservation allowing large process areas on one flowsheet.
• Process models look like plant P&IDs and PFDs with easily recognizable equipment symbols.
• Ability to customize equipment and unit ops real-time values per user requirements.
• Quick drag and drop object-based flowsheets increase the efficiency of model building.
• Stream View command shows dynamic flows across entire flow sheet in one table, making model tuning quick and intuitive.

Hyper-Fast Model Execution is now available for very fast processes or equipment. In Mimic v3.7.1 model execution threads have been enhanced to include 10, 25, and 50 msec model execution. This fast model execution can be applied to Mimic base models as well as advanced models. This allows users to build dynamic, real-time process models that exhibit the performance of their plant no matter how fast the process dynamics.

More Advanced Modeling Objects and Modeling Functions to make building real-time dynamic simulation in Mimic quicker and easier. The new Objects and Functions include:

• Pressure Regulator Object designed to maintain a target pressure drop or pressure with VLE balance.
• Orifice Plate Object designed to reduce the line pressure with VLE balance.
• Future Value Function Block to compute the future value of a process variable and rate of change with a good signal to noise ratio.
• PID Reset Functional Block provides reset action that compensates for a variable measurement update time.
• PID Performance Functional Block can be used in conjunction with a DeltaV ePID block to give the user information about their PID Performance.
• Joule-Thomson (JT) effect has been added to the outflow from Valves, Pressure Regulators and Orifice Plate objects.

A full list of all the functionality for Mimic v3.7.1 is available athttps://www.mynah.com/knowledge-base/mimic-v371-release-notes. At Emerson’s Process Simulation Center of Excellence, we are committed to make top quartile operational performance attainable to all users across the process industries. Faster, easier Lifecycle Dynamic Simulation with the lowest life cycle costs in the industry is our goal with every Mimic release.

More Information on Lifecycle Dynamic Simulation with Mimic

• Mimic Simulation Software v3.7.1 Release Notes
• Mimic Advanced Thermo Package
• Life Cycle Dynamic Simulation with Mimic
• Business Case for the Virtual Plant

I look forward to your comments, questions, or suggestions.

Hope to hear from you soon.

Mart Berutti, 02/16/18

This tutorial covers auto-sensing the VIM in DeltaV, creating a devices instance, creating a dataset, and viewing real-tim register values.

Part 4 of 4.

Part 1 - Starting VIMNet Explorer and Commissioning VIMs
Part 2 - Flash Upgrading VIMs
Part 3 - Configuring Devices with ModbusTCP