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.


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


#define TCPIP_THREAD_STACKSIZE      1024
#define TCPIP_THREAD_STACKSIZE      2048


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 and log in with your mbed account
  2. On mbed Device Connector, go to 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:


    "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 ( )
  2. Mount BP3595 onto GR-PEACH
  3. Close GR-PEACH's JP21 (
  4. In the mbed_app.json file, change


    "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:


"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:


    "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.

Tue Dec 13 13:45:11 2016 +0000
configs/*.json based configurations (#140)

* configs/*.json based configurations

Per Marcelo Salazar's proposal add configuration examples to a configs-folder.
By default the repo does not anymore have an mbed_app.json at all, but one should
copy one of the example configs, potentially modify it and use it.

Add mbedignore files to avoid the compilation problems.


* Clarify connection types per bearer

Mesh-networking ONLY supports UDP, others support both. Table to
illustrate UPD/TCP modes per network bearer.

Commit copied from

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mbed_official 45:b150e0aa009c 1 {
mbed_official 45:b150e0aa009c 2 "config": {
mbed_official 45:b150e0aa009c 3 "network-interface":{
mbed_official 45:b150e0aa009c 4 "help": "options are ETHERNET,WIFI,MESH_LOWPAN_ND,MESH_THREAD",
mbed_official 45:b150e0aa009c 5 "value": "MESH_LOWPAN_ND"
mbed_official 45:b150e0aa009c 6 },
mbed_official 45:b150e0aa009c 7 "mesh_radio_type": {
mbed_official 45:b150e0aa009c 8 "help": "options are ATMEL, MCR20",
mbed_official 45:b150e0aa009c 9 "value": "ATMEL"
mbed_official 45:b150e0aa009c 10 }
mbed_official 45:b150e0aa009c 11 },
mbed_official 45:b150e0aa009c 12 "macros": ["MBEDTLS_USER_CONFIG_FILE=\"mbedtls_mbed_client_config.h\""],
mbed_official 45:b150e0aa009c 13 "target_overrides": {
mbed_official 45:b150e0aa009c 14 "*": {
mbed_official 45:b150e0aa009c 15 "target.features_add": ["NANOSTACK", "LOWPAN_ROUTER", "COMMON_PAL"],
mbed_official 45:b150e0aa009c 16 "mbed-mesh-api.6lowpan-nd-channel-page": 0,
mbed_official 45:b150e0aa009c 17 "mbed-mesh-api.6lowpan-nd-channel": 18,
mbed_official 45:b150e0aa009c 18 "mbed-trace.enable": 0
mbed_official 45:b150e0aa009c 19 }
mbed_official 45:b150e0aa009c 20 }
mbed_official 45:b150e0aa009c 21 }