Closed rony-vargas closed 3 years ago
Station in general gives the LNS a lot of power to configure the gateway. This comes in handy when you find yourself having to fix/adjust local configuration remotely, if the need arises. Hence, the LNS config has priority over the station.conf config. This means, that the LNS must be sensible in what config it sends down.
Concretely, static hardware specific config should not be sent by the LNS unless the LNS knows exactly what it is doing.
For the case of TTN and the rssi_offset
field, you might want to bump this issue: https://github.com/TheThingsNetwork/lorawan-stack/issues/2130
Thanks @beitler that's make total sense to me. I will follow that issue and close this one.
This could be critical if I can demonstrate that SX1302 is missing packets because of that, if not, I still agree hardware parameters shouldn't be sent by LNS. I will try the basic packet forwarder (local.conf) with correct rssi_offset
and compare in the same board if there are still missed packets. I see others having similar "missing packets" issues with the SX1302
I am using a RAK2287 based gateway (SX1302) and it is dropping packets with high frequency, I have side by side a RAK2245 (SX1301) and it doesn't drop any packet from the nodes.
I believe one of the possible issues could be that the station is not honoring the
rssi_offset
from thestation.conf
, here is the log when the station starts and it shows the rssi offset to -166 which is set by TTN for US915 freq plan. but, is this right?See the ** marks for the line where it shows -166 rssi_offset. For this concentrator the
rssi_offset
value instation.conf
is set to-215.4
Should this really be overwritten by the freq plan config, or always should honor the
station.conf
file, which is documented in the Corecell Design?