It is definitely possible to modify the SensorTag 2 / CC2650 platform so that its behavior matches your use case. I - for example, a special firmware is currently being used, which does preliminary processing of sensor readings to the SensorTag and sends the data directly in the advertising message unlimitedly (of course, you need to adjust the intervals and payload in order to get decent battery life ).
I assume you have CCS and sources (SensorTagApp and SensorTagStack) on hand?
I recommend first flashing the current SensorTagStack first, if not already done (although I haven't been to 2.2 yet).
In the SensorTagApp project in the Application section, you will find SensorTag.c . There you should change:
#define DEFAULT_DISCOVERABLE_MODE GAP_ADTYPE_FLAGS_LIMITED
to
#define DEFAULT_DISCOVERABLE_MODE GAP_ADTYPE_FLAGS_GENERAL
This is a common tip and may already do the trick.
In my firmware, I also changed (in SensorTag.c , in the SensorTag_init function):
uint16_t advertOffTime = 0;
to
uint16_t advertOffTime = 1;
Please try these changes and return to me. If this was not enough, I will make a more thorough comparison of the stock firmware and my own firmware. I also recommend a more specific ti bluetooth low energy forum .
source share