I am designing custom BLE device protocol. My Device will be one of - Scales, Blood Pressure Monitor, Fitness Band.
The Protocol defines the collection procedure that my Android/iOS app (Collector) will use to collect sensor data from one of these devices.
We can assume that Collector is present 50% of the time and is scanning the air for a broadcasted Device to connect and collect data from it
My question is: What is an effective way of making device connectable, with battery power in mind?
My current approach:
Device is connectable, if
- (A) it has unsent measurements for some user,
- (B) user turned it on (by stepping on scales, pushing the button or whatever)
In case (B) Device broadcasts itself e.g. each 1 seconds and is available to be connected to Collector
In case (A) Device broadcasts itself e.g. each 5 seconds and is available to be connected to Collector
As soon as conditions (A)/(B) do not apply, device goes into sleeping mode - not broadcasting anything.
Is this effective approach by means of energy consumption? Or are there any better practices to accomplish "device visibility" ?
P.S. Could not find a better resource for asking that, but this question can be considered a programming question, as it is related to firmware programming
0 comments:
Post a Comment