What's the diffenence between Power Saving mode and normal mode?

Hi blacksmith,

please refer to the datasheet of the chip you are using / want to use. The power modes are explained there with the timer, which are working etc. There are different depths of "sleep" and therefore different functions available.

If you can give us the chip and the power mode you are talking about, we could help in more detail... =) THX

I am sorry for missing that, and thank you for your attention again!

I use a MSP430F2618 MCU, current consumption in POWER SAVING mode is just 1mA in my board, and I have tested timer still working, but seemed to be unstable. Sometimes, it couldn't connect to any router.

I don't know which power saving depth it's in.

Besides that, is there other difference? such as network strategy, when should it wake up(timer interrupt, I/O interrupt, and what?), ...

so, I want a much detail discription.

The answer should be in the source code, but if you give me some clue, that will save me a lot of time.

First things, first.

As I stated in the other thread, I'm not familiar with ZigbeePro, but usually the stack doesn't go deeper than P1 by default. I just make a guess that hasn't changed... ;-)

So, in P1 the timers should be still working. [I guess you are using osal_start_timerEx(), or am I wrong?] Unstability is weird here... But please somebody answer with experience in that stack.

From P1 you can normally use timer-based wake-up procedures or just interrupt procedures, which are working also in deeper sleep modes by the way.

Details and source code examples have to follow from somebody else as I do not even have the code ;-)

Hope you find it and keep me posted as I also have to start with this newer version of ZStack next year.

THX

In  hal_sleep.c file it defines

/* HAL power management mode is set according to the power management state. The default
 * setting is HAL_SLEEP_OFF. The actual value is tailored to different HW platform. Both
 * HAL_SLEEP_TIMER and HAL_SLEEP_DEEP selections will:
 *   1. turn off the system clock, and
 *   2. halt the MCU.
 * HAL_SLEEP_TIMER can be woken up by sleep timer interrupt, I/O interrupt and reset.
 * HAL_SLEEP_DEEP can be woken up by I/O interrupt and reset.
 */
#define HAL_SLEEP_OFF         MSP430_AM
#define HAL_SLEEP_TIMER       MSP430_LPM3
#define HAL_SLEEP_DEEP        MSP430_LPM4

so, in HAL_SLEEP_TIMER mode, timer still working.

but which power saving mode should it be?

same file hal_sleep.c defines void halSleep( uint16 osal_timeout )

 /* HAL_SLEEP_PM2 is entered only if the timeout is zero */
  halPwrMgtMode = (timeout == 0)? HAL_SLEEP_DEEP : HAL_SLEEP_TIMER;

so, I guess, if no timer used in OSAL, device should enter into HAL_SLEEP_DEEP automaticlly, in which only I/O interrupt and reset can wake it up.

and WorkingAgain? thank you for your attention, which project are you working on?

Hi blacksmith,

I think we are currently having a bit the same problem, just other chip for me, but I have actually more or less the same expressions etc.

FYI, the follgowing project is running (except sleepin part):

I have a remote software on a computer/server which is controlling the network(s) via SMS. So the Coord is connected via UART to the modem and I have a sensor network, which is collecting info. Upon request from the remote side the coordinator gets the info from the network and is sending back one or more SMS according to the load of info. The remote software compiles the info and displays the info for the user(s) and stores the process etc.

Now I have to change the network and let it sleep, which seems not to be so easy as I thought it will be...

Hi, yes, we do face some common problems...

can you speak chinese? do you use some IM software?

Pls see my email for IM addresses etc. THX

https://community.ti.com/forums/p/1467/5067.aspx#5067

yes the timer is still working in SLEEP MODE 2. Block all the timer, and the chip would work in PM3.