LAUNCHXL-CC26X2R1: Sleepy End Device Network Connection Status

Giribabu Paila

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: SYSCONFIG, Z-STACK, PACKET-SNIFFER

Hi
Can you suggest me how to send read attribute request(like every hour) to Basic cluster's(0x0000) version attribute(0x0000) of sleepy end device which is don't have support for poll control cluster(0x0020) . And how to query wake up time in sleepy end device.Example sensors Model ids wls-15zbs,sensor 3305-s.

over 5 years ago

0 YiKai Chen over 5 years ago

Guru 735685 points

What is the polling rate of your devices?

0 Giribabu Paila over 5 years ago in reply to YiKai Chen

Prodigy 50 points

Hi yk chen

Actually These sensors are doesn't have poll control cluster so we not able to get the check-in Interval we not able to get the polling rate.

0 Ryan Brown1 over 5 years ago in reply to Giribabu Paila

TI__Guru**** 218697 points

Hi Giribabu,

Yikai Chen is not asking about the poll control cluster but rather the POLL_RATE determined from SysConfig. If a ZED child does not check in at the rate as set by NWK_END_DEV_TIMEOUT_DEFAULT or determined by END_DEV_TIMEOUT_VALUE then it will be aged out by the ZC/ZR parent. You can create a custom application to inquire or calculate this poll rate but it cannot be discovered using the default Z-Stack. As you have no way of waking the ZED you will have to queue the message until the ZED sends a data request or disable sleep on the ZED.

Regards,
Ryan

0 YiKai Chen over 5 years ago in reply to Giribabu Paila

Guru 735685 points

If those devices are previous Zigbee HA profile devices, they might not support polling control. If you need poll control cluster support on devices, I suppose you should contact manufacturer to revise firmware.

0 Giribabu Paila over 5 years ago in reply to YiKai Chen

Prodigy 50 points

Hi Yikai Chen and Ryan

Actually Device is Sending Data request in every 300 seconds.

In code under zstackserverznp f8wConfig.h file .For End Device following are defined.

RFD_RCVC_ALWAYS_ON FALSE

POLL_RATE 1000

Do I need to change these values to change the poll rate of the device?

0 YiKai Chen over 5 years ago in reply to Giribabu Paila

Guru 735685 points

If those device doesn’t support poll controller cluster, it’s not possible to change polling rate remotely from coordinator.

0 Ryan Brown1 over 5 years ago in reply to Giribabu Paila

TI__Guru**** 218697 points

The macros described affect the local device, so they would only apply to the ZED which is asleep and polling. The situation is as YK stated.

Regards,
Ryan

0 Giribabu Paila over 5 years ago in reply to Ryan Brown1

Prodigy 50 points

Hi Ryan and yikai

Do we have any other way to know the sleepy end devices network status,sending woke up request to the Device?.
Actually Data Requests are coming from Device we able to see in sniffer.
How we can know this are reaching NPI server?

We are using TI CC26x2R1 as sniffer Receiving Packets through Ti SmartRF sniffer agent 2 with Wire shark in Windows,How does it possible to use in Ubuntu?

0 YiKai Chen over 5 years ago in reply to Giribabu Paila

Guru 735685 points

There’s no application callback to notify parent node that it receives data request. The only solution is poll control cluster support so it’s better for you to contact manufacturer to add poll control cluster.

0 Ryan Brown1 over 5 years ago in reply to Giribabu Paila

TI__Guru**** 218697 points

PACKET-SNIFFER is only known to be supported in Windows and is not tested with Linux environments.

Regards,
Ryan

0 Giribabu Paila over 5 years ago in reply to YiKai Chen

Prodigy 50 points

Hi Ryan,

How can we enable or implement the callback function to handle the data requests.? and where we have to enable data requests( i.e in ZNP firmware, NPI,zstack).

Regards,
Giribabu.

0 YiKai Chen over 5 years ago in reply to Giribabu Paila

Guru 735685 points

Data request is handled by Z-Stack library and no application callback or event for developers to process it.

Zigbee & Thread

Zigbee & Thread forum

LAUNCHXL-CC26X2R1: Sleepy End Device Network Connection Status