Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Join Request Accepted on Gateway, but not Node #289

Open
volnix opened this issue May 15, 2024 · 3 comments
Open

Join Request Accepted on Gateway, but not Node #289

volnix opened this issue May 15, 2024 · 3 comments

Comments

@volnix
Copy link

volnix commented May 15, 2024

I'm attempting to join an HTCC-AB01 Cubecell node to a private gateway. I've successfully joined a Heltec esp32 to this gateway.

With the CubeCell device I'm unable to successfully join (according to the node) and send an uplink packet. Below is the output from serial:

Copyright @2019-2020 Heltec Automation.All rights reserved.

AT Rev 1.3
+AutoLPM=1

+LORAWAN=1

+KeepNet=0
+OTAA=1
+Class=A
+ADR=1
+IsTxConfirmed=0
+AppPort=2
+DutyCycle=15000
+ConfirmedNbTrials=4
+ChMask=0000000000000000000000FF
+DevEui=695E38A9E008EFA4(For OTAA Mode)
+AppEui=0101010101010101(For OTAA Mode)
+AppKey=[redacted](For OTAA Mode)
+NwkSKey=15B1D0EFA463DFBE3D11181E1EC7DA85(For ABP Mode)
+AppSKey=D72C78758CDCCABF55EE4A778D16EF67(For ABP Mode)
+DevAddr=007E6AE1(For ABP Mode)

LoRaWAN US915 Class A start!

joining...join failed, join again at 30s later
join failed, join again at 30s later

On my gateway I see successful joins:

image

In AWS IoT Core, I see successful joins too:

image

Why am I seeing successful joins on the gateway and LNS, but not the device?

@volnix
Copy link
Author

volnix commented May 16, 2024

Update: I tried ABP mode as well and was also unsuccessful

@jackwilliams2480
Copy link

A little late, but I was running into this error and for a while couldn't understand what was going wrong. In my case, I found that the Heltec example code defaults to the first sub band for US915, which is 902.3 - 903.7MHz and on channels 0-7. The arduino code shows:

/*LoraWan channelsmask, default channels 0-7*/ 
uint16_t userChannelsMask[6]={ 0x00FF,0x0000,0x0000,0x0000,0x0000,0x0000 };

A lot of gateways default to the second sub band which is used by TTN. That is why your gateway might receive a request, because it is listening, not necessarily "connecting" to a device, send an accept, but the accept is out of scope for the node to receive back. At least that's my understanding, probably not fully correct. To fix this, you can either change your gateway to sub band 1, or the code to support subband 2, or whatever sub band you are using.

@eikaramba
Copy link

interesting, in regards to 868mhz i think it is not needed as "The EU868 band does not technically have a concept of a sub-band. The three default frequencies (868.1, 868.3, 868.5) are mandatory and operators have a choice to define the other 5 channels." from https://www.thethingsnetwork.org/forum/t/sub-band-handling-for-lorawan-eu868-band/61706/4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants