mirror of
https://github.com/sascha-hemi/pycom-documentation.git
synced 2026-03-22 06:06:28 +01:00
feat: this review contains improvements suggested by Kateryna
This commit is contained in:
Aline
@@ -1237,9 +1237,9 @@ theme = "doc-theme"
|
||||
weight = 20
|
||||
|
||||
[[menu.main]]
|
||||
name = "Pycom LoRa Server"
|
||||
url = "/pybytes/networks/lora/pycomLoraServerSetup/"
|
||||
identifier = "pybytes@networks@lora@pycomLoraServerSetup"
|
||||
name = "Chirpstack LoRa Server"
|
||||
url = "/pybytes/networks/lora/chirpstack/"
|
||||
identifier = "pybytes@networks@lora@chirpstack"
|
||||
parent = "pybytes@networks@lora"
|
||||
weight = 20
|
||||
|
||||
|
||||
@@ -3,6 +3,8 @@ title: "Networks"
|
||||
aliases:
|
||||
---
|
||||
|
||||
Pybytes supports four Network Types which you can configure both for each device and for the group of the devices within a project. Those Networks are WiFi, LoRa, Sigfox, and LTE CAT M1 / NB1. In this section the detailed setting procedure of every network type will be explained.
|
||||
|
||||
[**Sigfox**](/pybytes/networks/sigfox)
|
||||
|
||||
[**LoRa**](/pybytes/networks/lora)
|
||||
|
||||
@@ -5,18 +5,19 @@ aliases:
|
||||
|
||||
## Overview
|
||||
|
||||
Pybytes supports [The Things Network](https://www.thethingsnetwork.org/) and ChirpStack ([ChirpStack](https://www.chirpstack.io/)).
|
||||
Pybytes supports LoRa servers from [The Things Network](https://www.thethingsnetwork.org/) and from [ChirpStack](https://www.chirpstack.io/). During setup of the LoRa connection for your device, whether with TTN or with ChirpStack, Pybytes will automatically create the user profile on those servers.
|
||||
|
||||
About the traits of the different LoRa servers, you can uncover more following the links below.
|
||||
|
||||
|
||||
## TTN Server
|
||||
|
||||
Once a device is created in Pybytes with LoRa network, and the TTN Server is selected, the device is automatically created in TTN server.
|
||||
|
||||
### Further reading
|
||||
For more information check out [The Things Network](https://www.thethingsnetwork.org/docs/)
|
||||
|
||||
## ChirpStack
|
||||
|
||||
Pybytes has its own LoRa Server based on [ChirpStack](https://www.chirpstack.io/).
|
||||
|
||||
* [How to use it](pycomloraserversetup).
|
||||
* [How to use it](chirpstack).
|
||||
|
||||
90
content/pybytes/networks/lora/chirpstack.md
Normal file
90
content/pybytes/networks/lora/chirpstack.md
Normal file
@@ -0,0 +1,90 @@
|
||||
---
|
||||
title: "ChirpStack Setup"
|
||||
aliases:
|
||||
- chapter/pybytes/networks/lora/chirpstack
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
When a LoRa device is created or LoRa network is configured in **Pybytes → Settings -> LoRa** the user profile is automatically created at [ChirpStack](https://loraserver.pycom.io/).
|
||||
|
||||
## User profile
|
||||
|
||||
After creating a LoRa device or configure Pybytes to use ChirpStack, you should receive an email with ChirpStack username and password what you can use for accessing the data on <a href="https://loraserver.pycom.io/"> loraserver.pycom.io</a>.
|
||||
|
||||
The basic configurations are made by Pybytes, but if you want to overwrite the LoRa settings, it is possible to use these credentials.
|
||||
|
||||
### What is created by ChirpStack:
|
||||
|
||||
**Network-server** - Pycom
|
||||
|
||||
You can add your own server in the section Network-servers
|
||||
|
||||
**User** - Value
|
||||
|
||||
The User will be created based on the same credentials that are used in Pybytes and it can be managed in the section Org. Users. At the same place, the Admin status of the user can be changed.
|
||||
|
||||
**Organization** - Value (by default)
|
||||
|
||||
The Organization Value will be created based on the same credentials used by Pybytes and can be changed in the section Org. Settings.
|
||||
|
||||
**Service Profile** - Value (by default)
|
||||
|
||||
The Service Profile Name is connected to the Organization’s name.
|
||||
|
||||
**Device Profiles** - OTAA or ABP
|
||||
|
||||
There are two different devices profiles among which you should select the preferable.
|
||||
|
||||
**Applications** - Value (by default)
|
||||
|
||||
All devices created in Pybytes will be connected to this app.
|
||||
|
||||
**Devices** All devices that will be created in Pybytes.
|
||||
|
||||
|
||||
## Gateway
|
||||
|
||||
The user should set up their own Gateway in order to communicate with ChirpStack.
|
||||
|
||||
### How to set up a gateway:
|
||||
|
||||
1 - Login in ChirpStack (https://loraserver.pycom.io/)
|
||||
|
||||
2 - Click on **Gateway** on the main sidebar
|
||||
|
||||
3 - Click on **Create** button
|
||||
|
||||
4 - Fill the form with the information below
|
||||
|
||||
**Gateway name**
|
||||
|
||||
The name may only contain words, numbers, and dashes.
|
||||
|
||||
**Gateway description**
|
||||
|
||||
The description of the gateway.
|
||||
|
||||
**Gateway ID**
|
||||
|
||||
The gateway ID.
|
||||
|
||||
**Network-server**
|
||||
|
||||
Select the network-server to which the gateway will connect. When no network-servers are available in the dropdown, make sure a service-profile exists for this organization.
|
||||
|
||||
**Gateway-profile**
|
||||
|
||||
An optional gateway-profile which can be assigned to a gateway. This configuration can be used to automatically re-configure the gateway when LoRa Gateway Bridge is configured so that it manages the packet-forwarder configuration.
|
||||
|
||||
**Gateway discovery enabled**
|
||||
|
||||
When enabled (and LoRa Server is configured with the gateway discover feature enabled), the gateway will send out periodical pings to test its coverage by other gateways in the same network.
|
||||
|
||||
**Gateway altitude** (meters)
|
||||
|
||||
When the gateway has an on-board GPS, this value will be set automatically when the network has received statistics from the gateway.
|
||||
|
||||
**Gateway location** (set to current location)
|
||||
|
||||
For more information check out [ChirpStack official guide](https://www.chirpstack.io/guides/first-gateway-device/#add-a-lora-sup-reg-sup-gateway).
|
||||
@@ -1,65 +0,0 @@
|
||||
---
|
||||
title: "ChirpStack Setup"
|
||||
aliases:
|
||||
- pybytes/lora/pycomLoraServerSetup.html
|
||||
- pybytes/pycomLoraServerSetup.md
|
||||
- chapter/pybytes/lora/pycomLoraServerSetup
|
||||
---
|
||||
|
||||
## Overview
|
||||
|
||||
When a LoRa device is created or LoRa network is configured in **Pybytes → Settings -> LoRa** the user profile is automatically created at [ChirpStack](https://loraserver.pycom.io/).
|
||||
|
||||
## User profile
|
||||
|
||||
After creating a loRa device or configure Pybytes to use ChirpStack, the user should receive an email with ChirpStack username and password.
|
||||
|
||||
The basic configurations are made by Pybytes, but if the user wants to overwrite it, it is possible using these credentials.
|
||||
|
||||
### What is created by Pybytes?
|
||||
|
||||
Network-server - **Pycom**
|
||||
|
||||
User and Organization - Created based on the same credentials used by Pybytes.
|
||||
|
||||
Service Profile - Connected to organization.
|
||||
|
||||
Device Profile - Two different profiles, for OTAA and ABP devices.
|
||||
|
||||
Application - All devices will be connected to this app.
|
||||
|
||||
Device - All devices will be created by Pybytes.
|
||||
|
||||
|
||||
## Gateway
|
||||
|
||||
The user should set up their own Gateway in order to communicate with ChirpStack.
|
||||
|
||||
### How to set up a gateway?
|
||||
|
||||
* Login in ChirpStack (https://loraserver.pycom.io/)
|
||||
|
||||
* Click on **Gateway** on the main sidebar
|
||||
|
||||
* Click on **Create** button
|
||||
|
||||
* Fill the form with the information below
|
||||
|
||||
* *Gateway name* - The name may only contain words, numbers, and dashes.
|
||||
|
||||
* *Gateway description* - The description of the gateway.
|
||||
|
||||
* *Gateway ID* - The gateway ID.
|
||||
|
||||
* *Network-server* - Select the network-server to which the gateway will connect. When no network-servers are available in the dropdown, make sure a service-profile exists for this organization.
|
||||
|
||||
* *Gateway-profile* - An optional gateway-profile which can be assigned to a gateway. This configuration can be used to automatically re-configure the gateway when LoRa Gateway Bridge is configured so that it manages the packet-forwarder configuration.
|
||||
|
||||
* *Gateway discovery enabled* - When enabled (and LoRa Server is configured with the gateway discover feature enabled), the gateway will send out periodical pings to test its coverage by other gateways in the same network.
|
||||
|
||||
* *Gateway altitude* (meters) - When the gateway has an on-board GPS, this value will be set automatically when the network has received statistics from the gateway.
|
||||
|
||||
* *Gateway location* (set to current location)
|
||||
|
||||
## Further reading
|
||||
For more information check out [ChirpStack official guide](https://www.chirpstack.io/guides/first-gateway-device/#add-a-lora-sup-reg-sup-gateway).
|
||||
Reference in New Issue
Block a user