This program simply connects to a HTS221 I2C device to read Temperature & Humidity, and a WNC Cellular Module both of which are on the Avnet WNC Shield.

Dependencies:   mbed FXOS8700CQ

/media/uploads/JMF/avnet_logo.gif

AT&T Shape Hackathon QuickStart Instructions

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

Useful Links

Adding Additional Sensors

The FLOW_DEVICE_NAME field must contain the name of the instance of the Virtual Starter kit in FLOW that you will be communicating with. Usually this will be "vstarterkit001", but if you have problems communicating you can verify that this is indeed correct. Note that 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 there, as the DEVICE SERIAL field under Devices as in the image below.

Sensors: When executing, the FRDM-K64F board will upload 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 will report 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 on-board 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 will also be 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” will also be sent. To enable all these sensors, change the assignment to: iSensorsToReport = TEMP_HUMIDITY_ACCELEROMETER_PMODSENSORS;

Connecting up 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 used:

Signal=J10=(Shield) PMOD=Color in the image below
VCCPin 6Pin 6Red
GNDPin 5Pin 5Black
SDAPin4Pin 3Green
SCLPin3Pin 2Yellow

Link to AT&T M2X

M2X

Link to AT&T Flow

FLOW

Avnet WNC-Shield Information

Getting Started with the Avnet WNC-Shield & Hackathon 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 in source code

Inside the mbed “AvnetATT_shape_hackathon” project, the parameters that are needed to customize your board are in the config_me.h file.

  • FLOW parameters: This project assumes that you are using a fork of the “Starter Kit Base” project, which is a reference design that was created using AT&T’s FLOW (https://flow.att.com) that allows the creation of on-line 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, you will see the URL information that is specific to your instance. 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. Then there is the rest of the base URL, in green above, that 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 will compile your project and link 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

Changes

RevisionDateWhoCommit message
34:029e07b67a41 2016-07-23 stefanrousseau Fixed the char to be * char myJsonResponse[512];; default tip
33:eaf45dab650a 2016-07-21 fkellermavnet Changed sock read so it clears out the return data string upon call. If data is obtained then it puts it in the cleared string. Changed sock read so that it returns how many bytes/chars it received from the read.
32:8ba73eab6c72 2016-07-21 fkellermavnet replaced incorrect usage of string data() with correct c_str().
31:d7c386d2e95a 2016-07-20 stefanrousseau Make TEMP_HUMIDITY_ONLY the default again for the sensors.
30:48b43538e98b 2016-07-20 stefanrousseau Changed the motion sensor instantiation from static to dynamic inside the function that uses it. This is needed because the WNC on the shield corrupts the I2C bus during initialization.
29:e6c8bd41caa6 2016-07-16 stefanrousseau Changed proximity to value instead of string
28:886833917643 2016-07-15 JMF comment cleanup
27:f15839656a5d 2016-07-13 fkellermavnet Removed now merged in file that mbed automatically added that I didn't see on last commit.
26:8d6e7e7cdcae 2016-07-13 fkellermavnet Merged in my changes with Stefan's (hopefully correctly)
25:e7996d22a7e6 2016-07-13 fkellermavnet Only do 1 socket open (before was doing open -> write -> read -> close. So now do 1 open then write -> read -> write -> read ...
24:bd480d2aade4 2016-07-13 stefanrousseau Updated config_me header file descriptions and moved the sensor update interval there.
23:d6ceeb6d85ed 2016-07-13 stefanrousseau Added text to config_me. Also moved the sensor update definition there.
22:41e6c417ace1 2016-07-13 fkellermavnet Added a 10mS delay to the socket read function. 10mS for the first read and then 10mS in between each retry.
21:d0038d14ee7c 2016-07-13 fkellermavnet Cleaned up config_me.h a little and added some comments for the user variables. More comments need to be added. Cleaned up some of my unused debug code at the bottom of main().
20:27a4f27254d0 2016-07-13 fkellermavnet Set LED to RED for initialization, then BLUE after once the WNC is setup for internet comms, then GREEN after a response comes back from the server.; ; Then the LED is never touched and any incoming flow commands will set the color going forward.
19:f89baed3bd6f 2016-07-13 fkellermavnet Right before the SOCKCONN during the WNC software initialization once in a while the WNC seems to be dropping a char that is sent to it, 'A' specifically. So I put in 2 "AT" commands right before the SOCKCONN and that seems to clean it up.
18:b08471eb1d1c 2016-07-13 fkellermavnet Add a 3 sec delay between afterWNC hardware init is done and before the AT sockets commands are sent to the WNC.
17:38a8cc0c6ba5 2016-07-13 JMF Updated power-up sequence per WNC.
16:17c5916f2d12 2016-07-13 stefanrousseau Merged LED and JSON changes with power-up changes
15:61df4a452d38 2016-07-13 stefanrousseau Added JSON parsing and displaying the LED color
14:0c353e212296 2016-07-13 fkellermavnet Pulled in Steve Martin's new WNC initialization code.; Also removed the while(1) in case init fails, now it just continues to retry the initialization.
13:df9c49662797 2016-07-12 stefanrousseau TEMP_HUMIDITY only is the default
12:7c94ec5069dc 2016-07-12 stefanrousseau Fixed GET string format and added 3 options for the sensors to be read.
11:e6602513730f 2016-07-12 stefanrousseau Fixed I2C issues. ; a) Removed stop between HTS221 address and read; b) The latest MBED uses the slave address differently from the legacy. Stick with the old for now and fixed the HTS221 address to BF instead of 5F.; c) Made I2C definitions externs.
10:df54436ecd38 2016-07-11 fkellermavnet Changed wnc control code so that it can't do a read or a write to a socket if the socket is not opened successfully.
9:01144f2b8e03 2016-07-11 stefanrousseau Update to channel to serial
8:b08ec94d9e9f 2016-07-11 stefanrousseau changed to serial
7:489835c87d95 2016-07-11 stefanrousseau Changed device ID to serial
6:713b4cbf1a7d 2016-07-11 fkellermavnet Slowed down enhanced Steve's send cmd, wait for response when sending to the wnc uart. 1mS in between every char now.
5:3417b6a84ee3 2016-07-11 fkellermavnet Fixed get string to work proper with ATT test flow.
4:f83bedd9cab4 2016-07-11 stefanrousseau Added a sensors file that will write the FRDM-K64F motion sensor and the values from the SiLabs PMOD into a structure.
3:26b3cc155f39 2016-07-10 stefanrousseau Stefan added:; 1) Flow_parameters.h; 2) ms timer tick currently expires every 5 seconds; 3) function to parse values into sensor structure
2:0e2ef866af95 2016-07-10 JMF Adding in WNC code from Fred
1:af7a42f7d465 2016-07-09 JMF Adding string encode/decode;
0:9d5134074d84 2016-07-08 JMF Initial version of AT&T_Avnet Shape Hackathon WNC Shield board