ADR Edge case & Endians
- This topic has 4 replies, 2 voices, and was last updated 6 years ago by .
Viewing 5 posts - 1 through 5 (of 5 total)
Viewing 5 posts - 1 through 5 (of 5 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: AEP Model › ADR Edge case & Endians
I have a number of end-devices on DR5 but during the day the RF environments gets noisy. I can see SNR of -10 and lot of doped frames.
So I thought I might try ADR cmd on my dev setup in the office.
So I can decrease the DR to say DR3 I get one or two frames at that rate.
Then the network server says No, and bumps my end-device up to DR5.
I thought it was at least 20 frames before the NS did ADR evaluation?
It looks like my approach isn’t going to work any thoughts?
Also it I’m confused on a Dot AT+CHM uses Big Endian 01FF
and ADR cmd on the NS uses Little Endian FF01 for the Channel Mask?
> new Buffer(“0341ff0101”, “hex”).toString(“base64”)
‘A0H/AQE=’
Thanks
Lawrence
What version of AEP are you testing?
LoRaWAN 1.0.3
Section 1.2
The octet order for all multi-octet fields is little endian
The channel mask in LinkADRReq is sent little endian.
Jason thanks helps to look..
I’m running AEP v1.7.0 on a Conduit
I have a v1.6.2 in the field and in the office should I try that?
Lawrence
AEP 1.7.0 has improved ADR over 1.6.2.
The network server will need a minimum of 6 packets before sending an update.
The network server will assign a DR to each of the last 11 packets based on SNR. If a DR has 6 packets assigned and is higher than the current DR an LinkADRReq is sent, unless a request has been sent in the last 4 packets.
The ADR packets tracking is always occuring. So if a device as ADR bit unset and sends several uplinks. It can get a LinkADRReq on the first downlink after setting ADR bit.
Also it will send an update every four packets if lowering the power at max DR until SNR is below 3 dB or min Power is reached.
Ok so I should be ok in the field as once I’ve dropped DR & device is using it I send a ADR disable cmd which it has.
But doesn’t look like my edge case will be solvable with manual ADR when running on v1.7.0.
Thanks
Lawrence