Daiki Kato / Mbed OS GR-PEACH_HVC-P2_sample_client

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

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

Required hardware

• GR-PEACH ( https://developer.mbed.org/platforms/Renesas-GR-PEACH/ )
• HVC-P2( https://developer.mbed.org/teams/Renesas/code/GR-PEACH_HVC-P2_sample/ )
• LCD Shield ( https://developer.mbed.org/teams/Renesas/wiki/LCD-shield )
• BP3595 ( https://developer.mbed.org/components/BP3595-for-GR-PEACH/ )
• Ethernet cable and connection to the internet
  
  

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:

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

// 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

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

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

"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

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

Simplify UPD and IPv4/IPv6 selections



Idea is that MESH has to have hard-coded IPv6 server address, because

it does not have DNS capability. Other networks should have.



Also, UDP must be used with MESH - other networks we want to default to

TCP because it is typically more reliable (UDP gets closed due to firewalls).



Thirdly, IPv4/IPv6 selection should now happen automatically through

the mbed_app.json selections with no need to modify the .h-file anymore

by modifying the

            "lwip.ipv4-enabled": false,

            "lwip.ipv6-enabled": true

selections accordingly.



.

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