Match Description request not answered all the time

Leo47836

Other Parts Discussed in Thread: CC2530

Hi,

While integrating new Centralite security sensor, we observed a strange behavior on our coordinator based on Texas Instrument Zigbee Home 1.2.0 on CC2530.

After the association, Centralite is broadcasting a Match Description Request. If it doesn't receive any response, it leave the network after 2 seconds.

Our issue : our coordinator is sometimes responding, sometimes not.

Here are some logs :

Our coordinator correctly answers at time 104.9474 or at time 904.34. But it failed most of the time.

How could I proceed to fix this issue?

Regards,

Leo

over 11 years ago

0 Leo47836 over 11 years ago

Intellectual 520 points

Here is the log file :

6648.centralite_match_description_timeout.zip

0 YiKai Chen over 11 years ago in reply to Leo47836

Guru 735695 points

Do you put related clusters in input/output cluster lists of your coordinator?

0 Leo47836 over 11 years ago in reply to YiKai Chen

Intellectual 520 points

Thanks for your answer!

The Centralite sensor does send 2 Match Description Requests :
- one for cluster 0xFC0F (Occupancy Cluster)
- one for cluster 0x0500 (SS-IAS-Zone Cluster)

Our coordinador implements SSIAS-Zone Cluster (0x0500) that is why it does answer sometime.

Here is the list of input/output cluster of our Coordinator
InClusters 0x0000, 0x0003, 0x000A, 0x0501
OutClusters 0x0000, 0x0003, 0x0004, 0x0005, 0x0500, 0x0502

My question is why it doesn't answer all the time?

0 YiKai Chen over 11 years ago in reply to Leo47836

Guru 735695 points

Is your sensor far away from coordinator? I can't read signal strength from your sniffer log but I suspect this is about poor signal strength.

0 Leo47836 over 11 years ago in reply to YiKai Chen

Intellectual 520 points

The sensor is less than 1 meter of the box... I didn't suspect that would explain this behavior....

0 YiKai Chen over 11 years ago in reply to Leo47836

Guru 735695 points

You can try to set breakpoint at ZDO_ProcessMatchDescReq() and see what happens.

0 Leo47836 over 11 years ago in reply to YiKai Chen

Intellectual 520 points

It seems ok when I use the Debugger, It was working all the time. I have done it 20 times...

But I have observed that when I send some bind request on several cluster just before receiving the MatchDescReq, it could take some time before entering the ZDO_ProcessMatchDescReq... Strange behavior!

0 YiKai Chen over 11 years ago in reply to Leo47836

Guru 735695 points

Bind request is not processed in ZDO_ProcessMatchDescReq. Only Match request does. If coordinator receives match request, ZDO_ProcessMatchDescReq would be called in short time.

0 Leo47836 over 11 years ago in reply to YiKai Chen

Intellectual 520 points

Thanks a lot Chen!

I manage to reproduce the issue with the debugger activated.

But I also clearly see that the ZDO_ProcessMatchDescReq is received, that the ZDP_MatchDescRsp is called but I can't see the response on my sniffer...

Do you know if there could be a mecanise that could stop sending request that have reach the method "fillAndSend"?

Best Regards,
Leo

0 YiKai Chen over 11 years ago in reply to Leo47836

Guru 735695 points

If ZDP_MatchDescRsp is called, match response should be sent. What do you mean " if there could be a mecanise that could stop sending request that have reach the method "fillAndSend"?"

0 Leo47836 over 11 years ago in reply to YiKai Chen

Intellectual 520 points

My main issue that I observed ZDP_MatchDescRsp is called but I see no match response sent on the sniffer when a Bind Request has been done just before... I wonder if the match desc rsp request could be rejected after ZDP_MatchDescRsp is called...

Regards,

Leo

Zigbee & Thread

Zigbee & Thread forum

Match Description request not answered all the time