Chirpstack V3 Network Server configuration for AS_923_4

HaimL · January 12, 2024, 5:34pm

I need some help configuring the network server for AS_923_4 (i.e. 917-920). This is what I have so far. What else am I missing?

# See https://www.chirpstack.io/network-server/install/config/ for a full
# configuration example and documentation.
#
# This file is for the AS_923_4 band. See the examples/ folder for more
# configuration examples.

[postgresql]
dsn="postgres://user:password@postgres:5433/lorawan_nsas923_4?sslmode=require"


[redis]
servers=[ "servername1:6378", "servernam2:6378" ]
password="PASSWORD"

# Database index.
#
# By default, this can be a number between 0-15.
database=0

# Redis Cluster.
#
# Set this to true when the provided URLs are pointing to a Redis Cluster
# instance.
cluster=false

# Master name.
#
# Set the master name when the provided URLs are pointing to a Redis Sentinel
# instance.
master_name=""

# Connection pool size.
#
# Default (when set to 0) is 10 connections per every CPU.
pool_size=0

# TLS enabled.
#
# Note: this will enable TLS, but it will not validate the certificate
# used by the server.
tls_enabled=true


[network_server]
net_id="009234"

[network_server.band]
name="AS_923_4"
frequency_min=917300000
frequency_max=917500000

[network_server.network_settings]
enabled_uplink_channels=[1, 2, 3, 4, 5, 6]


[network_server.gateway.backend.mqtt]
server="tcp://mqtt:1883"
# Event topic template.
    event_topic="as923_4/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="as923_4/gateway/{{ .GatewayID }}/command/{{ .CommandType }}"

[join_server.default]
server="http://chirpstack-application-server:8003"

sp193 · January 16, 2024, 1:39am

You need to configure a gateway bridge to receive messages from your AS923-4 gateways and to use this topic prefix (which contains “as923_4”).

It is also perhaps necessary to configure the uplink channels that Chirpstack shall inform your devices of, otherwise the devices will only work with the default channels. See the regions.network.extra_channels blocks of this part of the documentation: Configuration - ChirpStack open-source LoRaWAN® Network Server documentation

HaimL · January 16, 2024, 9:51pm

Thank you for your feedback. I’m aware of the GW bridge config and already done it once for eu868. I’m just looking for NS 923_4 example configurations people have already tested.

brocaar · January 17, 2024, 12:32pm

Hi @HaimL, here you can find the list of band names:

github.com

brocaar/lorawan/blob/master/band/band.go#L55


      
          	CN_470_510 Name = "CN_470_510"
          	CN_779_787 Name = "CN_779_787"
          	EU_433     Name = "EU_433"
          	EU_863_870 Name = "EU_863_870"
          	IN_865_867 Name = "IN_865_867"
          	KR_920_923 Name = "KR_920_923"
          	US_902_928 Name = "US_902_928"
          	RU_864_870 Name = "RU_864_870"
          )
          
          // Available ISM bands (by common name).
          const (
          	EU868   Name = "EU868"
          	US915   Name = "US915"
          	CN779   Name = "CN779"
          	EU433   Name = "EU433"
          	AU915   Name = "AU915"
          	CN470   Name = "CN470"
          	AS923   Name = "AS923"   // 0 MHz frequency offset
          	AS923_2 Name = "AS923-2" // -1.80 MHz frequency offset
          	AS923_3 Name = "AS923-3" // -6.60 MHz frequency offset

It should be set to AS923-4.

[network_server.network_settings]
enabled_uplink_channels=[1, 2, 3, 4, 5, 6]

This does not apply to the AS923 bands and you can remove this config. By default there are two channels active:

This can be extended in the same way as the EU868 region using the extra_channels option:

github.com

brocaar/chirpstack-network-server/blob/master/packaging/files/chirpstack-network-server-eu868.toml#L80


      
          
          # 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]]

For the other AS23-4 related setting values (min/max DR, RX2 freq, etc…), you might want to take a look at the AS923-4 config file that is shipped with ChirpStack v4: https://github.com/chirpstack/chirpstack/blob/master/chirpstack/configuration/region_as923_4.toml.