Knowledge Base /
Release Notes
Ethernet/IP VIM2 v5.0.5 Release Notes
By Nobin William
Product: IOD-4112 - Rockwell PLC EtherNet/IP Driver for DeltaV VIM2

These release notes are for the Ethernet/IP VIM firmware for v5.0.5.

Product Description

These release notes are for the Ethernet/IP VIM2 firmware v5.0.5. Previous released driver is v5.0.4. The flash procedure is documented in the product manual.

Who Should Upgrade?

Recommended for all Ethernet/IP VIM2 applications.

What's New in This Release?

1. Scan Control Mechanism.
2. New IP addresses for VIM/VIM communications in redundant applications.

Enhancements/Optimizations Implemented:

Scan Control Dataset

Background:

By default, the VIM performs dataset scans as fast as the network request/response allows. All datasets of each device are continuously scanned in a cycle. All devices are scanned simultaneously.

An alternate scan control mechanism is built into the VIM to allow a DeltaV Control Module to trigger dataset scans, on demand, by writing to a special scan control dataset. The scan control dataset is not part of the VIM scan. It affects Input and Output with Readback datasets only. That is, only the reading of field data is controlled by this dataset. If not configured, all VIM scans work by default, as described above. If the dataset is configured, then field reads may be controlled as described below. This dataset may be configured only once for the entire VIM, and may reside under any configured device.

Write requests from DeltaV to the external devices are always handled by exception, and are not a part of the above scan mechanism. Writes have priority over reads. For Output with Readback datasets, only the field read part is controlled by the above mechanism.

Any one dataset out of the 128 available may be configured to be the scan control dataset. Excluding the scan control dataset, all remaining 127 datasets are controlled.

The scan control dataset is configured as follows:

Table 1 - Dataset Configuration

Data Direction Output with Readback
DeltaV Data Type 16-bit Unsigned Integer
Device Data Type 240
Start Address 0
Number of Values 34
Special Data 1-5 0

The dataset is divided into sections:

  1. Registers 1-8 are scan trigger bits
  2. Registers 9-16 select which datasets are under custom scan control
  3. Register 17-24 are reserved
  4. Register 25-32 are dataset scan disable bits
  5. Register 33-34 are device disable bits.
  6. Registers 35-100 are reserved.

Controlled Dataset Registers
R9 - R16 are a bit mask specifying if a dataset is part of the scan control mechanism. A bit value of 0 implies that the corresponding dataset is not part of scan control (0 by default). Such a dataset will be scanned continuously. If a bit is set to 1, then the dataset will be scanned only if the corresponding bit in registers R1 - R8 is also set. The VIM does not change the values of R9 - R16.

Table 2 - Simplex VIM Scan Control Enabled Register Mapping

Register Card/Port Controlled
9 Card 57, Port 1 or Card 61, Port 1
10 Card 57, Port 2 or Card 61, Port 2
11 Card 58, Port 1 or Card 62, Port 1
12 Card 58, Port 2 or Card 62, Port 2
13 Card 59, Port 1 or Card 63, Port 1
14 Card 59, Port 2 or Card 63, Port 2
15 Card 60, Port 1 or Card 64, Port 1
16 Card 60, Port 1 or Card 64, Port 2

Table 3 - Redundant VIM Scan Control Enabled Register Mapping

Register Card/Port Controlled
1 Card 57/58, Port 1
2 Card 57/58, Port 2
3 Card 59/60, Port 1
4 Card 59/60, Port 2
5 Card 61/62, Port 1
6 Card 61/62, Port 2
7 Card 63/64, Port 1
8 Card 63/64, Port 1

Dataset Scan Disable

R25 - R32 are a bit mask specifying if the scan of a dataset has been completely disabled. A bit value of 0 implies that the corresponding dataset is part of the scan, either controlled or continuous. Note that the values are 0 by default. If a bit is set to 1, then the dataset will not be scanned. Instead, an error will be reported to DeltaV Diagnostics indicating the dataset state (“Disabled Dataset via Scan Control”). In this way the datasets of one or more devices may be removed from the scan if the devices are down for maintenance. Scan of all other devices will continue to function normally. The VIM does not change the value of registers R25-R32.

Table 4 - Simplex VIM Dataset Scan Disable Register Mapping

Simplex VIM Dataset Scan
Disable Register Mapping
Card/Port Controlled
25 Card 57, Port 1 or Card 61, Port 1
26 Card 57, Port 2 or Card 61, Port 2
27 Card 58, Port 1 or Card 62, Port 1
28 Card 58, Port 2 or Card 62, Port 2
29 Card 59, Port 1 or Card 63, Port 1
30 Card 59, Port 2 or Card 63, Port 2
31 Card 60, Port 1 or Card 64, Port 1
32 Card 60, Port 1 or Card 64, Port 2

Table 5 -Redundant VIM Dataset Scan Disable Register Mapping

Register Card/Port Controlled
25 Card 57/58, Port 1
26 Card 57/58, Port 2
27 Card 59/60, Port 1
28 Card 59/60, Port 2
29 Card 61/62, Port 1
30 Card 61/62, Port 2
31 Card 63/64, Port 1
32 Card 63/64, Port 1

Device Disable

The device disable registers comprise a mask specifying if a device is enabled or disabled. Table 6 lists the devices represented with each register. A bit value of 0 implies that the corresponding device is enabled (default value), and a bit value of 1 represents a disabled device. Bit 1 of R33 corresponds to Device 1, and bit 16 corresponds to Device 16. Similarly, bit 1 of R34 corresponds to Device 17, and bit 16 corresponds to Device 32. The bit number is the device creation order in the VimNet Explorer. It is called the Network Index in the VimNet Explorer, VIM level display. Specifically, the first device created is controlled by R33 bit 1. The second device created is controlled by R33 bit 2, etc.

The VIM will attempt to connect to all enabled devices and not connect to disabled devices. Setting a bit while the VIM is online will cause the device to be disconnected. If a bit is set to 1, all datasets in the device will report an error to DeltaV Diagnostics indicating the device state (“Disabled Device”).

Table 6 - Device Disable Registers

Register Controlled Devices
33 Devices 1-16
34 Devices 17-32
35-38 Reserved

The following defects were corrected:

Prior to v5.0.5, VIM/VIM communications in redundant applications used fixed IP addresses 10.10.10.1 and 10.10.10.2. This sometimes conflicted with the same IP addresses used by plant floor devices. The current version now uses a private network IP range of 169.254.0.1 and .2. No change is required in the VIM configuration. When the VIMs are flashed to this new version, the VIMs will internally reconfigure themselves. Note that when the first VIM is flashed, it will lose communications with its partner until both VIMs are at the same version.

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

Emerson Automation Solutions
Process Simulation Center of Excellence
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017
+1.636.728.2000