Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Simonr — Tue, 26 Oct 2021 06:10:43 GMT

Depending on whether you're using a SoftDevice or not in your application the device will either go to sleep using the sd_app_evt_wait, or just use __WFE(); to wait for a wake-up event. The sd_app_evt_wait() also essentially does the same, except that it prepares the SoftDevice for sleep mode first.

Best regards,

Simon

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Abhijith.Desai — Mon, 25 Oct 2021 13:40:06 GMT

I was just going through the thread examples in SDK we have.

1. nRF5_SDK_for_Thread_and_Zigbee\examples\thread\simple_coap_server\pca10100\blank\ses

2.nRF5_SDK_for_Thread_and_Zigbee\examples\thread\cli\mtd\usb\pca10100\blank\ses

3. nRF5_SDK_for_Thread_and_Zigbee\examples\thread\cli\ftd\usb\pca10100\blank\ses

I could see that the thread_sleep(); function which is called to go to sleep

The thing is i could not see the function which i expected the otPlatRadioSleep(ot_instance); how exactly does the device go to sleep and i dont think prepare sleep is no really relavent for us..?

Regards

Abhijith

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Simonr — Fri, 22 Oct 2021 10:11:30 GMT

Adding the master key you posted in the sniffer trace you have uploaded did not "uncover" any extra information I'm afraid. Can you upload a new sniffer trace where this key is used to decode the packets?

Most of our Thread example projects I.E. the Thread CLI example uses the following check to check if there are no pending tasks or log processes ongoing before calling the thread_sleep(); function which will put the device to sleep along with any peripherals before going to sleep using __WFE();

Best regards,

Simon

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Abhijith.Desai — Thu, 21 Oct 2021 11:31:15 GMT

I tried to print only in the states and its corresponding radio states, i can see that the radio goes to sleep only once and then it remains in rx once it completes the process

the below code snippet is used in all the states of that function i shared.

if(THSM_WirelessState_previous != THSM_WirelessState)
{
printf("\n\r State : %d ..",THSM_WirelessState);
THSM_WirelessState_previous = THSM_WirelessState;
}
pres_state1 = otPlatRadioGetState(COMWIRELESS_ot_instance);
if(prev_state1 != pres_state1)
{
printf("\n Radio status: %d", pres_state1);
prev_state1 = pres_state1;
}

Note : Gap in the log represents the wakeup of device every 60s. guess this is helpful.

Also it would be good if we have any example for managing the receive and sleep states of radio.

And the enums remains the same

Regards

Abhijtihdevzone.nordicsemi.com/.../Print-states-in-diffent-states.txt

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Abhijith.Desai — Thu, 21 Oct 2021 11:01:42 GMT

I tried to print the data to extract the master key,

#ifdef DEBUG
ConsolePrint("Thread version : %s\n", (uint32_t)otGetVersionString());
ConsolePrint("Network name : %s\n", (uint32_t)otThreadGetNetworkName(COMWIRELESS_ot_instance));
ConsolePrint("Channel : %d\n", otLinkGetChannel(COMWIRELESS_ot_instance));
ConsolePrint("PAN ID : 0x%04x\n", otLinkGetPanId(COMWIRELESS_ot_instance));
#endif
const otExtAddress *pExtAddress = otLinkGetExtendedAddress(COMWIRELESS_ot_instance);
#ifdef DEBUG
ConsolePrint("ExtendedAddress: ");
for (uint8_t u8Counter = 0; u8Counter < OT_EXT_ADDRESS_SIZE; u8Counter++)
{
ConsolePrint("%02x ", pExtAddress->m8[u8Counter]);
}
ConsolePrint("\n");
#endif
const otMasterKey *pMasterKey = otThreadGetMasterKey(COMWIRELESS_ot_instance);
#ifdef DEBUG
ConsolePrint("MasterKey : ");
for (uint8_t u8Counter = 0; u8Counter < OT_MASTER_KEY_SIZE; u8Counter++)
{
ConsolePrint("%02x ", pMasterKey->m8[u8Counter]);
}
ConsolePrint("\n");
#endif

And i get this as the master key.. and the same key i am using in wireshark to decode it..

OT_DEVICE_ROLE_CHILD
Thread version : OPENTHREAD/20191113-00534-gc6a258e3; NRF52833; Apr 5 2020 21:43:42
Network name : RDS110R_Thread
Channel : 12
PAN ID : 0x6329
ExtendedAddress: 72 15 1f 60 49 d0 69 be
MasterKey : ea 88 12 96 01 83 2e bc 05 dc 06 b6 8f e3 94 20

I guess you can add the same decryption key in your preferences -> IEEE 802.15.4 -> Decryption keys so that you can see the decoded data

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Simonr — Thu, 21 Oct 2021 07:41:30 GMT

It would be great if you are able to upload a sniffer log with decoded packets. In the debug log, it's a bit hard to follow when only the states are being printed. Showing where the application goes in if() sets should be helpful as well.

Best regards,

Simon

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Abhijith.Desai — Wed, 20 Oct 2021 12:27:39 GMT

Yes for sure we are not handling any sleep and receive states of radio manually right now. the THSM_IDLE and THSM_SLEEP states are just doing the application part and switching we are not trying to put radio to sleep since they say not required to put manually to sleep of invoke receive states of radio https://github.com/openthread/openthread/issues/1495.

Please correct me if i am wrong in understanding

Yes regarding the network key you are right we cannot add it once it is finished sniffing, will see the configuration part you suggested.

Regards

Abhijith

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Simonr — Wed, 20 Oct 2021 06:12:08 GMT

Yes, I can see

Have you followed section 3.1.1 in the nRF Sniffer for 802.15.4 user guide to configure the decryption keys before starting to capture. This is something that must be done before capturing data and won't be "unlocked" by adding the correct key on a finished filter.

Regarding the log and THSM sleep. Yes I can see that the debug log is putting the THSM to sleep, but it does not seem to set the radio into a sleeping state. I'm not able to see what exactly your THSM_sleep_e and THSM_idle_e events are doing from your code snippets. What functions are they calling that puts the nRF into sleep exactly?

Best regards,

Simon

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Abhijith.Desai — Tue, 19 Oct 2021 11:04:23 GMT

Yes i could see in the debugger window that THSM will go to sleep and then to idle(you can get that information from the debug log i shared).

The state machine goes to sleep state but the radio state goes to sleep only once after pairing to network(that is what is my concern).

SOrry for wrong information about OMWIRELESS_RadioSleep() we are calling it but the entire part inside that function is commented (after knowing that it is not required to manually switch the sleep and receive states of radio)

ea88129601832ebc05dc06b68fe39420 or 4f42ca5cb60755cf61667e1a6beded7b or 47b314550ca8d0ef3f5842c038dd6b60 should be the key to open the sniffer data..

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Simonr — Tue, 19 Oct 2021 10:49:22 GMT

The logging here seems a bit off to me, since the one and only time the Radio status reports back 1 (radio sleep) is after a PREPARE_WAKEUP call from the THSM? After that it seems like the state machine goes to sleep and wakes up numerous times without interfacing with the radio peripheral at all. During debugging, do you have any indication that the THSM_SLEEP_e event actually puts the radio to sleep? What does the COMWIRELESS_RadioSleep(); function do exactly, and are you sure that it is getting called?

If you add some more prints (maybe inside the if settings, we should be able to see where the application goes in each state. We're not able to see much from the sniffer log unfortunately. Are you using another masterkey/IPv6 prefix than what is default? That would make Wireshark unable to decode the packets.

Best regards,

Simon

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Abhijith.Desai — Tue, 19 Oct 2021 08:50:39 GMT

I tried to print the values over the debug terminal the things i can see right now is once the communication is completed it stays in radio receive state.Please find the logs and also the enums and also find the sniffer data for pairing and then trying to communicate again devzone.nordicsemi.com/.../Sniff-power.pcapng devzone.nordicsemi.com/.../Print-states.txt.

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Abhijith.Desai — Mon, 18 Oct 2021 13:53:07 GMT

Thanks for your reply on this.

I have attached the RF state machine function haw we are handling it.. maybe ill be sharing the sniffer data soondevzone.nordicsemi.com/.../RF-State-machine.txt

RE: Open thread : Rx is always ON after communication is completed (Doesnt goes to sleep) - power consumption is high.

Simonr — Fri, 15 Oct 2021 12:09:52 GMT

I'm sorry, but I'm not able to see what the issue is by just your description of the issue. I would think that the device is still expecting some data after the joining/pairing is completed perhaps.

Can you share a snippet of your code, output of your debug log, and potentially a sniffer trace of what's going on over the air so we can get a better look at what's going on?

Best regards,

Simon