Hi,
By glancing over my options in Sensor Controller Studio, I see a couple different ways of scheduling my task (could be execution code or event code). My requirements are that the power consumption is held at a minimum and the period between code execution can be changed dynamically, ideally between 5 minutes and 30 minutes.
1* RTC based execution scheduling
This mode warns me, Note that the Sensor Controller will wake up at every RTC tick, and gives tips on how to keep current consumption low. I know that the tickPeriod can be set after project is merged with CPU project in CCS, and maybe I can share the number of ticks between SCS code and CPU code using Multi-buffered Output Data Exchange.
2* Timer event trigger
In the help file I read: Enabling this resource will cause the AUX domain to run at 32 kHz (instead of having no clock) when the Sensor Controller and System CPU are in standby mode. The resulting AUX domain clock switching increases slightly the time to enter and exit standby mode for both Sensor Controller and System CPU. To me this sounds like more power consumption while while SC and CPU is in standby mode. The mant and #exp values maybe I can change directly in CPU code since it uses a Timer peripheral? All though I don't think that adds any benefits to me.
To me it is not clear which way is better for lower power consumption.
