ST / Mbed OS mbed-os-example-client-IKS01Ax

mbedOS client example, modified to push X-Nucleo-IKS01A1/2 Environmental Sensor data to mbed Cloud Connector.

Dependencies:   X_NUCLEO_IKS01A1 X_NUCLEO_IKS01A2

The application is derived from the official mbedOS client example (link) and has been tested using a X-NUCLEO-IKS01A2 (default) or a X-NUCLEO-IKS01A1 motion and environmental sensors expansion board connected to a ST NUCLEO-F429ZI platform.
The following steps should be performed to make the application work:

  • Register and login into ARM mbed Connector.
  • Replace the default and empty security.h file with the one associated with your account and provided by the Connector (Security Credentials menu).
  • In order to use X-NUCLEO-IKS01A1 instead of default X-NUCLEO-IKS02A1 comment out the IKS01A2 macro definition in main.cpp file.
  • Choose NUCLEO-F429ZI as a target either from online compiler or from CLI, compile and flash.
  • Connect the board to your ethernet network, open a serial terminal (params 115200N1) and wait that the client is connected to the mbed Connector.
  • Press user button to start acquiring and pushing the environmental (pressure, temperature and humidity) data.

Note: environmental data are expressed using IPSO representation based on OMA LWM2M standard.

docs/radio_module_identify.md@0:003e60a0deb8, 2017-04-26 (annotated)

Committer:
nikapov
Date:
Wed Apr 26 18:23:56 2017 +0200
Revision:
0:003e60a0deb8
First version.

Original repository: https://github.com/ARMmbed/mbed-os-example-client

Version hash: 629b972f41109fd1b54bb755ea454d736a50069b

Who changed what in which revision?

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