Frank Vannieuwkerke / Mbed 2 deprecated Wi-Go_IOT_Demo_MKII

Port from Avnet's Internet Of Things full WiGo demo: SmartConfig - WebServer - Exosite - Android sensor Fusion App

Dependencies:   NVIC_set_all_priorities mbed cc3000_hostdriver_mbedsocket TEMT6200 TSI Wi-Go_eCompass_Lib_V3 WiGo_BattCharger

Wi-Go Reference Design Overview

For additional information on Wi-Go, please visit http://www.em.avnet.com/wi-go
For additional information on Freescale eCompass, please visit
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=E-Compass
Ported from Avnet's Wi-Go KEIL code.
Special thanks to Jim Carver from Avnet for providing the Wi-Go board and for his assistance.

Multiple Wi-Fi applications are provided within the latest version of Wi-Go software:

  • SmartConfig App for auto-setup of Wi-Go network parameters.
  • WebServer display of live sensor data.
  • Exosite portal sensor data feed by Wi-Go.
  • Freescale's Sensor Fusion App data feed by Wi-Go.

Wi-Go is intended for "untethered" portable operation (using it's high-capacity Lithium-Polymer battery). The serial terminal text interface is only required for initial setup, thereafter selection of an application from those available is via finger position on the Touch Slider during the initial 6 second startup period.

Running the Wi-Go Demo Suite

Warning

The on-board Firmware must be updated to mbed enable a Wi-Go system.
Goto the Component page to get the FirmwareUpdate tool (scroll down to the FirmwareUpdate topic).

MAG3110 sensor and eCompass Calibration!

As with the other sensor applications, the eCompass function requires quality calibration data to achieve best accuracy.
For the first 15 seconds after power-up it is recommended that "Figure 8" movements with Wi-Go be done in a smooth, repetitive pattern. Don't touch the slider pad during calibration.

Startup
The RGB LED blinks in a GREEN-ORANGE sequence to inform the user the module is waiting for input.
The RGB LED color designates which of the following Apps to launch.

RGB LED ColorApplication to Launch
OrangeErase all wireless profiles
PurpleSmartConfig
BlueWebServer
RedExosite Data Client
GreenAndroid Server

Swipe your index finger across the slider pad, the RGB LED color will change at approximately 20% intervals.
Removing your finger latches the last color displayed. After about 3 seconds, the selected app will start.
Another app can be selected when the slider pad is touched again within the 3 seconds timeout.

After launch of Exosite or Android Server Apps, the eCompass function then controls the RGB LED.
(not in WebServer mode where RGB LEDs are manually controlled by the User).

RGB LED ColorDirection Indication
BlueNear to North
GreenNorth
RedEast / West
PurpleSouth

__Note!__ The D1, D2 and D3 User LEDs on Wi-Go adhere to the following convention for the different Apps

User LED#Description of function controlling the LED
D1is the board heartbeat, derived from the timer interrupt
D2indicates network activity as follows:
Web Server Wi-Go webpage is being served.
Exosite Client Wi-Go is sending data.
Android App Wi-Go is sending data
D3WLAN Network is Connected

Detail of Wi-Go Applications

App #1: SmartConfig
See TI's pages on how to use the SmartConfig tool:

  • Preferred method : Configuration using the SmartConfig tool
  • SmartConfig download: Smart Config and Home Automation
    • iOS app : available at Apple app store.
    • Android app : download and install the Android SmartConfig Application on a PC.
      This file contains the source code as well as the compiled APK file.
      The APK file is stored in ti\CC3000AndroidApp\SmartConfigCC3X\bin.

App #2: WebServer display of live sensor data
__Note!__
When using the WebServer for the first time on a Wi-Fi network you will need to determine the IP address that's assigned to Wi-Go by the DHCP Server. To do this, it is recommended you use one of the following two methods:

  • While Wi-Go is initially tethered to a laptop via USB, launch of the WebServer Application and note the IP address that is reported on the terminal screen immediately after selection of this App.
  • Alternatively, use a 3rd party LAN SCAN type tool to view Wi-Go's IP address.
    eg. FING, - available for free download from Google Play or iTunes App Stores…

Wi-Go's WebServer Application is selected as follows:

  • Press RESET, followed by the eCompass Calibration (mentioned at the top of this page).
    Then use index finger on slider to select the WebServer App (RGB LED = BLUE).
    At end of the 3 second selection period the WebServer App shall launch.
  • If you are tethered to a laptop and have a terminal open the Wi-Fi network connection confirmation will be seen, eg. 

'*** Wi-Go board DHCP assigned IP Address = 192.168.43.102
  • Once you have noted Wi-Go's reported IP address, the USB cable may be disconnected and Wi-Go then used as intended, running on it's own battery power.
  • Use an Internet Browser on SmartPhone/Tablet/Laptop (connected to same Hot-Spot/Wireless Router subnet), to now connect to the noted Wi-Go IP address and view the WebServer output: /media/uploads/frankvnk/wi-go_webserver.png
  • the Webserver sensor data is auto-updated every 2 seconds a manual refresh (F5 on laptop).
  • In the event of an error, press refresh to regenerate the screen.
  • Use the mouse (or touch-screen) to exercise the RGB LED output.

App #3: Exosite Data Client
Wi-Go's sensor data gets transmitted via Wi-Fi to a cloud-based Exosite portal where the sensor measurements are displayed graphically on a "dashboard". Users can create unique customized dashboards using drag and drop GUI widgets from the library provided on the Exosite website.
__Note!__ For the Exosite application a "live" connection to the Internet is required !!!

  • Press RESET, followed by the eCompass Calibration (mentioned at the top of this page).
    Then use index finger on slider to select the Exosite Client App (RGB LED = RED)
  • On launching this App, note Wi-Go's MAC address displayed on your terminal
    (if not running a terminal use FING or other WLAN Scan tool to determine Wi-Go's MAC address) /media/uploads/frankvnk/mac_address.png
  • Using your computer's internet browser, go to avnet.exosite.com and sign-up for a free Avnet Trial Exosite Account: /media/uploads/frankvnk/avnet_trial_exosite.png
  • On the next screen, click on the Sign-Up Now button in the displayed Avnet Trial account option.
  • Complete the Account Info and Contact Info then click on Create Account (make sure to use a valid email address!).
  • Check for new incoming email from avnet.exosite.com to the address you provided and click on the link in this email to activate your new Exosite account.
  • Once activated, login using the email address and password that you chose in your registration. Your Exosite Portal and Dashboard should now display. The first time you log-in to your new account, the default Home dashboard will be displayed, pre-configured with two widgets. On the left is the Welcome widget for tips and information. On the right is the Device List widget.
    Dashboards are configurable, so at any time this default dashboard can be changed, widgets deleted and added (Clicking the upside-down triangle icon in a widget's Title bar will allow you to edit it).
  • Before going further with the Dashboard, you need to connect your Wi-Go device to your Exosite account. Do this by going to the left sidebar and selecting Devices followed by selecting the +Add Device link (on right of screen). /media/uploads/frankvnk/add_device.png
  • In the Setup screens that follow, enter the following
Select a supported deviceWi-Go
Enter device MAC Addressnn:nn:nn:nn:nn:nn [your Wi-Go's MAC address including colons]
Enter device Name[choose a descriptive name]
Enter device Location[description of your location]
  • Once completed, under Devices the name chosen for the added Wi-Go device should now be listed.
  • Click on this new Wi-Go device to examine (and edit if necessary) it's Device Information screen.
    /media/uploads/frankvnk/device_information.png
  • Click the CLOSE button to exit the Device Information screen.
  • On your Wi-Go kit now press RESET, followed by the eCompass Calibration (mentioned at the top of this page)
    and again select the Exosite Client App (RGB LED = RED) using your index finger.
  • Refresh your browser (press F5) a couple've times until the Active indicator changes to On (Green).
    /media/uploads/frankvnk/active_indicator.png
  • From the left sidebar click on Home and click on the recently named Wi-Go device which is located under the Device List.
    This will bring-up a default dashboard display similar to what's shown below.
    (Dashboards are typically accessed via the Dashboards menu entry). Check the dashboard is updating with live data by moving your Wi-Go Kit through different orientations.
    /media/uploads/frankvnk/dashboard.png
  • To create a custom dashboard, select Dashboards from the sidebar menu, followed by +Add Dashboard (on right side of Your Dashboards title bar). After completion of the initial configuration screen you will then be able to add Widgets to display the various Wi-Go data sources as well as pictures and text to support your application.
  • More guidance on the creation, editing and sharing of custom dashboards is available under the Exosite support pages

App #4: Android Sensor Fusion App

  • Press RESET, followed by the eCompass Calibration (mentioned at the top of this page)
    , then use index finger on slider to select the Android App (RGB LED = GREEN)
  • Freescale's ''Xtrinsic Sensor Fusion Toolbox'" will run on Android 3.0 or above phone or tablet. Free to download from Google Play, type Sensor fusion in the search box to find it. freescale.sensors.sfusion /media/uploads/frankvnk/sensor_fusion_toolbox.png
  • The Freescale App is well documented. To access the built-in documentation, press the NAV button at top of screen followed by Documentation from the scroll-down menu:
    /media/uploads/frankvnk/sensor_fusion_doc.png
  • Freescale's sensors site provides additional resources such as this overview: free-android-app-teaches-sensor-fusion-basics
  • Go to the Options Menu and select Preferences… /media/uploads/frankvnk/sensor_fusion_preferences.png
  • The following items need to be taken care of:
Enter WiGo's IP address
Enter the SSID (of the Hot-Spot or Wireless Access Point used by Wi-Go)
  • Press Save and Exit!
    /media/uploads/frankvnk/sensor_fusion_save_and_exit.png
  • Exit the Application completely then re-launch the Sensor Fusion Application.
  • Select the ''Source/Algorithm'" menu and change the data source to Wi-Go mag/accel /media/uploads/frankvnk/sensor_fusion_wigo_mag_accel.png
  • The Android App should now be displaying a 3-D image of Wi-Go that you can rotate and flip-over by moving the Wi-Go board accordingly…
  • Use NAV > Device View to display if this view does not come-up by default. /media/uploads/frankvnk/sensor_fusion_nav_device_view.png
  • A Serial Terminal connection is not necessary but if you happen to have one open you should see the following messages as Wi-Go connects to the Android App:
    "Server waiting for connection" followed by
    "connected, transmit buffer size= 96", and then
    "input = 0123456789"
    at which time Wi-Go starts streaming data to the Android App.

Sensors/MPL3115A2/MPL3115A2.cpp@6:cbd7f95bbca9, 2013-12-11 (annotated)

Committer:
frankvnk
Date:
Wed Dec 11 20:29:39 2013 +0000
Revision:
6:cbd7f95bbca9
Parent:
4:8f8d0d19e6f1 
faster i2c (375KHz) and 10ms systick

Who changed what in which revision?

UserRevisionLine numberNew contents of line
frankvnk 4:8f8d0d19e6f1 1 /* Copyright (c) 2010-2011 mbed.org, MIT License
frankvnk 4:8f8d0d19e6f1 2 *
frankvnk 4:8f8d0d19e6f1 3 * Permission is hereby granted, free of charge, to any person obtaining a copy of this software
frankvnk 4:8f8d0d19e6f1 4 * and associated documentation files (the "Software"), to deal in the Software without
frankvnk 4:8f8d0d19e6f1 5 * restriction, including without limitation the rights to use, copy, modify, merge, publish,
frankvnk 4:8f8d0d19e6f1 6 * distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the
frankvnk 4:8f8d0d19e6f1 7 * Software is furnished to do so, subject to the following conditions:
frankvnk 4:8f8d0d19e6f1 8 *
frankvnk 4:8f8d0d19e6f1 9 * The above copyright notice and this permission notice shall be included in all copies or
frankvnk 4:8f8d0d19e6f1 10 * substantial portions of the Software.
frankvnk 4:8f8d0d19e6f1 11 *
frankvnk 4:8f8d0d19e6f1 12 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING
frankvnk 4:8f8d0d19e6f1 13 * BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
frankvnk 4:8f8d0d19e6f1 14 * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
frankvnk 4:8f8d0d19e6f1 15 * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
frankvnk 4:8f8d0d19e6f1 16 * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
frankvnk 4:8f8d0d19e6f1 17 */
frankvnk 4:8f8d0d19e6f1 18
frankvnk 4:8f8d0d19e6f1 19 #include "MPL3115A2.h"
frankvnk 4:8f8d0d19e6f1 20
frankvnk 4:8f8d0d19e6f1 21 #define REG_WHO_AM_I 0x0C // return 0xC4 by default
frankvnk 4:8f8d0d19e6f1 22 #define REG_STATUS 0x00
frankvnk 4:8f8d0d19e6f1 23 #define REG_CTRL_REG_1 0x26
frankvnk 4:8f8d0d19e6f1 24 #define REG_CTRL_REG_3 0x28
frankvnk 4:8f8d0d19e6f1 25 #define REG_CTRL_REG_4 0x29
frankvnk 4:8f8d0d19e6f1 26 #define REG_CTRL_REG_5 0x2A
frankvnk 4:8f8d0d19e6f1 27 #define REG_PRESSURE_MSB 0x01 // 3 byte pressure data
frankvnk 4:8f8d0d19e6f1 28 #define REG_ALTIMETER_MSB 0x01 // 3 byte altimeter data
frankvnk 4:8f8d0d19e6f1 29 #define REG_TEMP_MSB 0x04 // 2 byte temperature data
frankvnk 4:8f8d0d19e6f1 30 #define REG_PT_DATA_CFG 0x13
frankvnk 4:8f8d0d19e6f1 31 #define REG_P_TGT_MSB 0x16
frankvnk 4:8f8d0d19e6f1 32 #define REG_P_WND_MSB 0x19
frankvnk 4:8f8d0d19e6f1 33
frankvnk 4:8f8d0d19e6f1 34 // Status flag for data ready.
frankvnk 4:8f8d0d19e6f1 35 #define PTDR_STATUS 0x03 // Pressure Altitude and Temperature ready
frankvnk 4:8f8d0d19e6f1 36 #define PDR_STATUS 0x02 // Pressure and Altitude data ready
frankvnk 4:8f8d0d19e6f1 37 #define TDR_STATUS 0x01 // Temperature data ready
frankvnk 4:8f8d0d19e6f1 38
frankvnk 4:8f8d0d19e6f1 39 MPL3115A2::MPL3115A2(PinName sda, PinName scl, int addr) : m_i2c(sda, scl), m_addr(addr) {
frankvnk 4:8f8d0d19e6f1 40 unsigned char data[2] = {REG_CTRL_REG_1, 0xB8};
frankvnk 6:cbd7f95bbca9 41 m_i2c.frequency(375000);
frankvnk 4:8f8d0d19e6f1 42 writeRegs(data, 2);
frankvnk 4:8f8d0d19e6f1 43 data[0] = REG_PT_DATA_CFG;
frankvnk 4:8f8d0d19e6f1 44 data[1] = 0x07;
frankvnk 4:8f8d0d19e6f1 45 writeRegs(data, 2);
frankvnk 4:8f8d0d19e6f1 46 data[0] = REG_CTRL_REG_1;
frankvnk 4:8f8d0d19e6f1 47 data[1] = 0xB9;
frankvnk 4:8f8d0d19e6f1 48 writeRegs(data, 2);
frankvnk 4:8f8d0d19e6f1 49 }
frankvnk 4:8f8d0d19e6f1 50
frankvnk 4:8f8d0d19e6f1 51 uint8_t MPL3115A2::isDataAvailable( void)
frankvnk 4:8f8d0d19e6f1 52 {
frankvnk 4:8f8d0d19e6f1 53 unsigned char status;
frankvnk 4:8f8d0d19e6f1 54 readRegs( REG_STATUS, &status, 1);
frankvnk 4:8f8d0d19e6f1 55 return ((status>>1) & 0x07);
frankvnk 4:8f8d0d19e6f1 56
frankvnk 4:8f8d0d19e6f1 57 }
frankvnk 4:8f8d0d19e6f1 58
frankvnk 4:8f8d0d19e6f1 59 uint8_t MPL3115A2::getAltimeterRaw( unsigned char *dt)
frankvnk 4:8f8d0d19e6f1 60 {
frankvnk 4:8f8d0d19e6f1 61 if ( isDataAvailable() & PDR_STATUS)
frankvnk 4:8f8d0d19e6f1 62 {
frankvnk 4:8f8d0d19e6f1 63 readRegs( REG_ALTIMETER_MSB, &dt[0], 2);
frankvnk 4:8f8d0d19e6f1 64 return 1;
frankvnk 4:8f8d0d19e6f1 65 }
frankvnk 4:8f8d0d19e6f1 66 else
frankvnk 4:8f8d0d19e6f1 67 return 0;
frankvnk 4:8f8d0d19e6f1 68 }
frankvnk 4:8f8d0d19e6f1 69
frankvnk 4:8f8d0d19e6f1 70 uint8_t MPL3115A2::getTemperatureRaw( unsigned char *dt)
frankvnk 4:8f8d0d19e6f1 71 {
frankvnk 4:8f8d0d19e6f1 72 if ( isDataAvailable() & TDR_STATUS)
frankvnk 4:8f8d0d19e6f1 73 {
frankvnk 4:8f8d0d19e6f1 74 readRegs( REG_TEMP_MSB, &dt[0], 1);
frankvnk 4:8f8d0d19e6f1 75 return 1;
frankvnk 4:8f8d0d19e6f1 76 }
frankvnk 4:8f8d0d19e6f1 77 else
frankvnk 4:8f8d0d19e6f1 78 return 0;
frankvnk 4:8f8d0d19e6f1 79 }
frankvnk 4:8f8d0d19e6f1 80
frankvnk 4:8f8d0d19e6f1 81 void MPL3115A2::readRegs(int addr, uint8_t * data, int len) {
frankvnk 4:8f8d0d19e6f1 82 char t[1] = {addr};
frankvnk 4:8f8d0d19e6f1 83 m_i2c.write(m_addr, t, 1, true);
frankvnk 4:8f8d0d19e6f1 84 m_i2c.read(m_addr, (char *)data, len);
frankvnk 4:8f8d0d19e6f1 85 }
frankvnk 4:8f8d0d19e6f1 86
frankvnk 4:8f8d0d19e6f1 87 void MPL3115A2::writeRegs(uint8_t * data, int len) {
frankvnk 4:8f8d0d19e6f1 88 m_i2c.write(m_addr, (char *)data, len);
frankvnk 4:8f8d0d19e6f1 89 }