Introduction
SPN is a piece of software from Kerlink that runs on their LoRaWAN gateways. Pilot Things connects to SPN to get LoRaWAN sensors data. There are 2 versions of SPN:
- SPN v1 which communicates using UDP protocol
- SPN V2 which communicates using http protocol
SPN v2 could also act as slave or master. The master gateway could manage slave gateways.
See https://www.kerlink.com/page-de-demonstration/network-operations/ for more details.
SPN version 1
Gateway configuration
To connect the Kerlink gateway to Pilot Things, connect to the gateway and modify the mpc.json main configuration file to active UDP forwarding:
"udp_transmitter": {
"enable": enable,
"ip_address": "xxxx",
"port": 5694
}
xxxx equals Pilot Things IP address.
Refer to Kerlink documentation and support for more information.
Pilot Things configuration
To configure the SPN in Pilot Things, go to network menu and select Kerlink-SPN channel in your node.
In the right pannel, the configuration section should look like this:
{
"gatewayId": "Default_gateway",
"accounts": [
{
"id": "kerlink 1",
"remoteIp": "",
"listenPort": 5694
}
]
}
The remoteIp field must contains the kerlink LoRaWan gateway IP address.
SPN version 2
Gateway configuration
SPN version 2 configuration is through a web interface. Connect to your station and go to Interfaces and remote HTTP REST menu :
Click enable remote HTTP REST. Fill up the following fields with :
- Host : your Pilot Things URL adresse like https://client.pilot-things.com
- Port : 443
- Path : fill with /ipe-kerlink-spn-http/{your_token}
Then save configuration. Your token is not available from the user interface yet. Ask your administrator to get it.
Pilot Things configuration - optional
In Pilot Things go to Administration and then Network menu. Ensure the Kerlink SPN connector is up and running.
In the configuration pannel, fill the fields with :
- url : the https url of the kerlink gateway
- user and password : the login and password used to connect to the gateway
These information are used for the downlink messages.
Comments
0 comments
Please sign in to leave a comment.