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 procedure looping-OTAA #26

Open
Ajaynithish opened this issue Dec 19, 2019 · 6 comments
Open

Join procedure looping-OTAA #26

Ajaynithish opened this issue Dec 19, 2019 · 6 comments

Comments

@Ajaynithish
Copy link

@Heltec-Aaron-Lee . I am using the OTAA example- Heltec mini gateway- Heltec wireless shell as node. The join request sent by node is accepted in the server(both things network and Chirp stack).
Problem is it is the only thing repeating again and again(join request and accept). The join accept message is not reaching the node.
Thanks
Ajay

@Heltec-Aaron-Lee
Copy link
Contributor

Which frequency did you use? How many nodes do you have? Can you try with another one?

@Ajaynithish
Copy link
Author

Actually I am sending at every three default frequencies used in India. Only one node. @Heltec-Aaron-Lee

@Heltec-Aaron-Lee
Copy link
Contributor

Uhh, I think I know the reason, India uses AS923, but the ESP32_LoRaWAN code still don't have that frequency support.

I will add AS923 and AU915 within the next two days.

@Ajaynithish
Copy link
Author

Ajaynithish commented Dec 19, 2019

India have IN865. I have altered the EU868 part of code for Indian specifications and the join request are sent at 865 frequency, but still no data uplink and Thanks for the quick replay . One thing I noticed is that the first Rx window is not even open a millisecond (the timeout interrupt is issued) does it exist or am I imagining? @Heltec-Aaron-Lee @gibus27
Screenshot from 2019-12-19 16-23-58

@onexecute
Copy link

onexecute commented Feb 6, 2020

Make sure gateway is centered on the same frequencies as the thing (end device).

@Heltec-Aaron-Lee
Copy link
Contributor

I did a big update in the last few days, please try the newest update.

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