# Big ESP32 + SX127x topic part 2 **URL:** \ **Category:** End Devices (Nodes)\ **Created:** [January 23, 2018, 2:11pm UTC](https://www.thethingsnetwork.org/forum/t/big-esp32-sx127x-topic-part-2/11973 "2018-01-23T14:11:55Z")\ **Posts on this page:** 1\ **Showing post:** 802
**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:** [August 30, 2018, 4:01pm UTC](https://www.thethingsnetwork.org/forum/t/big-esp32-sx127x-topic-part-2/11973/802 "2018-08-30T16:01:23Z")
> [@Lennyz1988](#): > > APB did also give me lot’s of problems. Messages not coming true, delays etc. Off-topic, but: ABP should not cause “lot’s of problems”. The only problems ABP might give you, which OTAA does not: - The need to reset frame counters when restarting a device. (Reset automatically for each OTAA Join Accept.) - The need to program the network settings into the device. (Set automatically in an OTAA Join Accept.) - Vendor lock-in to a specific network provider. (An OTAA node can join any network in its region, [if you can make it perform a new OTAA Join when needed](https://www.thethingsnetwork.org/forum/t/moving-a-device-from-loriot-to-ttn/17295/2).) So yes, OTAA is to be preferred (though it might be hard to join, if downlinks are not working), but **once a node has succeeded an OTAA Join, it’s behaving exactly the same as an ABP node**. On the other hand: if you’re doing an OTAA join very often, [you might run out of nonces](https://www.thethingsnetwork.org/forum/t/otaa-shows-activation-devnonce-not-valid-already-used/5079). So, for both ABP and OTAA, [one should persist the node’s state if that’s not preserved when sleeping](https://www.thethingsnetwork.org/forum/t/otaa-best-practice-how-to-not-join-every-time/14601/9). --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/big-esp32-sx127x-topic-part-2/11973)._