TheThingsNetwork: Difference between revisions

From NURDspace
Jump to navigation Jump to search
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Project
|Participants=bertrik
|Name=TheThingsNetwork
|Skills=LoRaWAN,Radio
|Status=Active
|Niche=Radio
|Purpose=World domination
|Picture=Lorixone.png
|Tool=No
|Category=Infra
}}
== Intro ==
== Intro ==
NurdSpace has a LorixOne LoRaWAN gateway.
NurdSpace has a LorixOne LoRaWAN gateway.
Line 4: Line 16:


More info:
More info:
* https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3
* current status on packet broker: https://mapper.packetbroker.net/api/v2/gateways/netID=000013,tenantID=ttn,id=nurdspace-lorix-one
* perhaps also relevant: https://www.thethingsindustries.com/docs/hardware/gateways/models/wifx-lorix-one/lbs/
* how to set it upd https://iot.wifx.net/docs/lorix-os/1.5/wifx-l1/user-s-guide/lorawan/lorawan-networks/the-things-network-industries/the-things-network-v3
 
Logging in: go to http://lorix-one-0f3a24.local
Username: admin, password: <SECRET>
 
The gateway forwards packets to TheThingsNetwork. Contact [[bertrik]] to become collaborator on TheThingsNetwork dashboard.
 
At the moment the gateway is fully configured, but off-line, stored in Melan's la.


== Hardware ==
== Hardware ==
There's a sticker on the outside:
There's a sticker on the outside:
FC:C2:3D:0F:3A:24 v1.0d
FC:C2:3D:0F:3A:24 v1.0d
This means it's the 256 MB flash version.


You can screw off the bottom, to reveal an ethernet port and an USB-B port.
You can screw off the bottom, to reveal an ethernet port and an USB-B port.
It gets power through a power-over-ethernet cable
It gets power from the power-over-ethernet cable.


== Software ==
== Software ==
Connect a USB A-to-B cable to the USB-B port.
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)
  screen /dev/ttyACM0 115200


=== Configuration ===
=== Configuration ===


==== network ====
==== Network connection (easiest) ====
See /etc/network/interfaces. Add:
The thing does DHCP, and is reachable at
<pre>
  lorix-one-0f3a24.local
auto eth0
e.g. http://lorix-one-0f3a24.local for the web interface
iface eth0 inet dhcp
</pre>


==== packages ====
==== Serial connection (fallback) ====
Packages are maintained with opkg.
Connect a USB A-to-B cable to the USB-B port.
Open a serial terminal at 115200 bits to /tty/ACM0 (typically)
  screen /dev/ttyACM0 115200


==== forwarder setup ====
==== Forwarder setup ====
When running 'opkg upgrade', it logged the following:
The gateway was fully re-installed, by flashing an entirely new image.
<pre>
Configuration can be done through the web interface (no CLI required).
noldus-lorix-one:~$ sudo opkg upgrade       
Configuring packet-forwarder.
Updating configuration files with gateway ID, type EU868
******************************************************************************************
Default global_conf.json file created from 4dBi outdoor antenna by default,
don't forget to chose the one corresponding to your antenna using the following command:
sudo cp /opt/lorix/cloud/ttn/global_conf_<antenna>.json global_conf.json
******************************************************************************************
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_2dBi_indoor.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/global_conf_4dBi_outdoor.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/packet-forwarder/local_conf.json
System startup links for /etc/init.d/packet-forwarder-gw already exist.
Configuring ttn-packet-forwarder.
Updating configuration files with gateway ID, type EU868
******************************************************************************************
Default global_conf.json file created from 4dBi outdoor antenna by default,
don't forget to chose the one corresponding to your antenna using the following command:
sudo cp /opt/lorix/cloud/ttn/global_conf_<antenna>.json global_conf.json
******************************************************************************************
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_2dBi_indoor.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/global_conf_4dBi_outdoor.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/ttn/local_conf.json
System startup links for /etc/init.d/ttn-gw already exist.
Configuring loriot.
System startup links for /etc/init.d/loriot-gw already exist.
Configuring clouds-manager.
System startup links for /etc/init.d/init-clouds-manager already exist.
Stopping cloud loriot... done.
Starting cloud loriot... done.
Configuring lora-gateway.
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/global_conf.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/utils/local_conf.json
Configuring factory-reset.
System startup links for /etc/init.d/factory-reset.sh already exist.
Configuring kersing-packet-forwarder.
Updating configuration files with gateway ID, type EU868
******************************************************************************************
Default global_conf.json file created from 4dBi outdoor antenna by default,
don't forget to chose the one corresponding to your antenna using the following command:
sudo cp /opt/lorix/cloud/mp-pkt-fwd/global_conf_<antenna>.json global_conf.json
******************************************************************************************
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_2dBi_indoor.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/global_conf_4dBi_outdoor.json
Gateway_ID set to fcc23dFFFE0f3a24 in file /opt/lorix/clouds/mp-pkt-fwd/local_conf.json
System startup links for /etc/init.d/mp-pkt-fwd-gw already exist.
noldus-lorix-one:~$
</pre>

Latest revision as of 23:53, 21 June 2025

TheThingsNetwork
Lorixone.png
Participants
Skills LoRaWAN, Radio
Status Active
Niche Radio
Purpose World domination
Tool No
Location
Cost
Tool category Infra

TheThingsNetwork

Lorixone.png {{#if:No | [[Tool Owner::{{{ProjectParticipants}}} | }} {{#if:No | [[Tool Cost::{{{Cost}}} | }}


Intro

NurdSpace has a LorixOne LoRaWAN gateway. This page is about setting it up for TheThingsNetwork.

More info:

Logging in: go to http://lorix-one-0f3a24.local Username: admin, password: <SECRET>

The gateway forwards packets to TheThingsNetwork. Contact bertrik to become collaborator on TheThingsNetwork dashboard.

At the moment the gateway is fully configured, but off-line, stored in Melan's la.

Hardware

There's a sticker on the outside: FC:C2:3D:0F:3A:24 v1.0d This means it's the 256 MB flash version.

You can screw off the bottom, to reveal an ethernet port and an USB-B port. It gets power from the power-over-ethernet cable.

Software

Configuration

Network connection (easiest)

The thing does DHCP, and is reachable at

 lorix-one-0f3a24.local

e.g. http://lorix-one-0f3a24.local for the web interface

Serial connection (fallback)

Connect a USB A-to-B cable to the USB-B port. Open a serial terminal at 115200 bits to /tty/ACM0 (typically)

 screen /dev/ttyACM0 115200

Forwarder setup

The gateway was fully re-installed, by flashing an entirely new image. Configuration can be done through the web interface (no CLI required).