Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The section below discusses Zigbee Bindings and how they can be createdThis guide explains the Zigbee concept of device binding and provides instructions for creating bindings using RapidConnect firmware and RapidConnect Desktop.


What is a Binding?

Binding between devices is the creation of a A binding is a unidirectional logical link connecting a cluster between a source node/endpoint /cluster identifier pair and a destination node/endpoint. These binding entries are kept in a Binding Table. Bindings are used for delivering to deliver Commands and Attribute Reports from a source node to a destination node(s)one or more destination nodes.

For example: I have a light switch and a light bulb. A binding could be created on the switch that instructed it to send commands to the light. When the switch wants to send an On/Off/Toggle command to the light, the app layer then sends the message using the binding table. This way the switch can be connected to different devices or groups of devices at runtimeI can create a binding for the On/Off cluster, using the switch as the source and the bulb as the destination. When a user changes the state of the switch (for example, turns if off), the Zigbee application running on the switch will recognize that its On/Off cluster has a binding with the bulb and the switch will then send an Off command to the bulb. Bindings can be configured at runtime, meaning that the logical pairings between devices (or groups of devices) can be updated easily.

What is a Binding Table

A binding table allows ZigBee devices to establish a designated destination for frames from a given source endpoint and with a given cluster ID. Each designated destination shall represent either a

?

The Coordinator and each Router on the network have a Binding Table to store the relationship between sources and destinations for various clusters. Destinations can be a specific endpoint on a specific device , or a group address.

Example Topology

Drawio
baseUrlhttps://mmbnetworks.atlassian.net/wiki
diagramNameBindings.xml
contentId422609316
width759
zoom1
pageId226787441
diagramDisplayNameBindings.xml
lbox1
contentVer1
height769.5
revision12

Creating Bindings

in RapidConnect Desktop

Bindings can be created easily in RapidConnect Desktop.

Pre-requisites

Network formed using a MMB Networks device

Using RapidConnect Desktop

RapidConnect Desktop makes it easy to configure bindings on a device running RapidConnect firmware.

Prerequisites

  1. Network formed using RapidConnect Desktop and RapidConnect hardware that has been configured as a Coordinator. For instructions on on how to do this, review the RapidConnect Desktop Quick Demo Guide.
  2. Coordinator has been configured with the On/Off ServerClient-Side Clustercluster.
  3. A remote device joined to supporting the Coordinator has the On/Off ClientServer-Side ClusterA RapidConnect Desktop application instance open, connected to the Coordinator device.cluster has joined the network

Create a Binding

Click on the button to open the Binding Menu

In the Binding Menu, you will see the following parameters:

  1. Destination. Node ID and Endpoint of the destination for the binding link.
  2. Source. Node ID and Endpoint of the source for the binding link.
  3. Cluster. The identifier Cluster ID of the cluster on the source device that is to be bound to the destination device.
  4. Bind Request. Sends the binding request to the source.
  5. Bindings. List of Binding Table entries.

Creating Bindings Using the RapidConnect Serial Protocol

Coming soon!

 


Panel
borderStylesolid
titleOn This Page

Table of Contents
maxLevel1


Panel
borderStylesolid
titleIn This Space

Page Tree


Panel
borderStylesolid
titleRelated Content

Filter by label (Content by label)
showLabelsfalse
max4
showSpacefalse
cqllabel in ("desktop","device_management") and parent = "113312124"



Style
{style}
  .wiki-content h1 { 
	font-family: 'Helvetica Neue', sans-serif; font-size: 30px; font-weight: bold; color: #7ab800; letter-spacing: 1px; line-height: 1; text-align: left;
    #border-bottom: 1px solid #98bddd !important; 
  }
.wiki-content h2 { 
	font-family: 'Helvetica Neue', sans-serif; font-size: 20px; font-weight: normal; color: #a1cd4c; letter-spacing: 1px; line-height: 1; text-align: left;
  }
.wiki-content h3 { 
	font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: normal; color: #a7a9ac; letter-spacing: 1px; line-height: 1; text-align: left;
  }
.wiki-content h4 { 
	font-family: 'Helvetica Neue', sans-serif; font-size: 15px; font-weight: normal; color:#a7a9ac; letter-spacing: 1px; line-height: 1; text-align: left;
  }
#title-text{
 font-family: 'Helvetica Neue', sans-serif; font-size: 40px; font-weight: 500; letter-spacing: 1px; line-height: 1; text-align: left;
}


.panel, #content .panel {
-moz-border-radius: 5px;
-webkit-border-radius: 5px;
border-radius: 5px;
}

.panel .panelHeader {
text-align: left;
line-height: 1em;
padding: 10px 10px 5px;
margin-bottom: 0;
background-color: #7AB800;
-moz-border-radius-topleft: 5px;
-moz-border-radius-topright: 5px;
-webkit-border-top-right-radius: 5px;
-webkit-border-top-left-radius: 5px;
border-top-right-radius: 5px;
border-top-left-radius: 5px;
}

{style}