Close call reporter in C++

Get access to the new Intel® IoT Developer Kit, a complete hardware and software solution that allows developers to create exciting new solutions with the Intel® Galileo and Intel® Edison boards. Visit the Intel® Developer Zone for IoT.

Introduction

This close-call fleet driving reporter application is part of a series of how-to Internet of Things (IoT) code sample exercises using the Intel® IoT Developer Kit, Intel® Edison board, Intel® IoT Gateway, cloud platforms, APIs, and other technologies.

From this exercise, developers will learn how to:

• Connect the Intel® Edison board or Intel® IoT Gateway, computing platforms designed for prototyping and producing IoT and wearable computing products.
• Interface with the Intel® Edison board or Arduino 101* (branded Genuino 101* outside the U.S.) board IO and sensor repository using MRAA and UPM from the Intel® IoT Developer Kit, a complete hardware and software solution to help developers explore the IoT and implement innovative projects.
• Run these code samples in the Intel® System Studio IoT Edition (Eclipse* IDE for C/C++ and Java* development) for creating applications that interact with sensors and actuators, enabling a quick start for developing software for the Intel® Edison board or Intel® Galileo board.
• Store the close-call data using Azure Redis Cache* from Microsoft, Redis Store* from IBM Bluemix*, or Elasticache* using Redis* from Amazon Web Services (AWS)*, different cloud services for connecting IoT solutions including data analysis, machine learning, and a variety of productivity tools to simplify the process of connecting your sensors to the cloud and getting your IoT project up and running quickly.
• Connect to a server using IoT Hub from Microsoft Azure*, IoT from IBM Bluemix*, IoT from Amazon Web Services (AWS)*, AT&T M2X*, Predix* from GE, or SAP Cloud Platform* IoT, different cloud-based IoT platforms for machine to machine communication.

What it is

Using an Intel® Edison board or Intel® IoT Gateway, this project lets you create a close-call fleet driving reporter that:

• monitors the Grove* IR Distance Interrupter;
• monitors the Grove* GPS;
• keeps track of close calls and logs them using cloud-based data storage.

How it works

This close-call reporter system monitors the direction in which the Grove* IR Distance Interrupter is pointed.

It also keeps track of the GPS coordinates, updating frequently to ensure accurate data.

Optionally, data can be stored using your own Microsoft Azure*, IBM Bluemix*, AT&T M2X*, AWS*, Predix*, or SAP* account.

Hardware requirements

Grove* Transportation and Safety Kit containing:

1. Intel® Edison board with an Arduino* breakout board
2. Grove Base Shield V2
3. Grove IR Distance Interrupter
4. Grove GPS

DFRobot* Starter Kit for Intel® Edison, containing:

1. Intel® Edison module with an Arduino* breakout board
2. IR Distance Sensor
3. GPS
4. I/O Expansion Shield

Software requirements

1. Intel® System Studio (Eclipse IDE for C/C++ and Java* development)
2. Microsoft Azure*, IBM Bluemix*, AT&T M2X*, AWS*, Predix*, or SAP* account (optional)

How to set up

This sample is already one of the IoT examples included in Intel® System Studio. To start using it, follow these steps:

1. From the main menu, select Intel® IoT > Import IoT Examples.
   
2. Expand the tree view for C++ > How To Code Samples > Close Call Reporter and click Import Example.
   
3. Select your developer board from the selection window then select Next.
   
4. Select Intel® IoT C/C++ project from the Select a project type window then click Next.
   
5. Select Yocto from the Selct target OS dropdown menu then click Next.
   
6. The next tab will ask for connection name and target name. If you do not know these click Search Target.
   
7. Select your Edison from the dropdown list. Select OK.
   
8. Your connection name and target name should be filled in. Select Finish.
   
9. A new window will open for you and you will need to choose a name for your project and click Next.
   
10. Your project source files will now be available on the on the upper left of your IDE by default.
    

Connecting the Grove* sensors

You need to have a Grove* Base Shield V2 connected to an Arduino* compatible breakout board to plug all the Grove devices into the Grove Base Shield V2. Make sure you have the tiny VCC switch on the Grove Base Shield V2 set to 5V.

1. Plug one end of a Grove cable into the Grove IR Distance Interrupter, and connect the other end to the D2 port on the Grove Base Shield V2.
   
2. Plug one end of a Grove cable into the Grove GPS, and connect the other end to the UART port on the Grove Base Shield V2.

Connecting the DFRobot* sensors

You need to have a DFRobot* I/O Expansion Shield connected to an Arduino* compatible breakout board to plug all the DFRobot* devices into the DFRobot* I/O Expansion Shield.

1. Plug one end of a DFRobot cable into the IR Distance Sensor, and connect the other end to the D4 port on the I/O Expansion Shield.

2. Plug the attached GPS cable TX (white) to the I/O Expansion Shield's RX pin. Plug the attached GPS cable RX (black) to the I/O Expansion Shield's TX pin. Plug the attached GPS cable power (red) to any of the I/O Expansion Shield's 5V pins. Plug the attached GPS cable ground (thicker black) to any of the I/O Expansion Shield's GND.

Intel® Edison board setup

This example also uses the restclient-cpp library to perform REST calls to the remote data server. The code can be found in the lib directory. The restclient-cpp library requires the libcurl package, which is already installed on the Intel® Edison board by default.

Intel® IoT Gateway setup

You can run this example using an Intel® IoT Gateway connected to an Arduino 101* (branded Genuino 101* outside the U.S.).

Make sure your Intel® IoT Gateway is setup, by following the directions on the web site here:

https://software.intel.com/en-us/getting-started-with-intel-iot-gateways-and-iotdk

The Arduino 101* (branded Genuino 101* outside the U.S.) needs to have the Firmata* firmware installed. If you have IMRAA installed on your gateway, this will be done automatically. Otherwise, install the StandardFirmata or ConfigurableFirmata sketch manually onto your Arduino 101* (branded Genuino 101* outside the U.S.).

IoT cloud setup

You can optionally store the data generated by this sample program using cloud-based IoT platforms from Microsoft Azure*, IBM Bluemix*, AT&T M2X*, AWS*, Predix*, or SAP*.

For information on how to connect to your own cloud server, go to:

https://github.com/intel-iot-devkit/iot-samples-cloud-setup

Data store server setup

Optionally, you can store the data generated by this sample program in a back-end database deployed using Microsoft Azure*, IBM Bluemix*, or AWS* along with Node.js*, and a Redis* data store.

For information on how to set up your own cloud data server, go to:

https://github.com/intel-iot-devkit/intel-iot-examples-datastore

Configuring the example for your hardware kit

To configure the example for the specific hardware kit that you are using, either Grove* or DFRobot*:

1. From the main menu, select Project > Properties dialog box is displayed.
2. Expand the section C/C++ General.
   Click on the Paths and Symbols sub-section, and click on the Symbols tab.
3. Now click on GNU C++, and click on the Add button.
4. In the Name field, enter "INTEL_IOT_KIT". In the Value field, enter either "GROVEKIT" (this is the default) or "DFROBOTKIT", depending on which hardware kit you wish to use.
5. Your new name symbol and value will now be displayed. Click OK.
6. Another dialog box will appear asking to rebuild project. Click OK.

Connecting your Intel® Edison board to Intel® System Studio

1. On the Target SSH Connections tab, right-click your device and select Connect.
   If prompted for the username and password, the username is root and the password is whatever you specified when configuring the Intel® Edison board.

Intel® IoT Gateway setup

You can run this example using an Intel® IoT Gateway connected to an Arduino 101.

Make sure your Intel® IoT Gateway is setup, by following the directions on the web site here:

https://software.intel.com/en-us/getting-started-with-intel-iot-gateways-and-iotdk

The Arduino 101 needs to have the Firmata* firmware installed. If you have IMRAA installed on your gateway, this will be done automatically. Otherwise, install the StandardFirmata or ConfigurableFirmata sketch manually onto your Arduino 101* (branded Genuino 101* outside the U.S.).

Running the example with the cloud server

To run the example with the optional backend data store, you need to set the SERVER and AUTH_TOKEN environment variables. You can do this in Intel® System Studio as follows:

1. From the Run menu, select Run Configurations.
   The Run Configurations dialog box is displayed.

2. Under C/C++ Remote Application, click close-call.
   This displays the information for the application.

3. In the Commands to execute before application field, add the following environment variables, except use the server and authentication token that correspond to your own setup:

   chmod 755 /tmp/close-call;export SERVER="http://intel-examples.azurewebsites.net/logger/close-call"; export AUTH_TOKEN="YOURTOKEN"
   

4. Click Apply to save your new environment variables.

Now when you run your program using the Run button, it should be able to call your server to save the data right from the Intel® Edison board or Intel® IoT Gateway.

Running the code on the Intel® Edison board or Intel® IoT Gateway

When you're ready to run the example, click Run at the top menu bar in Intel® System Studio.

This compiles the program using the Cross G++ Compiler, links it using the Cross G++ Linker, transfers the binary to the Intel® Edison board or Intel® IoT Gateway, and then executes it on the board itself.

After running the program, you should see output similar to the one in the image below.

IMPORTANT NOTICE: This software is sample software. It is not designed or intended for use in any medical, life-saving or life-sustaining systems, transportation systems, nuclear systems, or for any other mission-critical application in which the failure of the system could lead to critical injury or death. The software may not be fully tested and may contain bugs or errors; it may not be intended or suitable for commercial release. No regulatory approvals for the software have been obtained, and therefore software may not be certified for use in certain countries or environments.