CC2530: Coordinator Device Cannot Receive Any Data from End Device

Amira Prisha

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

We have three CC2530 ZigBee devices in three different locations. Two of them are using ZNP as their firmware. One of the devices is configured as a coordinator, and the other one is an end device. In this scenario, everything works fine and two devices exchange data properly.

However, we have another ZigBee end device which is attached to door with an unknown firmware. The connection between this device and the coordinator has been established without no problem, but the coordinator can not receive any data from the device which is attached to the door. We already checked the packets which are sent from the door device by making use of "Packet Sniffer". The log file of this program has been attached for more information.

The question is, why doesn't the coordinator receive any data?

Sincerely, AmiraPrisha.

packets.psd

over 5 years ago

0 Toby Pan over 5 years ago

TI__Mastermind 28440 points

Hi AmiraPrisha,

Which version of Z-Stack are you using for ZNP?

There's not much information I can observe in the log.
If possible, please send logs from the beginning:
1. Erase and then flash of the coordinator
2. Start packet sniffer
3. Enable joining on the coordinator
4. Enable commissioning (or reset) the end device on the door

Regards,
Toby

0 YiKai Chen over 5 years ago

Guru 735455 points

Do you design that unknown door sensor or it is from 3rd party? Do you do binding to make it know the destination to send report?

0 Toby Pan over 5 years ago

TI__Mastermind 28440 points

Any updates on this?

Please let us know if you require further support.

0 Amira Prisha over 5 years ago in reply to Toby Pan

Prodigy 90 points

I used the last version of Z-Stack (3.0.1)

The new log file of Packet Sniffer has been attached.

Thanks

newPackets.psd

0 Amira Prisha over 5 years ago in reply to YiKai Chen

Prodigy 90 points

The door is from 3rd party and it does work with Xbee Modules, I dont know what is binding? does it mean i use ZDO_BIND_REQ command to bind end Device ?

0 YiKai Chen over 5 years ago in reply to Amira Prisha

Guru 735455 points

Yes, I mean to use ZDO_BIND_REQ for binding. However, the 3rd party door sensor is asked to leave network and doesn’t join coordinator according to your latest sniffer log. I suspect the 3rd party devices doesn’t use Zigbee 3.0 so is asked to leave. Do you know what’s Zigbee profile the 3rd party device uses?

0 Amira Prisha over 5 years ago in reply to YiKai Chen

Prodigy 90 points

I think the door uses Zigbee 2006 (non-pro)

0 YiKai Chen over 5 years ago in reply to Amira Prisha

Guru 735455 points

If it's not Zigbee 3.0 device, you should set BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE to FALSE on coordinator to make it join.

0 Amira Prisha over 5 years ago in reply to YiKai Chen

Prodigy 90 points

thank you , I set BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE to FALSE and I think a problem that 3rd party device is asked to leave was solved, but yet the coordinator doesnt receive any msg from the device,The new log file has been attached. What else should I do?

Packets2.psd

0 YiKai Chen over 5 years ago in reply to Amira Prisha

Guru 735455 points

I don’t see you use ZDO_BIND_REQ for binding IAS Zone reporting for door sensor in your sniffer log. I suppose you have to do binding to make it work.

0 Amira Prisha over 5 years ago in reply to YiKai Chen

Prodigy 90 points

Sorry, I've just attached the correct log.I used ZDO_BIND_REQ but still the problem of receiving the message has not been resolved.where did i do wrong?

Thanking you for sharing your valuable time for me.

Packets4.psd

0 YiKai Chen over 5 years ago in reply to Amira Prisha

Guru 735455 points

I see you use 0x000B as Cluster ID but IAS zone cluster ID should be 0x0500.

0 Amira Prisha over 5 years ago in reply to YiKai Chen

Prodigy 90 points

I changed the Cluster ID to 0x0500 but the problem is still there.

0 YiKai Chen over 5 years ago in reply to Amira Prisha

Guru 735455 points

Do you use correct source and destination endpoint?

0 Amira Prisha over 5 years ago in reply to YiKai Chen

Prodigy 90 points

I use 0x0B for both of them

0 YiKai Chen over 5 years ago in reply to Amira Prisha

Guru 735455 points

Does 3rd party door sensor and your coordinator use 0x0B as endpoint?

0 Amira Prisha over 5 years ago in reply to YiKai Chen

Prodigy 90 points

I do not know anything from the door sensor, from the packets i guess the door endpoint is 0x0B , for coordinator
I tested different numbers even 0x0B.

0 YiKai Chen over 5 years ago in reply to Amira Prisha

Guru 735455 points

You should use ZDO_ACTIVE_EP_REQ with short address of door sensor to request sensor endpoint.

0 Toby Pan over 5 years ago in reply to Amira Prisha

TI__Mastermind 28440 points

Based on the logs, there may be an issue with the bind request that the end device sends to the coordinator.

The destination IEEE address seems to be reversed. It is 00:12:4B:00:0D:BB:D6:98 for the coordinator, but the bind request is using 98:D6:BB:0D:00:4B:12:00.

Perhaps that may be worth investigating.

Zigbee & Thread

Zigbee & Thread forum

CC2530: Coordinator Device Cannot Receive Any Data from End Device