This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1312R: TI15.4 send message to collector immediately on waking up

Part Number: CC1312R
Other Parts Discussed in Thread: TIDA-01477, TPL5111

Hello,

as part of a 15.4 network, I am looking to create a sensor that behaves similarly to: https://www.ti.com/tool/TIDA-01477

That is, the CC1312 will be powered off for 30 seconds or so, then powered on only for as long as it takes to send data to the collector, then powered off again.

On first associating to the collector, I can deal with a bit longer awake time, but subsequently, I am looking for the sensor to power up and send data as quickly as possible to the collector.

Right now, with example sensor code, the sensor rejoins, and eventually sends data, taking seconds (even if reporting is ~500ms).

I'm looking for pointers to shorten that time to a minimum.

Tx

  • Hi

    It is not clear to me which SW you are using. Are you using the sensor example for the CC1312R from our SDK (Which one?) or are you using the example code from TIDA-01477, ported to CC1312R?

    Siri

  • Hi Siri, sorry about the confusion.

    I am using the SDK (4.20) TI15.4 sensor example as a starting point for firmware. 

    I used the temp/humidity design as an example to state that the sensor will be powered off between readings .

    Ideally, after having saved collector / association info to NVS, the sensor would power on and send a message within milliseconds, foregoing any association overhead or having to wait for polling/reporting timers to expire.

  • Hi,

    When you say the sensor should "power off", what kind of power consumption are you looking for? (The behavior you are describing sounds very simple to implement if you keep the sensor in standby, but a lot more difficult if you send it to shutdown.)

  • TIDA-01477 uses a TPL5111 timer along with a load switch to power down sensors & CC13xx.

    So the CC device doesn't have to handle timers at all. It will get periodically powered on by external circuitry and should at that time send a message to the collector as quickly as possible. After completing its task, it can inform the timer IC that it is done through GPIO, at which point the timer will shut down downstream devices once more.

    As you can see, I am not talking about power saving modes, given this hardware configuration.

  • Hi,

    I think if you want the most efficient processing from the CC device you should be working with the power modes there as well. 

    The TI 15.4-Stack is not per default written to deal with sensors powering on and off. If you use the default TI 15.4-Stack example, each time you repower the sensors they will start up in orphan mode and start the process of reassociating with the collector. This will cost you more time than it sounds like you want to spend. 

    You can re-write the main loop of your application and configure the parameters of the TI 15.-4Stack to fit your use-case. Alternatively you can discard the TI 15.4-Stack approach and make a simple proprietary protocol where the device just wakes up, sends a beacon, waits for an ack etc.

  • Hi Marie,

    cool thanks. I will see about making changes to sensor code.