Differences

This shows you the differences between two versions of the page.

--- wiki:gateway_configuration [2017/10/19 15:23]
mpe
+++ — (current)
@@ Line 1: / Line 1: @@
-====== Gateway configuration ======
-To use an end-device with SPN, the end-device and the gateway need to use the same parameters.
-Some parameters are common to the entire fleet and some parameters are end-device specific.
-===== Generic LoRa configuration =====
-Generic LoRa configuration is done via the //configuration// menu.
-==== Regional parameters ====
-Depending on regions, the LoRaWAN specification differs. The //Region// menu allows you to define your region.
-==== RX configuration ====
-The iFemtoCell cannot listen to every frequency simultaneously. Up to 8 frequencies can be listened.
-To understand how the frequency configuration works, it is necessary to know that the station’s hardware contains two RF frontends. Each of these frontends has a 0.8 MHz Bandwidth. Thus, all 8 channels must be contained within these two 0.8 MHz intervals.
-To properly configure the Rx channels, the center frequencies of the frontends must be defined.
-Once the center frequencies are defined, each channel can be configured.
-Here are a few rules/information to configure the frequencies:
-  * Both frontends are not necessarly used
-  * Both frontend's bandwidth can overlap
-  * All 8 frequencies can be contained within one single frontend's bandwidth
-  * Not all 8 frequencies are necessarly used
-  * It is better to not use the center frequency of a frentend as channel
-==== Tx configuration ====
-Each country has specific reglementations about the power that a device can emit. To use an emitting power in accordance with the reglementations of a country, the maximum emitting power that can be used in the country need to be determined. To this value, 3dB needs to be substracted to compensate the gain of the antenna.
-If a end-device is close to the station it is recommended to lower the Tx power (otherwise it may saturate).
-==== LoRa network ID ====
-The //LoRa network// page only allows you to choose your LoRa ''NwkID''. The LoRa ''NwkID'' is applicable only for an OTAA fleet.
-<note important>After changing the network ID, you need to reboot the gateway</note>
-<note important>Be careful, once ''NwkID'' is updated, OTAA devices already activated must initiate another join procedure to communicate again with the new ''NwkID''.</note>
-NwkID range value: ''0-127''.
-Kerlink recommends to configure the LoRa ''NwkID'' before adding your end-devices to the fleet.
-===== End-device parameters =====
-Every end-devices need to be configured/registered one by one. This configuration is done via the //manage endpoints// tab under the //Endpoints// menu.
-<note important>The configuration of an end-device cannot be edited. To change the configuration you need to delete this end-device and re-create it. This will **delete all recieved data** from this end-device</note>
-==== Class ====
-SPN handles two kind of LoRa class functionality: class A and class C.
-The main difference between class A and C is that a class C device can receive data from the gateway at almost any time whereas the class A device can only receive data for a short duration after it emitted a packet. For more information about LoRa classes, refer to the [[https://www.lora-alliance.org/|LoRaWan specification]].
-==== Activation parameters ====
-To communicate, an end-device needs to be activated on the station. There are two type of activation: OTAA (Over The Air Activation) and ABP (Activation by Personalization).
-=== If the end-device uses OTAA ===
-For over-the-air activation, end-devices must follow a join procedure prior to participating in data exchanges with the network server. An end-device has to go through a new join procedure every time it has lost the session context information. The join procedure requires the end-device to be personalized with the following information before its starts the join procedure:
-  * A globally unique end-device identifier: ''DevEUI''
-  * The application identifier: ''AppEUI''
-  * An AES-128 key: ''AppKey''
-This information is used at each join procedure to derived unique session keys (''NwkSKey'', ''AppSKey''). These keys are then used to exchanged data between the end-device and the gateway.
-=== If the end-device uses ABP ===
-Activating an end-device by personalization means that the ''DevAddr'' and the two session keys (''NwkSKey'' and ''AppSKey'') are directly stored into the end-device instead of the DevEUI, AppEUI and the AppKey. The end-device is equipped with the required information for participating in a specific LoRa network when started.
-==== LoRa RF paramters ====
-When a packet is send by an end-device, the end-device opens two reception windows. The first window uses the same channel than the one used to send the frame. The second window uses a predefined frequency. During these windows, a frame send by the station can be received.
-By default, SPN automatically choses which window is used. When the second windows is used, by default, the packet is send at the frequency 869,525MHz with the datarate "0".
-If this configuration is not desired, it can be overriden using the //Override default Rx parameters// check box.

Wanesy™ SPN (End Of Life)

User Tools

Site Tools

Differences

Page Tools