Vraag

OTAA tx result "not joined" wheras message has been sent (and received)

  • 4 December 2018
  • 3 reacties
  • 695 keer bekeken
K
Hello All,

I am facing the following problem.
It is a node using the Microchip RN2483 (Version 1.0.3).
On startup the device sucessfully will join through OTAA.
Once the internal conditions are fulfilled (all sensor info is received) the module will intitate a mac tx uncnf
Result is a "not joined" response, but the message has effectively been transmitted.
The node thinking it might have been disconnected, initiates a join procedure and the cycle repeats itself.

Procedure is hardly reproducible, and seems to be somewhat location dependant, but not gateway specific.
Reseting a node in it's environment does not help.
Bringing a node back to office seems to help...

Would anybody have clue what is going (or what I am doing) wrong?

Thanks for any info

3 reacties

I
Reputatie 1
Badge
One common reason for "not joined' is your device simply did not receive the join accept message from the gateway.

Using wlogger you can see if ThinkPark received your JoinRequest message and sent an JoinAccept back.
I
Reputatie 1
Badge
So in the case the radio module "missed" the JoinAccept, it would think it is not joined, but still be able/try to transmit a message?
No,, as the JoinAccept message contains vital information needed to send messages to the network, e.g. device address.

The rejoin procedure has been implemented after having issues of same devices stopping sending after being disconnected (receiving a "not joined" after issuing mac tx command) with no apparent reasons after months of correct operation.

You should implement procedures to regularly re-join the network per 'guidelines' anyway, however nowhere is stated what 'regularly' is. I believe one of the reasons is: this mechanism allows the network to recycle device addresses (?) of defect/removed/whatever silent devices. I usually use a 1 week re-join interval, but guess that once a month would be fine as well.
K
One common reason for "not joined' is your device simply did not receive the join accept message from the gateway.

Using wlogger you can see if ThinkPark received your JoinRequest message and sent an JoinAccept back.

Thanks for your reaction.
So in the case the radio module "missed" the JoinAccept, it would think it is not joined, but still be able/try to transmit a message?
The rejoin procedure has been implemented after having issues of same devices stopping sending after being disconnected (receiving a "not joined" after issuing mac tx command) with no apparent reasons after months of correct operation.

Reageer


Forumvoorwaarden