# OTAA with LMIC and arduino+dragino\_shield doesn't work

**URL:** <https://www.thethingsnetwork.org/forum/t/otaa-with-lmic-and-arduino-dragino-shield-doesnt-work/4905>\
**Category:** End Devices (Nodes)\
**Created:** [January 18, 2017, 10:47am UTC](https://www.thethingsnetwork.org/forum/t/otaa-with-lmic-and-arduino-dragino-shield-doesnt-work/4905 "2017-01-18T10:47:29Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [February 19, 2017, 12:25pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-with-lmic-and-arduino-dragino-shield-doesnt-work/4905/9 "2017-02-19T12:25:14Z")

</div>

> [@3DPrinterDoctor](#):
>
> About 1 in 10 transmissions actually get passed the join request.

If “transmissions” refers to sending data, then unless it’s really only sending a few times a year, an OTAA node should not activate itself for each transmission; that’s just a waste of air time. If your node cannot save its state between transmissions then ABP might be a better fit, along with the decreased security of [disabling the frame counter checks](https://www.thethingsnetwork.org/forum/t/abp-node-stopped-working-fixed-by-creating-new-abp-why/3200/7). But going into a low power mode that preserves the activation details is much preferred.

As for OTAA: many more debugging steps and background in [OTAA ok, 12h later I get denied, reboot gateway –\> OK again …!?](https://www.thethingsnetwork.org/forum/t/otaa-ok-12h-later-i-get-denied-reboot-gateway-ok-again/2025) (Yes, that’s a long topic…)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/otaa-with-lmic-and-arduino-dragino-shield-doesnt-work/4905)._