Tomo Yamanaka / Mbed OS GR-LYCHEE_mbed-os-client-ZXingSample

Mbed Client sample for GR-LYCHEE where ZXing is incorporated.

Dependencies:   DisplayApp AsciiFont

Fork of GR-PEACH_mbed-os-client-ZXingSample by Renesas

Overview

This sample program shows how to use mbed Client together with ZXing which is an open-source, multi-format 1D/2D barcode image processing library. For more info on ZXing, please refer to https://github.com/zxing/zxing.

Required hardware

Application setup

  1. Select the connection type. For details, please refer to the following wiki:
    https://os.mbed.com/users/1050186/code/GR-LYCHEE_mbed-os-client-ZXingSample/wiki/Connection-type.
  2. Set the client credentials. For details, please refer to the following wiki:
    https://os.mbed.com/users/1050186/code/GR-LYCHEE_mbed-os-client-ZXingSample/wiki/Client-credentials.
  3. Change Wifi settings. For details, please refer to the following wiki:
    https://os.mbed.com/users/1050186/code/GR-LYCHEE_mbed-os-client-ZXingSample/wiki/Wifi-settings.

Building the example

To build this example:

  1. Import this example onto mbed Compiler.
  2. Configure the example in accordance with Application setup.
  3. Compile the example on mbed Compiler and download the resultant binary file.
  4. Plug the micro-USB cable into the OpenSDA port which lies on the next to the RESET button.
  5. Copy the binary previously downloaded to your PC to GR-LYCHEE to flash this example. When the copy is successfully completed, the board is ready to work.
  6. Press the RESET button on the board to run the example.
  7. For verification, please refer to the following wiki:
    https://os.mbed.com/users/1050186/code/GR-LYCHEE_mbed-os-client-ZXingSample/wiki/Monitoring-the-application.

Application resources

This example exposes four resources listed below:

  1. 3202/0/5700. Decode result of barcode data input from camera (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 green, yellow, orange and red is acceptable (PUT).

docs/radio_module_identify.md@22:a3cd35c5cff0, 2018-12-18 (annotated)

Committer:
1050186
Date:
Tue Dec 18 07:37:37 2018 +0000
Revision:
22:a3cd35c5cff0
Parent:
0:eb73febb2bba 
Modify README.md file.

Who changed what in which revision?

UserRevisionLine numberNew contents of line
<> 0:eb73febb2bba 1 ## Radio module identification
<> 0:eb73febb2bba 2
<> 0:eb73febb2bba 3 * Make sure that you are using the same radio modules on both server and client sides:
<> 0:eb73febb2bba 4
<> 0:eb73febb2bba 5 * If the radio module on the gateway router supports the 2.4 GHz frequency band, the client side must have an mbed 6LoWPAN shield that uses a 2.4 GHz radio module (such as Atmel AT86RF233).
<> 0:eb73febb2bba 6
<> 0:eb73febb2bba 7 * If the radio module on the gateway router supports the sub-GHz frequency band, the client side must have an mbed 6LoWPAN shield that uses a sub-GHz radio module (such as Atmel AT86RF212B).
<> 0:eb73febb2bba 8
<> 0:eb73febb2bba 9 * An easy way to identify which frequency band your setup uses is to check the **Antenna size** on the radio module:
<> 0:eb73febb2bba 10
<> 0:eb73febb2bba 11 * The sub-GHz band antenna is larger than the 2.4 GHz antenna.
<> 0:eb73febb2bba 12
<> 0:eb73febb2bba 13 * For the client side (mbed 6LoWPAN shield connected to an FRDM-K64F board), see the image below:
<> 0:eb73febb2bba 14 ![](img/Radio_Identifications.png)
<> 0:eb73febb2bba 15
<> 0:eb73febb2bba 16 * For the gateway router, see the image below:
<> 0:eb73febb2bba 17 ![](img/Radio_Identifications_GW.png)