Skip to content
This repository was archived by the owner on Apr 24, 2019. It is now read-only.

Commit 665a6b7

Browse files
committed
Added docs and img folders
radio_module_identify.md and related images added.
1 parent e837888 commit 665a6b7

File tree

3 files changed

+17
-0
lines changed

3 files changed

+17
-0
lines changed

docs/img/Radio_Identifications.png

1.62 MB
Loading
1.9 MB
Loading

docs/radio_module_identify.md

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

0 commit comments

Comments
 (0)