Hello Everyone
We noticed that everytime when we set ADR=off inside the RN2903, after the first transmission we received from the LoraServer the parameter ADR=TRUE (untill here, everything is OK), but after receiveing the DOWNLINK message with ADR=TRUE the Device (RN2903) turns its own flag ADR form FALSE to TRUE and starts to transmit packets as it is. Is this a BUG from the RN2903 or LoraServer is indeed forcing the ADR to the device as an incorrect action?
Below we can see the Lora Frames:
#############################################################################
UPLINK 1:
“uplinkMetaData”: {
“macPayload”: {
“fhdr”: {
“devAddr”: “09569c75”,
“fCtrl”: {
“adr”: false,
“adrAckReq”: false,
“ack”: false,
“fPending”: false,
DOWNLINK1:
"downlinkMetaData": {
“macPayload”: {
“fhdr”: {
“devAddr”: “09569c75”,
“fCtrl”: {
“adr”: true,
“adrAckReq”: false,
“ack”: true,
“fPending”: false,
“classB”: false
#############################################################################
UPLINK 2: (ADR MODIFIED FROM FALSE TO TRUE)
"uplinkMetaData": {
"rxInfo": [
"macPayload": {
"fhdr": {
"devAddr": "09569c75",
"fCtrl": {
"adr": true,
"adrAckReq": false,
"ack": false,
"fPending": false,
"classB": false
In short:
- RN2903 sends UPLINK with ADR: FALSE
- LORASERVER sends DOWNLINK with ADR:TRUE
- RN2903 modifies its ADR FILED from FALSE TO TRUE and send the UPLINK
my loraserver.toml has ADR as enabled:
# Disable ADR
#
# When set, this globally disables ADR.
disable_adr=false