This program connects to a few sensors via I2C and sends the data collected to a WNC Cellular Module which is located on an Avnet WNC-Shield card.

Dependencies:   FXOS8700CQ MODSERIAL mbed

/media/uploads/kevinkeryk/avnet_logo_tagline_rgb.png

Avnet Cellular IoT Instructions

  • One problematic area is setting the MY_SERVER_URL. When you copy the URL from the flow, you must make sure the MY_SERVER_URL is also set to the appropriate server. It can be either "run-east.att.io" or "run-west.att.io".

Useful Links

Adding Additional Sensors

The FLOW_DEVICE_NAME field must contain the name of the instance of the Virtual Starter Kit in FLOW you will be communicating with. Usually this is "vstarterkit001", but if you have problems communicating you can verify this is correct. Note: This device will not be created until you click the “Initialize” input on the Virtual Device tab of the Starter Kit project in FLOW. At that point, it becomes available in M2X and you can see it as the DEVICE SERIAL field under Devices as in the image below. /media/uploads/JMF/vstarterkit.png

Sensors: When executing, the FRDM-K64F board uploads sensor measurements to AT&T’s Flow environment every 5 seconds, using the Cellular shield board. You can adjust how often you want to do this by editing the SENSOR_UPDATE_INTERVAL_MS value in the header file.

Temperature and humidity: By default, the board reports readings from the HTS221 temperature and humidity sensor. These two values are sent to the HTTP IN /climate port in FLOW with field names “temp” and “humidity”. Temperature is in degrees Fahrenheit and humidity is a %. This default assignment is: iSensorsToReport = TEMP_HUMIDITY_ONLY;

Accelerometer: If you want to expand and use the onboard motion sensor, you can also send 3-axis accelerometer information from the board as “accelX”, “accelY”, and “accelZ”. This is useful if you want to know the stationary position of the board with regards to gravity, or whether it is in motion. These readings are in g’s. To send these values, change the assignment to: iSensorsToReport = TEMP_HUMIDITY_ACCELEROMETER;

PMOD Sensors: If you have a Silicon Labs sensor module that can plug into the PMOD connector on the Cellular shield, you are able to measure proximity, UV light, ambient visible and infrared light from the Si1145 sensor. This PMOD also has a temperature and humidity sensor, but in this case it is redundant. When enabled, the fields “proximity”, “light_uv”, “light_vis” and “light_ir” are also sent. To enable all these sensors, change the assignment to: iSensorsToReport = TEMP_HUMIDITY_ACCELEROMETER_PMODSENSORS;

Connecting the PMOD sensors: Because the pinouts do not align, the SiLabs PMOD sensor board cannot be plugged into the J10 PMOD receptacle on the shield directly. The following wiring instructions must be followed:

SignalJ10ShieldPMOD Color in the image below
VCCPin 6Pin 6Red
GNDPin 5Pin 5Black
SDAPin4Pin 3Green
SCLPin3Pin 2Yellow

/media/uploads/JMF/xyz.jpg

AT&T M2X and FLOW Instructions

M2X & FLOW Instructions

Link to AT&T M2X

M2X

Link to AT&T Flow

FLOW

Avnet WNC-Shield Information

Getting Started with the Avnet WNC-Shield Software

  • This project uses Revision 119 of the MBED library because of I2C implementation differences with the tip (Revision 121).
  • This project uses Revision 4 of the FXOS8700CQ library for sensors.

Easily Modifiable Parameters

Inside the mbed Avnet_ATT_Cellular_IOT project, the parameters needed to customize your board are in the config_me.h file.

  • FLOW parameters: This project assumes you are using a fork of the Starter Kit Base project, which is a reference design created using AT&T’s FLOW (https://flow.att.com) that allows the creation of online virtualization and other IoT functionality. The default parameters in the config_me.h file are done for a specific instance of this project. When you fork the original project, you get your own instance and it will have its own base address. At the bottom of the FLOW environment, when you click on the Endpoints tab, URL information that is specific to your instance is displayed. Of note is the Base URL. In the example below (as in the default mbed project), the Base URL is: https://run-west.att.io/1e464b19cdcde/774c88d68202/86694923d5bf28a/in/flow You have to take note of two parts of this address. The run-west.att.io part is the server URL, and you have to make sure the
  • MY_SERVER_URL field in config_me.h matches this. The rest of the base URL, in green above, needs to be pasted into the FLOW_BASE_URL field.

There is also a FLOW_INPUT_NAME field. This should match the name of the HTTP IN port in the FLOW project that you want to send sensor data to. The default is "/climate", as in the FLOW image below.

/media/uploads/JMF/sf.png

Where is the Binary I compiled

When the COMPILE button is pressed, it compiles your project and links it. The result is placed in the DOWNLOAD folder you use when downloading files from the Internet. It will be called AvnetATT_shape_hackathon_K64F.bin.

Additional Information on Compiling/Configuring

Comprehensive instructions can be found at: Quick Start Instructions

Committer:
root@developer-sjc-indigo-compiler.local.mbed.org
Date:
Mon Dec 11 21:51:32 2017 +0000
Revision:
83:55778a2d5c5e
Parent:
68:6e311c747045
Added tag att_cellular_K64_wnc_14A2A_20171211 for changeset 65cde5d7070c

Who changed what in which revision?

UserRevisionLine numberNew contents of line
fkellermavnet 68:6e311c747045 1 /* ===================================================================
fkellermavnet 68:6e311c747045 2 Copyright © 2016, AVNET Inc.
fkellermavnet 68:6e311c747045 3
fkellermavnet 68:6e311c747045 4 Licensed under the Apache License, Version 2.0 (the "License");
fkellermavnet 68:6e311c747045 5 you may not use this file except in compliance with the License.
fkellermavnet 68:6e311c747045 6 You may obtain a copy of the License at
fkellermavnet 68:6e311c747045 7
fkellermavnet 68:6e311c747045 8 http://www.apache.org/licenses/LICENSE-2.0
fkellermavnet 68:6e311c747045 9
fkellermavnet 68:6e311c747045 10 Unless required by applicable law or agreed to in writing,
fkellermavnet 68:6e311c747045 11 software distributed under the License is distributed on an
fkellermavnet 68:6e311c747045 12 "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
fkellermavnet 68:6e311c747045 13 either express or implied. See the License for the specific
fkellermavnet 68:6e311c747045 14 language governing permissions and limitations under the License.
fkellermavnet 68:6e311c747045 15
fkellermavnet 68:6e311c747045 16 ======================================================================== */
JMF 0:9d5134074d84 17
JMF 0:9d5134074d84 18 #ifndef HTS221_H_
JMF 0:9d5134074d84 19 #define HTS221_H_
JMF 0:9d5134074d84 20
JMF 0:9d5134074d84 21 class HTS221 {
JMF 0:9d5134074d84 22 public:
JMF 0:9d5134074d84 23 HTS221(void);
JMF 0:9d5134074d84 24 int begin(void);
JMF 0:9d5134074d84 25 int activate(void);
JMF 0:9d5134074d84 26 int deactivate(void);
JMF 0:9d5134074d84 27
JMF 0:9d5134074d84 28 int bduActivate(void);
JMF 0:9d5134074d84 29 int bduDeactivate(void);
JMF 0:9d5134074d84 30
JMF 0:9d5134074d84 31 int readHumidity(void);
JMF 0:9d5134074d84 32 double readTemperature(void);
JMF 0:9d5134074d84 33 private:
JMF 0:9d5134074d84 34 int storeCalibration(void);
JMF 0:9d5134074d84 35 unsigned char _h0_rH, _h1_rH;
JMF 0:9d5134074d84 36 unsigned int _T0_degC, _T1_degC;
JMF 0:9d5134074d84 37 unsigned int _H0_T0, _H1_T0;
JMF 0:9d5134074d84 38 unsigned int _T0_OUT, _T1_OUT;
JMF 0:9d5134074d84 39 double _temperature;
JMF 0:9d5134074d84 40 int _humidity;
JMF 0:9d5134074d84 41 unsigned char _address;
JMF 0:9d5134074d84 42
JMF 0:9d5134074d84 43 unsigned char readRegister(unsigned char slaveAddress, unsigned char regToRead);
JMF 0:9d5134074d84 44 int writeRegister(unsigned char slaveAddress, unsigned char regToWrite, unsigned char dataToWrite);
JMF 0:9d5134074d84 45 };
JMF 0:9d5134074d84 46
stefanrousseau 11:e6602513730f 47 #define HTS221_ADDRESS 0xBF
JMF 0:9d5134074d84 48
JMF 0:9d5134074d84 49 //Define a few of the registers that we will be accessing on the HTS221
JMF 0:9d5134074d84 50 #define WHO_AM_I 0x0F
JMF 0:9d5134074d84 51 #define WHO_AM_I_RETURN 0xBC //This read-only register contains the device identifier, set to BCh
JMF 0:9d5134074d84 52
JMF 0:9d5134074d84 53 #define AVERAGE_REG 0x10 // To configure humidity/temperature average.
JMF 0:9d5134074d84 54 #define AVERAGE_DEFAULT 0x1B
JMF 0:9d5134074d84 55
JMF 0:9d5134074d84 56 /*
JMF 0:9d5134074d84 57 * [7] PD: power down control
JMF 0:9d5134074d84 58 * (0: power-down mode; 1: active mode)
JMF 0:9d5134074d84 59 *
JMF 0:9d5134074d84 60 * [6:3] Reserved
JMF 0:9d5134074d84 61 *
JMF 0:9d5134074d84 62 * [2] BDU: block data update
JMF 0:9d5134074d84 63 * (0: continuous update; 1: output registers not updated until MSB and LSB reading)
JMF 0:9d5134074d84 64 The BDU bit is used to inhibit the output register update between the reading of the upper
JMF 0:9d5134074d84 65 and lower register parts. In default mode (BDU = ?0?), the lower and upper register parts are
JMF 0:9d5134074d84 66 updated continuously. If it is not certain whether the read will be faster than output data rate,
JMF 0:9d5134074d84 67 it is recommended to set the BDU bit to ?1?. In this way, after the reading of the lower (upper)
JMF 0:9d5134074d84 68 register part, the content of that output register is not updated until the upper (lower) part is
JMF 0:9d5134074d84 69 read also.
JMF 0:9d5134074d84 70 *
JMF 0:9d5134074d84 71 * [1:0] ODR1, ODR0: output data rate selection (see table 17)
JMF 0:9d5134074d84 72 */
JMF 0:9d5134074d84 73 #define CTRL_REG1 0x20
JMF 0:9d5134074d84 74 #define POWER_UP 0x80
JMF 0:9d5134074d84 75 #define BDU_SET 0x4
JMF 0:9d5134074d84 76 #define ODR0_SET 0x1 // setting sensor reading period 1Hz
JMF 0:9d5134074d84 77
JMF 0:9d5134074d84 78 #define CTRL_REG2 0x21
JMF 0:9d5134074d84 79 #define CTRL_REG3 0x22
JMF 0:9d5134074d84 80 #define REG_DEFAULT 0x00
JMF 0:9d5134074d84 81
JMF 0:9d5134074d84 82 #define STATUS_REG 0x27
JMF 0:9d5134074d84 83 #define TEMPERATURE_READY 0x1
JMF 0:9d5134074d84 84 #define HUMIDITY_READY 0x2
JMF 0:9d5134074d84 85
JMF 0:9d5134074d84 86 #define HUMIDITY_L_REG 0x28
JMF 0:9d5134074d84 87 #define HUMIDITY_H_REG 0x29
JMF 0:9d5134074d84 88 #define TEMP_L_REG 0x2A
JMF 0:9d5134074d84 89 #define TEMP_H_REG 0x2B
JMF 0:9d5134074d84 90 /*
JMF 0:9d5134074d84 91 * calibration registry should be read for temperature and humidity calculation.
JMF 0:9d5134074d84 92 * Before the first calculation of temperature and humidity,
JMF 0:9d5134074d84 93 * the master reads out the calibration coefficients.
JMF 0:9d5134074d84 94 * will do at init phase
JMF 0:9d5134074d84 95 */
JMF 0:9d5134074d84 96 #define CALIB_START 0x30
JMF 0:9d5134074d84 97 #define CALIB_END 0x3F
JMF 0:9d5134074d84 98 /*
JMF 0:9d5134074d84 99 #define CALIB_T0_DEGC_X8 0x32
JMF 0:9d5134074d84 100 #define CALIB_T1_DEGC_X8 0x33
JMF 0:9d5134074d84 101 #define CALIB_T1_T0_MSB 0x35
JMF 0:9d5134074d84 102 #define CALIB_T0_OUT_L 0x3C
JMF 0:9d5134074d84 103 #define CALIB_T0_OUT_H 0x3D
JMF 0:9d5134074d84 104 #define CALIB_T1_OUT_L 0x3E
JMF 0:9d5134074d84 105 #define CALIB_T1_OUT_H 0x3F
JMF 0:9d5134074d84 106 */
JMF 0:9d5134074d84 107
JMF 0:9d5134074d84 108 #endif