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.
Part Number: CC1310
Tool/software: Code Composer Studio
I want to minimize the power consumption when the sensor is not connected to a network. (currently 2mA using the TIDA 00489 design)
I want the sensor to search every 15 mins for 3 times, if no network is found, I want to delete the NV memory. For the latter one I use Ssf_clearAllNVItems();
Thanks for your help
If my post answers your question, please click on "This Resolved my issue" button to benefit others who have the same issue.
Example to combine rfWakeOnRadioRx into rfWakeOnRadioTx to do TX/RX in the same WOR project.
How to create micro second delay on CC2652R
How to check APS ack in TI Z-Stack
How to detect button hold in CC26x2, CC13x0, CC13x2 SDK.
660 Zigbee devices in the same Zigbee network!
How to setup Mosquitto on Raspberry Pi and make Contiki/Contiki-NG cc26xx-web-demo do mqtt publish to it.
How to connect Contiki-NG cc26xx-web-demo to IBM Watson IoT Platform
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to YiKai Chen:
we used the exact same design and send it to a manufacturer. I would suspect that it has something to do with the code.
Maybe I should check the behavior of more of the modules and figure out if there are leakage currents. Any idea where to look exactly? Have you tried the Sensor/Collector stack code and measured the consumption with this module?
In reply to Slev1n:
Well, porting itself is not the problem, this worked pretty good. All the basic functionality I want with the TIDA Board works with the Sensor/collector example fine after some minor changes. But I am wondering why the power consumption is so high when the sensor is not connected to a network. When it has found a host and connected itsself, the power drops to around 80µA, here the sensor is active all the time I guess and counting the movements. When it is passing the data to the collector the current increases of course. Since the measurement equipment was not the best choice for this purpose, I will make these consumptions measurements again, but I want to see, if my proposed improvements can lower the consumption. Thus I need some help to get them working. And I would be pleased if others could share their consumption to have a better comparability.
In reply to Hector_r:
thank you for the elaborate answer.
I am not sure what mode I use, I checked the "collector -> config.h" file. I guess it is "non-beacon" mode because "config_fh_enable" = false and CONFIG_MAC_BEACON_ORDER = 15. And I found in the sensor settings, that CONFIG_RX_ON_IDLE = false. Well, that seems to be pretty low power consuming, or is the "beacon" mode less power consuming?
Thank you a lot for the explanation regarding: CONFIG_ORPHAN_BACKOFF_INTERVAL and CONFIG_SCAN_BACKOFF_INTERVAL (interestingly, both are set to 5s in sensor-> config.h) as well as pointing out the "scanCnfCb". Is there a more elaborate explanation of the different things being set in the config.h files and the functions used? Because sometimes the comments are enough, but often I do not exactly know what is meant.
Regarding the state the sensor was in, I think it wasn't an orphan when I measured the 2mA but I can't remember exactly though. Hence, I will try to make more accurate measurements with detailed comments and different scenarios. The 2mA would be a big issue, because we would insert the battery, before sending our final device to the customer and this can take some time and then the battery is already empty before it reaches the destination. Another problem is the fact, that if it connects to any network before reaching the final destination, it would not connect to the final network, thus if it doesnt find its previous network, I will reset it to factory new after some time, allowing it to connect to a new one.
Since I am most likely in "non-beacon" mode, I am using the active or orphan scans...ok.
I will now try to make more precise current consumption measurements using high precision resistor, ultra low noise voltage amplifier and a daq-device and will report back.
I do now have access to a pretty good source meter, allowing me to check the idle current. Currently, I cannot log the peaks, but maybe I have the time in the future to write a software logging data from the device.
In all three states, I see quick rises to 100-250µA (3-5 times per 10s) but most of the time it stays at 73µA.
I reduced the transmit power of the sensor and changed the intervals for reporting, config, polling etc. and changed the scan duration to 2s. Although I can not measure the peaks quantitatively correct I can detect them qualitatively, demonstrating, that the number of peaks per time interval decreased massively, like expected.
So, changing the intervals and lowering the scan time as well as the transmit power are working. However, 73µA idle and the 100-250µA fluctuations are not acceptable for our application. When I flash the TIDA Firmware (with my minor changes) I have 7µA consumption still higher than 2.65µA but much more acceptable.
If you tell me, that with this code example, a single digit µA is not possible during idle, I will try implementing the TIDA-01476
UPDATE: I just noticed, that in feature.h the mode is set to: #define FEATURE_ALL_MODES So I guess, all modes are basically allowed but due to other settings, only "non-beacon" is used?! Or how can I interpret "Feature all modes"?
UPDATE 7th November:
Flashing the TIDA board with the TIDA 00849 Firmware and changing the code to count movements (thus it is always active) gives me an idle-current of approx. 10µA. Hence, it has something to do with the code, not any hardware current leakage or whatsoever. The TIDA-01476 advertises a low current consumption while active like the TIDA-00489 at around 2.65µA. I changed the TIDA-01476 firmware from movement detection to movement counting and I kept the collector code as before. I still have 73µA idle current and I dont think it is because the sensor is always active.
I am at a lost right here, any assumptions and suggestions are more than welcome.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.