Quantcast
Viewing all articles
Browse latest Browse all 63778

Forum Post: Your opinion about CapTIvate use case :)

Hi guys! Let's see what is your opinion about this use case :) At the beginning, I thought "yes, this can be easily done with CapTIvate" but now I have started and I am not sure about the best way to proceed. Imagine I place my CapTIvate proximity just underneath a chair. I mean, attached to the bottom of it, obviously not in the place where the user sits on but the "bottom side" of it :) It is easy to detect when the user seats. However, I think it is not as easy to discern when he / she leaves because of a simple reason. Since the user may be sitting for several hours, the "sensor time-out" parameter will fire because "the sensor time-out threshold specifies a maximum amount of time a sensor may be in a touch or proximity state before it is reset". So, the sensor will be reset. This provokes the proximity to stop detecting the user because of reset, I have tested this in the code. This could be understood as the user has left, even if he / she has not! Next, if the user effectively wakes up, there will be a "negative touch event". One could think about using this latter as an indicator of user leaving. But this approach would, in turn, prevent me of detecting users sitting less than the "sensor time-out" value. Ok, so let's hear your opinions! Obviously I want to keep the low-power feature of the whole system :) Maybe reducing the "active mode scan rate"? :) I do not need immediate response from the sensor :) Have a really nice weekend! I look forward to your knowledge!

Viewing all articles
Browse latest Browse all 63778

Trending Articles