CC2530: Cluster List for Temperature Sensor Sample

Marat Akhmetov

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

Hi.

I'm trying to lunch Thermostat and Temperature Sensor sample. Flashed the firmware but I can not bind them with each other. Which of the devices should be initiator and with one is target?

As I understand the temperature sensor to report it's temperature value using reporting capabilities has to have a binding record in it's binding table. The binding table is filled during the finding and binding procedure. BUT, according to BDB source code the binding is done using OutClusterList of temperature sensor and InClusterList of Thermostat, but the ZCL_CLUSTER_ID_MS_TEMPERATURE_MEASUREMENT is not in the OutClusterList of temperature sensor.

over 8 years ago

0 YiKai Chen over 8 years ago

Guru 735695 points

Try to refer to section 15.7.1 Finding & binding procedure for a target endpoint in Z-Stack 3.0 Developer's Guide.pdf

0 Marat Akhmetov over 8 years ago in reply to YiKai Chen

Intellectual 560 points

There is only one function that starts commissioning and finding & binding procedure - that is bdb_StartCommissioning(). But how does it determine if current device is going to be a target or initiator?

And I repeat to make a match the OutClusterList of temperature sensor should have ZCL_CLUSTER_ID_MS_TEMPERATURE_MEASUREMENT but it doesn't.

0 YiKai Chen over 8 years ago in reply to Marat Akhmetov

Guru 735695 points

Have you read section 15.7.1 Finding & binding procedure for a target endpoint in Z-Stack 3.0 Developer's Guide.pdf?

0 Marat Akhmetov over 8 years ago in reply to YiKai Chen

Intellectual 560 points

Yes. It says "if an endpoint has a cluster that is meant to be initiator, the finding and binding process for this endpoint will be executed as initiator"
What does that mean "cluster is meant to be initiator"? How do I know if it's meant to be or not?

0 YiKai Chen over 8 years ago in reply to Marat Akhmetov

Guru 735695 points

Initiator or targer is assigned by "ep->epDesc->epType = bdb_zclFindingBindingEpType(ep->epDesc);" in afRegisterExtended.

0 Marat Akhmetov over 8 years ago in reply to YiKai Chen

Intellectual 560 points

Ok. That's clear ) Thank you.

How about temperature reporting. For the temperature sensor to report is temperature it should have a binding record in its binding table. To have this record there it should be the initiator of finding and binding.

See bdb_checkMathchingEndpoints()

status = bdb_zclFindingBindingAddBindEntry( initiator outclusterlist, target inclusterlist)

Is this correct?

0 YiKai Chen over 8 years ago in reply to Marat Akhmetov

Guru 735695 points

Yes, your understanding is correct.

0 Marat Akhmetov over 8 years ago in reply to YiKai Chen

Intellectual 560 points

If my understanding is correct then why ZCL_CLUSTER_ID_MS_TEMPERATURE_MEASUREMENT is not in the OutClusterList of temperature sensor? That's why finding and binding on temperature sensor as initiator fails.

0 YiKai Chen over 8 years ago in reply to Marat Akhmetov

Guru 735695 points

As initiator, ZCL_CLUSTER_ID_MS_TEMPERATURE_MEASUREMENT should be in the InClusterList of temperature sensor. I suggest you to use Ubiqua Protocol Analyzer to check what happens over the air to know more about why finding and binding on temperature sensor as initiator fails.

0 Marat Akhmetov over 8 years ago in reply to YiKai Chen

Intellectual 560 points

According to bdb_zclFindingBindingEpType it's true. But binding fails in

bdb_checkMathchingEndpoints()
...
status = bdb_zclFindingBindingAddBindEntry( initiator outclusterlist, target inclusterlist)

it returns 0xB1. I suppose because outclusterlist doesn't contain ZCL_CLUSTER_ID_MS_TEMPERATURE_MEASUREMENT

0 YiKai Chen over 8 years ago in reply to Marat Akhmetov

Guru 735695 points

It’s target need to contain ZCL_CLUSTER_ID_MS_TEMPERATURE_MEASUREMENT in out clusters.

0 Ryan Brown1 over 8 years ago in reply to Marat Akhmetov

TI__Guru**** 223597 points

The default examples contain all of the clusters necessary for proper binding and work out-of-box. We assume that you are using Z-Stack 3.0.1 unmodified examples, please clarify if not. Are you testing with SmartRF05EB EVMs, a thermostat coordinator, and temp sensor router or end device?

Regards,
Ryan

0 Marat Akhmetov over 8 years ago in reply to Ryan Brown1

Intellectual 560 points

Yes 3.0.1 unmodified samples.

No it's not SmartRF05EB but a custom cc2530 with no LCD. LCD capabilities has been turned off. I've already tried SampleOn/off switch a Samplelight and they are working fine.

0 YiKai Chen over 8 years ago in reply to Marat Akhmetov

Guru 735695 points

I suggest you to use Uniqua Protocol Analyzer to check what happen over the air.

0 Marat Akhmetov over 8 years ago in reply to YiKai Chen

Intellectual 560 points

Yet can not check it with protocol analyzer, but could it be because both devices (temperature sensor and thermostat) are EndDevices?

Just check using debugging Temperature Sensor reaches bdb_startResumeCommissioningProcess() and executes

bdb.CommissioningModeMsg.bdbCommissioningMode = BDB_COMMISSIONING_FINDING_BINDING;

bdb.CommissioningModeMsg.bdbCommissioningStatus = BDB_COMMISSIONING_FB_INITIATOR_IN_PROGRESS;

bdb_NotifyApp(...)

so I think it sends identify requests.

The thermostat device blinks its identify LED.

Both devices are connected to Zigbee HA Gateway. Gateway is set up as Coordinator.

0 YiKai Chen over 8 years ago in reply to Marat Akhmetov

Guru 735695 points

Yes, that might be the problem. Try to set your thermostat aa RX always on device or a router to test again.

0 Marat Akhmetov over 8 years ago in reply to YiKai Chen

Intellectual 560 points

Thats it!!! Switched Thermostat to router and it binding happened!

1.How do I change RX always on? Or is it better to set it as a router?

2.Do you mean that two battery powered end devices can not be bound for data exchange?

0 Ryan Brown1 over 8 years ago in reply to Marat Akhmetov

TI__Guru**** 223597 points

1. -DRFD_RCVC_ALWAYS_ON=TRUE in f8wConfig.cfg
2. Device announcements are not processed by sleeping end devices which is an issue for F&B commissioning, an alternative is manual binding.

Regards,
Ryan

0 Marat Akhmetov over 8 years ago in reply to Ryan Brown1

Intellectual 560 points

Chen, my thermostat end device was not set as a sleeping. POWER_SAVING was turned off. Still "RX always on" should be set to 1?

0 YiKai Chen over 8 years ago in reply to Marat Akhmetov

Guru 735695 points

Yes, you still have to set -DRFD_RCVC_ALWAYS_ON=TRUE in f8wConfig.cfg

Zigbee & Thread

Zigbee & Thread forum

CC2530: Cluster List for Temperature Sensor Sample