# 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:** 5
**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:** [January 25, 2020, 3:15pm UTC](https://www.thethingsnetwork.org/forum/t/otaa-lmic-node-no-longer-showing-in-ttn-console-after-65535-frames-up/33668/5 "2020-01-25T15:15:00Z")
> [@Allen](#): > > I setup a test device to send data every ~3 sec For testing, one can also use the `ttnctl` command line tool to set the frame counter to some specific value, and then make the test node start with that value too, rather than starting at zero. This might also be needed [when the difference between device and TTN exceeds `MAX_FCNT_GAP`](https://www.thethingsnetwork.org/forum/t/after-resetting-frame-counters-payload-is-shown-on-gateway-traffic-but-not-in-application/19331/12), being 16,384. (But when adhering to [the Fair Access Policy](https://www.thethingsnetwork.org/forum/t/limitations-data-rate-packet-size-30-seconds-uplink-and-10-messages-downlink-per-day-fair-access-policy-guidelines/1300) that should only happen when erroneously resetting the frame counters in TTN Console.) > [@Allen](#): > > Changing my benchtop device in the TTN settings page immediately restored communication with the device. Just for future reference: what is the correct setting (for your LMIC device)? (I’d assume 32 bits, which is also the default in TTN Console.) --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/otaa-lmic-node-no-longer-showing-in-ttn-console-after-65535-frames-up/33668)._