# OTAA LMIC node no longer showing in TTN console after 65535 frames up **URL:** \ **Category:** Application Development\ **Created:** [January 25, 2020, 11:41am UTC](https://www.thethingsnetwork.org/forum/t/otaa-lmic-node-no-longer-showing-in-ttn-console-after-65535-frames-up/33668 "2020-01-25T11:41:31Z")\ **Posts on this page:** 1\ **Showing post:** 8
**Author:** ![Jeff-UK](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/jeff-uk/32/35697_2.png) [@Jeff-UK](https://www.thethingsnetwork.org/forum/u/Jeff-UK)\ **Post date:** [January 26, 2020, 3:47pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-lmic-node-no-longer-showing-in-ttn-console-after-65535-frames-up/33668/8 "2020-01-26T15:47:16Z")
Hi @Allen as @Kersing states you are potentially conflating the two issues and I would add that whilst the regs allow higher duty cycles, there have been many posts on the Forum and elsewhere as to why you should not take that as permissive wrt social responsibility let alone wrt TTN FUP, e.g. this recent post from yours truely 😉 if you wouldnt mind taking a moment to read and note the **can** vs **should** element 🙂 > [@LoRaWAN Network Configuration](https://www.thethingsnetwork.org/forum/t/lorawan-network-configuration/33361/5): > > This is the TTN Forum, supporting private none TTN/TTI based networks is outside of scope.! Also wrt duty cycle regs. note just because they say you can use up to an given limit does not mean you should - atleast other than in exceptional circumstances (short term testing/mapping coverage/capacity for longer term optimisation and associated benefits, or during emergencies/alarm conditions). Even with LoRa’s interference mitigation and co-existance techniques the airwaves will become quickly clo… --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/otaa-lmic-node-no-longer-showing-in-ttn-console-after-65535-frames-up/33668)._