I have started to migrate my devices to the v3 stack.
There were no problems at first and everything works as expected.
About my nodes, I use the IMST IM881A for LoRaWAN. (MAC 1.0.2)
However, I have problems with the nodes that have a high distance to the gateways.The SF factor is slowly increased by the node. With v2, some stayed at SF9. Others at SF10-12. Now the SF factor is increased again normally. But whenever the first packets arrive with e.g. SF10, it is reduced again to SF7 by ADR command. And then I get huge data gaps. Every time something arrives again, but the ADR command resets the DR to 5.
Why does the v3 stack do that? The Network Server must see on the counter that the last 100 packets or more have not arrived. Why does it always set to SF7 again?
Does anyone have an idea what the problem is and how I can change it?
I use unconfirmed uplinks. 5-10 per hour.
I can’t say for sure if this case was really reduced to SF7, because I didn’t record the console. But I have seen it before, although the receiving values were not so good.
The ADR from the v3-stack is unfortunately bad in my experience and should be adjusted.I measure meteorological data and these should be more or less complete.
Found another case where it is the same.
This is how it looks then, on 03/28 I turned off my TTIG.
Then I waited, but ADR comes to no satisfactory settings. Almost everything is lost
This was not the case with TTN-v2. ADR adapted more slowly, but actually about 50% of the packets arrived after successful adaptation.
Can I use ttn-lw-cli to add my own values?
ttn-lw-cli end-devices set <app-id> <dev-id> --mac-state.desired-parameters.adr-data-rate-index
ttn-lw-cli end-devices set <app-id> <dev-id> --mac-state.desired-parameters.adr-tx-power-index
ttn-lw-cli end-devices set <app-id> <dev-id> --mac-state.desired-parameters.adr-nb-trans