Rak2287 configuration help

charuga · June 17, 2022, 10:32am

Please Help,
I bought 10 pieces of Rak2287 EU433 for raspberry-pi (as in the picture)
I installed everything (https://github.com/RAKWireless/rak_common_for_gateway). How do I configure globalconf because there is only CN433 in the setup, there is no EU433 and also in the server chirpstack network toml file?

GLOBAL CONF

{
“SX130x_conf”: {
“com_type”: “SPI”,
“com_path”: “/dev/spidev0.0”,
“lorawan_public”: true,
“clksrc”: 0,
“antenna_gain”: 0, /* antenna gain, in dBi /
“full_duplex”: false,
“fine_timestamp”: {
“enable”: false,
“mode”: “all_sf” / high_capacity or all_sf */
},
“radio_0”: {
“enable”: true,
“type”: “SX1250”,
“single_input_mode”: true,
“freq”: 434375000,
“rssi_offset”: -207.0,
“rssi_tcomp”: {“coeff_a”: 0, “coeff_b”: 0, “coeff_c”: 20.41, “coeff_d”: 2162.56, “coeff_e”: 0},
“tx_enable”: true,
“tx_freq_min”: 433050000,
“tx_freq_max”: 434900000,
“tx_gain_lut”:[
{“rf_power”: -6, “pa_gain”: 0, “pwr_idx”: 0},
{“rf_power”: -3, “pa_gain”: 0, “pwr_idx”: 1},
{“rf_power”: 0, “pa_gain”: 0, “pwr_idx”: 2},
{“rf_power”: 3, “pa_gain”: 1, “pwr_idx”: 3},
{“rf_power”: 6, “pa_gain”: 1, “pwr_idx”: 4},
{“rf_power”: 10, “pa_gain”: 1, “pwr_idx”: 5},
{“rf_power”: 11, “pa_gain”: 1, “pwr_idx”: 6},
{“rf_power”: 12, “pa_gain”: 1, “pwr_idx”: 7},
{“rf_power”: 13, “pa_gain”: 1, “pwr_idx”: 8},
{“rf_power”: 14, “pa_gain”: 1, “pwr_idx”: 9},
{“rf_power”: 16, “pa_gain”: 1, “pwr_idx”: 10},
{“rf_power”: 20, “pa_gain”: 1, “pwr_idx”: 11},
{“rf_power”: 23, “pa_gain”: 1, “pwr_idx”: 12},
{“rf_power”: 25, “pa_gain”: 1, “pwr_idx”: 13},
{“rf_power”: 26, “pa_gain”: 1, “pwr_idx”: 14},
{“rf_power”: 27, “pa_gain”: 1, “pwr_idx”: 15}
]
},
“radio_1”: {
“enable”: true,
“type”: “SX1250”,
“single_input_mode”: true,
“freq”: 433575000,
“rssi_offset”: -207.0,
“rssi_tcomp”: {“coeff_a”: 0, “coeff_b”: 0, “coeff_c”: 20.41, “coeff_d”: 2162.56, “coeff_e”: 0},
“tx_enable”: false
},
“chan_multiSF_All”: {“spreading_factor_enable”: [ 5, 6, 7, 8, 9, 10, 11, 12 ]},
“chan_multiSF_0”: {“enable”: true, “radio”: 1, “if”: -300000},
“chan_multiSF_1”: {“enable”: true, “radio”: 1, “if”: -100000},
“chan_multiSF_2”: {“enable”: true, “radio”: 1, “if”: 100000},
“chan_multiSF_3”: {“enable”: true, “radio”: 1, “if”: 300000},
“chan_multiSF_4”: {“enable”: true, “radio”: 0, “if”: -300000},
“chan_multiSF_5”: {“enable”: true, “radio”: 0, “if”: -100000},
“chan_multiSF_6”: {“enable”: true, “radio”: 0, “if”: 100000},
“chan_multiSF_7”: {“enable”: true, “radio”: 0, “if”: 300000},
“chan_Lora_std”: {“enable”: false, “radio”: 1, “if”: -200000, “bandwidth”: 250000, “spread_factor”: 7,
“implicit_hdr”: false, “implicit_payload_length”: 17, “implicit_crc_en”: false, “implicit_coderate”: 1},
“chan_FSK”: {“enable”: false, “radio”: 1, “if”: 300000, “bandwidth”: 125000, “datarate”: 50000}
},

"gateway_conf": {
    "gateway_ID": "0000000000000000",
    /* change with default server address/ports */
"server_address": "127.0.0.1",
    "serv_port_up": 1700,
    "serv_port_down": 1700,
    /* adjust the following parameters for your network */
    "keepalive_interval": 10,
    "stat_interval": 30,
    "push_timeout_ms": 100,
    /* forward only valid packets */
    "forward_crc_valid": true,
    "forward_crc_error": false,
    "forward_crc_disabled": false,
    /* GPS configuration */
    "gps_tty_path": "/dev/ttyAMA0",
    /* GPS reference coordinates */
    "ref_latitude": 0.0,
    "ref_longitude": 0.0,
    "ref_altitude": 0,
    "autoquit_threshold": 20,
    /* Beaconing parameters */
    "beacon_period": 0, /* disable class B beacon */
    "beacon_freq_hz": 508300000, 
    "beacon_freq_nb": 8, 
    "beacon_freq_step": 200000, 
    "beacon_datarate": 10, 
    "beacon_bw_hz": 125000, 
    "beacon_power": 27
},

"debug_conf": {
    "ref_payload":[
        {"id": "0xCAFE1234"},
        {"id": "0xCAFE2345"}
    ],
    "log_file": "loragw_hal.log"
}

}

###################################################

TOML file

This configuration configures ChirpStack Network Server for the EU868 band using a MQTT

broker to communicate with the gateways. Many options and defaults have been

omitted for simplicity.

For other bands, see the ./examples/ sub-directory.

See Configuration - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server for a full

configuration example and documentation.

PostgreSQL settings.

Please note that PostgreSQL 9.5+ is required.

[postgresql]

PostgreSQL dsn (e.g.: postgres://user:password@hostname/database?sslmode=disable).

Besides using an URL (e.g. ‘postgres://user:password@hostname/database?sslmode=disable’)

it is also possible to use the following format:

‘user=chirpstack_ns dbname=chirpstack_ns sslmode=disable’.

The following connection parameters are supported:

* dbname - The name of the database to connect to

* user - The user to sign in as

* password - The user’s password

* host - The host to connect to. Values that start with / are for unix domain sockets. (default is localhost)

* port - The port to bind to. (default is 5432)

* sslmode - Whether or not to use SSL (default is require, this is not the default for libpq)

* fallback_application_name - An application_name to fall back to if one isn’t provided.

* connect_timeout - Maximum wait for connection, in seconds. Zero or not specified means wait indefinitely.

* sslcert - Cert file location. The file must contain PEM encoded data.

* sslkey - Key file location. The file must contain PEM encoded data.

* sslrootcert - The location of the root certificate file. The file must contain PEM encoded data.

Valid values for sslmode are:

* disable - No SSL

* require - Always SSL (skip verification)

* verify-ca - Always SSL (verify that the certificate presented by the server was signed by a trusted CA)

* verify-full - Always SSL (verify that the certification presented by the server was signed by a trusted CA and the server host name matches the one in the certificate)

dsn=“postgres://chirpstack_ns:dbpassword@localhost/chirpstack_ns?sslmode=disable”

Redis settings

Please note that Redis 2.6.0+ is required.

[redis]

Redis url (e.g. redis://user:password@hostname/0)

For more information about the Redis URL format, see:

https://www.iana.org/assignments/uri-schemes/prov/redis

url=“redis://localhost:6379”

Network-server settings.

[network_server]

Network identifier (NetID, 3 bytes) encoded as HEX (e.g. 010203)

net_id=“000000”

LoRaWAN regional band configuration.

Note that you might want to consult the LoRaWAN Regional Parameters

specification for valid values that apply to your region.

See: https://www.lora-alliance.org/lorawan-for-developers

[network_server.band]
name=“EU433”

LoRaWAN network related settings.

[network_server.network_settings]
enabled_uplink_channels=[]

Disable ADR

When set, this globally disables ADR.

disable_adr=false

# Extra channel configuration.
#
# Use this for LoRaWAN regions where it is possible to extend the by default
# available channels with additional channels (e.g. the EU band).
# The first 5 channels will be configured as part of the OTAA join-response
# (using the CFList field).
# The other channels (or channel / data-rate changes) will be (re)configured
# using the NewChannelReq mac-command.
#

[[network_server.network_settings.extra_channels]]

frequency=867100000

min_dr=0

max_dr=5

[[network_server.network_settings.extra_channels]]

frequency=867300000

min_dr=0

max_dr=5

[[network_server.network_settings.extra_channels]]

frequency=867500000

min_dr=0

max_dr=5

[[network_server.network_settings.extra_channels]]

frequency=867700000

min_dr=0

max_dr=5

[[network_server.network_settings.extra_channels]]

frequency=867900000

min_dr=0

max_dr=5

# Class B settings
[network_server.network_settings.class_b]
# Ping-slot data-rate.
ping_slot_dr=0

# Ping-slot frequency (Hz)
#
# Set this to 0 to use the default frequency plan for the configured region
# (which could be frequency hopping).
ping_slot_frequency=0

Network-server API

This is the network-server API that is used by ChirpStack Application Server or other

custom components interacting with ChirpStack Network Server.

[network_server.api]

ip:port to bind the api server

bind=“0.0.0.0:8000”

Backend defines the gateway backend settings.

The gateway backend handles the communication with the gateway(s) part of

the LoRaWAN network.

[network_server.gateway.backend]

Backend

type=“mqtt”

# MQTT gateway backend settings.
#
# This is the backend communicating with the LoRa gateways over a MQTT broker.
[network_server.gateway.backend.mqtt]
# MQTT topic templates for the different MQTT topics.
#
# The meaning of these topics are documented at:
# https://www.chirpstack.io/gateway-bridge/
#
# The default values match the default expected configuration of the
# ChirpStack Gateway Bridge MQTT backend. Therefore only change these values when
# absolutely needed.

# Event topic template.
event_topic="gateway/+/event/+"

# Command topic template.
#
# Use:
#   * "{{ .GatewayID }}" as an substitution for the LoRa gateway ID
#   * "{{ .CommandType }}" as an substitution for the command type
command_topic_template="gateway/{{ .GatewayID }}/command/{{ .CommandType }}"

# MQTT server (e.g. scheme://host:port where scheme is tcp, ssl or ws)
server="tcp://localhost:1883"

# Connect with the given username (optional)
username=""

# Connect with the given password (optional)
password=""

Metrics collection settings.

[metrics]

Timezone

The timezone is used for correctly aggregating the metrics (e.g. per hour,

day or month).

Example: “Europe/Amsterdam” or “Local” for the the system’s local time zone.

Rak2287 configuration help

This configuration configures ChirpStack Network Server for the EU868 band using a MQTT

broker to communicate with the gateways. Many options and defaults have been

omitted for simplicity.

For other bands, see the ./examples/ sub-directory.

See Configuration - ChirpStack open-source LoRaWAN<sup>®</sup> Network Server for a full

configuration example and documentation.

PostgreSQL settings.

Please note that PostgreSQL 9.5+ is required.

PostgreSQL dsn (e.g.: postgres://user:password@hostname/database?sslmode=disable).

Besides using an URL (e.g. ‘postgres://user:password@hostname/database?sslmode=disable’)

it is also possible to use the following format:

‘user=chirpstack_ns dbname=chirpstack_ns sslmode=disable’.

The following connection parameters are supported:

* dbname - The name of the database to connect to

* user - The user to sign in as

* password - The user’s password

* host - The host to connect to. Values that start with / are for unix domain sockets. (default is localhost)

* port - The port to bind to. (default is 5432)

* sslmode - Whether or not to use SSL (default is require, this is not the default for libpq)

* fallback_application_name - An application_name to fall back to if one isn’t provided.

* connect_timeout - Maximum wait for connection, in seconds. Zero or not specified means wait indefinitely.

* sslcert - Cert file location. The file must contain PEM encoded data.

* sslkey - Key file location. The file must contain PEM encoded data.

* sslrootcert - The location of the root certificate file. The file must contain PEM encoded data.

Valid values for sslmode are:

* disable - No SSL

* require - Always SSL (skip verification)

* verify-ca - Always SSL (verify that the certificate presented by the server was signed by a trusted CA)

* verify-full - Always SSL (verify that the certification presented by the server was signed by a trusted CA and the server host name matches the one in the certificate)

Redis settings

Please note that Redis 2.6.0+ is required.

Redis url (e.g. redis://user:password@hostname/0)

For more information about the Redis URL format, see:

https://www.iana.org/assignments/uri-schemes/prov/redis

Network-server settings.

Network identifier (NetID, 3 bytes) encoded as HEX (e.g. 010203)

LoRaWAN regional band configuration.

Note that you might want to consult the LoRaWAN Regional Parameters

specification for valid values that apply to your region.

See: https://www.lora-alliance.org/lorawan-for-developers

LoRaWAN network related settings.

Disable ADR

When set, this globally disables ADR.

[[network_server.network_settings.extra_channels]]

frequency=867100000

min_dr=0

max_dr=5

[[network_server.network_settings.extra_channels]]

frequency=867300000

min_dr=0

max_dr=5

[[network_server.network_settings.extra_channels]]

frequency=867500000

min_dr=0

max_dr=5

[[network_server.network_settings.extra_channels]]

frequency=867700000

min_dr=0

max_dr=5

[[network_server.network_settings.extra_channels]]

frequency=867900000

min_dr=0

max_dr=5

Network-server API

This is the network-server API that is used by ChirpStack Application Server or other

custom components interacting with ChirpStack Network Server.

ip:port to bind the api server

Backend defines the gateway backend settings.

The gateway backend handles the communication with the gateway(s) part of

the LoRaWAN network.

Backend

Metrics collection settings.

Timezone

The timezone is used for correctly aggregating the metrics (e.g. per hour,

day or month).

Example: “Europe/Amsterdam” or “Local” for the the system’s local time zone.

Join-server settings.

Default join-server settings.

This join-server will be used when resolving the JoinEUI is set to false