CC1312R, TIDA-010024, 6LoWPAN Mesh: a few questions

Hi Alex,

1. How are you measuring power consumption?  Have you verified proper measurement of a CC1312R project which only enters standby/low-power mode?

2. Where do you gather that the debug_push_leaf should not send any keep-alive packets?  To achieve low power consumption, this mode disables routing capability, turns RX off when idle and runs on top of the TI 15.4-Stack sleep mode.  The default KEEP_ALIVE_TX_TIMEOUT_VALUE is 60 seconds if this corresponds with the packets you are observing with the sniffer, please share the logs if you think they could be of any use.

Regards,
Ryan

1. I measured it with a multimeter and EneryTrace. Also I found these posts that confirmed this as well:

https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/p/780195/2886673?tisearch=e2e-sitesearch&keymatch=debug_push_leaf#2886673

quote: "after it is connected and it goes to the state of sleeping with 0.04 mA,"

https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/p/912777/3382594?tisearch=e2e-sitesearch&keymatch=TIDA-010024#3382594

quote: "The debug_push_leaf appears to achieve around 40uA since I believe it is reaching standby power state"

But it is too much as for the battery powered device!

2.Parameter "xFH_KEEP_ALIVE" is locked with "x" in Predefined Symbols, so it should not send it.

I want to make the device sending my data every 3 minutes, so I changed the settings for the periodical clock that calls app_send() and I see that it runs every 3 minutes. So it works fine.

But also I see that the node device sends something else in between my packets. What does it do and why?

Even if the "keep alive" was still working as you say with period KEEP_ALIVE_TX_TIMEOUT_VALUE 60s, I'd see the periodical keep alive messages every 60 seconds, but the suspisuous transactions are not such periodical. I have only two ti15.4 devices and they talk each other when it is not supposed to be.

It is my ti15.4 node. What does it send with this weird periodical timing?

Ryan Brown1 said:

Where do you gather that the debug_push_leaf should not send any keep-alive packets? 

Here: e2e.ti.com/.../2886673

It appears you found great E2E references to ascertain more information about the TIDA-010024 LEAF behavior.  You can also further investigate the captured Data Frames or debug the CC1352R device to determine the purpose of the transmitted packets.  As Wonsoo explained, please understand that TI doesn't offer software debug or support with the example sources of reference TIDs and that CONTIKI is an open-source project not maintained by TI: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/p/780195/2886892#2886892 

Regards,
Ryan