Vertex group & Vertex cluster

Let’s talk a little about the structure of the E2D system.

As you should know the basic unit is a Vertex. When you start commissioning we recomend connecting it to a LAN network. When you connect more Vertexes to your LAN network they will join your first Vertex in a Cluster.

So a Vertex Cluster is a system made out of up to 25 Vertexes connected to one LAN network. Diferent Clusters will have diferent names, which we call Cluster UID or CUID. So all Vertexes in one Clutser will have the same CUID.
Of course there are many diferent types of buildings, so choose to commission Vertexes, that will be likely to work together, or in the same area to be in the same Cluster. You do not need to fill each Cluster, they might have a lot less devices then 25, try to use common sense when joining them into Clusters.

A Vertex group consists of one or more Vertexes inside one cluster. They communicate with each other with peer to peer (server/client) communication. A Vertex controller in a group ‘sees’ (knows only of the existence of) other Vertexes in the same group. Communication between groups is still possible, but may be slower. You can create up to 15 groups. Using groups is an optimization of communication, where you can separate and limit communication between floors, areas, etc.

How to manage a cluster?

To manage your cluster enter NetConfig: http://VERTEX_IP/netconfig/home

After that, you will see all units which you want to configure as groups.

The last step is sending the configuration to Vertexes with CUID. Choose to send the configuration with the old CUID.

For a better understanding, consider these two examples:

1. Vertex controllers in one Vertex group in one cluster in one network

2. 

   Vertex controllers in different Vertex groups in one cluster in one network