enmo’s IoT.Over.Beacon technology enables new and valuable use cases for the TI SimpleLink™ Bluetooth Smart®/Multi-Standard SensorTag
So how do you use our IoT.Over.Beacon technology in your TI SensorTag firmware? You merely integrate our IoT.Over.Beacon library in your firmware.
You write your firmware as you do today, using the TI Code Composer Studio. When you want to output data from the SensorTag to a phone, you call our library. You give the data to output to our library and it automatically handles transmitting in IoT.Over.Beacon mode; it will do a call-back when data has been read by the phone. There is no charge for our library.
The content on the landing page you created in the enmo Platform is automatically displayed in the App, including a graph and table of the logged sensor data (if you’ve added these elements to your landing page). You can even push captured IoT data to an Endpoint and then populate content on your landing page from an Endpoint. Need to revise the content on your landing page? Then change it in our platform and iterate until you’re satisfied.
But what if you want to do a quick prototype, what if you don’t have time to develop your own full-up firmware?
Then you can use our reference firmwares. You can just program our reference firmwares into your TI SensorTag and immediately start developing your solution. Use our reference firmwares and our Development Apps and start capturing IoT data in minutes!
For step-by-step directions on how to use these reference firmwares, please see our TI SensorTag recipes.
The different reference firmwares we currently offer is shown in the table below (there is no charge for any of these).
IoT.Over.Beacon transmission initiated by user via button push
|SensorTag starts logging data when button is pushed (all 10 sensor values are stored once per second)
SensorTag stops logging data when button is pushed again – it then starts broadcasting in IoT.Over.Beacon mode
When phone comes into range, all stored data is read by phone or after 5-minutes has elapsed, whichever occurs first – after which, SensorTag returns to step 1
User must push button again to start data logging again
51 seconds of data can be stored by this reference firmware, after which data is overwritten
IoT.Over.Beacon transmission automatically occurs every 10-minues
|SensorTag starts logging data when button is pushed (all 10 sensor values are stored once every 5-minutes)
Every 10 minutes the TI SensorTag broadcasts in IoT.Over.Beacon mode
If phone is nearby, then:
If the phone does NOT read data within 1-minute of broadcasting start, then:
This data logging process continues until the user stops by pressing the TI SensorTag button again
Approximately 4-hours of data can be stored by this reference firmware, after which data is overwritten
IoT.Over.Beacon transmission occurs upon detection of movement by SensorTag accelerometer
|SensorTag starts logging data when SensorTag is moved for at least 10-seconds (all 10 sensor values are stored once per second)
Data logging continues until no movement is detected for 5-seconds. At that point, TI SensorTag broadcasts in IoT.Over.Beacon mode
The broadcasting continues until This data logging process continues until the logged data has been read by the phone or after 5-minutes has elapsed, whichever occurs first – after which, SensorTag returns back to step 1
|N/A||Source Code for Above Firmwares||enmo’s source code for the above firmwares will soon be available on GitHub. Engineers can use them as a starting point to develop their own firmware for the TI SensorTag. Contact us for updated availability.|
|EN-TI-ST-CCS-LIB-1||IoT.Over.Beacon library||IoT.Over.Beacon library for TI Code Composer Studio IDE.
Call this library from your firmware when you want to output data from a SensorTag to a phone.
Screen shots of an example landing page showing data captured by TI SensorTag are shown below. This landing page includes a form where the user can upload a short video.