Month: November 2025

Profibus DP Interface Cards

In DeltaV v12 and later, the number of DSTs per connected

Profibus DP device will be 1 DST in most cases. The DST

type counted will be the most valuable type used to

reference a signal for each device. If references are made

to more than 16 signals from a device, additional signal

references beyond the 16th reference will each count

as a DST. A motor starter, for example, with 4 to 5 signal

references, will consume 1 DST (typical an AI or DO DST).

A remote I/O island will consume 1 DST for the first 16

signal references, and 1 DST for each additional signal

reference beyond the 16th signal reference.

DeviceNet Interface Cards

In DeltaV v12 and later, the number of DSTs per connected

DeviceNet device will be 1 DST in most cases. The DST type

counted will be the most valuable type used to reference

a signal for each device. If references are made to more

than 16 signals from a device, additional signal references

beyond the 16th reference will each count as a DST.

A motor starter, for example, with 4 to 5 signal references,

will consume 1 DST (typical an AI or DO DST). A remote I/O

island will consume 1 DST for the first 16 signal references,

and 1 DST for each additional signal reference beyond the

16th signal reference.

DeltaV Licensing Guidelines

DeltaV I/O licensing for the VIM2 depends on the I/O cards

the VIM is emulating and follows that card type’s rules.

Programmable Serial Interface Cards

Serial dataset registers can be referenced directly in control

modules as analog or discrete I/O providing fast easy data

exchange with the serial device. Direct module-to-Dataset/

register references are recommended for control signals.

Alternatively, users can read multiple registers from a

Dataset into a single “marshalling” module at the cost of a

single DST. Marshalling modules provide a cost-effective

way to integrate serial data from analyzers and other data

sources. Serial dataset registers can also be passed as

SCADA values directly to Workstations and Continuous

Historians without consuming DST’s.

See the M-series Serial Interface Series 2 product data

sheet for additional details.

EtherNet/IP

The VIM2 with the EtherNet/IP Driver provides the following

compatible functions using the Common Industrial Protocol

(CIP) as defined in the EtherNet/IP Specification from

Open DeviceNet Vendor Association (ODVA) and ControlNet

International. The driver emulates either Programmable

Serial cards or DeviceNet cards on the DeltaV I/O bus.

The VIM2 EtherNet/IP Scanner Driver provides:

I/O Scanner (Transport Class 1 originator,

using connected implicit messaging).

I/O Adapter (Transport Class 1 target, using connected

implicit messaging).

Unconnected explicit (UCMM) messaging client.

Connected explicit (Transport Class 3 originator) messaging client.

Additional Integration Options

Please review the PK Controller and Ethernet I/O Card

(EIOC) product data sheets for additional Industrial

Ethernet protocol integration options.

Additional Integration Options

Please review the PK Controller and Ethernet I/O Card

(EIOC) product data sheets for additional Industrial

Ethernet protocol integration options.

PROFINET

The VIM2 with the PROFINET Driver acts as an I/O

Controller in a PROFINET network, exchanging data with

I/O Devices using Real-Time (RT) messaging. Isochronous

real-time (IRT) communication is not supported. The driver

supports the PROFINET v2.2 specification and emulates

Profibus DP cards on the DeltaV I/O bus.

Field device communications comprise I/O data, alarms,

and diagnostics. Other aspects of field data, e.g., data

records and logbook information, are not supported.

Alarm and diagnostic data are reported to PC-based

VIMNet Explorer tools. Only I/O data and corresponding

status are reported to the DeltaV controller.

FMC722 Subsea

The VIM2 with the FMC722 Driver supports

communications with FMC Technologies Topside Processing

Unit (TPU) using the FMC722 (TPC) protocol.

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

Rockwell PLC Scanner

The VIM2 with the Rockwell PLC Scanner Driver provides

the following compatible functions using the Common

Industrial Protocol (CIP) as defined in the EtherNet/IP

Specification from Open DeviceNet Vendor Association

and ControlNet International. This driver emulates

Programmable Serial cards on the DeltaV I/O bus.

The VIM2 EtherNet/IP Scanner Driver provides:

IO Adapter (Transport Class 1 target, using connected

implicit messaging). Supported in simplex or

dual simplex configurations.

Unconnected explicit (UCMM) messaging client

Embedded DF1 (PCCC). Supported in simplex,

dual simplex, and redundant configurations.

Rockwell PLC Scanner

The VIM2 with the Rockwell PLC Scanner Driver provides

the following compatible functions using the Common

Industrial Protocol (CIP) as defined in the EtherNet/IP

Specification from Open DeviceNet Vendor Association

and ControlNet International. This driver emulates

Programmable Serial cards on the DeltaV I/O bus.

The VIM2 EtherNet/IP Scanner Driver provides:

IO Adapter (Transport Class 1 target, using connected

implicit messaging). Supported in simplex or

dual simplex configurations.

Unconnected explicit (UCMM) messaging client

Embedded DF1 (PCCC). Supported in simplex,

dual simplex, and redundant configurations.

Supported Industrial Ethernet Protocols

Modbus TCP

The VIM2 with the Modbus TCP Driver supports the

following Modbus communications protocol function codes

to read and write values to and from Modbus devices,

as specified by the Modbus Application Protocol

Specification from Modbus-IDA.org. This driver emulates

Programmable Serial cards on the DeltaV I/O Bus.

The VIM2 Modbus TCP/IP Driver supports the following

Modbus function codes:

Code 8 – Diagnostic Loop Back Test

Code 15 – Force Multiple Coils

Code 16 – Preset Multiple Registers

The VIM2 can function as both a Modbus TCP master

and slave simultaneously. Master or slave mode is set

at the virtual port level. The master and slave capability

are available in simplex implementations; in redundant

applications, only master mode is supported.

VIM2 Dual Simplex or Redundant Setups

Two VIM2s can either be setup as a dual simplex or

redundant pair for installations that either consists of

many field devices or require additional communication

resiliency, respectively.

If two VIMs are configured for dual simplex operation, both

VIM2s will work as Standalone units and no redundancy link

cable is installed.

If two VIMs are configured for redundant operation, the

active and standby VIM2s monitor each other with a

continuous status command using the redundancy link

cable supplied with each redundant pair. The active VIM2

communicates over the network to the Industrial Ethernet

device and the standby sends an intermittent signal to the

device to maintain communication integrity.

The Ethernet I/O drivers are available separately from the

VIM2 hardware. Each operating VIM requires one license

for the running protocol. For example, a redundant pair of

VIMs requires two copies of the driver running on that pair,

but an offline spare does not require licensing.

VIMNet Explorer

VIMNet Explorer allows the user to commission the VIM2;

setup primary, secondary, and/or redundant VIM2s; define

the Ethernet I/O network; and view advanced diagnostics

information. The user can specify the IP address, Subnet

Mask, and Gateway of each VIM2 and set the node address

and names of each Ethernet I/O device integrated with

the VIM2. VIMNet Explorer is also used to flash upgrade a

VIM from one version of a driver to another or to replace

an existing driver type with another. Only one Ethernet I/O

driver may be loaded in the VIM2 at one time.

VIMNet Explorer application must run on a workstation

that has network connectivity to the Ethernet I/O network.

This may be a DeltaV workstation with the third network

interface card (NIC) connected to the Ethernet I/O network

or may be a non-DeltaV workstation. Connection to the

VIM2 is done through the RJ-45 Network Connection on the

bottom of the VIM2.

VIMNet Explorer installation media is downloadable from Guardian.