Send the data of GR-PEACH_HVC-P2_sample to the cloud.

Dependencies:   AsciiFont GR-PEACH_video GraphicsFramework LCD_shield_config R_BSP USBHost_custom easy-connect-gr-peach

Fork of mbed-os-example-client by mbed-os-examples

Note at the time of sample import

Please not check the "Update all libraries to the latest version" at the time of import.

Warning!

When exporting and using it, increase the following stack size.

mbed-os/features/FEATURE_LWIP/lwip-interface/lwipopts.h

#define TCPIP_THREAD_STACKSIZE      1024
->
#define TCPIP_THREAD_STACKSIZE      2048

Overview

This is a sample to send the analysis result of GR-PEACH_HVC-P2_sample to the cloud using mbed-client. Please refer to following for operation of HVC-P2.

Import programGR-PEACH_HVC-P2_sample

Sample to operate omron HVC-P2 on GR-PEACH.


Required hardware

Application setup

Client credentials

To register the application to mbed Device Connector, you need to create and set the client side certificate.

  1. Go to https://connector.mbed.com/ and log in with your mbed account
  2. On mbed Device Connector, go to https://connector.mbed.com/#credentials and click the Get my device security credentials button to get new credentials for your device.
  3. Replace the contents in security.h of this example with content copied above.

Ethernet settings

This sample uses Ethernet as the default connection type. To change the connection type, set WIFI_BP3595 in mbed_app.json:

mbed_app.json

"network-interface":{
    "help": "Options are ETHERNET, WIFI_ESP8266, WIFI_BP3595",
    "value": "ETHERNET"
},


To specify MAC address, add fllowing function to main.cpp. (When using Wifi, setting of MAC address is not necessary.)

Specify MAC address

// set mac address
void mbed_mac_address(char *mac) {
    mac[0] = 0x00;
    mac[1] = 0x02;
    mac[2] = 0xF7;
    mac[3] = 0xF0;
    mac[4] = 0x00;
    mac[5] = 0x00;
}


Wifi settings

This example can use BP3595 Wifi Interface for managing the wireless connectivity. To run this example using Wifi, you need:

  1. A BP3595 Wifi module ( https://developer.mbed.org/components/BP3595-for-GR-PEACH/ )
  2. Mount BP3595 onto GR-PEACH
  3. Close GR-PEACH's JP21 (https://developer.mbed.org/teams/Renesas/wiki/Jumper-settings-of-GR-PEACH)
  4. In the mbed_app.json file, change

mbed_app.json

"network-interface":{
    "help": "Options are ETHERNET, WIFI_ESP8266, WIFI_BP3595",
    "value": "WIFI_BP3595"
},


Provide your Wifi SSID and password here and leave \" in the beginning and end of your SSID and password as shown in the example below:

mbed_app.json

"wifi-ssid": {
    "help": "WiFi SSID",
    "value": "\"SSID\""
},
"wifi-password": {
    "help": "WIFI Password",
    "value": "\"Password\""
}


Specify the security type for connection to be used. When the security type is WPA2, you need to specify NSAPI_SECURITY_WAP as follows:

mbed_app.json

"wifi-security":{
    "help": "Options are NSAPI_SECURITY_WEP, NSAPI_SECURITY_WPA, NSAPI_SECURITY_WPA2, NSAPI_SECURITY_WPA_WPA2",
    "value": "NSAPI_SECURITY_WEP"
},

By default, NSAPI_SECURITY_WPA_WPA2 is specified here.

Application resources

This example exposes four resources listed below:

  1. 3202/0/5700. Recognition result from HVC-P2 (GET).
  2. 3201/0/5850. Blink function, blinks LED when executed (POST).
  3. 3201/0/5853. Blink pattern, used by the blink function to determine how to blink. In the format of 1000:500:1000:500:1000:500 (PUT).
  4. 3201/0/5855. Blink color, used by the blink function. Any of red, green, blue, cyan, yellow and magenta is acceptable (PUT).

For more info on how to get notifications when resource 1 changes, or how to use resource 2, 3 and 4, please look at

Import programGR-PEACH_mbed-connector-ZXingSample-node

Node.js based Web Application for mbed Device Connector specific to GR-PEACH_mbed-os-client-ZXingSample

# This is a Web Application for GR-PEACH_mbed-os-client-ZXingSample, but it can also be used for this sample.

Committer:
mbed_official
Date:
Thu Jul 28 23:14:13 2016 +0100
Revision:
3:e98843ff559d
Updating mbed-os.lib with mbed-os-5.1.0-rc3


Commit copied from ./src/github.com/ARMmbed/mbed-os-example-client

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mbed_official 3:e98843ff559d 1 # Object files
mbed_official 3:e98843ff559d 2 *.o
mbed_official 3:e98843ff559d 3 *.ko
mbed_official 3:e98843ff559d 4 *.obj
mbed_official 3:e98843ff559d 5 *.elf
mbed_official 3:e98843ff559d 6
mbed_official 3:e98843ff559d 7 # Precompiled Headers
mbed_official 3:e98843ff559d 8 *.gch
mbed_official 3:e98843ff559d 9 *.pch
mbed_official 3:e98843ff559d 10
mbed_official 3:e98843ff559d 11 # Libraries
mbed_official 3:e98843ff559d 12 *.a
mbed_official 3:e98843ff559d 13 *.la
mbed_official 3:e98843ff559d 14 *.lo
mbed_official 3:e98843ff559d 15
mbed_official 3:e98843ff559d 16 # Shared objects (inc. Windows DLLs)
mbed_official 3:e98843ff559d 17 *.dll
mbed_official 3:e98843ff559d 18 *.so
mbed_official 3:e98843ff559d 19 *.so.*
mbed_official 3:e98843ff559d 20 *.dylib
mbed_official 3:e98843ff559d 21
mbed_official 3:e98843ff559d 22 # Executables
mbed_official 3:e98843ff559d 23 *.exe
mbed_official 3:e98843ff559d 24 *.out
mbed_official 3:e98843ff559d 25 *.app
mbed_official 3:e98843ff559d 26 *.i*86
mbed_official 3:e98843ff559d 27 *.x86_64
mbed_official 3:e98843ff559d 28 *.hex
mbed_official 3:e98843ff559d 29
mbed_official 3:e98843ff559d 30 yotta_modules/
mbed_official 3:e98843ff559d 31 yotta_targets/
mbed_official 3:e98843ff559d 32 build/
mbed_official 3:e98843ff559d 33 .yotta.json
mbed_official 3:e98843ff559d 34 source/security.h