I expect that concentratord starts and read messages received on lora gateway.
Steps to reproduce this issue
Steps:
Download last chirpstack concentratord from github
decompress package
create concentratord.toml config file:
[concentratord]
# Log level.
#
# Valid options are:
# * TRACE
# * DEBUG
# * INFO
# * WARN
# * ERROR
# * OFF
#log_level="INFO"
log_level="TRACE"
# Log to syslog.
#
# When set to true, log messages are being written to syslog instead of stdout.
log_to_syslog=false
# Statistics interval.
stats_interval="30s"
# Disable CRC status filter.
#
# By default, the Concentratord will ignore received frames which do not have
# a valid CRC. This option makes it possible to disable this filter such that
# received frames without (valid) CRC can be analyzed.
disable_crc_filter=false
# Configuration for the (ZeroMQ based) API.
[concentratord.api]
# Event PUB socket bind.
event_bind="ipc:///tmp/concentratord_event"
# Command REP socket bind.
command_bind="ipc:///tmp/concentratord_command"
# When set to non-zero values, the static gateway location will be reported
# when the gateway does not have a GNSS module or when no GNSS location fix
# is available.
latitude=0.0
longitude=0.0
altitude=0
4. start concentratord via cli:
```RUST_BACKTRACE=full ./chirpstack-concentratord-sx1302 -c concentratord.toml```
## Could you share your log output?
already shared
## Your Environment
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm
lora gateway: WM1302
region: EU868
I attach UDP packet forwarder sx1302_hal working config files (udp_packet_forwarder_configs.zip)
[udp_packet_forwarder_configs.zip](https://github.com/user-attachments/files/16359604/udp_packet_forwarder_configs.zip)
What happened?
I used UDP packet forwarder to communicate with lora gateway model seeed_wm1302 and it works fine. I used this fork: https://github.com/peterpanstechland/sx1302_hal.git
Now I'm trying to use Chirpstack concentratord and it failed to start, this is the log:
What did you expect?
I expect that concentratord starts and read messages received on lora gateway.
Steps to reproduce this issue
Steps:
create concentratord.toml config file:
LoRa gateway configuration.
[gateway]
Antenna gain (dB).
antenna_gain=0
Public LoRaWAN network.
lorawan_public=true
Region.
#
The region of the gateway. Options:
EU868, US915, CN779, EU433, AU915, CN470, AS923, AS923_2, AS923_3, AS923_4,
KR923, IN865, RU864
#
Not not all the gateway models implement all regions.
region="EU868"
Gateway vendor / model.
#
This configures various vendor and model specific settings.
model="seeed_wm1302"
Gateway vendor / model flags.
#
Flag can be used to configure additional vendor / model features. The
following flags can be used:
#
Global flags:
GNSS - Enable GNSS / GPS support
USB - Use USB for concentrator communication (default is SPI)
model_flags=[]
Time fallback.
#
In case the gateway does not have a GNSS module or is unable to aquire a
GNSS fix, use the system-time for setting the 'time' field on RX.
time_fallback_enabled=true
LoRa concentrator configuration.
[gateway.concentrator]
Static gateway location.
[gateway.location]