Inserting a VND integration - Metasys - LIT-12013150 - System Integration - Modbus Vendor Integration - 10.1 - 9.0.7

Network Engine Commissioning for Modbus Vendor Integration Application Note

Product name
Modbus Vendor Integration
Document type
Application Note
Document number
Revision date


  1. Use the Launcher to log on to the network engine's SMP. If you need to install the Launcher, refer to the Launcher Installation Instructions (LIT-12011783).
  2. Drag the NxE, SNE, or SNC device object from the navigation panel to the display panel. The Focus tab screen appears.
  3. Click Insert > Integration . The Insert Integration Wizard appears.
  4. In the Select Object Type window, click VND Integration, and then click Next.
  5. In the Destination window, click the NxE, SNE, or SNC object, and then click Next.
  6. In the Identifier window, enter a short (10 characters or less), unique name for the integration. For example, ModbusRTU or ModbusTCP. Click Next.
  7. In the Configure window, click the Hardware tab. In the Vendor Driver field, enter the name of the driver according to the following table.
    Note: The Vendor driver file name is case sensitive. Enter only one driver name.
    Table 1. Vendor driver filenames to use

    Network engine

    First driver

    Second driver

    Subsequent drivers

    NCE25, NAE35, NAE45, NAE55, NIE29, NIE39, NIE49, NIE59, SNExxxxx, SNCxxxxx





    ModbusDriver_TCP_2.dll (3rd)

    ModbusDriver_TCP_3.dll (4th)

    Figure 1. Insert Integration Wizard - configure

  8. In the Vendor Reference field, enter RTU (for RS-485 or RS-232) or TCP (for Ethernet) to indicate the communication mode. For the NAE85, enter TCP only.
  9. Click Next.
  10. In the Summary window, click Finish. The Extension Wizard appears.
  11. Click New in the Resource section of the Extension Wizard. The Select File window appears.
  12. In the Select File window, click Browse.
  13. Browse to the Modbus integration (VMD) file for your Modbus device model and click Open to populate the File Name field in the Select File window.
    Figure 2. Selecting a VMD file

    Note: The VMD file is specific to the model, not to the device. For example, if 50 Modbus devices of the same model are present, use the same VMD file as the resource file for each device.
  14. Click Next.
  15. In the Configure window, verify the resource object name and file name. The file name in the Status section of the Configure window consists of the name of the integration object, a period separator, and the full name of the VMD file. This resource file name has a maximum length of 40 characters and it is recommended that you keep the integration object name short. Also, the resource file name must match the file name you enter in parameter 8 of the Modify List dialog box when you insert a field device. See Table 1.
  16. Click Next.
    Figure 3. Insert Resource File Wizard - configure

  17. In the Summary window, click Finish. The newly added VMD file appears in the Resource section of the Extension Wizard.
    Figure 4. Extension Wizard with resource file

  18. Click Done.
  19. If you need to add a second Modbus integration, repeat Step 3 to Step 18 for the second integration, which includes inserting a resource file again to support the second integration. See Table 1 for the driver filenames to use. You can add up to four Modbus integrations for an NAE85.