Setups
General information
Wirnet™ iBTS information
Wirnet™ iFemtoCell information
Wirnet™ iFemtoCell-evolution information
Wirnet™ iStation information
System management
Network management
LoRa Features
KerOS customization
Support and resources
Setups
General information
Wirnet™ iBTS information
Wirnet™ iFemtoCell information
Wirnet™ iFemtoCell-evolution information
Wirnet™ iStation information
System management
Network management
LoRa Features
KerOS customization
Support and resources
This is an old revision of the document!
The classical communication case is:
The protocol used by the end-device, the gateway and the LNS is the LoRaWAN protocol. You will find a presentation, a technical introduction, and the detailed specification on the official website.
The LoRa specific hardware differs from one type of gateway to another. It defines the capabilities of the gateways such as the number of channels, the diversity, the sensibility, …
Wirnet™ iBTS gateways are composed of multiple boards. The LoRaLOC boards are responsible for the management of LoRa packets. Depending on the Wirnet™ iBTS hardware versions, up to 4 LoRaLOC board can be integrated into the gateway.
Each LoRaLOC board is composed of:
Each SX1301 is capable of demodulating 8x 125KHz LoRa bands, 1x 250KHz LoRa bands and 1x FSK band. Since there are 2x SX1301 in each LoRaLOC, a LoRaLOC can use up to 16x 125KHz LoRa bands.
Each frontend has 2x SMB antennas ports. The use of both SX1301 can be achieved with only one antenna. Actually, using 2 antennas is only useful to cover a wider area. For example, two directional antennas could be used from the same place or two omnidirectional antennas could be used from different places.
Each LoRaLoc is calibrated on a testbench. The result of the calibration process is copied at each startup in the /tmp/calib_loraloc.json file.
The LoRa specific hardware of the gateways is driven by an FPGA. This FPGA is regularly updated by Semtech to improve its performances, to add new features and to correct bugs.
Kerlink provides a Hardware Abstraction Layer (HAL) to use the LoRa Specific hardware. This HAL is a static library written in C. Each version of the HAL relies on a version of the FPGA, therefore to use programs that use the HAL, the first thing to do is to update the FPGA.
For almost all users, the use of the FPGA and of the HAL is transparent. Kerlinks provides a CPF (see next paragraph) that takes care of the FPGA update and integrates the HAL.
The packet forwarder is a set of two daemons (working together) used to send the packets received from the end-devices to the LNS and vice-versa, hence its name.
The packet forwarder is the main program of a LoRa gateway. It has to be installed to implement a LoRaWAN network.
More details about how to install/configure the CPF here.
Each country has different regulation about RF transmission. Since this is the LNS that schedules the LoRa packets and chooses the RF power used by the gateways, make sure that your LNS configuration fits with your country regulation.
LNS do not handle the LBT feature (Listen Before Talk). A few countries (Japan and Korea) requires it. This feature is directly activated in the packet forwarder configuration.