How could we set the device into PM3 while it was on Hold_auto_start

If you use Z-Stack, it only support PM2 because Z-Stack use timer interrupt to wake-up for event processing. There is no API to enable PM3 in Z-Stack.

Maybe i have not make it clear for you ！

I change the POLLRATE item as 0 in the f8wConfig.cfg file and enable Power_SAVING at first
-DPOLL_RATE=0
-DQUEUED_POLL_RATE=0
-DRESPONSE_POLL_RATE=0

Secondly ， i enable the HOLD_AUTO_START，

Finish those two step ， i think that the device will holding not to join the network and keep in PM3
until anyothers toggle（maybe like key press）， then i will use the NLME_SetPollRate() Function to change the POLLRATE,
To change the device Mode into PM2

but it was always cost 9mA while the device power on ，and it was HOLD_AUTO_START, but can't go into PM3

Do you enable POWER_SAVING?

i am sure ，i already enable it

Do you connect CC debugger when doing current measurement? If yes, please remove CC debugger. If no, there must be some unsed IO pins that are leaking current.

no！ not CC debug ，not unused IO ！
when i disable HOLD_AUTO_START, the device was OK go into PM3 after it join network

Thank you ！ DarkSide

          i have already success in setting the device in PM3 while its hold auto start.

         It just like what you said ！

        but i don't know whether it is right or not  to  put the  osal_pwrmgr_device( PWRMGR_BATTERY ); in the last of the APP init function?

Heros have the same mind !
but i put it in the app init function , it was also OK.

and could you know how long does the devices waitting for the next search the network step after it was failed

When device can not have Zigbee network to join, it would keep sending beacon request and the interval of beacon duration is defined by BEACON_REQUEST_DELAY in f8wconfig.cfg.