Difference between revisions of "Node Specifications"

From CityLab Testbed
Jump to navigation Jump to search
Line 4: Line 4:
 
* WiFi 802.11ac on 2.4 GHz and 5GHz
 
* WiFi 802.11ac on 2.4 GHz and 5GHz
 
* Bluetooth 4.0 (with full BLE support)
 
* Bluetooth 4.0 (with full BLE support)
* IEEE 802.15.4 on 2.4 GHz and 868MHz
+
* IEEE 802.15.4 on 2.4 GHz and IEEE 802.15.4g 868MHz
 
* Dash7 on 433MHz and 868MHz
 
* Dash7 on 433MHz and 868MHz
 
* LoRaWAN on 868MHz (client only)
 
* LoRaWAN on 868MHz (client only)
Line 12: Line 12:
  
 
== Node Hardware ==
 
== Node Hardware ==
 
  
 
Each node uses a <b>[http://pcengines.ch/apu2c4.htm PCEngines apu2c4]</b> board as a central controller.
 
Each node uses a <b>[http://pcengines.ch/apu2c4.htm PCEngines apu2c4]</b> board as a central controller.
Line 33: Line 32:
  
 
== Connected USB Devices ==
 
== Connected USB Devices ==
=== OpenUSB ===
+
 
=== EZR USB ===
+
Each experiment node is equipped with a number of embedded wireless devices connected trough USB. These devices usually consist of a microcontroller with either an embedded or an add-on wireless radio.
=== WFM32GG+RFM95W ===
+
Each device is equipped with a JTAG/SWD-debugger for programming the device. If the device does not have an on-board debugger a standalone JTAG/SWD-debugger is provided for the device. Likewise each device is also equipped with a USB-to-serial converter to allow the device to communicate with the host. As with the JTAG-debugger the device is connected to a standalone USB-to-serial converter if it does not have one onboard.
 +
 
 +
=== OpenUSB (IEEE 802.15.4) ===
 +
 
 +
The OpenUSB mote consists of an [https://web.archive.org/web/20161221222441/www.openmote.com/hardware/openmote-cc2538-en.html OpenMote-CC2538] connected to an OpenUSB base board.
 +
It has the following features:
 +
* <b>MCU: </b> [http://www.ti.com/product/CC2538 TI CC2538] SoC (32K ram, 512K flash)
 +
* <b>2.4 GHz radio: </b> IEEE 802.15.4 tranceiver embedded in the MCU
 +
* <b>868 MHz radio: </b> [http://www.ti.com/product/CC1200 TI CC1200] general purpose tranceiver (compatible with IEEE 802.15.4g)
 +
 
 +
Serial & JTAG Interface:
 +
* <b>Serial communication: </b>[http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT232R.pdf FT232R] USB to serial converter (onboard)
 +
* <b>Debugger: </b>[https://www.olimex.com/Products/DSP/Emulators/TMS320-XDS100-V3/ Olimex TMS320-XDS100-V3] (standalone)
 +
 
 +
Please note that the JTAG debugger is (1) only supported in windows, (2) <b>not</b> required to flash/erase the OpenUSB mote and (3) only present to allow the system administrators to recover bricked OpenUSB motes. Flashing / Erasing the OpenUSB mote is done through the [http://processors.wiki.ti.com/index.php/CC2538_Bootloader_Backdoor serial] port. See the [[OpenUSB Tutorial]] for more information.
 +
 
 +
=== EZR USB (Dash 7) ===
 +
 
 +
The experiment node contains two [https://github.com/MOSAIC-LoPoW/dash7-ap-open-source-stack/tree/master/hardware/EZR32-USB EZRUSB] boards. These boards are identical except that one is equipped with a 433MHz radio front-end and the other one is equipped with an 868MHz radio front-end.
 +
These boards have the following features:
 +
* <b>MCU: </b> [https://www.silabs.com/products/wireless/proprietary/ezr32-leopard-gecko-sub-ghzEZR Leopard Gecko] SoC (32K ram, 256K flash)
 +
* <b>Radio: </b> general purpose, Dash7 compatible, 433MHz/868Mhz tranceiver embedded in the MCU
 +
 
 +
Serial & JTAG Interface:
 +
* <b>Serial communication:</b>[http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_CABLES.pdf FTDI TTL232R] USB to serial cable
 +
* <b>Debugger:</b>[https://www.olimex.com/Products/ARM/JTAG/ARM-USB-TINY-H/ Olimex ARM-USB-TINY-H] (standalone)
 +
 
 +
Please note that, for security reasons, the USB-port of the EZR USB is <b>not</b> connected to the host. Communication with the EZR USB module is only possible over the serial interface.
 +
 
 +
=== EFM32GG+RFM95W (LoRa) ===
 +
 
 +
LoRa(WAN) connectivity is provided through a [https://www.silabs.com/products/development-tools/mcu/32-bit/efm32-giant-gecko-starter-kit EFM Giant Gecko] development board connected to an RFM95W LoRa tranceiver.
 +
* <b> MCU: </b>[https://www.silabs.com/documents/public/data-sheets/EFM32GG990.pdf Silabs EFM32GG990F1024] (128K ram, 1024K flash)
 +
* <b>Radio: </b>[https://webshop.ideetron.nl/RFM95W?Lng=en RFM95W] 868MHz LoRa Tranceiver
 +
 
 +
Serial & JTAG Interface:
 +
* <b>Serial communication:</b>[https://www.sparkfun.com/products/12731 Sparkfun 232RL] USB to serial breakout board (standalone)
 +
* <b>Debugger:</b>[https://www.segger.com/products/debug-probes/j-link/models/j-link-plus/ JLink Plus] (onboard)
  
 
== Antennas ==
 
== Antennas ==

Revision as of 17:12, 30 January 2018

The electronics of the City of Things experiment nodes

There is currently only a single type of node available in the City of Things testbed. It consists of of an apu2c4 embedded pc with two WiFi interfaces and a number of additional radio modules that are connected through USB. It supports the following wireless technologies out of the box:

  • WiFi 802.11ac on 2.4 GHz and 5GHz
  • Bluetooth 4.0 (with full BLE support)
  • IEEE 802.15.4 on 2.4 GHz and IEEE 802.15.4g 868MHz
  • Dash7 on 433MHz and 868MHz
  • LoRaWAN on 868MHz (client only)

All these components are housed in a waterproof metal box to protect them from the elements. The antenna's of the node are housed in a separate (plastic) enclosure and the two are connected by low-loss coax cables.


Node Hardware

Each node uses a PCEngines apu2c4 board as a central controller. This board is equipped with the following hardware:

  • CPU: AMD GX-412TC 1GHz Quad-core CPU (onboard)
  • Memory: 4GB DDR3-1333 MHz (onboard)
  • Storage: 240GB Samsung EVO 850 SSD (mSATA)

The apu2c4 is also equipped with the following WiFi cards:

Compex WLE900VX
  • Atheros (ath10k) QCA9880 Chipset
  • Supports IEEE 802.11 a/b/g/n/ac
  • Operates on both 2.4GHz and 5GHz
  • Connected to three dual-band antennas (3x3 MIMO is supported).
Intel 7260 WiFi-AC + Bluetooth
  • Intel 7260 Chipset
  • Supports WiFi a/b/g/n/ac and Bluetooth 4.0
  • Operates on both 2.4GHz and 5GHz (client mode only)
  • Connected to two dual-band antennas (2x2 MIMO is supported).

Connected USB Devices

Each experiment node is equipped with a number of embedded wireless devices connected trough USB. These devices usually consist of a microcontroller with either an embedded or an add-on wireless radio. Each device is equipped with a JTAG/SWD-debugger for programming the device. If the device does not have an on-board debugger a standalone JTAG/SWD-debugger is provided for the device. Likewise each device is also equipped with a USB-to-serial converter to allow the device to communicate with the host. As with the JTAG-debugger the device is connected to a standalone USB-to-serial converter if it does not have one onboard.

OpenUSB (IEEE 802.15.4)

The OpenUSB mote consists of an OpenMote-CC2538 connected to an OpenUSB base board. It has the following features:

  • MCU: TI CC2538 SoC (32K ram, 512K flash)
  • 2.4 GHz radio: IEEE 802.15.4 tranceiver embedded in the MCU
  • 868 MHz radio: TI CC1200 general purpose tranceiver (compatible with IEEE 802.15.4g)

Serial & JTAG Interface:

Please note that the JTAG debugger is (1) only supported in windows, (2) not required to flash/erase the OpenUSB mote and (3) only present to allow the system administrators to recover bricked OpenUSB motes. Flashing / Erasing the OpenUSB mote is done through the serial port. See the OpenUSB Tutorial for more information.

EZR USB (Dash 7)

The experiment node contains two EZRUSB boards. These boards are identical except that one is equipped with a 433MHz radio front-end and the other one is equipped with an 868MHz radio front-end. These boards have the following features:

  • MCU: Leopard Gecko SoC (32K ram, 256K flash)
  • Radio: general purpose, Dash7 compatible, 433MHz/868Mhz tranceiver embedded in the MCU

Serial & JTAG Interface:

Please note that, for security reasons, the USB-port of the EZR USB is not connected to the host. Communication with the EZR USB module is only possible over the serial interface.

EFM32GG+RFM95W (LoRa)

LoRa(WAN) connectivity is provided through a EFM Giant Gecko development board connected to an RFM95W LoRa tranceiver.

Serial & JTAG Interface:

Antennas