I’m having issues with getting my node to join the network. Here’s the summary: Node: https://northernmechatronics.com/products Gateway: RG191 Stack: Semtech Code: Class C example Since last week I’ve learned that I can mask the channels I transmit on to use only the 8 which my gateway listens …

TTN at this moment supports only class A… soon the V3 stack will be released that supports class C TTN network stack V3 central 1 https://www.thethingsnetwork.org/article/the-things-network-v3-stack https://www.youtube.com/watch?v=qw3Plxja1Qo

Okay I’ve now tried with the ClassA example and I’m seeing the same behavior. Sometimes the messages have a hard time even getting to the gateway. However if I select ABP activation then the messages arrive much more consistently. Is there any way to debug why a particular join request isn’t acknow…

can you make a console screenshot of a join attempt

I’ve discovered an issue with regards to antenna selection in my code. With that fixed the connection to the gateway seems much more reliable. Now I just need to sort out the join. I haven’t had a successful join in a few days now so I will double check all the EUIs but here’s a capture of what I’m …

yes, and from what I see the node and gateway are very close and that can have a negative influence to. try SF 7

I was able to join successfully again so I’m fairly certain the EUIs and keys are correct. However the join response is still very unreliable. 80-90% of the time it goes through all 8 channels without successfully connecting. I tried changing the SF to 7 but the console still shows it as 10 until it…

It seems like I’ve discovered a pattern to this which may present a clue. If I create a new device in an application I get a join accept immediately on the first request, and then up-links come through consistently. If I then reset the device the second join request accepted and then up-links are co…

So, TTN Console is not showing a Join Accept if the join fails? Then I assume OTAA shows "Activation DevNonce not valid: already used" ? (Ah, your screenshot indeed confirms no Join Accept is created. Click the Join Request for more details.)

Hmm this seems to make sense. A quick check in the Semtech FW shows that the DevNonce is just incremented on each boot which would explain the behavior I’m seeing. Is there anyway to clear this on TTN without having to delete the device? I’m guessing the firmware should probably handle this differe…

[image] danby: Is there anyway to clear this on TTN without having to delete the device? Well, like noted in the topic I linked to: [image] OTAA shows "Activation DevNonce not valid: already used" A workaround from @htdvisser on Slack, if you really need to clear the nonces that TTN has s…

Inconsistent/Unreliable Join Issues

End Devices (Nodes)

BoRRoZ November 11, 2018, 6:04pm 2

TTN at this moment supports only class A… soon the V3 stack will be released that supports class C

TTN network stack V3 central 1
https://www.thethingsnetwork.org/article/the-things-network-v3-stack
https://www.youtube.com/watch?v=qw3Plxja1Qo