we run the software twice more, once with ADR off and once with ADR off and FI=3.
Unfortunately, the results are the same and I am really wondering how this hasn't appeared before in the forum. I will not post an image since it looks exactly the same: at random time, some of the devices rejoin.
This might seem like a minor issue, however, both our deployment scenarios - for which we purchased the last dozen of devices - are heavily affected by this. The SodaqOnes are to be deployed in two different types of landscape: very hilly and coastal water.
The devices will register in a controlled environment (adequate reception) and then will go mobile. Devices WILL get out of range but, as we have seen from our tests with other LoRa devices, a registered device which transmits while it moves on the edge of the coverage has significant chances to be received in such a landscape (frequent changes in altitude, flat rock surroundings, very low vegetation, no vegetation at all, water reflections, reflections on passibng by cargo boats etc). We need those chances to be used to transmit data and not reattempt a Join request which -under low quality signal conditions- will most probably fail.
Of course, there is ABP but having to use ABP for our deployment due to this is considered a downside.
Has anyone really tried to reproduce that?