# Unconsistent uplink messages

**URL:** <https://www.thethingsnetwork.org/forum/t/unconsistent-uplink-messages/27447>\
**Category:** Dragino\
**Created:** [June 24, 2019, 12:43pm UTC](https://www.thethingsnetwork.org/forum/t/unconsistent-uplink-messages/27447 "2019-06-24T12:43:42Z")\
**Posts on this page:** 1\
**Showing post:** 6

<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:** [June 24, 2019, 2:25pm UTC](https://www.thethingsnetwork.org/forum/t/unconsistent-uplink-messages/27447/6 "2019-06-24T14:25:44Z")

</div>

So, I’m quite sure you’re actually seeing this:

> [@arjanvanb](#):
>
> or do you not see any data until some value of the frame counter is reached?

Look at the counters! And see [ABP node stopped working -\> Fixed by creating new ABP.. Why? :) - #7 by arjanvanb](https://www.thethingsnetwork.org/forum/t/abp-node-stopped-working-fixed-by-creating-new-abp-why/3200/7)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/unconsistent-uplink-messages/27447)._
