CC2650STK: Enable POWER_SAVING on CC2650STK SensorTag - zStack_home_1.2.2a

thanks and I'm sorry...I was wrong...I wanted to say it is possible to enable POWER_SAVING on CC2650STK.

And how do I disable "Data polling"? in sensortagapp.c what is the function to modify?

Ok, thanks...but which variable, ZNWK_POLL_RATE in znwk_config.h:

/**
 * End Device Poll Rate -
 * The number of milliseconds to wait between data request polls to the coordinator.
 */
#if !defined ( ZNWK_POLL_RATE )
  #define ZNWK_POLL_RATE 5000
#endif

or DPOLL_RATE in f8wConfig.cfg:

/* The number of milliseconds to wait between data request polls to the coordinator. */
-DPOLL_RATE=1000

Ok ok...but my curiosity ... but this is an error:

xIGHTSENSOR_ENABLED simbol is set by default in SensorTag application! I think it's xLIGHTSENSOR_ENABLED...related to the LIGHTSENSOR_ENABLED variable in SensorTag (?)

It’s a unused define so it doesn’t matter. If you want to enable it, it’s correct to use LIGHTSENSOR_ENABLED

another relative question: In this scenario (POWER_SAVING enabled, DPOLL-RATE = 0), after it joins a Zigbee network,I assume that CC2650stk would consume 3uA if there is no poll or send no message...

Ok ok...thanks.

To TURN ON/OFF a specific on board sensor, I can simply use the driver functions.

For example, for MPU-9250 use this function:

/*******************************************************************************
* @fn          sensorMpu9250PowerOn
*
* @brief       This function turns on the power supply to MPU9250
*
* @return      none
*/
void sensorMpu9250PowerOn(void)
{
  extern PIN_Handle hGpioPin;

  // Make sure I2C interface is in a known state
  bspI2cSelect(BSP_I2C_INTERFACE_0,0);
  bspI2cDeselect();

  // Turn on power supply
  PIN_setOutputValue(hGpioPin,Board_MPU_POWER, Board_MPU_POWER_ON);
  delay_ms(100);
  sensorMpu9250Init();
}

/*******************************************************************************
* @fn          sensorMpu9250PowerOff
*
* @brief       This function turns off the power supply to MPU9250
*
* @return      none
*/
void sensorMpu9250PowerOff(void)
{
  extern PIN_Handle hGpioPin;

  // Make sure I2C interface is in a known state
  bspI2cSelect(BSP_I2C_INTERFACE_0,0);
  bspI2cDeselect();

  // Turn off power supply
  PIN_setOutputValue(hGpioPin,Board_MPU_POWER, Board_MPU_POWER_OFF);
}

And to verify this, I can use:

/*******************************************************************************
* @fn          sensorMpu9250PowerIsOn
*
* @brief       Return true if MPU power is on
*
* @return      none
*/
bool sensorMpu9250PowerIsOn(void)
{
 return PIN_getOutputValue(Board_MPU_POWER) == Board_MPU_POWER_ON;
}

Correct?

Instead in my sensortagapp.c I use this driver functions:

// Initialise the Motion Sensor driver
  sensorMpu9250Init();

In my readConvertAccel function I use:

Step 1:

// Enable acceleromter readout
sensorMpu9250Enable(mpuConfig | 0xFF);

Step 2:

// Read data from the Mpu9250 motion sensor
      ret = sensorMpu9250AccRead(&accelData.v.accel);

Step 3:

accel_X = sensorMpu9250AccelConvert(accelData.a[0]);
accel_Y = sensorMpu9250AccelConvert(accelData.a[1]);
accel_Z = sensorMpu9250AccelConvert(accelData.a[2]);

Final step:

send report to ZigBee Coordinator...

And repeat this step every (for example 1 hour) defined in:

#define DEFAULT_MOTION_REPORTING_INTERVAL   3600    // Motion Sensor Reporting Interval

I do not use sensorMpu9250PowerOff() and sensorMpu9250PowerOff() function...

thanks

ok, thank you...So I can use sensorMpu9250PowerOn() function before the read and convert operation and after use sensorMpu9250PowerOff() function...This for each cycle

thanks!...instead for hdc1000 there are no powerOn/powerOff functions...I use:

sensorHdc1000Init()
sensorHdc1000Start()
sensorHdc1000Read(uint16_t *rawTemp, uint16_t *rawHum)
sensorHdc1000Convert(uint16_t rawTemp, uint16_t rawHum, float *temp, float *hum)

but I do not see functions to TURN OFF or ON...

although for tmp007, BMP280 and for opt3001 would seem possible in terms of driver functionality...and as described:

/*******************************************************************************
 * @fn          sensorOpt3001Enable
 *
 * @brief       Turn the sensor on/off
 *
 * @return      none
 ******************************************************************************/

/*******************************************************************************
* @fn sensorTmp007Enable
*
* @brief Turn the sensor on/off
*
* @return none
******************************************************************************/

/**************************************************************************************************
 * @fn          sensorBmp280Enable
 *
 * @brief       Enable/disable measurements
 *
 * @param       enable - flag to turn the snesor on/off
 *
 * @return      none
 */

and have a different meaning on CC2650STK because unfortunately the schematic is that!

Ok, I was seeing just that!

last questions:

1. The sensors directly connected to VDD (not controllable) practically always in sleep-mode (if I'm not going to use them in my application)?
2. The MPU9250 sensor can TURN OFF/ON, but the SPH0641LU4H sensor, since it is not used right in the SensorTag application, will be turned off, right? I'm not going to write the status of the DIO_13 power pin to a high value (VDD), so it should already be turned off, I think...

thank you so much!

In fact in Board.c file (located in : \ti\tirtos_simplelink_2_11_01_09\packages\ti\boards\SensorTag\CC26XXST_0120):

PIN_Config BoardGpioInitTable[] = {
    Board_LED1       | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MAX,     /* LED initially off             */
    Board_LED2       | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MAX,     /* LED initially off             */
    Board_KEY_LEFT   | PIN_INPUT_EN | PIN_PULLUP | PIN_IRQ_BOTHEDGES | PIN_HYSTERESIS,        /* Button is active low          */
    Board_KEY_RIGHT  | PIN_INPUT_EN | PIN_PULLUP | PIN_IRQ_BOTHEDGES | PIN_HYSTERESIS,        /* Button is active low          */
    Board_RELAY      | PIN_INPUT_EN | PIN_PULLDOWN | PIN_IRQ_BOTHEDGES | PIN_HYSTERESIS,      /* Relay is active high          */
    Board_MPU_INT    | PIN_INPUT_EN | PIN_PULLDOWN | PIN_IRQ_NEGEDGE | PIN_HYSTERESIS,        /* MPU_INT is active low         */
    Board_TMP_RDY    | PIN_INPUT_EN | PIN_PULLUP | PIN_HYSTERESIS,                            /* TMP_RDY is active high        */
    Board_BUZZER     | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MAX,     /* Buzzer initially off          */
    Board_MPU_POWER  | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MAX,    /* MPU initially on              */
    Board_MIC_POWER  | PIN_GPIO_OUTPUT_EN | PIN_GPIO_LOW | PIN_PUSHPULL | PIN_DRVSTR_MIN,     /* MIC initially off             */
    Board_SPI_FLASH_CS | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MIN,  /* External flash chip select    */
    Board_SPI_DEVPK_CS | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MIN,  /* DevPack chip select           */
    Board_AUDIO_DI | PIN_INPUT_EN | PIN_PULLDOWN,                                             /* Audio DI                      */
    Board_AUDIODO | PIN_GPIO_OUTPUT_EN | PIN_GPIO_HIGH | PIN_PUSHPULL | PIN_DRVSTR_MIN,       /* Audio data out                */
    Board_DP2 | PIN_INPUT_EN | PIN_PULLDOWN,                                                  /* DevPack */
    Board_DP1 | PIN_INPUT_EN | PIN_PULLDOWN,                                                  /* DevPack */
    Board_DP0 | PIN_INPUT_EN | PIN_PULLDOWN,                                                  /* DevPack */
    Board_DP3 | PIN_INPUT_EN | PIN_PULLDOWN,                                                  /* DevPack */
    Board_DP4_UARTRX | PIN_INPUT_EN | PIN_PULLDOWN,                                           /* DevPack */
    Board_DP5_UARTTX | PIN_INPUT_EN | PIN_PULLDOWN,                                           /* Devpack */
    Board_DEVPK_ID | PIN_INPUT_EN | PIN_NOPULL,                                               /* Device pack ID - external PU  */

    PIN_TERMINATE
};

Right now I'm checking that the battery dies in 1 month with the original SensorTag fw (zstack_home_1_02_02a_44539) as stated in a previous post by @YiKai

In my case I will not use TMP007 (even because obsolete) but only HDC1000 and MPU9250 (accelerometer only, with REPORTING_INTERVAL = 3600).

thanks ;-)

I did the test and the battery (CR2032) died in 2 days with the original SensorTag application fw zstack_home_1_02_02a_44539).

with:

#define DEFAULT_ILLUM_REPORTING_INTERVAL 3   // 3 secs - Illumin (Lux) Sensor Reporting Interval

#define DEFAULT_TEMP_REPORTING_INTERVAL 10 // 10 secs - IR Sensor Reporting Interval

and LIGHTSENSOR_ENABLED disabled!

I only set:

staTsDstAddr.addrMode = zstack_AFAddrMode_SHORT;  // zstack_AFAddrMode_NONE;
staTsDstAddr.addr.shortAddr = 0; // coordinator short address = 0x0000
staTsDstAddr.endpoint = 0; // coordinator Destination End-Point = 8
staTsDstAddr.panID = 0;

to be able to send reports to the Coordinator.

Hi YiKai,

below the tests and consumption measures I have done:

TEST 0 (zstack_home_1_02_02a_44539, ORIGINAL FW):

Notes: MPU initially on in BoardGpioInitTable (Board.c file)

After the successful JOIN:

with MPU POWER ON. So about 3 mA continuous...that's why the battery in my previous test in fact died after about 2 days (assuming a capacity of 200 mAh aprox).

If instead MPU is initialized to OFF, after the successful JOIN:

And during the operation of read, convert and SEND_REPORT (tmp007) I measured approximately:

TEST 1 (my FW):

Notes: Including hdc1000 and MPU9250 sensors, with the following active features:

- HDC1000: reading and converting temperature and sending the report (every 1 hour) to ZC.

- MPU9250: 200 readings and conversions of X, Y and Z accel (duration of operation 1 second aprox) and sending MIN, MAX and AVG (every 1 hour) to ZC.

  Using the sensorMpu9250PowerOn(), sensorMpu9250PowerOff() and sensorMpu9250PowerIsOn() driver functions...to save energy (and MPU initially off in BoardGpioInitTable (Board.c file)).

The result is similar to those of the TEST 0:

during the operation of read, convert and SEND_REPORT (hdc1000) I measured approximately 0.0001 A.

And during the operation of reading, conversion (200 operation in loop) and sending the report (MIN, MAX and AVG values) I measured as max value about 0.0035 A.

With the oscilloscope I do not see values of the order of microAmpere...but I suppose that when the module is in sleep-mode, I have to consider the sum of all the contributions of the powered modules and in sleep mode (from datasheet), Correct?