# Overview
# Introduction
The wireless sensors designed and manufactured by Radio Bridge provide full sensor to cloud solutions for Internet of Things (IoT) applications. Radio Bridge LoRaWAN sensors can connect to a variety of LoRaWAN compliant network servers, located either on a local gateway or as a cloud-based network server. From there, the sensor messages can be sent to the Radio Bridge web-based console or a third-party application. This document provides instructions for connecting LoRaWAN sensors using several different methods. For more information on the web-based console, visit https://console.radiobridge.com (opens new window)
# Stand-Alone vs Network Provider
A network provider for LoRaWAN will set up LoRa base stations and charge for accessing their network much like a cell phone provider will charge to connect your phone to their network. In some cases, however, it may be desirable to set up a stand-alone gateway that does not use a network provider. Reasons for this may include lack of coverage in remote area or simply reducing the cost when there are many sensors in the field.
# AppEUI / JoinEUI
The LoRaWAN AppEUI, now known as the JoinEUI (they are sometimes used interchangeably), is consistent among Radio Bridge products and thus is not listed on the product labels. Earlier products use a generic, non-unique, JoinEUI, and newer products use a unique JoinEUI as described in the following table.
Table 1: AppEUI/JoinEUI for Radio Bridge Products
| AppEUI/JoinEUI | Description |
|---|---|
| 01-01-01-01-01-01-01-01 | Used in the following product families: RBS301, RBS304, RBS305, and RBS306 |
| 78-94-E8-00-00-00-00-00 | Used in product families not listed above |
Note that the AppEUI/JoinEUI can be modified at the time of manufacturing to match the end customer’s requirements. Please contact Radio Bridge for more details on customization and pre-configuration.
# Revision History
Table 2: Revision History
| Revision | Date | Description |
|---|---|---|
| 1.0 | August 2018 | Initial release of the document |
| 1.1 | September 2018 | Added section for general gateways |
| 1.2 | January 2019 | Added support for TTN |
| 1.3 | February 2019 | Added process ID for TTN |
| 1.4 | May 2019 | Added APPEUI definition to TTN |
| 1.5 | June 2019 | Added Senet |
| 1.6 | July 2019 | Added Loriot |
| 1.7 | February 2020 | Added ChirpStack |
| 1.8 | April 2020 | Additional add gateway features, A |
| 1.9 | April 2020 | Added new AppEUI/JoinEUI |
| 1.10 | June 2020 | Added Kerlink integration |
| 1.11 | March 2021 | New Python script for stand-alone Multitech gateway |
| 1.12 | July 2021 | Updated for TTN v3 |
# Document Conventions
Table 3: Document Conventions
| Font / Icon | Meaning |
|---|---|
 | Important notes |
 | Warnings and cautions |