mbed-os-examples / Mbed OS mbed-os-example-client
Committer:
mbed_official
Date:
Fri Dec 02 08:45:12 2016 +0000
Revision:
37:9a9428fc4b26
Parent:
0:7d5ec759888b
Switch the default transport-mode to TCP

The UDP tends to be quite unreliable with IPv4 and NAT and this
can give bad experience for new users. We should default to TCP
to provide more stable platform for testing the capabilities.

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

Who changed what in which revision?

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