Knowledge Base /
Technical Notes
Steps Required to Rebuild the VIMNet Explorer Configuration File
By Adisa Shaljani
Product: DeltaV Virtual IO Module - VIM2

This technical note shows the step by step procedure to rebuild the VIMNet Explorer configuration file (*.vio file).

VIMNet Explorer Configuration

The VIMNet configuration is contained in a file with a VIO extension. This file contains the MAC addresses of the VIMs, assigned IP addresses, and other details of the VIM network. In essence, this file is the VIMNet database. It is essential that this file be used whenever the VIMNet Explorer is opened to look at the VIM configuration.

If the VIMNet Explorer is opened either without a VIO file, or with a different, incorrect file, any Commissioned VIMs found on the network will appear as unrecognized devices. As unrecognized devices, these VIMs are placed in the Decommissioned list with Status as “Commissioned Bad." This is shown in figure 1.0. This is an expected behavior. Note that the VIMs found are not actually in a bad state, nor have they stopped performing their communications tasks. The sample screenshots show steps to recreate Ethernet/IP configuration for redundant VIMs.

If you can locate the original .VIO file that was used to configure this VIM, you should open it by selecting from main menu "File->Open," but if you have misplaced the .VIO file you will need to rebuild it again by following the procedure below.

Procedure to rebuild the .VIO file

Step 1. Install the latest version of the VIMNet Explorer. After the install you will be asked to provide the IP address for the VIM Network. This is the IP address of the NIC that is connected to the VIM directly or through a switch.

Important Note: The NIC that is connected to the VIM network must be set up with the static IP address. The Physical Network IP address must match the IP address of network card that is connected to the VIM.

Step 2. In the VIMNet Explorer, right-click on the Physical Network and select "Properties."

The following dialog will appear where you need to specify the correct IP address, then click "OK."

Step 3. Right-click on the "I/O Net" and "Add New Controller." The default name is "Node01," but you can rename it by right-clicking on it and selecting the rename option.

Step 4. Right-click on the Node name and select "New IO VIM."

Step 5. Check the “VIM Is Redundant box” to make this a redundant placeholder.

Choose the Type of firmware: In your case it will be Ethernet IP.

Important Note: You need to have a record of the IP addresses and subnet masks you have used for the VIM A, VIM B, and the ENBT cards in PLC chassis A and B. The placeholder name doesn’t have to match with what you have configured in the VIM. But the IP addresses must match.

Enter the VIM placeholder name, the IP address for the VIM A and VIM B, then enter the matching subnet masks.

Step 6. Next step is to add the redundant device(s) under the serial cards. These must match what you had configured before. Drill down into the card, then Right-click on the port and select "Add Device."

Step 7. Select the device address, and click "Add," enter the IP address of the ENBT card in chassis A, and select radio button next to Single Network Card Redundancy Switching IP. Click "OK" to add the device.

Step 8. Click on Decommissioned VIMs and you should see your VIMs that are already commissioned and talking to your ENBT cards.

Step 9. Right-click on the VIM placeholder and select "Reconcile VIM."

Step 10. Pick the VIM A from the list. Click on VIM A button on the second dialog box shown below.

Step 11. Right-click on the VIM placeholder and select the "Reconcile VIM."

Step 12. Select the "VIM B" to be reconciled.

Important Note: After you reconcile both VIMs, you should have VIMs commissioned as a redunant pair and they should still be talking to ENBT cards. No configuration upload is required.

Step 13. Finally, as a last step you will need to save the .vio file. Go to main menu, click on "File ->Save as." We recommend that you save the .vio and keep it on this machine in case of configuration changes, but also keep a backup on some other storage medium.