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.
Tool/software:
sdk: SimpleLink CC13xx CC26xx SDK (6.41.00.17)
ti temperature sensor example: temp_sensor_LP_CC2652R7_tirtos7_ticlang
I tested that when connecting to the openthread network, the current consumed for the first connection (that is, there is no timeout record in the openthread network) is 6~7mA, and the current consumed for other connections is 2~3mA.
What I want to ask is, can this current consumption be reduced?
Thank you
Why are these two initialization functions needed? Do they need to be encrypted and decrypted when connecting to openthread? If they cause excessive power consumption, can we transmit directly without encryption?
When I deleted these two initialization functions, the program crashed, indicating that they are necessary functions?
Hi,
Moving forward, we recommend to use the latest delivery for TI OpenThread. See this post for reference: https://e2e.ti.com/support/wireless-connectivity/zigbee-thread-group/zigbee-and-thread/f/zigbee-thread-forum/1368600/certified-thread-v1-3-release-is-now-on-github
For the examples previously in the SDK, hopefully the below helps.
Please see if these posts help:
Regarding AESECB_init and SHA2_init, yes they are required, since Thread Protocol uses various crypto operations.
Regarding OtRtosApi_lock/unlock, yes it is necessary, please refer to: https://dev.ti.com/tirex/content/simplelink_cc13xx_cc26xx_sdk_6_41_00_17/docs/thread/html/thread/application-development.html#openthread-api-mutex
Thanks,
Toby
Thank you for your answer, but I don't know how to use the latest TI OpenThread, and I haven't found any tutorials or sample programs. I can't find the temperature sensor sample program I want in SimpleLink CC13xx CC26xx SDK (7.41.00.17). Can you help me? Thank you
Those examples are no longer supported moving forward, and we recommend using the cli or rcp examples. https://github.com/TexasInstruments/ot-ti/tree/main/examples/apps
You can consider porting to the github if you need a Thread-only application and want to define a custom application layer (as was done in 6.41 SDK).
How to use this github repo (including building) may be found through the documentation, where you can start navigating the docs here: https://github.com/TexasInstruments/ot-ti/blob/main/README.md
Regarding low power, regardless of SDK or github, here are some additional points:
Hi, Toby
Thanks for your patient answer.
Does this mean that I pull the code from ot-ti on github, write the code in it, build it with the script "./script/build" after writing the code, and then burn the resulting file into the development board? If so, where should I customize the application layer? I looked at the thread-migration-guide, but it doesn't seem to be what I want.
Regarding low power consumption, I made sure that I didn't use EnergyTrace connected to JTAG. The graph I measured is below.
When the current is low, it is in standby mode.
I have removed it from the launch board with the JTAG/LED jumper disconnected, and disabled the LED/UART/etc in SysConfig and the application in the code, but the power consumption when it is connected to openthread is still so high, reaching 7mA.
Thanks,
Gasen
Hi Gasen,
Does this mean that I pull the code from ot-ti on github, write the code in it, build it with the script "./script/build" after writing the code, and then burn the resulting file into the development board? If so, where should I customize the application layer? I looked at the thread-migration-guide, but it doesn't seem to be what I want.
You would need to create your own application layer.
It would look similar to this: https://github.com/TexasInstruments/ot-ti/blob/e7fbbcc60c25d1dec3ed4d02cff9acd866091ce7/examples/apps/cli/main.c#L97
But instead your own processing is added. You can still reference the temp_sensor source code as an example.
I have removed it from the launch board with the JTAG/LED jumper disconnected, and disabled the LED/UART/etc in SysConfig and the application in the code, but the power consumption when it is connected to openthread is still so high, reaching 7mA.
7mA sounds like RF is active. This is expected while the device is attempting to join the network. This requires use of the RF, where "Radio receive current" is 6.4mA and "Radio transmit current" at 0dBm is 7.3mA. This is expected.
However, after joining the network, it should go into a low power mode regularly, as you can see when the current is low. For sleepy devices, it would wake up every X sec to perform check-ins with its parent, and during that process the device current consumption of ~7mA is within expectations.
Thanks,
Toby