Knowledge Base /
Release Notes
ModbusTCP VIM2 4.4.3 Release Notes
By Nobin William
Product: IOD-4111 - Modbus TCP IP Driver for DeltaV VIM2

The following release notes are for the ModbusTCP VIM2 firmware v4.4.3.

Product Description

These release notes are for the ModbusTCP VIM2 firmware v4.4.3. Previous released driver is v4.4.2. The flash procedure is documented in the product manual.

If upgrading the VIM2 from firmware v4.2.0 or earlier, follow the two step procedure below:

1. First flash VIM's at v4.2.0 to v4.2.1.
2. Once the VIM's are at v4.2.1, flash to v4.4.3.

If upgrading the VIM2 from simulation firmware v2.5.4 or earlier, follow the two step procedure below:

1. First flash VIM's to v2.5.5*.
2. Once the VIM's are at v2.5.5, flash to v4.4.3.

Note that when flashing the firmware to v4.4.3 from any version prior to v4.4.1, the VIM will decommission itself. This is due to the device database size change in the VIM.

*Contact MYNAH Technologies Technical Support to get Simulation firmware v2.5.5.

Who Should Upgrade?

Mandatory for all Modbus TCP VIM2 applications.

What's New in This Release?

Added new dataset reporting mechanism.

The Following Enhancements/Optimizations Were Implemented:

Current mechanism to report incoming field data to DeltaV is based on change of state. If any register in a dataset has changed in the current scan, the VIM2 reports it to DeltaV. A new user configurable reporting mechanism has been implemented to report dataset changes on a periodic interval. If no change is pending, then nothing is reported. This functionality applies to datasets which are of type Input or Output with Readback. The objective of this enhancement is to prevent Railbus overload and memory buffer depletion in the VIM2.

For this reporting mode, user configures the high byte of special data 4 with a non-zero value. The low byte is reserved. If the high byte is 0, the dataset is reported immediately based on change of state (current default). The high byte value ranges from 1-255. Each count corresponds to 200ms. If the user configures a 1 in the high byte, the VIM2 will report the dataset on a 200ms period, if there is any change pending. A configured value of 255 gives a maximum reporting period of 51 seconds.

The Following Defects Were Corrected:

1. In redundant mode, an intermittent defect was identified in VIM2/VIM2 communications. When the Active VIM2 was powered down, a switchover occurred as expected. However, the newly Active VIM2 would enter into a state where it would continuously toggle Active/Standby. This defect has been corrected.

2. During active communications, some field devices report their data in partial fragments. The VIM2 expected complete, non-fragmented responses only, and incorrectly rejected the incoming partial response. This defect has been corrected.


MYNAH Technologies
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017