Knowledge Base /
Technical Notes
DeltaV Virtual IO Module Network Ports
By Edin Rakovic on 05.15.12
Product: DeltaV Virtual IO Module

The Virtual IO Module (VIM) provides intuitive network setup. However, on networks where a Network Firewall blocks certain Network ports, the communications suffer. The following is a list of exact port numbers that need to be opened on firewalled networks.

Please refer to MYNAH Technologies DeltaV Virtual IO Module Network Gateway knowledge based article for a complete description of Virtual IO Module features, description and specifications, supported industrial ethernet protocols and firmware ordering information. The following table lists the ports necessary for communications with the VIM from VIMNet Explorer. These ports will need to be enabled for proper communications at each network firewall. The common firewall present on most computers is the Windows Firewall. For more information, please refer to the following article "Open a port in Windows Firewall". For other network firewalls please contact your Network Administrator.

Virtual IO Module Network Ports

Software Port Number Protocol Description
VIMNet Explorer (PPV) 1024 TCP/UDP Ping to discover all VIMs on the subnet
VIMNet Explorer (PPV) 51000 TCP/UDP Listens for messages from the VIM
VIMNet Explorer (PPV) 52000 + (IP address & 0xFF) TCP/UDP

Sends messages to the VIM (i.e. last octet of address, gives 52001)

Modbus TCP/IP VIM 502 (user selectable) TCP Connection to each ModbusTCP device
EthernetIP VIM 44818 TCP Explicit Messages - UCMM(PCCC)
EthernetIP VIM 2222 UDP Implicit Messages - Class 1/3
FMC VIM 1201 (default, user selectable/TPU) TCP Connection to each TPU
VIMNet Explorer Diagnostics 52000 TCP/UDP Listens for messages from the VIM
VIMNet Explorer Diagnostics 52001 TCP/UDP Sends messages to the VIM

Regarding the Decommissioned VIMs List

The Decommissioned VIMs List is populated based on responses from decommissioned VIMs that send a periodic UDP message from source port 1024 to destination port 51000. When the Decommissioned VIMs List is refreshed manually, VIMNet Explorer sends a broadcast request to all VIMs to update immediately. The destination port for this broadcast message is always 1024 but the source port is determined by Windows based on the next available port. The VIMs will respond with a UDP message with a source port of 1024 and a destination port to match the broadcast message previously sent by VIMNet Explorer.

The port on the VIMNet Explorer computer for the refresh message is dynamic, not static, which makes applying firewall rules based on ports difficult. If the firewall rules are applied based on the above table then the Decommissioned VIMs->Refresh List functionality will be lost. This is not a critical feature because in theory the list will be populated eventually.


If you have any questions or concerns regarding this procedure, contact the MYNAH Support Team by opening a support ticket at using your account. If you do not currently have an account at, please click here for instructions on how to do so.