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

Product Description

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


Follow this procedure if flashing the VIM2 from Simulation Firmware to Modbus TCP/IP for the first time or if upgrading from Modbus TCP/IP v4.2.0 or earlier:

  1. Download the latest version of the Simulation firmware from the same Site Page as the Modbus TCP/IP firmware.
  2. Flash the VIM2 with the latest version of Simulation firmware.
  3. Lastly, flash the VIM2 with v4.5.1 firmware

Note that when flashing the firmware to v4.5.1 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.

Who Should Upgrade?

Mandatory for all Modbus TCP VIM2 applications.

The Following Enhancements/Optimizations Were Implemented:

Some devices do not accept Modbus Function 0xF (Force Multiple Coils) and 0x10 (Preset Multiple Registers). These functions are used when the VIM performs dataset block writes, even if the dataset is configured with 1 value. A change has been made to instead use Function 0x5 and 0x6 under block write mode when there is only 1 value to write. The VIM continues to use function 0xF and 0x10 when more than 1 value is configured.

The Following Defects Were Corrected:

  1. In redundant applications, VIM/VIM communications were lost after upgrading the VIM firmware to v4.5.0. The solution to correct this issue was to first decommission the VIM and then commission and upload it again.

    Upgrading to v4.5.1 corrects the issue in that a commissioning and upload are not required. However, VIM/VIM communications will still be lost. This is because the VIM/VIM communications IP has been changed from and .2 to a private network range of and .2. The solution is to ignore the DeltaV Diagnostics message indicating this communication loss. Do a manual switchover to the newly flashed VIM and then flash the VIM with older firmware. Once both VIMs are at v4.5.1 or later, the VIM/VIM communications will be restored.
  2. On loss of communication with a device using communication mode RTU via TCP, only the first failed dataset was marked with error. Other datasets in the device incorrectly remained in stale but good status. This issue has been corrected.

Please contact us for any questions

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