UG164: ThunderBoard-React
(RD-0057-0201) User's Guide
The ThunderBoard-React is a cloud-connected, Bluetooth®
Smart-enabled, sensor-driven platform that enables customers to
demo, evaluate, and develop their own unique applications.
It leverages Silicon Labs’ BGM111 Bluetooth Smart module as a wireless system-on-achip (SoC) to collect to various sensor data and deliver it to the cloud through Bluetooth
Low Energy (BLE)-enabled iOS/Android mobile apps. This document provides an overview of the kit including hardware, software application, cloud platform and mobile app.
It also contains instructions and guidelines to evaluate the simplicity of adding Bluetooth to your project to connect to the cloud.
silabs.com | Smart. Connected. Energy-friendly.
KEY POINTS
• Low-cost, Bluetooth Smart solution that
collects and delivers data to the cloud
• Hardware includes BGM111 Bluetooth
Smart module linked to sensor inputs
• ThunderBoard React connects to BLEenabled iOS/Android mobile apps
• Apps connect to a cloud-based multi-client,
real-time synchronization database
Rev. 0.2
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Introduction
1. Introduction
ThunderBoard-React is a low-cost, BLE solution that collects and delivers data to the cloud.
Figure 1.1. System Application Diagram
The ThunderBoard-React is a great demonstration and evaluation tool to easily add BLE connectivity to a sensor or actuator application. The mobile app seamlessly communicates between the ThunderBoard and the cloud database to visualize sensor data collected
or control the LED states on the ThunderBoard-React hardware. Individual components of the ThunderBoard-React can be easily integrated and modified in order to add BLE-to-cloud connectivity for a user’s particular application.
All instructions, collateral and source files for this solution can be found here: http://www.silabs.com/thunderboardreact.
Figure 1.2. ThunderBoard-React
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 1
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Quick Start
2. Quick Start
This section describes how to quickly start using the ThunderBoard-React with its mobile apps and cloud database. For detailed instructions, refer to Section 4. Operation.
1. Download the mobile app
a. Links to the iOS and Android mobile app can be found here: http://www.silabs.com/thunderboardreact
2. Supply power to the Thunderboard-React
a. Insert the CR2032 battery into the battery holder ensuring the (+) are properly oriented.
b. Set SW3 switch where its toggle is closest to Vbat.
3. Connect the ThunderBoard-React to the mobile app.
a. Launch the mobile app on the phone, ensuring the phone’s Bluetooth radio is enabled.
b. On the ThunderBoard-React, press the SW-0 button. The blue LED (LED-B) should blink to indicate it is sending a BLE beacon.
c. Locate the device on the app which should display “ThunderBoard-React #nnnnn”.
d. Click on the device in the mobile app to connect to it.
e. A successful pair is known if the mobile app displays available demos. On the hardware, the blue LED should stop flashing
and the green LED should flash once.
4. Select the demo.
a. For this quick start, select the I/O demo.
b. Once the demo is activated, it will take you to the demonstration screen.
5. Use the demo.
a. Press the SW-0 and SW-1 on the ThunderBoard-React and witness on the mobile app its visual response along the top area
of the phone screen.
b. On the mobile app itself, press the two buttons in the middle and witness on the ThunderBoard-React that its blue LED (LEDB) and green LED (LED-G) are statically illuminated.
c. Pressing both buttons again on the mobile app to extinguish the LEDs.
6. Stream to the Cloud.
a. Ensure the mobile phone has the ability to connect to the internet either through Wi-Fi or a cellular connection for this portion
of the demonstration.
b. While in the I/O demo, along the top portion of the screen, drag over the toggle switch to activate the cloud streaming mode.
c. Data is now being sent from ThunderBoard-React to the mobile app which is then streaming the data into the internet to a
cloud database.
d. To see the live stream select the share icon (up arrow in an open box) next to the toggle switch on the mobile app and then
select the phone’s mobile browser. This will launch the browser and place the mobile app in the background still streaming
data to the cloud.
e. In the browser witness the switch and LED data is being shown.
f. While still connected, press on the buttons on the ThunderBoard-React and witness the resultant change in states on the
cloud.
7. Share the Cloud stream session.
a. While streaming, the mobile app can send an email using the mobile phone’s email client.
b. Send an email to another device client (such as a laptop or another mobile phone with a web browser).
c. Launch off the emailed link and witness the simultaneous cloud session being displayed on this device while the original
phone is connected to the ThunderBoard-React. The cloud platform supports provides real-time data synchronization across
multiple clients.
8. End the cloud stream.
a. Method 1: return to the mobile app and move the upper toggle switch to disable the cloud stream session.
b. Method 2: back out of the I/O demonstration until reaching the looking for devices page on the mobile app.
c. Method 3: power off the ThunderBoard-React by moving the SW3 toggle switch to Vext.
9. Turn off the device:
a. On the ThunderBoard-React, move SW3 toggle switch to where it is nearest Vext.
10. Review the cloud session:
a. If emailed, this provided link will display the resultant summary of the cloud streaming session.
b. This link will be available for 30 days.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 2
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Overview
3. Overview
The ThunderBoard-React solution provides:
• A low-cost, Bluetooth-enabled sensor platform
• Open-source, native mobile apps
• A cloud database that supports multiple clients
This solution allows customers to demo, evaluate, and develop their own unique applications.
3.1 Part Number
The part number convention is RD-XXX-YYYY, where:
RD Reference Design
XXXX Reference Design Number
YYYY Reference Design Component
This document will use the reference design number (RD-XXXX) when describing the complete design, and the reference design component (RD-XXXX-YYYY) when describing a specific component.
The following table provides a description and PCB marking for each part number.
Note: Some cases lack sufficient space on the PCB, and an internal “IST” marking appears on the PCB instead of the “RD” part number.
Table 3.1. Part Numbers and Description
Part Number
PCB Marking
Description
RD-0057-0201
N/A
ThunderBoard-React Bluetooth Sensor Reference Design Kit with BGM111, Si7021,
Si7201 and Si1133.
RD-0057-0101
IST-A0057 Rev 2.0
ThunderBoard-React Bluetooth Sensor Evaluation Board with BGM111, Si7021,
Si7201 and Si1133.
3.2 Reference Design Kit
Kit Contents:
• ThunderBoard-React hardware reference design
• Standex / Meder M13 magnet enclosed in plastics with screw holes
• Quick start card to obtain the latest reference design collateral
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 3
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Overview
3.3 Hardware Features
The ThunderBoard React hardware platform contains the following features:
• Silicon Labs Blue Gecko BGM111 Bluetooth® Smart Module
• 32-bit ARM® Cortex-M4 CPU
• 256 KB Flash
• 32 KB RAM
• TX power: up to +8 dBm
• RX sensitivity down to -93 dBm
• Silicon Labs Si7021 relative humidity and temperature sensor
• Temperature sensor accuracy: ±0.4 oC
• Humidity sensor accuracy: ±3% RH
• I2C interface
• Silicon Labs Si1133 ambient light and UV sensor
• Ambient light sensor range: 1 to 128 kilo lux
• UV index sensor range: 1 to 11
• I2C interface
• Silicon Labs Si7201 omni-polar, hall-effect sensor
• Operating point: 30 Gauss max
• Release point: 10 Gauss min
• Push-pull output
• Invensense MPU-6500 6-axis motion sensor
• 3-axis accelerometer
• 3-axis gyroscope
• I2C interface
• Two momentary buttons (SW-0, SW-1)
• Blue and green LEDs (LED-B, LED-G)
• 10-pin 0.050”, 1.27 mm mini-simplicity debug connector
• PCB footprint for up to 8Mb external flash device
• Break-out pin pads to connect to BGM111 GPIOs
• CR2032 coin cell battery slot
Figure 3.1. ThunderBoard-React Hardware Diagram
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 4
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Overview
3.4 ThunderBoard-React Firmware Features
The ThunderBoard-React firmware application contains the following features:
• Pre-compiled and source application firmware
• Sleep mode for battery savings
• Beacon notification to interface to an enable mobile app
• Bluetooth-compatible GATT service profiles
3.5 ThunderBoard Mobile App Features
The Silicon Labs ThunderBoard mobile apps contains the following features:
• Bluetooth-compatible connectivity support
• Beacon notification support
• iOS/Android pre-compiled and source application code found on GitHub
• iOS app uses native Swift code
• Android app uses native java code
3.6 ThunderCloud Software Features
The ThunderBoard-React’s web client (thundercloud.silabs.com) contains the following features:
• Leverages Firebase, a scalable cloud solution that can rapidly deploy:
• Real-time synchronization database capable of supporting multiple clients
• User authentication security
• Web hosting
• ThunderCloud uses ReactJS framework for its overall architecture:
• Leverages npm as a package manager
• Alt.js for the flux implementation
• React Router for routing within the app
• D3.js For data-driven charts
• LESS for CSS pre-processing
• Gulp for building and minifying code
• These tools and architecture allows for:
• Simultaneous connection of 1000’s of ThunderBoard-React devices via mobile app
• Multiple device clients synchronously connected to a single cloud session
• Persistence storage of past cloud sessions (up to 30 days).
• Source code can be obtained at http://www.GitHub.com/SiliconLabs.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 5
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4. Operation
This section describes the various operational modes of the ThunderBoard-React hardware, the Silicon Labs ThunderBoard mobile
apps, the thundercloud database and how each interact to create a low-cost, BLE-enabled, cloud-connected solution. For this section,
the screen captures will be using the iOS mobile app even though the instructions apply to both mobile apps. For features where the
Android mobile app operates differently than iOS, these instructions will also be provided.
Open App
Beacon Notification
BLUETOOTH
DISABLED
NO DEVICE
FOUND
DEVICE(S)
FOUND
Prompts
prompts to
enable BT
prompts to
turn on device
Beacon info
& connect
CHOOSE
DEMO
shows
available
demos
DEMO
shows current
data & cloud
stream option
SEND LINK
DEVICE
SETTINGS
APP
SETTINGS
bluetooth
settings
Personalize &
preferences
CLOUD
SYNC
choose SMS
or Email
SEND SMS/
EMAIL
link to cloud,
link to more
info
option to send
link or view
now
Opens
default
browser
SEND SMS/
EMAIL
link to cloud,
link to more
info
VIEW
CLOUD
SYNC
data over time
and summary
MORE INFO
Product
collateral,
code
Figure 4.1. Mobile App and Cloud Flow Diagram
4.1 Download the Mobile Apps
Specific links to the iOS AppStore and Google Play Store to obtain the free Silicon Labs ThunderBoard mobile apps can be found here:
http://www.silabs.com/thunderboard-react
4.2 Supply Power to the Thunderboard-React
If present, remove the battery tab from the battery holder. Set SW3 switch where its toggle is closest to Vbat to supply power to the
device. Setting the toggle closest Vext will power-down the device. At power up, the device will enter into a self-test mode. If it discovers an error, it will emit alternating green and blue LEDs. For more information on the self-test, refer to the firmware section. If changing
CR2032 batteries, ensure the positive side of the battery (+) is aligned to the metal battery tab’s plus marking (+).
Figure 4.2. ThunderBoard-React with Battery Tab
The hardware can additionally be powered via the mini-simplicity debug connector (J3). To do this ensure the SW3 switch is set to
where its toggle is closest to Vext.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 6
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.3 Connect ThunderBoard-React to the Mobile App
Once the mobile app is successfully installed on the phone and the hardware is powered, the following sub-sections will describe how
to successfully pair them.
4.3.1 Launch the Mobile App
Upon selecting the Silicon Labs ThunderBoard icon on an iOS/Android mobile phone, the app will launch with this introduction screen
for a few seconds and then will look for nearby ThunderBoard-React devices:
Figure 4.3. Mobile App Launch Screen
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 7
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.3.2 Enable Beacon Notification
On the ThunderBoard-React, press either the SW-0 or SW-1 button. The LED-B will blink to indicate it is sending a BLE beacon. For
power-savings, the beacon will only be enabled for 30 seconds. If necessary, to re-activate the BLE beacon, re-press one of the buttons.
Figure 4.4. LEDs and Buttons on ThunderBoard-React
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 8
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.3.3 Looking for Devices
After the launch screen completes, the app will display various informal messages as it is looking for a ThunderBoard device. Valid
screens should either have the message “Looking for Devices” or it should display the found device(s).
Figure 4.5. Valid Screens While the App Looks for Device(s)
Once a device is found, it can be selected as described in the next section. The found device will display its unique name and measured received signal level from the perspective of the mobile phone.
If “Bluetooth is Disabled” is displayed, go to the mobile phone’s settings and ensure its airplane mode is not enabled and the Bluetooth
radio is enabled. If “No Devices Found” is displayed, ensure the ThunderBoard-React is in nearby range, is powered and its Blue LED
is flashing.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 9
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
Figure 4.6. Error Messages While Looking for Device(s)
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 10
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.3.4 Selecting From Found Device(s)
After ThunderBoard-React device(s) have been found, tap on the desired device to connect to it.
Figure 4.7. Connecting to a Device
A successful connection is known if the mobile app displays available demos as well as the device’s information is shown along the
bottom border. On the hardware, the blue LED should stop flashing and the green LED should flash once.
Figure 4.8. App Screen after Successful Connection
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 11
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
From this screen along the bottom border, the device’s unique name will be displayed as well as its estimated battery health. Clicking
the back arrow from this screen, will disconnect (un-pair) the device from the mobile app.
To enable opening the app using the beacon notification, click on the gear icon for global settings as described in the user app settings
section.
4.4 User App Settings
While either in the looking for devices or in the choose demo screens, one can configure user defined settings.
Figure 4.9. User App Settings
While in this screen, the user can specify their contact information that will then be displayed when sharing links. The user can also
specified desired measurement and temperature units. The user can also enable beacon notifications which will alert the app when a
beaconing ThunderBoard-React is within the radio’s signal range and available for connection.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 12
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.5 Configuring Beacon Notifications
Within the User App Settings, a user can enable/disable beacon notifications. When these notifications are enabled, a known ThunderBoard-React can be allowed to notify the mobile app of its nearby presence and then allow it to open the app directly into the choose
demo screen. To allow or remove a ThunderBoard-React, click on ALLOW or REMOVE for that particular device. Note, to allow a device it must have already been connected to the app.
Figure 4.10. Device Beacon Notification Settings
For iOS phones: In iOS, beacon notifications are used to alert a mobile phone it is within a nearby beacon. As a result, the phone can
sometimes inhibit notifications so as to avoid flooding the mobile phone with continual notifications as it resides on a boundary of a
beacon’s radio signal range. The best method to reliably demonstrate this feature is to have the allowed ThunderBoard-React device
powered off, power it up and then press the SW0 or SW1 button. Within seconds the beacon should trigger a notification and the dialog
box will allow a user to open the mobile app.
For Android phones: with OS version 4.4, beacon notifications with this demonstration only work if the mobile app is launched and is at
least residing in the phone’s background.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 13
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.6 Select a Demo
Once the mobile app is connected (paired) to a Thunderboard-React, it will display the following available demos:
• Motion: Uses the accelerometer, gyroscope and hall-effect sensors
• Environment: Uses the temperature, relative humidity, ambient and UV sensors
• I/O: Uses the two momentary push buttons and two LEDs
The next sub-sections will describe each demo and how to operate them. The following sections will then describe how to stream each
of these demos to the cloud where they can be viewed and shared by multiple device clients. Both live and completed streamed demo
sessions can be viewed by multiple clients.
To select a specific demo, click on it.
Figure 4.11. Selected Demo Loading Screen
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 14
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.6.1 Motion Demo
Figure 4.12. Motion Demo Screen
The motion demo can demonstrate the following:
• 3-axis orientation, numerically and visually via a 3D rendered model
• 3-axis acceleration, numerically
• Speed and distance via the hall-effect sensor’s output displayed as a CSC service
For orientation and acceleration, the ThunderBoard-React’s axes can be calibrated. To do so, rest the ThunderBoard-React in an upright position (top of the device facing up). While leaving the device untouched and not moving, click on “calibrate”. The mobile app will
perform a calibration calculation for a few seconds, displaying a pop-up message while it is doing so until it completes. Once completed, move the ThunderBoard-React and notice the device is now aligned to the 3D model on the mobile app screen. The specifics of
the device-to-app refresh rate as well as the angle values shown in the app can be found in the firmware section.
For speed and distance, the hall-effect sensor is to be paired with a magnet. The firmware is designed to display this sensor as a CSC
service, which means it will assume every nearby magnetic sensor contact point will be counted as a full wheel revolution. From each
revolution, it will determine a speed and distance based on a specific wheel diameter commonly found in pinewood derby races. For
more information on refresh rates and speed values, please refer to the firmware section.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 15
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.6.2 Environment Demo
Figure 4.13. Environment Demo Screen
This demonstration uses the Si1133 and Si7021 to display the following environment sensors (with range).
Table 4.1. Environment Demo Measurements
Sensor
Type
Min
Max
Unit
Si1133
Ambient Light
1
99,999
lux
UV Index
1
11
─
Temperature1
–40
85
C
Relative Humidity
0
100
%
Si7021
Note:
1. Farenheit equivalents can also be displayed via the user app setting.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 16
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.6.3 I/O Demo
Figure 4.14. I/O Demo Screen
For a simple demonstration, the mobile app can show how a button press on the device can result in a change on the mobile app
screen, and vice versa. Upon pressing either SW-0 or SW-1, the mobile app will animate the two circle icons along the top area of the
demo screen. Upon pressing either the left or right icons in the lower section of the screen the blue and green LEDs on ThunderBoardReact can be statically illuminated.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 17
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.7 Stream to the Cloud
While connected to a ThunderBoard-React, the mobile app can simultaneously stream the live demo session to the cloud where multiple device clients can view its live stream. This same link will also display the final results of that stream and will remain available for
later viewing for up to 30 days. All available demos can be streamed to the cloud.
While in a demo to stream it to the cloud, move the toggle stream to ON located along the top right area of the mobile app. The demo’s
results are now being simultaneously transmitting on the app screen and streamed into the cloud. While in this streaming mode the
session can be shared via a link (see Send a Link to the Cloud Session Section) or it can be immediately viewed from the same mobile
device by using its mobile browser and placing the app in the phone’s background (See View the Cloud Session).
Figure 4.15. Stream to Cloud Enabled
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 18
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.7.1 Send a Link to the Cloud Session
Once a cloud stream session is enabled, the user also has the ability to share the stream to others as well as view the session from the
cloud on the same mobile device. To do any of these options, select the share icon along the top right of the app screen (the share icon
looks like an up arrow out of an open box). Upon selecting, the mobile app will display a pop up window with various available options.
Figure 4.16. Sharing the Cloud Session
To share the link, select from a multitude of sharing options (e.g., Email, Twitter, Facebook). For this document, the SMS message and
the email link will be described.
To share via email, in iOS select the email client and a draft email will appear. Add a recipient(s), edit the draft email as needed and
send it. On completion the phone will return the user to the mobile app.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 19
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
Figure 4.17. Sharing the Cloud Session via Email
To share via SMS message, in iOS select the message client and a draft message will appear. Add a recipient(s), edit the draft as
needed and send it. On completion the phone will return the user to the mobile app.
Figure 4.18. Sharing the Cloud Session via Message
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 20
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.7.2 View the Cloud Session
While in the mobile phone with the app streaming to the cloud, to view the live session directly from the cloud, open the share icon and
select the mobile browser. If connected to the internet the screen will now display a mobile view of the cloud streaming session. While
in this mode the app will move to the background and maintain the connections to the connected ThunderBoard-React device and the
cloud database in the internet. The cloud database is a responsible web design and will render the session based on the screen’s size.
For live streams the cloud view will show the last 30 seconds of collected data. Once a live stream ends, this same link will display the
entire stream session in a summary format.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 21
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
Figure 4.19. Mobile Version of the Viewed Live Cloud Session
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 22
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.7.3 View From Another Client
While viewing the cloud session from the same mobile client is a great way to demonstrate the cloud-connectivity of the ThunderBoardReact platform, one of the innovative features of this demo is its ability to support multiple clients from its cloud database using
Firebase.
To view from another device client, this client should be sent a shared link. This other device(s) can then click on the link and open up a
separate, synchronized view from the cloud database.
Figure 4.20. Large screen viewing a Live Cloud Session
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 23
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Operation
4.7.4 View Past Sessions
Each device’s last ten sessions that have been shared to the cloud can be view from the cloud screen. To do so click on “Past Sessions” in the lower center section of the screen. These past sessions will be available for 30 days from the end of their session time.
Figure 4.21. Past Sessions
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 24
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Hardware
5. Hardware
This section describe the key aspects of the ThunderBoard-React hardware design.
mini-simplicity
connector
Si7021
Relative
Humidity
& Temperature
Sensor
MPU-6500
I2C
LED-B
I2C
BGM111
6-axis
accelerometer
& gyroscope
LED-G
Bluetooth Smart
module with
chip antenna
Si1133
I2C
and
Cortex M4 CPU
Si7201
hall-effect
sensor
Ambient Light &
UV Sensor
SW-0
SW-1
Figure 5.1. Hardware Block Diagram
Figure 5.2. ThunderBoard Printed Circuit Board (Front & Back)
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 25
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Hardware
5.1 Mini-Simplicity Debug Connector
The ThunderBoard-React includes a 10-pin mini-simplicity debug connector (J3) to allow a user to develop, program and debug the
firmware application with the hardware. For more information on the firmware application, please refer to the 6. Firmware section.
Figure 5.3. J3 Mini-Simplicity Debug Connector
Table 5.1. Mini-Simplicity Debug Connector Pin Assignments
Pin
Name
1
VAEM
2
GND
3
RST
4
VCOM_RX
5
VCOM_TX
6
SWO
7
SWDIO
8
SWCLK
9
PTI_FRAME
10
PTI_DATA
Note:
1. The connector on the hardware is a keyed male 10-pin 0.050” 1.27 mm, 2x5 array.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 26
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Hardware
5.2 User Accessible Pads
For further design modification, the hardware also includes solder pads that a user can use to interact with the design with external
circuitry. These can be found bordering the BGM111 footprint and are labelled along the bottom side of the printed circuit board.
Figure 5.4. User Accessible Pad Arrays
Table 5.2. User Accessible Pad Pin Assignments
Schematic Pins
BGM111 Pins
Schematic Signals
TP16
PD13
—
TP17
PD14
—
TP18
PD15
—
TP19
PA2
LED-B
TP21
PA3
SW0
TP22
PA5
—
TP23
PF7
SW1
TP24
PF6
LED-G
TP25
VMCU
PWR
TP26
GND
GND
TP27
VMCU
PWR
TP28
GND
GND
Note:
1. Additional test points found along the printed circuit board: PF3, PF4, PF5, SCL, SDA, VBAT, GND.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 27
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6. Firmware
This section describes the ThunderBoard-React application firmware.
6.1 Obtaining the Firmware Application
The firmware for the ThunderBoard-React can be found within the Silicon Labs Bluetooth Smart SDK as a sample application. This
sample application can be opened and built with the App Builder tool in Simplicity Studio.
6.2 Build Instructions
The instructions describe how to build the device firmware.
1. Obtain the Silicon Labs Bluetooth Smart SDK.
2. Install Simplicity Studio.
3. Create a new application in App Builder.
4. Create a project using the ThunderBoard-React application.
5. Generate and note the directory in which the project files were created.
6. Compile in IAR.
At this point, you can load the image onto the ThunderBoard-React hardware.
6.3 Programming the Hardware
The ThunderBoard-React can be re-programmed with an available .bin file using the 10-pin mini simplicity debug header connected to
a Wireless STK with a mini-simplicity cable. The Simplicity Commander commander application found in the Silicon Labs Bluetooth
Smart SDK is used to program the .bin file into ThunderBoard-React.
1. Open Simplicity Commander.
2. Connect the mini-simplicity cable to ThunderBoard-React and the Wireless STK.
3. Ensure the ThunderBoard-React SW3 is set to Vext.
4. Connect the Wireless STK to the computer with Simplicity Commander.
5. In EA commander, click CONNECT along the upper left area of the tool.
6. Select Kit on the left pane
7. Browse to the .bin file and click Erase chip and then Flash Chip
8. Power-cycle the board by removing the mini-simplicity cable off of the ThunderBoard-React and then setting the SW3 to Vbat
where it is powered with the battery
9. To ensure a successful program of the application: Press any button and ensure the Blue LED (LED-B) flashes.
6.4 Sensor and IO Firmware Handling
The following sensor data is obtained by the BMG111 module and made available via the Bluetooth Smart connection:
• 3-axis accelerometer
• 3-axis gyroscope
• Relative humidity
• Temperature
• Ambient Light
• UV index
• Battery level
• Hall effect detection
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 28
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.4.1 Accelerometer and Gyroscope
The accelerometer and gyroscope in the MPU-6500 is used to present acceleration and orientation of the sensor board. The orientation
of the board is defined into three axes: X, Y and Z as shown in Figure 6.1 Hardware Axis Orientation on page 29.
Figure 6.1. Hardware Axis Orientation
To minimize offset in the gyroscope data, the firmware supports a calibration (reset orientation) command. When a calibration is started
the sensor board must be left stationary until the calibration is complete. LED-G will be lit as long as the calibration is ongoing.
When the calibration (Reset orientation) command is issued, a reference coordinate system (x, y, z in Figure 6.2 Orientation Representation on page 29) is defined to be equal to the hardware’s actual X, Y, Z positioning. After calibration successfully completes, any
change in orientation after the orientation reset will be represented the difference in angles between X, Y and Z and x, y and z according to Figure 6.2 Orientation Representation on page 29. The angles presented are Alpha (α), Beta (β) and Gamma (γ).
Figure 6.2. Orientation Representation
The accelerometer data is sampled at 5 Hz and delivered as a GATT attribute at the same rate. The gyroscope data is sampled at 200
Hz by the firmware and the orientation angles are calculated, but the GATT attributes are only updated at 5 Hz.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 29
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.4.2 Environment Sensors
The Si7021 measures both relative humidity and temperature, whereas the Si1133 measures ambient light and UV index. The sensors
are measured when a read command is received and the measurement data is included in the read response.
6.4.3 Battery Level
The battery level is sensed by the BGM111 by measuring the supply voltage level and translating this into a % of remaining charge
using a look-up table specific for a given CR2032 battery. The battery level is measured every 10 seconds.
6.4.4 Hall-effect sensor
The hall-effect sensor is used to count wheel revolutions by detecting nearby magnetic fields beyond a threshold and will increment a
revolution counter every time the sensor outputs a rising edge. The GATT client is notified of the updated revolution count at a 5 Hz rate
through the CSC service.
6.5 Firmware Operation
The firmware operates as a Bluetooth Smart peripheral and has five main states.
Any button
pushed
Connection
opened
ADVERTISEMENT
BEACONING
SLEEP
30 second
timeout
CONNECTED
Connection
closed
OK
Not OK
Reset
SELF TEST
ERROR
Figure 6.3. Firmware Application State Diagram
6.5.1 Self-test state
After the device wakes up from reset, it performs a self-test to check that all sensors are can be accessed and that there are no hardware failures. Is the test is OK the device transitions to the sleep state. If a failure is found, the error state is entered.
6.5.2 Error state
If an error is found the device stays in the error state until the device is reset by removing the battery and re-installing the battery. While
in this state the blue LED (LED-B) and green LED (LED-G) will blink in an alternating pattern.
6.5.3 Sleep state
In this state the Bluetooth Smart stack is not operational, all sensors are put in their lowest power state and the BGM111 is put in a
Deep Sleep state (EM2). The current consumption in this state is around 10 µA. While in this state, both the blue and green LEDs are
extinguished.
6.5.4 Advertisement State
In this state the Bluetooth Smart stack is in advertising mode using the data found in Table 6.1 Beacon Advertisement Data on page
31. All sensors are put in their lowest power state and the BGM111 is in Sleep (EM1) between each advertisement transmission. If a
connection is made to a central device, the advertisement is stopped and the device enters the connected state. If no connection is
made within 30 seconds, the device goes back to the deep sleep state. While in this state the blue LED (LED-B) is blinking once a
second and the green LED (LED-G) is off.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 30
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.5.5 Connected state
This state is entered once a device is connected to a central device. In this state the device acts as a GATT server. In this state all
sensors are configured to their operational state. The BGM111 is in Sleep (EM1) when not handling the stack or the sensors.
• The green LED (LED-G) blinks once when a connection is opened.
• Both LEDs can be set/cleared by the central device (GATT client) through the Bluetooth Smart connection (Automation IO service).
6.6 Bluetooth Smart Over-the-air Definition
This section describes the over-the-air interface between the phone application and the ThunderBoard-React including advertisement
data, scan response and GATT services and characteristics.
6.6.1 Advertisement
The EFR32 Blue Gecko alternates between two advertisement payloads which are swapped every second. One payload is an iBeacon
payload and the other is a regular non-beacon payload containing the local name and a manufacturing specific firmware ID.
6.6.2 iBeacon Advertisement Payload
Below is the advertisement payload sent out by the BGM111 in an uni-directed connectable mode. It implements an Apple iBeacon
format and advertises on all advertisement channels.
Table 6.1. Beacon Advertisement Data
Type
Value
Description
UINT8
0x02
FLAGS_LENGTH
UINT8
0x01
FLAGS_TYPE
UINT8
0x05
FLAGS_BREDR_NOT_SUPPORTED
FLAGS_LIMITED_DISCOVERABLE
UINT8
0x1A
MANDATA_LENGTH
UINT8
0xFF
MANDATA_TYPE
UINT16
0x004C
MANDATA_BEACON_COMPANYID
UINT16
0x1502
MANDATA_BEACON_TYPE
UINT128
0xCEF797DA-2E91-4EA4-A424-F45082AC0682 MANDATA_BEACON_UUID
UINT16
0x00nn
MANDATA_BEACON_MAJOR
UINT16
0xnnnn
MANDATA_BEACON_MINOR
UINT8
0xC3
MANDATA_BEACON_RSSI
The major and minor values of the beacon payload together constitute a 24-bit ID that is unique to an individual ThunderBoard device.
The two Least Significant Octets of the unique ID equals the 16-bit minor value. The Most Significant Octet of the unique ID equals the
Least Significant Octet of the major value. The unique ID is equal to the #nnnnnnnn decimal value given in the Device Name in the
table above. The unique ID is also equal to the 3 Least Significant Octets of the Manufacturer Identifier in 6.7.3 Device Information
Service (0x180A).
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 31
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.6.3 Non-beacon Advertisement Payload
Below is the non-beacon advertisement payload sent by the EFR32 Blue Gecko on all advertisement channels.
Table 6.2. Non-beacon Advertisement Payload
Type
Value
Description
UINT8
0x02
FLAGS_LENGTH
UINT8
0x01
FLAGS_TYPE
UINT8
0x05
FLAGS_BREDR_NOT_SUPPORTED
FLAGS_LIMITED_DISCOVERABLE
UINT8
0x06
MANDATA_LEN
UINT8
0xFF
MANDATA_TYPE
UINT16
0x0047
MANDATA_COMPANY_ID
UINT16
0x0001
MANDATA_FIRMWARE_ID
UINT8
Length of local name +1
UINT8
0x09
UINT8[n]
Local name
LOCALNAME_LENGTH
LOCALNAME_TYPE
LOCALNAME
The MANDATA_FIRMWARE_IDE field can be used to uniquely identify the capabilities of the board firmware.
Local name is the same as “Device Name” in the Generic Access Service. If the “Device Name” is changed, the Local name will be
changed accordingly.
6.7 GATT Description
6.7.1 Generic Access Service (0x1800)
Table 6.3. Characteristics included in Generic Access Service
Characteristic
UUID
Device Name
0x2a00
Interpretation
Byte
Encoding
UFT8S
Properties
Descriptors
Read Write1
“Thunder React #nnnnn”
nnnnn is a 5-decimal digit serial
Appearance
0x2a01
0:1
UINT16
Read
0: Unknown
Note:
1. The Device name can be written by a GATT client, but the length of the name written is limited to 20 characters.
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 32
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.7.2 Generic Attribute Service (0x1801)
Table 6.4. Characteristics Included in Generic Attribute Service
Characteristic
Service Changed
UUID
Interpretation
0x2a05
Byte
Encoding
0:1
UINT16
Properties
Descriptors
Indicate
Start of affected attribute handle range
2:3
UINT16
End of affected attribute handle range
The Service Changed Attribute is included to avoid caching of the device name in iOS devices.
6.7.3 Device Information Service (0x180A)
Table 6.5. Characteristics included in Device Information Service
Characteristic
UUID
Manufacturer Name
String
0x2a29
Model Number String
0x2a24
Interpretation
Byte
Encoding
Properties
UFT8S
Descriptors
Read
“Silicon Labs”
UTF8S
Read
“RD-0057”
Hardware Revision
String
0x2a27
Firmware Revision
String
0x2a26
System ID
0x2a23
UTF8S
Read
4 digit string
UTF8S
Read
X.Y.Z revision format
0:4
UINT40
Read
Manufacturer Identifier
5:7
UINT24
Organizationally Unique Identifier
6.7.4 Battery Service (0x180f)
Table 6.6. Characteristics included in Battery Service
Characteristic
UUID
Battery Level
0x2a19
Interpretation
Byte
Encoding
0
UINT8: Battery level in %
silabs.com | Smart. Connected. Energy-friendly.
Properties
Descriptors
Read Notify
Client Characteristic
Configuration
Rev. 0.2 | 33
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.7.5 Environmental Sensing Service (0x181a)
Table 6.7. Characteristics included in Environmental Sensing Service
Characteristic
UUID
Humidity
0x2a6f
Interpretation
Byte
Encoding
0:1
UINT16
Properties
Descriptors
Read
Unit in % with resolution of
0.01%
Temperature
0x2a6e
0:1
INT16
Read
Units in °C with resolution of
0.01 °C
UV Index
0x2a76
0
UINT8
Read
Unit-less
6.7.6 Ambient Light Service (0xd24c4f4e-17a7-4548-852c-abf51127368b)
Table 6.8. Characteristics included in Ambient Light Service
Characteristic
UUID
Ambient Light
0xc8546913bfd9-45eb-8dde-9f8754
f4a32e
silabs.com | Smart. Connected. Energy-friendly.
Interpretation
Byte
Encoding
0:3
UINT32
Properties
Descriptors
Read
Lux with resolution of 0.01 lux
Rev. 0.2 | 34
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.7.7 Cycling Speed and Cadence Service (0x1816)
Table 6.9. Characteristics included in Cycling Speed and Cadence Service
Characteristic
UUID
CSC Measurement
0x2a5b
Interpretation
Byte
Encoding
0
Bit 0: Wheel Revolution Data
Present (1 = True)
1:4
UINT32
Properties
Descriptors
Notify
Client Characteristic
Configuration
Cumulative Wheel Revolutions
CSC Feature
0x2a5c
5:6
UINT16: Last Wheel Event Time
given with a resolution of 1/1024
s.
0:1
Bit 0: Wheel Revolution Data
Supported
Read
(1 = True)
SC Control Point
0x2a55
0
UINT8
Write
Op Code
Indicate
Client Characteristic
Configuration
0x01: Set Cumulative Value
1:4
UINT32
Cumulative Value
5
UINT8
Request Op Code
0x01: Set Cumulative Value
6
UINT8
Response Value
0x01: Success
0x02: Not supported
0x03: Invalid parameter
0x04: Operation Failed
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 35
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.7.8 Acceleration and Orientation Service (0xa4e649f4-4be5-11e5-885d-feff819cdc9f)
Table 6.10. Characteristics included in Acceleration and Orientation Service
Characteristic
UUID
Acceleration Measure- 0xc4c1f6e2-4be5-1
ment
1e5-885dfeff819cdc9f
Orientation
Measurement
Control Point
0xb7c4b694bee3-45dd-ba9ff3b5e994f49a
0x
71e30b8c-4131-47
03-b0a0b0bbba75856b
Interpretation
Properties
Descriptors
Notify
Client Characteristic
Configuration
Notify
Client Characteristic
Configuration
UINT8
Write
Op Code
Indicate
Client Characteristic
Configuration
Byte
Encoding
0:1
INT16: Acceleration along X-axis.
Units in g with resolution of 0.001 g
2:3
INT16: Acceleration along Y-axis.
Units in g with resolution of 0.001 g
4:5
INT16: Acceleration along Z-axis.
Units in g with resolution of 0.001 g
0:1
INT16: Orientation alpha angle in
deg (+180 to -180) with resolution
of 0.01 deg
2:3
INT16: Orientation beta angle in
deg (+90 to -90) with resolution of
0.01 deg
4:5
INT16: Orientation gamma angle in
deg (+180 to -180) with resolution
of 0.01 deg
0
0x01: Start calibration
0x02: Reset orientation
0x10: Response Code
1
UINT8
Request Op Code
Only used in response
2
UINT8
Response Value
0x01: Success
0x02: Error
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 36
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
6.7.9 Automation IO Service (0x1815)
Table 6.11. Characteristics included in Automation IO Service
Characteristic
UUID
Digital
0x2a56
Interpretation
Properties
Descriptors
Array of 2 2-bit values
Read
Each 2 bit values correspond to the
state of an IO:
Notify
Client Characteristic
Configuration,
Byte
Encoding
0
(Input or output type
can be read from the
Characteristic Presentation Format descriptor)
Characteristic Presentation Format,
0b00 = Inactive state
Number of digitals
0b01 = Active state
0b10 = Tristate state
0b11 = Unknown state
The least significant 2-bit value corresponds to digital IO 0
Digital
0x2a56
(Input or output type
can be read from the
Characteristic Presentation Format descriptor)
0
Array of 2 2-bit values
Each 2 bit values correspond to the
state of an IO:
Read Write
Characteristic Presentation Format,
Number of digitals
0b00 = Inactive state
0b01 = Active state
0b10 = Tristate state
0b11 = Unknown state
The least significant 2-bit value corresponds to digital IO 0
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 37
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Firmware
Table 6.12. Descriptors included in characteristics for Automation IO Service
Descriptor
Characteristic Presentation Format
UUID
0x2904
Interpretation
Byte
Encoding
0
Digital IO Format
Properties
Read
UINT8
Value = 27: Opaque Struct
1
Exponent
INT8
Value = 0
2:3
Unit
UINT16:
Value = 0x2700 (Unit-less)
4
Namespace
UINT8
Value = 1 (Bluetooth SIG Assigned Numbers)
5:6
Description
UINT16
Value = 1: Digital input
Value = 2: Digital output
Number of digitals
0x2909
Number of digital IOs represented by this characteristic
Read
UINT8
Value = 2
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 38
UG164: ThunderBoard-React (RD-0057-0201) User's Guide
Software
7. Software
This section describes how to obtain the mobile app and cloud software. Each application also includes a readme.md which provides
an overview and how to make use of the source code if one wants to modify the particular application.
Android Mobile App
The android mobile app source code can be found here:
https://github.com/SiliconLabs/thunderboard-react-android
iOS Mobile App
The iOS mobile app source code can be found here:
https://github.com/SiliconLabs/thunderboard-react-ios
ThunderCloud
The cloud platform’s source code can be found here:
https://github.com/SiliconLabs/thundercloud
silabs.com | Smart. Connected. Energy-friendly.
Rev. 0.2 | 39
Smart.
Connected.
Energy-Friendly.
Products
Quality
Support and Community
www.silabs.com/products
www.silabs.com/quality
community.silabs.com
Disclaimer
Silicon Laboratories intends to provide customers with the latest, accurate, and in-depth documentation of all peripherals and modules available for system and software implementers using
or intending to use the Silicon Laboratories products. Characterization data, available modules and peripherals, memory sizes and memory addresses refer to each specific device, and
"Typical" parameters provided can and do vary in different applications. Application examples described herein are for illustrative purposes only. Silicon Laboratories reserves the right to
make changes without further notice and limitation to product information, specifications, and descriptions herein, and does not give warranties as to the accuracy or completeness of the
included information. Silicon Laboratories shall have no liability for the consequences of use of the information supplied herein. This document does not imply or express copyright licenses
granted hereunder to design or fabricate any integrated circuits. The products are not designed or authorized to be used within any Life Support System without the specific written consent
of Silicon Laboratories. A "Life Support System" is any product or system intended to support or sustain life and/or health, which, if it fails, can be reasonably expected to result in significant
personal injury or death. Silicon Laboratories products are not designed or authorized for military applications. Silicon Laboratories products shall under no circumstances be used in
weapons of mass destruction including (but not limited to) nuclear, biological or chemical weapons, or missiles capable of delivering such weapons.
Trademark Information
Silicon Laboratories Inc.® , Silicon Laboratories®, Silicon Labs®, SiLabs® and the Silicon Labs logo®, Bluegiga®, Bluegiga Logo®, Clockbuilder®, CMEMS®, DSPLL®, EFM®, EFM32®,
EFR, Ember®, Energy Micro, Energy Micro logo and combinations thereof, "the world’s most energy friendly microcontrollers", Ember®, EZLink®, EZRadio®, EZRadioPRO®, Gecko®,
ISOmodem®, Precision32®, ProSLIC®, Simplicity Studio®, SiPHY®, Telegesis, the Telegesis Logo®, USBXpress® and others are trademarks or registered trademarks of Silicon Laboratories Inc. ARM, CORTEX, Cortex-M3 and THUMB are trademarks or registered trademarks of ARM Holdings. Keil is a registered trademark of ARM Limited. All other products or brand
names mentioned herein are trademarks of their respective holders.
Silicon Laboratories Inc.
400 West Cesar Chavez
Austin, TX 78701
USA
http://www.silabs.com
工商网监
湘ICP备2023018690号
