Sample program showing how to connect GR-PEACH into Watson IoT through mbed Connector and Watson's Connector Bridge

Dependencies:   AsciiFont DisplayApp GR-PEACH_video LCD_shield_config LWIPBP3595Interface_STA_for_mbed-os USBDevice

Overview

This sample program shows how to connect GR-PEACH into Watson IoT through mbed Connector and Watson's Connector Bridge. Note that this program is derived from https://github.com/ARMmbed/mbed-ethernet-sample-techcon2016.

In this program, at first, the barcode data input from camera is decoded on GR-PEACH using ZXing which is an open-source, multi-format 1D/2D barcode image processing library. Then, the decoded string is sent to Watson IoT via mbed Device Connector and Watson's Connector Bridge. At last, the delivered string is confirmed via NodeRED flow.

Required hardware

Application setup

  1. Select the connection type. For details, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Connection-type.
  2. Set the client credentials. For details, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Client-credentials.
  3. Change Ethernet settings. For details, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Ethernet-settings.
  4. Change Wifi settings. For details, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Wifi-settings.

Building this sample program

  1. Import this sample program onto mbed Compiler.
  2. Configure this sample program in accordance with Application setup.
  3. Compile the example on mbed Compiler and download the resultant binary file.
  4. Plug the Ethernet cable into GR-PEACH if you are using Ethernet mode. /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen7.png
  5. Plug the micro-USB cable into the OpenSDA port with lies on the next to the RESET button.
  6. Copy the binary previously downloaded to your PC to GR-PEACH to flash this sample program. When the copy is successfully completed, the board is ready to work.
  7. Press the RESET button on the board to run this sample program.
  8. For verification, please refer to the following wiki:
    https://developer.mbed.org/teams/Renesas/code/mbed-os_Watson-IoT_ZXing_sample/wiki/Monitoring-the-application.

Application resources

This sample program exposes two resources listed below:

  1. /311/0/5850 : Trigger to toggle LED on GR-PEACH (PUT). When "1" is sent to this resource by PUT method, LED should be turned off. Otherwise, LED should be turned on.
  2. /888/0/7700: Decode result of barcode data input from camera (GET)

Setup of Watson IoT

  1. You should create Watson IoT Instance by the following procedure:
    • Login IBM Bluemix from https://console.ng.bluemix.net/ and login it.
    • Select Services as follows: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen6.png
    • Select Internet of Things" as follows: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen7_1.png
    • Press Get Started as follows: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen8.png
    • Configure Watson IoT Instance
      • Leave unbound /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen9.png
      • Select the Free plan, then click Create /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen10.png

  2. You should create Watson IoT Application Credentials Once you successfully create Watson IoT Instance, you should see the following Watson IoT dashboard: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen11.png
    • On dashboard, launch the Connect your devices dashboard /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen12.png
    • Click APPS /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen13.png
    • Click Generate API Key /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen14_1.png
    • Record the API Key and Authenticatoin Token. Then click Generate after adding a comment /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen15.png Note that these two values will be needed in the later step.
  3. Watson IoT NodeRED Application should be created in accordance with the following procedure:
    • Go back to your Bluemix Dashboard: https://console.ng.bluemix.net
    • Click Create Application /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen16.png
    • Select Node-RED Starter /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen17.png
    • Enter a unique App name and Click Create /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen18.png
    • Application will Stage after a few minutes
    • Application will report app is running when the staging has completed
  4. Watson NodeRED Application should be binded to Watson IoT instance
    • You can now see the dashboard below: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen19.png
    • Click Connections. Then, press Connect Existing /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen20.png
    • Click on Watson IoT Instance badge. Then, press Connect /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen21.png
    • NodeRED application will restage. This will take a while. Please wait for Your app is running state /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen22.png /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen23.png
  5. You should acquire mbed Device Connector DOMAIN value
    • Go to the mbed Device Connector Dashboard: https://connector.mbed.com and log in /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen41.png
    • Select Access Key in order to create a new token /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen42.png
    • Click CREATE NEW ACCESS KEY and enter a unique name. Then, push ADD bution /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen43.png
    • an API token is generated. Need to save the generated string for later steps /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen44.png
  1. You should configure Watson IoT ARM mbed Connector Bridge
    • Go back to the Watson IoT Dashboard and select Extensions /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen24.png
    • Press Add Extension /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen25.png
    • Add ARM mbed Connector /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen26_1.png
    • Setup the bridge /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen27.png
    • Enter your Connector API Token to Access Key and MBED_DOMAIN to Domain Id, respectively. Then, click Check Connection /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen28.png
    • If the connection is successfully established, you can see Connection Established. Then, press Done /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen29.png
  2. NodeRED Flow Example should be imported
    • Open NODEFLOW_GR-PEACH.txt
    • Navigate to the URL that you recorded earlier for your Watson IoT NodeRED Application (i.e. http://<app name>.mybluemix.net) and Select Go to your NodeRED flow editor /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen30.png
    • Select menu, Import and Clipboard /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen31.png
    • Paste the entire contents of JSON code described in NODEFLOW_GR-PEACH.txt and click Import /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen32.png
  3. Watson IoT Application Node Flow should be configured
    • Double-click input node and link them to your Watson IoT instance. /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen33.png
    • Click on the edit button /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen34.png
    • First enter arbitrary name. Then, Watson API Key and Watson Auth Token previously acquired. Finally, press Add to save /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen35.png
    • Enter MBED_ENDPOINT_NAME in security.h as Device ID. Then, press Done to save /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen36.png
    • Double-click output node /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen37.png
    • Edit API Key and Device Id in the same manner as that for input node
    • Click LED OFF and LED ON node and replace MBED_ENDPOINT_NAME_GOES_HERE with MBED_ENDPOINT_NAME as shown below: /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen38.png
    • Click Deproy to deploy NodeRED application /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen39.png
  4. Invoke sample program
    • Press the reset button on GR-PEACH
    • The decode result of barcode data should be shown in debug window /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen40_1.png
    • Also, you can toggle LED by clicking Turn LED OFF and Turn LED ON injection node /media/uploads/HinoNaka/mbed-os_watson-iot_zxing_sample_screen40_2.png
Revision:
0:ad834d403a8c
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/mbedConnectorInterface/mbed-connector-interface/DeviceManagementResponder.h	Thu Nov 24 13:59:16 2016 +0900
@@ -0,0 +1,181 @@
+/**
+ * @file    DeviceManagementResponder.h
+ * @brief   mbed CoAP Endpoint Device Management Responder class
+ * @author  Doug Anson
+ * @version 1.0
+ * @see
+ *
+ * Copyright (c) 2016
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *     http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+#ifndef __DEVICE_MANAGEMENT_RESPONDER_H__
+#define __DEVICE_MANAGEMENT_RESPONDER_H__
+
+// Logger
+#include "mbed-connector-interface/Logger.h"
+
+// Authenticator Support
+#include "mbed-connector-interface/Authenticator.h"
+
+// invocation handler signature
+typedef void (*initialize_fn)(const void *logger);
+typedef bool (*manifest_fn)(const void *ep,const void *logger,const void *manifest,uint32_t manifest_length);
+typedef bool (*image_set_fn)(const void *ep,const void *logger,const void *image,uint32_t image_length);   
+typedef bool (*responder_fn)(const void *ep,const void *logger,const void *data); 
+
+class DeviceManagementResponder {
+    public:
+        /**
+        Default constructor
+        @param logger input logger instance
+        @param authenticator input authentication instance
+        */
+        DeviceManagementResponder(const Logger *logger,const Authenticator *authenticator);
+        
+        /**
+        Copy constructor
+        @param resource input the DeviceManagementResponder that is to be deep copied
+        */
+        DeviceManagementResponder(const DeviceManagementResponder &manager);
+    
+        /**
+        Destructor
+        */
+        virtual ~DeviceManagementResponder();
+        
+        /**
+        Set the Endpoint instance
+        @param ep input the endpoint instance pointer
+        */
+        void setEndpoint(const void *ep);
+        
+        /** 
+        Set our Initialize handler function
+        @param initialize_fn input the device initialize function pointer
+        */
+        void setInitializeHandler(initialize_fn initialize_fn);
+        
+        /** 
+        Set our Reboot Responder handler function
+        @param reboot_responder_fn input the device reboot responder function pointer
+        */
+        void setRebootResponderHandler(responder_fn reboot_responder_fn);
+        
+        /** 
+        Set our Reset Responder handler function
+        @param reset_responder_fn input the device reset responder function pointer
+        */
+        void setResetResponderHandler(responder_fn reset_responder_fn);
+        
+        /** 
+        Set our FOTA manifest handler function
+        @param fota_manifest_fn input the FOTA manifest handler function pointer
+        */
+        void setFOTAManifestHandler(manifest_fn fota_manifest_fn);
+        
+        /** 
+        Set our FOTA image set handler function
+        @param fota_image_set_fn input the FOTA image set function pointer
+        */
+        void setFOTAImageHandler(image_set_fn fota_image_set_fn);
+        
+        /** 
+        Set our FOTA invocation handler function
+        @param fota_invocation_fn input the FOTA invocation handler function pointer
+        */
+        void setFOTAInvocationHandler(responder_fn fota_invocation_fn);
+        
+        /**
+        ACTION: Deregister device
+        @param challenge input the input authentication challenge
+        */
+        virtual void deregisterDevice(const void *challenge);
+        
+        /**
+        ACTION: Reboot device
+        @param challenge input the input authentication challenge
+        */
+        virtual void rebootDevice(const void *challenge);
+        
+        /**
+        ACTION: Reset device 
+        @param challenge input the input authentication challenge
+        */
+        virtual void resetDevice(const void *challenge);
+        
+        /**
+        Set our FOTA manifest
+        @param manifest input the FOTA manifest
+        @param manifest_length input the length of the FOTA manifest
+        */
+        virtual void setFOTAManifest(char *manifest,uint32_t manifest_length);
+        
+        /**
+        Get our FOTA manifest
+        @return the FOTA manifest
+        */
+        virtual char *getFOTAManifest();
+        
+        /**
+        Get our FOTA manifest length
+        @return the FOTA manifest length
+        */
+        virtual uint32_t getFOTAManifestLength();
+        
+        /**
+        Set our FOTA image
+        @param fota_image input the FOTA image
+        @param fota_image_length input the length of the fota image
+        */
+        virtual void setFOTAImage(void *fota_image,uint32_t fota_image_length);
+        
+        /**
+        Get our FOTA image
+        @return the FOTA image
+        */
+        virtual void *getFOTAImage();
+        
+        /**
+        Get our FOTA image length
+        @return the FOTA image length
+        */
+        virtual uint32_t getFOTAImageLength();
+        
+        /**
+        ACTION: Invoke FOTA (default: empty action)
+        @param challenge input the input authentication challenge
+        */
+        virtual void invokeFOTA(const void *challenge);
+    
+    private:
+        Logger                      *m_logger;
+        Authenticator               *m_authenticator;
+        void                        *m_endpoint;
+        char                        *m_manifest;
+        int                          m_manifest_length;
+        void                        *m_fota_image;
+        uint32_t                     m_fota_image_length;
+        
+        initialize_fn                m_initialize_fn;
+        responder_fn                 m_reboot_responder_fn;
+        responder_fn                 m_reset_responder_fn;
+        manifest_fn                  m_fota_manifest_fn;
+        image_set_fn                 m_fota_image_set_fn;
+        responder_fn                 m_fota_invocation_fn;
+        
+        bool                         authenticate(const void *challenge);
+};
+
+#endif // __DEVICE_MANAGEMENT_RESPONDER_H__
\ No newline at end of file