Erroneous join behaviour with loraserver

ChirpStack Network Server
1

Hello again, I face some issues with some lorawan nodes (from libelium) that bothers me for some time.
The most important issue is the change at the join procedure that the node follows.

If it has used the loriot server previously and you perform a reset at a distance from the gateway, it then gradually lowers the data rate (SF7 all the way to SF12) in order to join successfully.
If it has used the loraserver previously and you perform a reset at a distance from the gateway, the data rate gets stuck (SF7 and then SF9 forever) and it never reaches the gateway.

Do you have any idea about what could cause this erroneous behaviour ? Thank you…
(Notice that I have no access to the node’s code, consider this as a RN2483 black box with ADR: true.)

2

It is very unlikely that a join-attempt is influenced by LoRa Server. As long as the device is not joined, LoRa Server doesn’t have any control over the data-rate so you should see the same behaviour as with any other network-server.

Only after a join-accept (sent by LoRa Server) LoRa Server is able to control the data-rate etc…

1 Like
3

That seems to a be a problem with the device code.

We have some RN2483 and they seem to be working fine (Join starts in 12 and is not modified) and they work perfectly with LoRa-Server

1 Like