Problem with Seeed WM1302

ChirpStack Gateway OS
1

Hello community, my little Test Configuration for LoRa:

  1. Pi4b with Seed WM1302 Pi-Head
  2. Chirpstack 4.2 with Full-Image

The Seed Gateway WM1302 comes out form Sensecap M1 Helium-Hotspot.
I think the gw is ok and works correct.

My problem is, the Seed run max. 2 Min. and than goes offline.
I see the the gateway_id , add with this ID a gateway…but 2 Min. offline
Going back to to Chirp Stack - concentratord - check the config, apply again, but only for
a short time online.

tail systemlog:…
ue Aug 8 17:44:18 2023 daemon.notice mosquitto[1471]: 1691516658: New connection from 127.0.0.1:33094 on port 1883.
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Triggering sx1302 reset
Tue Aug 8 17:44:18 2023 daemon.notice mosquitto[1471]: 1691516658: New client connected from 127.0.0.1:33094 as ef76c9b5a742d0cc (p2, c0, k30).
Tue Aug 8 17:44:18 2023 daemon.notice mosquitto[1471]: 1691516658: New connection from 127.0.0.1:33096 on port 1883.
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Triggering sx1261 reset
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Setting i2c device path, path: /dev/i2c-1
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Setting i2c temperature sensor address, address: 57
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Setting board configuration, lorawan_public: true, clock_source: 0
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Setting up fine timestamp, enable: false
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Setting up concentrator channels
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring radio, radio: 0, enabled: true, center_freq: 867500000, type: SX1250
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring radio, radio: 1, enabled: true, center_freq: 868500000, type: SX1250
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Setting up concentrator channels
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring multi-SF LoRa channel, channel: 0, enabled: true, freq: 868100000, rf_chain: 1, if_freq: -400000
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring multi-SF LoRa channel, channel: 1, enabled: true, freq: 868300000, rf_chain: 1, if_freq: -200000
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring multi-SF LoRa channel, channel: 2, enabled: true, freq: 868500000, rf_chain: 1, if_freq: 0
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring multi-SF LoRa channel, channel: 3, enabled: true, freq: 867100000, rf_chain: 0, if_freq: -400000
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring multi-SF LoRa channel, channel: 4, enabled: true, freq: 867300000, rf_chain: 0, if_freq: -200000
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring multi-SF LoRa channel, channel: 5, enabled: true, freq: 867500000, rf_chain: 0, if_freq: 0
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring multi-SF LoRa channel, channel: 6, enabled: true, freq: 867700000, rf_chain: 0, if_freq: 200000
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring multi-SF LoRa channel, channel: 7, enabled: true, freq: 867900000, rf_chain: 0, if_freq: 400000
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring Std LoRa channel, enabled: true, freq: 868300000, rf_chain: 1, if_freq: -200000
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Configuring FSK channel, enabled: true, freq: 868800000, rf_chain: 1, if_freq: 300000
Tue Aug 8 17:44:18 2023 user.info chirpstack-concentratord-sx1302[4026]: Starting the concentrator
Tue Aug 8 17:44:19 2023 daemon.notice mosquitto[1471]: 1691516659: New client connected from 127.0.0.1:33096 as 69fa08887929239c (p2, c0, k30).
Tue Aug 8 17:44:21 2023 user.info chirpstack-concentratord-sx1302[4026]: Gateway ID retrieved, gateway_id: “0016c001f10c0018”
Tue Aug 8 17:44:21 2023 user.info chirpstack-concentratord-sx1302[4026]: Initializing JIT queue, capacity: 32
Tue Aug 8 17:44:21 2023 user.info chirpstack-concentratord-sx1302[4026]: Creating socket for publishing events, bind: ipc:///tmp/concentratord_event
Tue Aug 8 17:44:21 2023 user.info chirpstack-concentratord-sx1302[4026]: Creating socket for receiving commands, bind: ipc:///tmp/concentratord_command
Tue Aug 8 17:44:21 2023 user.info chirpstack-concentratord-sx1302[4026]: Enabling GPS device, tty_path: /dev/ttyAMA0
Tue Aug 8 17:44:21 2023 user.info chirpstack-concentratord-sx1302[4026]: Starting GPS validation loop
Tue Aug 8 17:44:22 2023 user.warn chirpstack-concentratord-sx1302[4026]: GPS time reference is not valid, age: 1691516662.172278443s
Tue Aug 8 17:44:23 2023 user.warn chirpstack-concentratord-sx1302[4026]: GPS time reference is not valid, age: 1691516663.172560841s
Tue Aug 8 17:44:24 2023 user.warn chirpstack-concentratord-sx1302[4026]: GPS time reference is not valid, age: 1691516664.172826629s
Tue Aug 8 17:44:25 2023 user.warn chirpstack-concentratord-sx1302[4026]: GPS time reference is not valid, age: 1691516665.173111178s
Tue Aug 8 17:44:26 2023 user.warn chirpstack-concentratord-sx1302[4026]: GPS time reference is not valid, age: 1691516666.173384375s
Tue Aug 8 17:44:27 2023 user.warn chirpstack-concentratord-sx1302[4026]: GPS time reference is not valid, age: 1691516667.17365711s
Tue Aug 8 17:44:28 2023 user.warn chirpstack-concentratord-sx1302[4026]: GPS time reference is not valid, age: 1691516668.173917604s
Tue Aug 8 17:44:29 2023 user.warn chirpstack-concentratord-sx1302[4026]: GPS time reference is not valid, age: 1691516669.174178469s
Tue Aug 8 16:36:49 2023 daemon.err uwsgi[1260]: *** has_emperor mode detected (fd: 7) ***
Tue Aug 8 16:36:49 2023 daemon.err uwsgi[1260]: [uWSGI] getting INI configuration from /etc/uwsgi/vassals/luci-webui.ini
Tue Aug 8 16:36:49 2023 daemon.err uwsgi[1260]: Tue Aug 8 16:36:49 2023 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini has been spawned
Tue Aug 8 16:36:49 2023 daemon.err uwsgi[1260]: Tue Aug 8 16:36:49 2023 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini is ready to accept requests
Tue Aug 8 16:36:49 2023 daemon.info uwsgi-luci: spawned uWSGI master process (pid: 4740)
Tue Aug 8 16:36:50 2023 daemon.err uwsgi[1260]: Tue Aug 8 16:36:50 2023 - [emperor] vassal /etc/uwsgi/vassals/luci-webui.ini is now loyal
Tue Aug 8 16:36:50 2023 daemon.err uwsgi[1260]: *** has_emperor mode detected (fd: 8) ***
Tue Aug 8 16:36:50 2023 daemon.err uwsgi[1260]: [uWSGI] getting INI configuration from /etc/uwsgi/vassals/luci-cgi_io.ini
Tue Aug 8 16:36:50 2023 daemon.err uwsgi[1260]: Tue Aug 8 16:36:50 2023 - [emperor] vassal /etc/uwsgi/vassals/luci-cgi_io.ini has been spawned
Tue Aug 8 16:36:50 2023 daemon.err uwsgi[1260]: Tue Aug 8 16:36:50 2023 - [emperor] vassal /etc/uwsgi/vassals/luci-cgi_io.ini is ready to accept requests

Any solution ? or more Logs / Debugging ?

2

I assume you are using GW OS v4.2.0-test.1. I’m aware there are some issues with this test-version and I’m working on an update (either today or else tomorrow). Known GPS related issues with this test-release are:

  • Linux console is mounted to UART interface to which the GNSS module is connected (thus console output goes to GNSS module and GNSS data is also going to console)
  • There is a missing config option causing some memory-alignment issues when interfacing with the Semtech HAL
  • Specifically for the Seeed WM1302 module, the GNSS module is not compatible with the Semtech HAL (the next version will come with GNSS disabled, maybe in one of the next versions I will add partial support, e.g. for at least providing location but not fine-timestamp)
3

@brocaar, thx for your answer. i will wait for the next release. But crazzy, process Gateway running
for 2 minutes and than stopped

Today i testing the Seed WM1302 Gateway Module with PiHat and the Seed Lora-net/sx1302_hal
and running seed’s packet-forwarder with no error and timeout process…

Thx for your work on the ChirpStack.

4

It is not crazy, it is caused by incorrect processing of the GNSS data, which at some point breaks the gps loop, which blocks the other threads (because a mutex is not released because of a panic).

5

This topic was automatically closed after 89 days. New replies are no longer allowed.