Knowledge Base /
Technical Notes
DeltaV Industrial Ethernet Drivers Quickstart Guide
By Jake Nichelson
Product: DeltaV Virtual IO Module - VIM2

Introduction

This article walks through the workflow of using the DeltaV Virtual IO Module (VIM) starting with registering for an account at MYNAH.com to creating DeltaV datasets.

  1. Locate the Site ID
  2. Register for an Account
  3. Download the latest version of VIMNet Explorer and the VIM Firmware
  4. Install the VIM Hardware
  5. Prepare the VIMNet Explorer Computer
  6. Install, Run, and Set Up VIMNet Explorer
  7. Commission the Simulation VIM
  8. Flash Upgrade the VIM with the VIM Firmware
  9. Create the IO VIM Placeholder
  10. Commission the IO VIM
  11. Create the IO VIM Configuration
  12. Upload the Configuration to the VIM
  13. Verify Cards are Emulated by the VIM
  14. Configure the DeltaV Datasets

1. Locate the Site ID

Every instance of the VIM has an associated Site ID. This is a unique number that allows MYNAH to track, maintain, and support each unique licensed instance of the VIM firmware. This is NOT the same number as, nor is there any direct correlation to, the DeltaV System ID. Every time a copy of any VIM firmware is purchased, the Site ID is emailed with the Order Confirmation to all listed parties on the PO. VIM firmware Site IDs are allocated per purchase order and per type. For example:

  • If one Modbus TCP/IP VIM firmware is purchased, one unique Site ID will be provided.
  • If two copies of the Modbus TCP/IP VIM firmware are purchased with a single PO, only one Site ID will be provided.
  • If one Modbus TCP/IP VIM firmware is purchased and another is purchased later or with a different PO, each firmware will have a unique Site ID.
  • If one Modbus TCP/IP VIM firmware and one ODVA EtherNet/IP VIM firmware are purchased, two Site IDs will be provided; one for each type regardless of whether they are all purchased with the same PO.
  • If two copies of the Modbus TCP/IP VIM firmware and one ODVA EtherNet/IP VIM firmware are purchased with the same PO, two Site IDs will be provided.

A Site ID will be required to download associated files and receive support. The Site ID can be found in the confirmation email sent to all listed parties on the PO. If the confirmation email cannot be found, register for an account at MYNAH.com, open a support ticket requesting the Site ID, and provide the following information:

  • Company Name and location that owns the VIM firmware
  • Firmware type
  • Date of purchase

2. Register for an Account at MYNAH.com

MYNAH recommends that every person who requires access to downloads and technical support register for a unique user account at MYNAH.com. End customers, Emerson Local Business Partners and integrators may all register for an account, open support tickets, and access downloads associated with a Site ID. To access the registration form, go to http://www.mynah.com, click "MENU," expand Client Login under Resources, and click "Register." New users will have the opportunity to specify Site IDs when registering. Access to the downloads for the Site ID will be granted if the Site ID is provided at registration.

The application for registration will be reviewed by MYNAH staff during normal business hours. The approval process will typically only take a few minutes. Applications submitted after business hours will be reviewed on the next business day. A confirmation email with instructions for logging in will be sent once the account has been approved.

If the Site ID was not specified at the time of registration or the firmware was purchased after registration, Site IDs can still be applied to the user account. Simply open a support ticket and request to add the Site ID to your account.

For more details about an account at MYNAH.com and how to open a support ticket, see the following link: My Account at mynah.com Features and Directions

3. Download the latest version of VIMNet Explorer and the VIM Firmware

The latest versions of the VIM firmware and VIMNet Explorer downloads can be found on the Site ID page that can only be accessed by users that have successfully linked their accounts to the Site ID. To access the Site ID page, log onto your account, click "MENU" at the top-left, and click the "Software Licenses" button. The Software Licenses page will list all of the Site IDs associated with the user account, including overview details about the site such as: the Company Name, Product Family, and Support Expiration. Click the Site ID to access the Site ID page. Note: Any number of users may be attached to and access the Site ID page.

Notice the Support Expiration section. Downloads will not be available for this Site ID if support has expired. Annual support will need to be purchased through the Emerson Local Business Partner to continue access to downloads and technical support.

If support is not expired, attached users can download any of the files listed in the Site ID's Downloads section by following the links. The following files will be available:

  • Latest version of VIMNet Explorer
  • Latest version of the VIM firmware
  • Latest version of the Simulation Firmware (All new VIM2 hardware are pre-flashed with Simulation firmware)

Download these files to the computer which will run VIMNet Explorer.

4. Install the VIM Hardware

Virtual IO Module Hardware Installation

5. Prepare the VIMNet Explorer Computer

The following items are requirements for VIMNet Explorer:

  • Disable Anti-Virus software
  • Turn off Windows Firewall
  • VIMNet Explorer must be run with Administrator privileges (right-click the VIMNet Explorer icon and select Run as Administrator).

If these requirements are not met, MYNAH cannot guarantee complete and proper functionality of VIMNet Explorer. Anti-virus software, the Windows Firewall, and the lack of Administrative privileges on the computer can all prevent VIMNet Explorer from properly accessing the computer's network card, resulting in failures that include but are not limited to:

  • Failure to detect VIMs on the network
  • Failure to commission/flash VIMs or upload the configuration
  • Failure to gather diagnostics information from the VIM using VIMNet Diagnostics

If any of these failures are encountered, check that the requirements have been met. These failures very rarely occur when the above requirements have been met. If any of these failures is encountered after ensuring that the above requirements are met, please contact MYNAH Technical support.

6. Install, Run, and Set Up VIMNet Explorer

After the files have been downloaded from the Site ID page, extract all of the .zip files. Run the VIMNet Explorer installer and follow the installer's instructions.

Once installed, locate VIMNet Explorer under the Windows Start Menu, right-click the icon, and select "Run As Administrator." This step is necessary even if logged into the Windows machine as an administrator. If VIMNet Explorer is launched without Administrator privileges, it will open but VIM operations over the network, such as commissioning and flashing, may fail.

If prompted to select a network card (NIC) when VIMNet Explorer is initially launched, select the IP Address of the computer from the "Available NIC" selection and click the "Add" button. The IP Address of the NIC that is connected to the VIM/PLC network must be used. Only the correct IP Address should be listed in the Used Addresses field. If there are multiple IP Addresses listed there, select and delete all IP address that are not connected to the VIM/PLC network. Once the PC IP address on the VIM/PLC network is the only IP in the list, click "OK" to continue to VIMNet Explorer.

Verify that the network settings are correct. Right-click "Physical Network" in the tree on the left side of the VIMNet Explorer window and select "Properties." Again, make sure that only the correct IP Address is listed under the Used IP Address. Delete any other IP Addresses from the list.

VIMNet Explorer Installation

7. Commission the Simulation VIM

All new VIM2 hardware shipped to customers will be pre-loaded with Simulation firmware. This firmware is designed for process simulation use with Mimic Simulation Software and the Mimic Railbus SIO Driver. Simulation Firmware is not a valid Industrial Ethernet Gateway firmware. The VIM must be commissioned and flashed to the desired firmware before it can be used as a gateway VIM. A VIM cannot be commissioned to a placeholder in VIMNet Explorer that does not match the firmware type currently loaded on the VIM. In VIMNet Explorer, there are two classes of VIM placeholders; Simulation VIM placeholders, and I/O Net VIM placeholders. Because new VIM hardware shipped from Emerson comes with Simulation Firmware, they must be commissioned to a Simulation VIM placeholder to be flashed to the appropriate Gateway IO Driver for use in a real process.

To get started, click the Decommissioned VIMs list to see the list of available VIMs on the network. If any of the VIMs are missing from the list, right-click "Decommissioned VIMs" and select "Refresh." Refreshing the list sends a special beacon on the network and all VIMs are designed to respond to this message. VIMNet Explorer will populated the decommissioned VIMs list based on the responses that are received. If no VIMs are listed, VIMNet Explorer was either not able to send the command or no responses were received.

If no VIMs are listed under the Decommissioned VIMs list, verify the following:

  • The computer has been prepared correctly based on the steps provided above
  • VIMNet Explorer was run as Administrator as instructed previously
  • The network connection to the VIM is good; it may be helpful to simplify the network by connecting the VIM directly to the computer

Once all of the VIMs are available in the Decommissioned VIMs list, create a VIM placeholder under "Simulation Net." Right-click the Simulation Net and select "New Simulation VIM." Provide a valid and available IP Address and a valid subnet mask for the VIM. Use the Ping button to verify that no other device on the network has this IP Address. Click "OK" when done.

Right-click the Simulation VIM placeholder and select "Commission." All Simulation VIMs should be listed as available for commissioning. VIMs with different firmware types will not be listed. Select the VIM to commission and click "OK." Once the VIM has been commissioned, the IP Address at the placeholder will be applied to the VIM. Use the VIMNet Explorer computer to ping the VIM's IP Address to verify that the VIM is correctly responding on the network.

[VIDEO DEMO] Starting VIMNet Explorer and Commissioning VIMs

8. Flash Upgrade the VIM with the VIM Firmware

At this point, the VIM should have Simulation firmware flashed and be commissioned with a valid IP Address. The VIM must be flashed to a different firmware to act as an Industrial Ethernet Gateway. At least two .hex files should have been included in the files downloaded from the Site ID page: a Simulation firmware .hex file and an Industrial Ethernet Gateway .hex file. For VIM2 hardware that is currently flashed with Simulation firmware version 2.5.3 or below, a flash to latest Simulation firmware is required. Once the VIM is flashed to the latest Simulation firmware, the VIM can be flashed using the Industrial Ethernet Gateway .hex file downloaded from the Site ID page.

In VIMNet Explorer, right-click the Simulation VIM placeholder again and select "Properties." Click the "Flash Upgrade" button, browse to and select the .hex file, and click "OK." This will start the flash process and it may take several minutes to complete. If the flash fails for any reason, check the following:

  • Verify that the system requirements have been met as previously discussed
  • Verify that the VIM responds to network pings
  • Verify that the correct file (.hex) is being selected for flashing
  • Verify that the .hex file is saved on the local computer and is not stored on a thumb drive or network drive

If the VIM firmware type was not changed during the flash upgrade, as would be the case when flash upgrading from an older version of Simulation firmware to the latest, the VIM will remain commissioned. After this initial VIM flash to the latest version of Simulation firmware is complete, the instructions above should be repeated to flash upgrade the VIM to the Industrial Ethernet Gateway firmware.

If the VIM firmware type was changed during the flash upgrade, the VIM should be automatically decommissioned because a VIM cannot be commissioned to a placeholder that does not match its firmware type. Sometimes it may take a moment for VIMNet Explorer to show that the VIM has been decommissioned. If the icon is not updating, press the F5 key to update the display. The VIM should also be listed under the Decommissioned VIMs list with the updated firmware version that matches the version listed in the name of the .hex file. This VIM is now ready to be commissioned to an I/O VIM placeholder.

[VIDEO DEMO] Flash Upgrading VIMs

9. Create the IO VIM Placeholder

An I/O VIM placeholder must now be created, similar to how a Simulation VIM placeholder was created when the VIM was flashed with Simulation firmware. Right-click I/O Net and select "New Controller." Provide a name for the controller to match the name of the controller in DeltaV. Right-click the controller and select "New IO VIM." A new configuration window will appear. Perform the following:

  • Select the firmware type
  • Check the box “VIM is Redundant” if this is a redundant application
  • Check the box “M-Series IO” if this is an M-Series VIM
  • Check the box for “VIM 2” if this is a VIM2
  • Select the serial card range (57-60 or 61-64) if the VIM is Simplex; all cards will be used if the VIM is redundant
  • Provide a name, IP Address, and Subnet for the VIM(s)
  • Click the Ping button to verify that the provided IP Address is available

Click "OK" to finish once the VIM placeholder has been configured.

10. Commission the IO VIM

Right-click the newly created I/O VIM Placeholder and select "Commission." Your VIM should appear in the list of available VIMs. Select the VIM and click "OK." Click "OK." to confirm the commission. Verify that the VIM has been properly commissioned by using the VIMNet Explorer computer to ping the VIM.

If the VIM does not appear in the list of available VIMs, check the following:

  • Verify that the system requirements have been met as previously discussed
  • Verify that the VIM is decommissioned by checking the LED status on the VIM
  • Verify that the VIM is listed in the Decommissioned VIMs list with the correct firmware version
  • Verify that the VIM firmware type was correctly selected in the VIM placeholder configuration

Commission a Simplex VIM

Commission a Redundant VIM

11. Create the IO VIM Configuration

The next step is to add devices in VIMNet Explorer that correspond to the devices in DeltaV. If a device is configured in DeltaV under Card 57, Port 1, then a device must be added in VIMNet Explorer under Card 57, Port 1. Make sure to create a device in VIMNet Explorer for every device in DeltaV regardless of which firmware is flashed to the VIM.

To add a device, expand the VIM, expand one of the cards, right-click the Port, and select "Add Device." A new windows will pop up for defining the device. Change the Device Address to match the device address in DeltaV Explorer. Click the "Add" button and specify the IP Address of the device and click "OK." Click "OK" again to finish the device configuration.

Modbus TCP: Field Device Configuration, Field Device IP Address

Rockwell PLCs EtherNet/IP: Field Device Configuration, Field Device IP Address

Generic Devices EtherNet/IP: Field Device Configuration, Field Device IP Address

ODVA EtherNet/IP: Field Device Configuration, Field Device IP Address

If using the IOD-4101/4111 or IOD-4102/4112 firmwares, no additional configuration for the device is required. If using IOD-4104/4114 or IOD-4116, at least one connection definition must be created and assigned to the device. The connection definition defines the communication details. When IOD-4101/4111 or IOD-4102/4112 are used, the communication details are defined by the dataset configuration in DeltaV.

Generic EtherNet/IP Connection Definition

ODVA EtherNet/IP Connection Definition

The I/O VIM Configuration will be complete once all of the devices have been added (with connection definitions if necessary).

[VIDEO DEMO] Configuring Devices with ModbusTCP

12. Upload the Configuration to the VIM

Once the configuration is finished, right-click the VIM and select "Upload Configuration to VIM." There is an option to upload the configuration to VIM A, VIM B, or Both if this is a redundant VIM pair. The configuration will need to be uploaded to both VIMs, either individually or all at once. The VIM's serial cards should be visible to the controller across the railbus after uploading the configuration to the VIM.

13. Verify Cards are Emulated by the VIM

The VIM should emulate the DeltaV serial cards after the configuration has been uploaded. The VIM cards can be added to DeltaV automatically or manually. To automatically add the VIM's cards to DeltaV and verify that the VIM is emulating the cards in one step, right-click <Controller> -> I/O and select "Auto-sense I/O Cards." The VIM's configured cards (57- 60 or 61-64) should be auto-sensed by the controller and added to the controller's I/O automatically. Next, download all four cards. After the download, right-click the controller and select "Diagnose" to open DeltaV Diagnostics. Verify that the Serial Cards do not show "Configured but not Present" errors. The VIM is properly emulating the serial cards if there are no errors at this point.

If the cards are added manually, then the emulation will need to be verified through DeltaV Diagnostics. To add the cards manually, right-click lt;Controller> -> I/O and select "New Card." Select the following settings for the card:

  • Card Class: Serial Cards
  • Card Type: 2 Ports, Programmable, RS232|RS485
  • Card Series: M or S Series depending on the series of the controller
  • Slot Position: 57-60, or 61-64

All four of the VIM's cards must be added then downloaded. Once the cards have been downloaded, right-click the controller and select "Diagnose" to open DeltaV Diagnostics. Verify that the Serial Cards do not show "Configured but not Present" errors. The VIM is properly emulating the serial cards if there are no errors at this point.

14. Configure the DeltaV Datasets

Instructions for configuring DeltaV datasets for the Rockwell PLC EtherNet/IP driver and Modbus TCP/IP driver can be found in the VIMNet Explorer Help files:

Modbus TCP/IP DeltaV Dataset Configuration

(Rockwell PLCs) EtherNet/IP DeltaV Dataset Configuration

The DeltaV dataset configuration for the Generic EtherNet/IP and ODVA EtherNet/IP drives is defined by the connection definition. In VIMNet Explorer, browse down to "Device→Connection Definition→Dataset." Click on the dataset. The DeltaV dataset configuration for this connection definition will be listed on the right-hand side. Copy the configuration exactly to the dataset in DeltaV.

[VIDEO DEMO] Configuring Datasets with ModbusTCP

Contact

MYNAH Technologies
+1.636.728.2000
support@mynah.com