Tuesday, January 23, 2018

Creating and triggering events


Events and triggers are functionalities implemented starting with 10.0.0.0 version of the blessTags application – but, only in the full version of this application.
Events are things that happen within your blessTags app environment at which you might want to act in a specific way. Up to now, these events might be things like a specific value of a sensor (embedded on a SensorTag) that meet a condition or a series of conditions.
Currently, the blessTags application supports events from the following providers: all the sensors information that is acquired and displayed, from a SensorTag, on the user interface.

blessTags user interface

Each active numeric data source, presented in black color on the blessTags user interface, can be a source of events. In the figure presented above, only the information from the pressure sensor cannot be used as a source of events - this only happens because the application user has not activated one of the data reading mechanisms (reading or notifying) from this sensor positioned in the SensorTag. For example, the z-channel acceleration or the humidity or the ambient temperature or, why not, the SensorTag’s battery power level, etc. can be considered as sources of events. 
The events can be generated by the instantaneous value, the mean value or the variance value of the data flow from a specific sensor.
To create and trigger events, you must double-click on a specific value associated with a specific sensor. As a result, the following window will appear.

Setting events and specific triggers

An event will be generated if the desired value (instantaneous, mean or the variance) is lower or higher than a threshold value or is inside or outside of a specific range of values. 
If one of the specific conditions is meet a trigger will be generated. As a result, the user will receive a visual or an audible alert or a data saving process will be generated (previously configured by the user: specifying the saving channels and a data window length). You can also choose any combination of these triggers.
If the trigger was a data saving process, from the moment when an event was generated, in the end, the user must additionally save all these data series manually to a file. 
The user has the possibilities to display and delete all the triggering events globally. To do these the user must go into developer mode from where he/she has these possibilities using two specific buttons – see the figure from below.

Developer user inter