Knowledge Base /
Product Bulletins
DeltaV Virtual IO Module Network Gateway
By Martin Berutti
Product: IOD-4101 - Modbus TCP/IP Master Driver (General Modbus TCP/IP Communications)

Note: The MYNAH Virtual I/O Module (VIM) is discontinued/maintained as of January 2014. No new units will be sold and technical support will be limited. The Emerson Virtual I/O Module 2 is the official replacement of the VIM.

M-Series VIM2

S-Series VIM2

The Virtual IO Module (VIM) Network Gateway provides a native DeltaV IO interface to Industrial Ethernet networks and devices that use the Modbus TCP/IP, EtherNet/IP, or the FMC722 protocol.

Using the VIM, DeltaV Controllers can read and write signals from plant floor devices connected to Industrial Ethernet networks such as PLCs, Motor Control Centers, and Weigh Scales.

Industrial Ethernet Integration to DeltaV Using the Virtual IO Module Network Gateway

Key Features of the Virtual IO Module Network Gateway

Seamless DeltaV Integration - Each Virtual IO Module is seen by the DeltaV Controller as up to 4 Virtual DeltaV Serial Cards. Commissioned Virtual IO Modules are auto-sensed by the DeltaV controller as DeltaV Serial Card(s)

Configured in DeltaV Explorer - Dataset configuration is done in the DeltaV Explorer in the same manner as a DeltaV Serial Card. IO signals can be used in DeltaV Control Modules and displayed on DeltaV Operate graphics.

Intuitive Setup - The VIMNet Explorer Utility makes setup of the Virtual IO Module easy and intuitive. Graphical, drag-and-drop functionality makes setting up the plant Ethernet network quick and easy.

Powerful Integration Solution - Each Virtual IO Module can emulate up to 4 DeltaV Serial Cards and support up to 128 Serial Card Datasets of information. Communication over the plant Ethernet network is fast and efficient.

Flexible Networking - User configurable IP addressing allows the Virtual IO Module to be used in almost any plant environment regardless of networking scheme. The Virtual IO Modules and the plant Ethernet devices must be on the same IP subnet to communicate.

1:1 Module Redundancy - Redundancy can be added to any system by adding a second Virtual IO Module and configuring the two modules as a redundant pair. The Virtual IO Module appears as up to 4 Redundant DeltaV Serial Card pairs. Automatic switchover of primary to standby cards is handled like the DeltaV Serial Card. The operator is given clear notification of a switchover at the operator display. Manual switchover can be controlled in DeltaV Diagnostics.

Redundant Virtual IO Modules with Redundant DeltaV Controllers

Modular Rugged Package - The DeltaV Virtual IO Module mounts in the same manner as the DeltaV controller. It mounts in the controller slot of a DeltaV 2-wide horizontal or 4-wide vertical carrier and uses a standard DeltaV Power Supply. The advanced design of the DeltaV Virtual IO Module will provide years of uninterrupted use.

VIM Product Description and Specification

The Virtual I/O Module mounts on a 2-wide carrier on the left-hand-side of the DeltaV controller. A dedicated DeltaV power supply is required. The DeltaV Controller auto-senses a commissioned Virtual IO Module as 4 DeltaV Serial Cards.

  • In simplex installations, these cards will be sensed in slots 57-60 or 61-64.
  • In redundant installations, the redundant pairs will be sensed in slots 57 to 64.

Configuration of the IO signals from the commissioned Virtual IO Module is done in the DeltaV Explorer in the same manner as a DeltaV Serial card.

VIMNet Utility - The VIMNET Utility allows the user to commission the Virtual I/O Module, setup primary and redundant Virtual I/O Modules, and the Industrial Ethernet Network. The user is able to specify the IP address, Subnet Mask, and Gateway of each Virtual IO Module and set the node address and names of each Plant Ethernet Network device that is used by the Virtual IO Module. The VIMNET Utility runs on the MS Windows XP or Windows 7 operating system and has an intuitive, graphical user interface. Connection to the Virtual IO Module is done through the Module RJ-45 Ethernet Connection.

Module Redundancy - Two Virtual IO Modules can be set up as a redundant pair for installation that require backup plant networks. Each Virtual IO Module will be installed on its own 2-wide carrier, with its own power supply to the left of the DeltaV Controller.

The active and standby Virtual IO Modules monitor each other with a continuous status command using the redundancy link cable supplied with each redundant pair. The active Virtual I/O Module communicates over the network to the Industrial Ethernet device and the standby sends an intermittent signal to the device to maintain communication integrity.

Redundant Industrial Ethernet Architecture Using the Virtual IO Module Network Gateway

Specifications of the DeltaV Virtual IO Module

Physical Specifications
Power Requirement Supplied by System Power Supply through 2-wide Power/Controller Carrier
Maximum Current 750 mA at 5 VDC
Fuse Protection 3.0 A, non-replaceable fuses
Power Dissipation 4.0 W typical, 5.4 W maximum
VIM User Memory 16 MB
Mounting On right slot of power/controller carrier OR vertical carrier
External Plant Ethernet Network One 10BaseT half-duplex 8-pin RJ-45 Connection
Redundancy Link One RJ-11 Serial Connection (cable supplied with redundant Modbus modules)
Size Dimensions 4.1 cm w x 15.9 cm h x 10.7 cm d
Weight 278 grams
Environmental Specifications
Operating Temperature 0 to 60 ° C (32 to 140 ° F)
Storage Temperature -40 to 85 ° C (-40 to 185 ° F)
Relative Humidity 5 to 95%, non-condensing
Airborne Contaminants ISA-S71.04-1985 Airborne Contaminants Class G2
Shock 10 g ½-sine wave for 11 ms
Vibration 1 mm peak-to-peak from 5 Hz to 16 Hz, 0.5 g from 16 Hz to 150 Hz
LED Indicators – On Status
Green -- Power Indicates DC power is applied
Red -- Error Indicates an error condition
Green -- Active Indicates that the VIM is commissioned and active
Green -- Standby Not used
Yellow Flashing -- Network Indicates valid network communication
Yellow Flashing – Ctlr I/O Indicates valid DeltaV I/O Bus communication
All except Power flashing, alternating even and odd Visual ID of controller initiated from user interface software by ping command
VIM Capacity
# Emulated DeltaV Serial Cards 4
# data sets per VIM 128 (32 per Emulated Card)
# TCP/IP Connections per VIM
  • IOD-4101 ModbusTCP:
    • Redundant mode: 16 slave field devices
    • Simplex mode: 32 slave field devices
    • Simplex mode mix:16 slave and 16 master field devices
  • IOD-4102 EthernetIP:
    • Redundant mode: 16 devices
    • Simplex mode: 32 devices
  • IOD-4104 Generic EthernetIP:
    • Simplex mode only: 32 devices
  • IOD-4105 FMC722 Ethernet Protocol:
    • Simplex mode only: normal expectation is two FMC TPU per VIM

Supported Industrial Ethernet Protocols

Modbus TCP/IP - The Virtual I/O Module with the Modbus TCP/IP Master Driver supports the following Modbus communications protocol function codes to read and write values to and from a Modbus slave device, as specified by the Modbus Application Protocol Specification from Modbus-IDA.org.

The Virtual I/O Module Modbus TCP/IP Driver supports the following Modbus function codes:

  • Code 1 - Read Coil Status
  • Code 2 - Read Input Status
  • Code 3 - Read Holding Registers
  • Code 4 - Read Input Registers
  • Code 5 - Force Single Coil
  • Code 6 - Preset Single Register
  • Code 8 - Diagnostic Loop Back Test
  • Code 15 - Force Multiple Coils
  • Code 16 - Preset Multiple Registers

The VIM can function as both a Modbus TCP/IP master and slave simultaneously. Master or slave mode is set at the virtual port level. In master-only mode, this driver can communicate with a maximum of 32 slave devices. Systems that use both master and slave mode can communicate with a maximum of 16 slaves and 16 masters at the same time. The master and slave capability is available in simplex implementations only. In redundant applications, only master mode is supported.

EtherNet/IP - The Virtual I/O Module with the EtherNet/IP Scanner Driver provides the following compatible functions using the Control and Information Protocol (CIP) as defined in the EtherNet/IP Specification from Open DeviceNet Vendor Association & ControlNet International.

Systems using either mode can communicate with a maximum of 16 devices at the same time.

The Virtual IO Module Ethernet/IP Scanner Class Driver provides:

  • EtherNet/IP Scanner Class (originator) functionality
  • UCMM (unconnected) messaging client and server Class 3 (connected) messaging client and server, including encapsulated DF1 message Class 1 (I/O) connection client and server

FMC722 Ethernet Protocol -

The VIM FMC scanner is an online process in the VIM. It is designed to run continuously; updates to the configuration are by uploads from the VimNet Explorer and downloads from DeltaV controller. Once installed, commissioned and uploaded, the VIM FMC scanner automatically opens its connection to the TPU when DeltaV downloads the card configuration (all four cards in DeltaV). The IO Point definitions are configured into the VIM scan table the DeltaV configuration is loaded.

  1. During the scan, each point type is processed, checking for updates from the mapped DeltaV output registers. Outputs to the TPU will be by exception on receipt of the output from the DeltaV database.
  2. Inputs from the field (TPU) are monitored, and changed inputs are sent to DeltaV real-time database asynchronously to the DeltaV outputs as received.
  3. FMC Pings are sent to TPU at a 10 second interval asynchronously to inputs and outputs. Ping responses are processed as part of the input monitoring process. Failure to receive ping response within the 10 second interval triggers a timeout. Following 3 retries, the TCP connection to field (TPU) will be terminated and will result in all associated datasets in DeltaV going to bad status.

On VIM restart (following power loss), the Configuration is read from EPROM in the VIM and the communications is automatically restored.

Each sensor/actuator IO point is an object and consists of multiple parameters; each parameter is a separate DeltaV register. As each parameter value may of a different data type, the registers for an individual IO point will be mapped to separate dataset/register combinations. A register in a separate dataset will be assign for each parameter required for a point. This means there will be one dataset for each point value and the register in each dataset corresponds to the tag index (under the device, not TPU).

There will be a maximum number of tags in a single VIM. This number will limit the number of SPCU’s that may be connected to the VIM. The more tags in an individual SPCU, the fewer SPCU’s. Based on how the tags are entered into the datasets under a device, there will be further limits on the total tags (as some datasets may not be fully utilized). Note also that 32-bit datasets (integer and floating point) in DeltaV only allow 50 registers while discrete, 8 and 16-bit datasets allow 100.

The DeltaV Virtual I/O Module (VIM) provides a native DeltaV I/O interface to open plant Ethernet networks and devices that use FMC722 (TCP) protocol. DeltaV controllers can read and write signals from the connected TPUs. As such, the VIM is a Network Gateway between DeltaV controllers and field subsea devices supporting network communications.

DeltaV Hardware and Software Requirements

To follow are the DeltaV Hardware and Software requirements for use of the DeltaV Virtual IO Module:

  • The Virtual IO Module must be mounted in a DeltaV Controller slot on a DeltaV 2-wide horizontal or vertical carrier. Please refer to the appropriate DeltaV Controller product data sheets for details: DeltaV MD or M5 Controller, Power Supply, and 2-Wide Controller Carrier.
  • Each Virtual IO Module requires a dedicated DeltaV power supply. Please refer to the DeltaV Power Supplies product data sheet for details.
  • Each configured DeltaV Serial Card Port (16 Datasets) will require one VE4102, Serial Interface Port License. Please refer to the DeltaV Serial Interface product data sheet for details. Not required for DeltaV v9.3 or higher.
  • DeltaV System Software v6.3 is required to use the DeltaV Virtual IO Module.

DeltaV Software Licensing Requirements (DST count) will be impacted by DeltaV Module configuration use of DeltaV Virtual IO Module registers in the same way as serial card registers. The following guidelines can be applied:

  • A DeltaV Serial Module data set can contain up to 100 values (a value can be any boolean, 8-bit or 16-bit number), and up to16 data sets are supported by each of the 2 ports on the serial card. If the data set registers are configured as floating point or 32-bit values, then the maximum values is 50. However, the serial device, in general, limits the total capacity of the interface.
  • Each data set counts as one DST as long as a single module references all values in the data set. If multiple modules reference values in a data set, then the DST count for the data set is equal to the number of modules referencing the data set.
  • Values used in modules containing control function blocks will be counted as Control DSTs.
  • Values referenced only in graphics or a history collection count as SCADA values, not DSTs.

Ordering Information

The product numbers in the table below are for the complete DeltaV Virtual IO Module Network Gateway. For each DeltaV Virtual IO Module a Software License must be purchased. The VIMNet Configuration Utility is included with each complete purchase. All software is distributed on www.mynah.com and is subject to MYNAH Technologies Software License Agreement. A completed MYNAH software registration form is required before shipment. One year of technical support from the date of shipment is included with each purchase.

Hardware Module
VIM-4201 DeltaV Virtual IO Module
Software Licenses
IOD-4101 Modbus TCP/IP Master Driver for DeltaV VIM
IOD-4102 Ethernet/IP Scanner Driver for DeltaV VIM
IOD-4104 Generic Device Ethernet / IP Scanner Driver for DeltaV VIM
IOD-4105 FMC722 Ethernet Protocol Driver for Deltav VIM