DHCP
When DHCP is enabled in VPvision on one of the LAN ports other than LAN2, it will wait for a router to provide the system with an IP address. DHCP (the protocol) will supply the gateway, subnet mask, and IP address to the network interface.
When DHCP is disabled you need to configure the IP address for the interface.
Reply timeout/ missing real time data
When you’re missing data from the Moxa device this is most likely caused by wrong configuration of the device. By default we provision the Moxa remote IO devices with 10.0.0.2, VPVision is provisioned with 10.0.0.1. The VPRouter is playing the role of a switch, which handles the packages between those devices. The VPRouter can also be conneced to the remote IO module via one of the two LAN ports on top of it, which also act as a small, unmanaged switch in this case. See picture below.

The VPRouter is configured with IP address 10.0.0.254 and also acts as the one, and only gateway for VPVision to retreive updates from our update server.
The reason to use static IP addresses instead of DHCP is to make sure you’re always assigning the same exact IP address per device. When using DHCP, without static definitions in the router, it’s possible the device would receive a different IP address after a power cycle, or after update of the DHCP server (This may happen every 24 hours). This would create issues, especially when using remote IO modules, as VPVision would not be able to find the remote modules anymore.
Solution
1. For a 2-LAN port VPVision model: Change the default IP address of LAN 1 (192.168.1.253) to another IP address, which matches the customer's Ethernet network configuration. Make sure to write this down and communicate it to the user.

Please note, you can’t use the same subnet on both LAN-01 and LAN-02 as this will cause issues with the real time data acquisition deamon.
2. For the standard 4-LAN port VPVision models: Assign a static IP address to LAN 3 or LAN 4. When using DHCP, make sure to note down the IP address for the end user. Make sure to inform the end user about the fact that the IP address might change, and that a static IP address is recommended.

VP does not recommend DHCP as this may result in VPVision becoming unfindable on the customer's network. Keeping IP addresses static is more convenient.