Make NTU Hackathon
a simple mbed client example
Fork of
mbed-os-example-client
by 
mbed-os-examples
docs/radio_module_identify.md@63:f725470c419a, 2017-02-08 (annotated)
- Committer:
- Maggie17
- Date:
- Wed Feb 08 03:23:16 2017 +0000
- Revision:
- 63:f725470c419a
- Parent:
- 0:7d5ec759888b
For Make NTU Hackathon;
Who changed what in which revision?
| User | Revision | Line number | New 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 |  |
| Yogesh Pande |
0:7d5ec759888b | 15 | |
| Yogesh Pande |
0:7d5ec759888b | 16 | * For the gateway router, see the image below: |
| Yogesh Pande |
0:7d5ec759888b | 17 |  |