...
...
...
...
...
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 recommend 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. Different Clusters will have different names, which we call Cluster UID or CUID. So, all Vertexes in one Cluster will have the same CUID. Of course, there are many different types of buildings, so choose to commission Vertexes that will likely work together or be in the same area to be in the same Cluster. You do not need to fill each Cluster; they might have a lot fewer devices than 25. Try to use common sense when joining them into Clusters.
In the settings tab you can see your Clusters' topology in or see information about each Vertex.
...
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.
...
Vertex cluster is a system of up to 25 Vertex controllers. Communication between clusters is done via TCP/IP. All Vertexes in one cluster share the same cluster ID - CUID (a Node.js based identifier with collision-resistant communication). Vertexes in a cluster can be divided into groups.
Vertex Cluster is a system which allows sending information between devices connected to controller(s) and enables you to create a bigger lighting management system.
Some important definitions:
Vertex Group- is a part of Vertex Cluster. You can separate gateways intoVertex Groupsin your cluster. InsideVertex Group, gateways are communicating each other and send commands.Vertex Groupcan see otherVertex Groups(routing table), but commands from otherVertex Groupsare not received.CUID (Cluster Unique Identifier) - is a Node.js based identifier with collision-resistant communication.
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. You have 15 Vertex groups in one network, so you can create up to 15 stand alone Vertex groups.
| Info |
|---|
Vertex group in netconfig is NOT the same as vertex group in GUI/Node-RED. Vertex group in netconfig is a group of Vertex controllers. Vertex group in GUI/Node-RED is a group of luminaires. |
...
The last step is sending the configuration to Vertexes with CUID. You can choose Choose to send the configuration with the old CUID or generate a new one (default). .
| Info |
|---|
It is important when you are replacing one Vertex |
...
. CUID identifies your site. By selecting the old CUID you don't |
...
have to authorise it again (you don’t lose access and connection to Glamox Connect). |
...
For a better understanding, consider these two examples:
Vertex controllers in one Vertex group in one cluster in one network
Vertex controllers in different Vertex groupgroups in one cluster in one network
| Info |
|---|
One LAN network = one CUID |
Hardware explanation of clusters
See below the structure diagram of Vertex communication in the cluster. Prosody XMPP server due to routing table is able to transmit and receive commands or messages to other Vertex prosody XMPP server by ethernet connection.
...
For more information go to: