LAN network design
Network planning
Create a schematic diagram of the LAN network. This helps you plan the required number of LAN ports and network switches.
Include additional devices in your planning, such as the ATLAS remote access kit and the connection to the BMS (Building Management System).
LAN network design rules
Maximum distance between devices: 100 m
BMS connection: Use Modbus TCP/IP
LAN switches require an external power supply
Up to 400 Vertex controllers can operate in one cluster (for more, create additional clusters)
One ATLAS remote access kit can connect to up to 25 Vertexes. If your system is larger, add one ATLAS remote access kit for every additional 25 Vertexes.
Good practices
Always leave spare ports on each switch. Don’t use all available switch ports. Keep at least one free for future expansion or service needs.
Daisy chaining
Vertex 4 has two LAN ports, which allow for daisy-chaining connections between controllers.
Vertex controllers must always be wired in a star topology. Closed loops or ring topologies are not allowed and will cause communication issues.
Connection with the LAN switch
Connection without the LAN switch
Switch connections are the most robust, but daisy chaining is fine if you stick to 8 controllers per network connection and avoid loops.
Up to 8 controllers per 100 Mb/s network connection is safe, even if they are sending frequent data updates.
Keep daisy chains short — this makes troubleshooting easier and limits the impact if a device or cable fails.
If your system also handles BMS integration load (for example MQTT/Modbus-TCP subscriptions) or uses multiple LMS E2D Touch Panels or dashboards, spread controllers across multiple switch ports — this prevents the network connection from becoming overloaded.
If you have different types of controllers in your project, you will need to follow these instructions:
(Classic) Merging Vertex 2 and Vertex 3 within the same cluster Merging Vertex 2 and Vertex 3 within the same cluster
For more information, go to: