CC2538: Power Management using ZStack 3.0.1

Sylvain Louchez

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

This is a point-to-point Coordinator <=> ZED application

The battery-powered ZED needs to be in "sleep mode" between ZigBee exchanges both in the Associated/ Bound state, and when Orphaned.

See enclosed image of the power consumption trace.

See the yellow trace, current is measured across 3 ohms, and 20mV per division on scope

[1] while 'connected' and when ZigBee is active peaks are approx 35mA, and when at rest, we're as near to zero as the device allows (2538 processor in power mode 2)

[2] when the coordinator is turned off, and when the ZED sends a data request which doesn't receive a response,

The current profile is as follows. Following the ZED wake-up

- after 2.5 seconds - we read data from sensors:drawing 35mA for about 400mSec

- after 4 seconds, we set Poll rate to ZERO, expecting the Zstack to shut off (this works for Zstack 1.2, and clearly something is missing with Zstack 3.)

What is the new mechanism recommended for 3.0.1?

Thanks in advance for your help

over 7 years ago

0 YiKai Chen over 7 years ago

Guru 735695 points

In Z-Stack 3.0.1, the device should only wake up shortly to send beacon requests to search parent node every 10 seconds when it’s in orphan state.

0 Ryan Brown1 over 7 years ago

TI__Guru**** 221947 points

There are some known power consumption issues in Z-Stack 3.0.1 which have been resolved in 3.0.2: processors.wiki.ti.com/.../Zigbee_Known_Issues_and_Proposed_Fixes

Otherwise, the beacon request frequency mentioned by YK is established in the Application -> zcl_[application].c file of your project, inside the BDB_COMMISSIONING_PARENT_LOST case of zcl[application]_ProcessCommissioningStatus and controlled by SAMPLEAPP_END_DEVICE_REJOIN_DELAY in zcl_[application].h

Regards,
Ryan

0 Sylvain Louchez over 7 years ago in reply to Ryan Brown1

Prodigy 220 points

I'm sorry to report that we had no success.
We made sure that the 3.0.1. errata was incorporated in our code (it was) and verified nothing in 3.0.2. was different in our project.
Are there direct means of "telling" the stack to trigger going into sleep mode, something we could do directly from the application code?

0 Ryan Brown1 over 7 years ago in reply to Sylvain Louchez

TI__Guru**** 221947 points

There are changes in the Z-Stack core in 3.0.2 which cannot be applied to a 3.0.1 project. Make sure that POWER_SAVING is defined and you could investigate osal_pwrmgr_device( PWRMGR_BATTERY );

Regards,
Ryan

0 YiKai Chen over 7 years ago in reply to Sylvain Louchez

Guru 735695 points

Do you use TI CC2538DK when you test this?

0 Sylvain Louchez over 7 years ago in reply to YiKai Chen

Prodigy 220 points

Hi YK, no we're using our own board which has multiple sensors on the I2C bus plus 5 inputs configured for interrupts. However this board has been working with the 1.2 stack version for over 1 year and the custom code is well tested and understood.

We are using the TI kit boards for the coordinator, although I don't think this is relevant info :)

We are also busy on other things right now, so we can put this on ice?

Thanks for the help..

0 Ryan Brown1 over 7 years ago in reply to Sylvain Louchez

TI__Guru**** 221947 points

Relevant previous threads, but for the CC2530:

e2e.ti.com/.../672150
e2e.ti.com/.../665870

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

CC2538: Power Management using ZStack 3.0.1