Closed mjohanning99 closed 9 months ago
So after trying some more stuff, what finally worked was using the configuration for the iC880A and setting the reset pin to be 25. Not entirely sure why the default configuration for the LoRaGo PORT doesn't work; maybe something needs to be changed in the configuration for it?
And now it doesn't work anymore. Even when doing the same thing as yesterday, the same error I had has come back.
I decided to upgrade to version 4.0.0 and still could not get the LoRaPort GO to work. However, by selecting the iC880A gateway configuration in gateway-config
and then manually setting the reset_pin
in /etc/chirpstack-concentratord/sx1301/concentratord.toml
and then restarting concentratord through gateway-config
, I was able to consistently get the LoRaPort GO shields I have working. Setting the reset pin through the TUI of gateway-config
and does not anything. It worked only after manually setting the value of reset_pin
in the above-mentioned configuration file to 25
It really seems like there is a misconfigured reset pin somewhere in the default config for the LoRaPort GO; though that would not explain how setting a reset pin through gateway-config
did not work.
Is this still an issue with the latest OpenWrt based ChirpStack Gateway OS?
What happened?
I have connected a LoRaGo PORT to my Raspberry Pi 3 and used the LoRaGo PORT configuration in the "Setup LoRa concentrator shield" menu in gateway-config. However, no lights are glowing and no gateway ID is being configured.
I did see a closed issue here (#66) and commented on it a while ago, but there has not yet been an answer. As it still doesn't work months later, I decided to open another issue.
What did you expect?
The concentrator to start and work and to be given a gateway ID.
Steps to reproduce this issue
Connect the LoRaGo PORT to a Raspberry Pi and configuring it using gateway-config.
Could you share your log output?
Your Environment
Gateway OS 3.6.0 base Raspberry Pi 3