Fcnt reached 65535 now only bad-mic

37 views
Skip to first unread message

MPC

unread,
Oct 16, 2020, 5:22:21 AM10/16/20
to LoRaWAN Server Users
Hi, searched the group for this problem but could not find anything regarding this error.

I have a sensor working in class A ABP Mode sending data at regular intervals. This has been working for days but when the Fcnt reached 65535 all messages on the LoRaWAN server showed up as bad-mic.

Tried to delete the sensor and re-enter the details on the server but now the fcnt-gap-too-large error is shown and although the frames showup, no data is shown and the application for the sensor is missing.

In the profile we have FCnt Check as disabled.

Any help or guidance greatly appreciated?

MPC

MPC

unread,
Oct 16, 2020, 7:11:07 AM10/16/20
to LoRaWAN Server Users
Okay it seems to be a bug in our sensor. Once the sensor reaches 65535 it stops incrementing the frame counter?

Sorry for the false alarm.

MPC

Reply all
Reply to author
Forward
0 new messages