CCS/CC2530: Binding of two End-Devices

Florian Hinrichs59

Intellectual 300 points

Part Number: CC2530
Other Parts Discussed in Thread: MSP430F2370, , Z-STACK

Tool/software: Code Composer Studio

Hello,

i am working with the CC2530 Zigbee Chip in combination with an application processor (MSP430F2370).

My minimal system looks like this: 1 Coordinator + 2 End-Devices.

My approach shall be to bind these 2 End-Devices to each other as I send a ZDO_END_DEVICE_BIND_REQ from each end device to the coordinator after I registered my application with AF_REGISTER. But I always get the response 0x89 back. The end device bind request was unsuccessful due to a failure to match any suitable clusters.

End-Device 1: Switch (send message to End-Device 2) = Client

End-Device 2: ON/OFF (receives message and switches a lamp on/off) = Server

I use the following application configurations from the ZNP2530 Mini Kit:

struct applicationConfiguration getApplicationConfigurationForEndDevice()
{
    printFtdi("Getting Application Configuration For End Device\r\n");
    struct applicationConfiguration ac;
    memset(&ac, 0, sizeof(struct applicationConfiguration));
    ac.endPoint =                       DEFAULT_ENDPOINT;       //0xD7
    ac.profileId =                      DEFAULT_PROFILE_ID;     //0xD7D7
    ac.deviceId =                       DEVICE_ID;              //doesn't matter
    ac.deviceVersion =                  DEVICE_VERSION;         //doesn't matter
    ac.latencyRequested =               LATENCY_NORMAL;
    ac.numberOfBindingInputClusters =   1;
    ac.bindingInputClusters[0] =       	0x0001;
    ac.numberOfBindingOutputClusters =  0; //1
    return ac;
}

I don't really know how I have to configure the bindinginputcluster and bindingoutputclaster. They are different for End-Device 1 and 2? And which role plays the coordinator. The Coordinator is actually only available in order to route the messages, so that I dont need there application registrations, correct?

over 8 years ago

0 YiKai Chen over 8 years ago

Guru 735695 points

If you install Z-Stack Home 1.2.2a, you can refer to HA-SampleLight and HA-SampleSwitch under C:\Texas Instruments\Z-Stack Home 1.2.2a.44539\Projects\zstack\ZAP to see how it implement this.

0 Florian Hinrichs59 over 8 years ago in reply to YiKai Chen

Intellectual 300 points

Thank you for your quick response.

I had a look on the sources but one point is confusing with binding. The SampleSwitch wants to combine with the SampleLight, but there are different endpoints (SAMPLESW_ENDPOINT 12 for Switch and SAMPLELIGHT_ENDPOINT 13 for light). I thought for binding, the endpoints must be equivalent?!

0 YiKai Chen over 8 years ago in reply to Florian Hinrichs59

Guru 735695 points

No, the source and destination endpoint can be different.

0 Florian Hinrichs59 over 8 years ago in reply to YiKai Chen

Intellectual 300 points

Which parameters the ZNP then evaluates in order to say that two devices can bind?

0 YiKai Chen over 8 years ago in reply to Florian Hinrichs59

Guru 735695 points

Two devices have to support the same cluster on their in/out cluster.

0 Florian Hinrichs59 over 8 years ago in reply to YiKai Chen

Intellectual 300 points

In which direction the clusters have to fit to each other?

The SampleSwitch assign the following cluster:

 ZDP_EndDeviceBindReq( &dstAddr, NLME_GetShortAddr(),
                           SAMPLESW_ENDPOINT,
                           ZCL_HA_PROFILE_ID,
                           0, NULL,   // No incoming clusters to bind
                           ZCLSAMPLESW_BINDINGLIST, bindingOutClusters,
                           TRUE );

While the SampleLight registers this cluster:

ZDP_EndDeviceBindReq( &dstAddr, NLME_GetShortAddr(),
                           SAMPLELIGHT_ENDPOINT,
                           ZCL_HA_PROFILE_ID,
                           ZCLSAMPLELIGHT_BINDINGLIST, bindingInClusters,
                           0, NULL,   // No Outgoing clusters to bind
                           TRUE );

That means to me that endpoints can be different, in&outcoming clusterslists can be different but the profile id MUST be the same? How the in&outcoming clusters have to fit together?

0 YiKai Chen over 8 years ago in reply to Florian Hinrichs59

Guru 735695 points

Using SampleLight and SampleSwitch as example, we would like to do end device binding to make SampleSwitch to send ON/OFF command to SampleSwitch. You have to put ZCL_CLUSTER_ID_GEN_ON_OFF in OutClusterList of ZDP_EndDeviceBindReq on SampleSwitch and ZCL_CLUSTER_ID_GEN_ON_OFF in InClusterList of ZDP_EndDeviceBindReq on SampleLight

0 Florian Hinrichs59 over 8 years ago in reply to YiKai Chen

Intellectual 300 points

So, I found the mistake, why the binding doesn't work. It seems so that there is a small mistake in the CC2530ZNP Interface Specification.

In the message structure is the 8 Byte IEEE Address missing.

Zigbee & Thread

Zigbee & Thread forum

CCS/CC2530: Binding of two End-Devices