Wirnet™ i-series

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== CPF 1.1.6: Installation and configuration ======


===== How to install the Common Packet Forwarder? =====

  - Choose the packet forwarder to install from the [[wiki:resources:resources#common_packet_forwarder|Wirnet products resource page]]. Choosing the latest version of the packet forwarder is recommended.
  - Download the //"lorad"// and //"lorafwd"// ''.ipk'' packages files.
  - Install the ''.ipk'' files using the instructions of the [[wiki:keros_custo:sw_updates|software updates page]]. Packages can be installed simultaneously.
//The CPF installation on a Wirnet iBTS takes some time since the FPGA is updated during this process. Expect approximately 15 to 30 minutes, depending on the number of connected modems. //

The installation of the //"lorad"// and //"lorafwd"// packages adds the following files on the system:

<code bash>
├── etc
│   ├── default
│   │   ├── lorad   # Overall lorad configuration
│   │   └── lorafwd # Overall lorafwd configuration
│   ├── init.d
│   │   ├── lorad   # Script to start/stop lorad
│   │   └── lorafwd # Script to start/stop lorafwd
│   ├── logrotate.d
│   │   ├── lorad   # Configuration file for lorad log rotation
│   │   └── lorafwd # Configuration file for lorafwd log rotation
│   ├── monit.d
│   │   ├── lorad   # Configuration of the lorad monitoring
│   │   └── lorafwd # Configuration of the lorafwd monitoring
│   ├── profile.d
│   │   ├── lorad   # Environment variables for lorad
│   │   └── lorafwd # Environment variables for lorafwd
│   ├── rcK.d
│   │   ├── K50lorad   # autostop of lorad
│   │   └── K51lorafwd # autostop of lorafwd
│   ├── rcU.d
│   │   ├── S40lorad-fpga
│   │   ├── S50lorad   # autostart of lorad
│   │   └── S51lorafwd # autostart of lorafwd
│   ├── rsyslog.d
│   │   ├── lorad   # Configuration file for lorad log
│   │   └── lorafwd # Configuration file for lorafwd log
│   └── sysupgrade.d
│       ├── lorad.conf
│       └── lorafwd.conf
└── user
    ├── etc
    │   ├── lorad
    │   │   ├── ibts
    │   │   │   ├── AS923-JP_16CH.json  # Frequency plan template
    │   │   │   ├── AU915-AU_64CH.json  # ...
    │   │   │   ├── EU868-FR_16CH.json  # ...
    │   │   │   ├── EU868-FR_2x8CH.json # ...
    │   │   │   ├── IN865-IN_8CH.json   # ...
    │   │   │   ├── RU864-RU_16CH.json  # ...
    │   │   │   └── US915-US_64CH.json  # ...
    │   │   ├── misc
    │   │   │   └── remote-api.json
    │   │   ├── wifc
    │   │   │   ├── AS923-JP_8CH.json        # Frequency plan template
    │   │   │   ├── AU915-AU_8CH.json        # ...
    │   │   │   ├── EU868-FR_8CH.json        # ...
    │   │   │   ├── IN865-IN_8CH.json        # ...
    │   │   │   ├── RU864-RU_8CH.json        # ...
    │   │   │   ├── RU864-RU_8CH_Legacy.json # ...
    │   │   │   └── US915-US_8CH.json        # ...
    │   │   ├── wiis
    │   │   │   ├── AS923-JP_8CH.json        # Frequency plan template
    │   │   │   ├── AU915-AU_8CH.json        # ...
    │   │   │   ├── EU868-FR_8CH.json        # ...
    │   │   │   ├── IN865-IN_8CH.json        # ...
    │   │   │   ├── RU864-RU_8CH.json        # ...
    │   │   │   ├── RU864-RU_8CH_Legacy.json # ...
    │   │   │   └── US915-US_8CH.json        # ...
    │   │   └── fevo
    │   │       ├── AS923-JP_8CH.json        # Frequency plan template
    │   │       ├── AU915-AU_8CH.json        # ...
    │   │       ├── EU868-FR_8CH.json        # ...
    │   │       ├── IN865-IN_8CH.json        # ...
    │   │       ├── RU864-RU_8CH.json        # ...
    │   │       ├── RU864-RU_8CH_Legacy.json # ...
    │   │       └── US915-US_8CH.json        # ...
    │   └── lorafwd
    │       └── lorafwd.toml # LNS configuration
    ├── sbin
    │   ├── lorad-ibts # lorad binary for iBTS
    │   ├── lorad-wifc # lorad binary for iFemtoCell
    │   ├── lorad-wiis # lorad binary for iStation
    │   ├── lorad-fevo # lorad binary for iFemtoCell-Evolution
    │   ├── lorafwd    # lorafwd binary
    │   ├── lorafwdctl
    │   └── loramodem  # Only for Wirnet iBTS
    └── share
        └── lorad
            └── fpga_v61.bin # Only for Wirnet iBTS
</code>

===== How to configure and monitor the packet forwarder? =====

The configuration is achieved in 3 steps:
  * //lorad// configuration
  * //lorafwd// configuration
  * monitoring and auto-start configuration

==== lorad configuration ====


The goal of the lorad configuration is to define the frequency plan that will be used to receive packets from the end-devices, to enable the LBT feature and configure the class B beacons.

  * A few frequency plan templates are pre-installed on the gateway (under ''/user/etc/lorad/PLATFORM'' where //PLATFORM// equal to //ibts//, //wifc// or //wiis//): it is strongly recommended to copy the expected frequency plan templates in ''/user/etc/lorad/'' directory and create symlink ''/user/etc/lorad/lorad.json'' to this copied file. The goal is to keep templates unmodified.
  * Edit ''/etc/default/lorad'' and make sure that the ''CONFIGURATION_FILE'' field links to the template you previously copied.
  * Edit the template you copied to adapt it to your needs. Since the hardware of Wirnet iBTS and Wirnet iFemtoCell gateways is different, the configuration on each gateway differs (although it is quite similar).

++++ Wirnet iFemtoCells and Wirnet iStation|

The Wirnet iFemtoCells and Wirnet iStation cannot listen to all LoRa frequencies simultaneously. Up to 8 frequencies can be handled at the same time by the demodulator (SX1301).\\
\\
To understand how the frequency configuration works, it is necessary to know that the Wirnet iFemtoCells and Wirnet iStation hardware contain an RF front-ends connected to 2 SX1257 chips. A look at the [[wiki:lora:features#lora_specific_hardware|]] may help to understand. Each of these chips 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 chips 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 chips are not necessarily used.
  * Both chips' bandwidth can overlap.
  * Channels can overlap.
  * All 8 frequencies can be contained within one single chip's bandwidth.
  * Not all 8 frequencies are necessarily used.
  * Avoid the use of the chip's center frequencies as a channel.

\\
There are many configuration fields among the templates, but most of them are by default correctly filled.\\
\\
**Front-end configuration**

  * ''antenna_gain'': Is used to define the gain of the antenna. If you use the default Kerlink antenna don't change it. This field has to be correctly filled, otherwise, the gateway will use more power to emits packets than what was initially planned by the LNS.
  * ''insertion_loss'': Is used to define the attenuation due to the cable between the gateway and the antenna. When there is no cable, the correct value is 0.
  * ''radio_n''
    * ''enable'': Enable/disable SX1257.
    * ''freq'': Is used to define the center frequency of the SX1257. All channels will be around this particular frequency (+/- 0.4Mhz). 
    * ''tx_enable'': Enable/disable tx data on SX1257.

<code>
"lorawan_public": true,
"antenna_gain": 3,
"antenna_gain_desc": "Antenna gain, in dBi",
"insertion_loss": 0,
"insertion_loss_desc": "Insertion loss, in dBi",
"radio_0": {
	"enable": true,
	"freq": 867500000,
	"tx_enable": true,
	"tx_freq_min": 863000000,
	"tx_freq_max": 870000000,
},
"radio_1": {
	"enable": true,
	"freq": 868500000,
	"tx_enable": false
},
</code>

**Radio frequencies configuration**

  * ''chan_multiSF_X''
     * ''enable'': Enable/disable the channel.
     * ''radio'': Define which frontend (SX1257) is used by the channel (''0'' or ''1'' expected). 
     * ''if'': Intermediate frequency. Value that defines a channnel frequency (value added to the center frequency). 

<code>
/* Lora MAC channels, 125kHz, all SF */
"chan_multiSF_0": { "enable": true, "radio": 0, "if": -400000 },
"chan_multiSF_1": { "enable": true, "radio": 0, "if": -200000 },
"chan_multiSF_2": { "enable": true, "radio": 0, "if": 0 },
"chan_multiSF_3": { "enable": true, "radio": 0, "if": 200000 },
"chan_multiSF_4": { "enable": true, "radio": 0, "if": 400000 },
"chan_multiSF_5": { "enable": true, "radio": 1, "if": -400000 },
"chan_multiSF_6": { "enable": true, "radio": 1, "if": -200000 },
"chan_multiSF_7": { "enable": true, "radio": 1, "if": 0 },
</code>

**Listen Before Talk configuration**

Listen Before Talk (LBT) is a technique used in radiocommunications whereby a radio transmitter first senses its radio environment before starting a transmission.\\
\\
This feature is mandatory in a few countries (such as Japan and Korea).

  * ''enable'': Enable or disable LBT.
  * ''rssi_target'': The RSSI threshold to detect if the channel is busy or not (dBm).
  * ''chan_cfg''
    * ''freq_hz'': The LBT channel frequency in Hz. These frequencies need to be the same as the one in the ''chan_multiSF_X'' JSON arrays.
    * ''scan_time_us'': The LBT channel scan time to be used (only two available values: 128µs or 5000µs).

<code>
/* Listen Before Talk */
"lbt_cfg": {
        "enable": true,
        "rssi_target": -80,
        "chan_cfg": [
                { "freq_hz": 922000000, "scan_time_us": 5000 },
                { "freq_hz": 922200000, "scan_time_us": 5000 },
                { "freq_hz": 922400000, "scan_time_us": 5000 },
                { "freq_hz": 922600000, "scan_time_us": 5000 },
                { "freq_hz": 922800000, "scan_time_us": 5000 },
                { "freq_hz": 923000000, "scan_time_us": 5000 },
                { "freq_hz": 923200000, "scan_time_us": 5000 },
                { "freq_hz": 923400000, "scan_time_us": 5000 }
        ]
},
</code>

++++
==== lorafwd configuration ====

The goal of the lorafwd configuration is mainly to define to which LNS LoRa packets will be forwarded to.

  * Edit ''/user/etc/lorafwd/lorafwd.toml''. This configuration file is formatted using the TOML v0.5.0 language:  
    * Most keys are pre-configured with correct values.
    * The description of each key is directly written in the configuration file.
    * Hereunder are the keys that must changed to chose your LNS:
      * ''gwmp.node = "localhost"'': The address of the LNS.
      * ''gwmp.service.uplink = 20000'': The uplink port of the LNS.
      * ''gwmp.service.downlink = 20000'' : The downlink port of the LNS.


==== Monitoring and auto-start configuration ====

By default, both lorad and lorafwd are started at boot time. If for some reason, one of the daemons stops, it will be automatically restarted by ''monit''.

  * The autostart behavior is handled by the symlinks ''/etc/rcU.d/S50lorad'' and ''/etc/rcU.d/S51lorafwd''.
  * The monitoring behavior is handled by the ''/etc/monit.d/lorad'' and ''/etc/monit.d/lorafwd'' files.

The daemons can be started/stopped/rebooted and monitored with ''monit''. See [[wiki:systeme_mana:monitoring#monit_daemon|monit page]] for more details.

Both daemons are independent. If one is stopped/restarted, the other one does not need to be stopped/restarted.

==== Log managment ====

Both daemons generates logs in the ''/var/log/lora.log*'' files.

The verbosity of the daemons can be increased using the ''EXTRA_ARGS'' field under ''/etc/default/lorad''and ''/etc/default/lorafwd''.

__lorad:__
  * NOTICE = ''-v'': displays start and stop traces
  * INFO = ''-vv'': 
    * Displays the configuration of the hardware (frequencies, bandwidth, spreading factor, antenna, LBT, ...)
    * Displays the number of uplinks and beacons sent.
    * Displays TAI/PPS info
    * ...
  * DEBUG = ''-vvv'': Displays the hexdump of the packets

__lorafwd:__ 
  * NOTICE = ''-v'': displays start and stop traces
  * INFO = ''-vv'': 
    * Displays the configuration of the forwarder (gateway ID, LNS, uplink/downlink port, GWMP configuration, ...)
    * Displays the uplinks and downlink meta-data
    * Displays the acknowledge / heartbeat / drop traces
    * ...
  * DEBUG = ''-vvv'': Displays the hexdump of the packets


==== gateway EUI ====

Gateway EUI is used by LNS to identify from which gateway messages come from. 

By default, EUI are generated this way:

  * Wirnet iBTS: 7276FF002E<last 6 characters of the CPU serial number>
  * Wirnet iFemtoCell: 7276FF00<last 8 characters of the CPU board serial number>
  * Wirnet iStation: 7076FF00<last 8 characters of the CPU board serial number>
  * Wirnet iFemtoCell-Evolution: 7076FF00<last 8 characters of the CPU board serial number>

When lorafwd starts, a file containing the default EUI is generated.

<code bash>
cat /var/run/lora/gateway-id.toml 
gateway.id = 0x7076FF0064050789
</code>

If a new EUI has been defined under ''/user/etc/lorafwd'', then, this new EUI is used by lorafwd. Otherwise, the default EUI is used.
++++
Wirnet™ i-series

User Tools

Site Tools

Page Tools
