You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
just a quick question concerning ADR and link check validation.
Afaics, ADR is enabled by default since in LMIC_reset(), LMIC.adrEnabled ist set to FCT_ADREN.
In the example code (OTAA), link check validation is disabled once the node joined.
case EV_JOINED:
Serial.println(F("EV_JOINED"));
// Disable link check validation (automatically enabled
// during join, but not supported by TTN at this time).
LMIC_setLinkCheckMode(0);
break;
which essentially sets adrAckReq to LINK_CHECK_OFF
Which makes sense of course since the node just changed its data rate and it needs to validate that the network still receives the uplink frames.
To put it in a nutshell, since ADR is enabled by default, disabling link check validation of a node that joins a network supporting/utilizing ADR is useless (but in the same time doesn't harm).
Can somebody confirm this?
Thanks and all the best, Frank
The text was updated successfully, but these errors were encountered:
Hi all,
just a quick question concerning ADR and link check validation.
Afaics, ADR is enabled by default since in LMIC_reset(), LMIC.adrEnabled ist set to FCT_ADREN.
which essentially sets adrAckReq to LINK_CHECK_OFFIn the example code (OTAA), link check validation is disabled once the node joined.
However, since ADR is enabled and once the network sends MAC commands that result in data rate optimizations, link check validation is enabled again.
Which makes sense of course since the node just changed its data rate and it needs to validate that the network still receives the uplink frames.
To put it in a nutshell, since ADR is enabled by default, disabling link check validation of a node that joins a network supporting/utilizing ADR is useless (but in the same time doesn't harm).
Can somebody confirm this?
Thanks and all the best, Frank
The text was updated successfully, but these errors were encountered: