Integrating DeltaV Systems Using Modbus TCP Via VIM or VIM2 - MYNAH Technologies, LLC

10/30/2015
IntegratingDeltaVSystemsusingModbusTCPviaVIMorVIM2|MYNAHTechnologies,LLC
KNOWLEDGE BASE / TECHNICAL NOTES
Integrating DeltaV Systems

using Modbus TCP via VIM
or VIM2
By David Story
PRODUCT FAMILY: DELTAV VIRTUAL IO MODULE
This technical note describes the use of the Virtual IO Module to integrate data
from two DeltaV systems using Modbus TCP, with the VIM/VIM2 congured as
master and slave.
Using Modbus TCP and the Virtual IO Module (VIM or VIM2, M-Series or S-Series)
is a simple and eective way to link two DeltaV systems together over an
Industrial Ethernet network. The following should be considered when applying
this solution:
Slave functionality is available in Simplex applications only, i.e., the Slave
VIM/VIM2 must be deployed as Simplex. Master VIM/VIM2 may be Simplex or
Redundant.
In the case where both Master and Slave functions are required simultaneously,
the VIM/VIM2 must be Simpelx and can communicate with 16 slaves as Master,
and 16 masters as Slave.
https://www.mynah.com/content/modbustcpvim%E2%80%93masterslavecommunicationssetup
1/24
10/30/2015
Each DeltaV system will require one VIM or VIM2 and an IOD-4101, Modbus TCP
Driver.
DeltaV DST rules for serial card datasets shall apply on each system. Please see
the product bulletin for the DeltaV Virtual IO Module Network Gateway
(http://www.mynah.com/content/deltav-virtual-io-module-network-gateway)
for guidelines on DST counting for both VIM and VIM2.
This application notes demonstrates how to congure one VIM as a Modbus
master and another one as a Modbus slave for integration of two DeltaV systems.
It shows the conguration parameters for both master and slave VIM. In addition
it demonstrates how to congure one of VIMs ports as slave and the other as
master.
VIMNet Explorer Configuration of Master VIM

In the VIMNet Explorer user needs to add master ModbusTCP VIM placeholder.
The user can choose the IP address and subnet mask per his/her network
requirements.
Next step is to commission the VIM placeholder to a real physical VIM card.
2/24
10/30/2015
The following step is to add a SLAVE VIM device with device address and IP
address. The IP address needs to match congured slave VIMs IP address.
Next step is to upload the conguration to the master VIM. Right mouse click on
the Master_VIM placeholder and select VIM Conguration Upload as shown
below.
3/24
10/30/2015
VIMNet Explorer Configuration of Slave VIM

In the VIMNet Explorer user needs to add ModbusTCP VIM placeholder for Slave
VIM. The user can choose the IP address and subnet mask per his/her network
requirements.
4/24
10/30/2015
Next step is to commission the VIM placeholder to a real physical VIM card.
The following step is to add a SLAVE VIM device with device address and IP
address. The IP address needs to match congured slave VIMs IP address.
Next step is to upload the conguration to the slave VIM. Right mouse click on the
Slave_VIM placeholder and select VIM Conguration Upload as shown below.
5/24
10/30/2015
DeltaV Configuration of Master VIM

The DeltaV conguration of datasets is very simple. It starts by Auto-sensing for
new IO cards.
Once the 4 Programmable Serial cards are inserted, the IO needs to be
downloaded.
In order to start conguring devices user needs to choose the card and expand it
to see the ports. Right mouse click on Port1 and go to Properties. Check the
checkbox to enable this port as shown below.
6/24
10/30/2015
Click on Advanced tab. The following dialog will appear:
In this dialog, leave the default selection as Master mode. Then congure retry
count, message timeout and transmit delay according to your application. The
serial parameters on Communications tab are not used for VIM communications.
Next step is to right mouse click on Port and Add Serial Device. It opens the
following dialog box, where user needs to specify the device address and
description. Then click OK.
7/24
10/30/2015
Next, user needs to congure datasets in the Serial Device. To add a new dataset,
right mouse click on the Serial Device and select New Dataset. The following
dialog will appear:
In master mode user can select the direction. Its optional but user can also add
the dataset description to make the conguration more readable.
On the DeltaV tab user will select the DeltaV data type.
8/24
10/30/2015
On the PLC tab user will select the device data type, starting address (oset), and
number of values. In example below, the device data type is 3 or Holding
Registers.
The special data tab is not used unless the Floating Point data type is used. In that
case, user needs to congure 1 in special data 2.
9/24
10/30/2015
In another example we have congured a coil dataset.
On the DeltaV tab user needs to select the DeltaV data type.
On the PLC tab user needs to enter the device data type that is equivalent to coils.
Starting address is the oset of the full address, and number of values is desired
number of values for this dataset.
10/24
10/30/2015
The special data tab is not used for VIM slave communications except when data
type used is oating point with status.
Floating Point Dataset
11/24
10/30/2015
12/24
10/30/2015
13/24
10/30/2015
DeltaV Configuration of Slave VIM

The DeltaV conguration of datasets is very simple. It starts by Auto-sensing for
new IO.
Once the 4 Programmable Serial cards are inserted, the IO needs to be
downloaded.
In order to start conguring devices user needs to choose the card and expand it
to see ports.
Right mouse click on Port1 and go to Properties. Check the checkbox to enable
this port as shown below.
14/24
10/30/2015
Click on Advanced tab. The following dialog will appear:
In this dialog user needs to select the Slave mode. Select the transmit delay. Click
OK. The rest of messaging parameters are not available. The parameters under
Communications tab are not used for VIM communications.
15/24
10/30/2015
Next step is to right mouse click on Port and Add Serial Device. It opens the
following dialog box, where user needs to specify the device address and
description. Then click OK.
Next, user needs to congure datasets in the Serial Device. To add a new dataset,
right mouse click on the Serial Device and select New Dataset. The following
dialog will appear:
In slave mode the data direction is not signicant. Its optional but user can add
the dataset description to make the conguration more readable.
16/24
10/30/2015
On the DeltaV tab user will select the DeltaV data type.
On the PLC tab user will select the device data type, starting address (oset), and
number of values. In example below, the device data type is 3 or Holding
Registers.
17/24
10/30/2015
The special data tab is not used unless the Floating Point data type is used. In that
case, user need to congure 1 in special data 2.
In another example we have congured a coil dataset.
On the DeltaV tab user needs to select the DeltaV data type.
18/24
10/30/2015
On the PLC tab user needs to enter the device data type that is equivalent to coils.
Starting address is the oset of the full address, and number of values is desired
number of values for this dataset.
The special data tab is not used for unless the data type selected is Floating Point
with Status.
19/24
10/30/2015
Below is the example of DeltaV conguration for Floating Point Slave Dataset.
20/24
10/30/2015
21/24
10/30/2015
In the following dialog box user needs to specify value of 1 in special data 2 eld.
It sends the message to master that data in slave in Floating Point format and vice
versa.
Following screen capture shows the VIMNet Diagnostics with the master and
slave VIM.
22/24
10/30/2015
23/24
10/30/2015
MYNAH Technologies LLC

390 South Woods Mill Road, Suite 100
Chestereld, MO 63017 USA
+1.636.728.2000 (International)
+1.636.728.2001 (Fax)
Email: support@mynah.com
Web: www.mynah.com
MYNAH Technologies 2012 - 2015. All rights reserved.

Designs are marks of MYNAH Technologies, Emerson Process Management, DeltaV, and the DeltaV design are marks of one of the
Emerson Process Management of companies. All other marks are property of their respective owners. The contents of this
publication are presented for informational purposes only, and while every eort has been made to ensure their accuracy, they are
not to be construed as warrantees or guarantees, expressed or implied, regarding the products or services described herein or their
use or applicability. All sales are governed by our terms and conditions, which are available on request. We reserve the right to
modify or improve the design or specication of such products at any time without notice.
While this information is presented in good faith and believed to be accurate, Mynah Technologies does not guarantee satisfactory
results from reliance upon such information. Nothing contained herein is to be construed as a warranty or guarantee, express or
implied, regarding the performance, merchantability, tness or any other matter with respect to the products, nor as a
recommendation to use any product or process in conict with any patent. Mynah Technologies reserves the right, without notice,
to alter or improve the designs or specications of the products described herein.
24/24

Integrating DeltaV Systems Using Modbus TCP Via VIM or VIM2 - MYNAH Technologies, LLC

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Integrating DeltaV Systems Using Modbus TCP Via VIM or VIM2 - MYNAH Technologies, LLC

Transféré par

Droits d'auteur :

Formats disponibles

10/30/2015

KNOWLEDGE BASE / TECHNICAL NOTES

Integrating DeltaV Systems

VIMNet Explorer Configuration of Master VIM

VIMNet Explorer Configuration of Slave VIM

DeltaV Configuration of Master VIM

Click on Advanced tab. The following dialog will appear:

In another example we have congured a coil dataset.

Floating Point Dataset

DeltaV Configuration of Slave VIM

Click on Advanced tab. The following dialog will appear:

In another example we have congured a coil dataset.

MYNAH Technologies LLC

MYNAH Technologies 2012 - 2015. All rights reserved.

Vous aimerez peut-être aussi