-
Notifications
You must be signed in to change notification settings - Fork 2
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
AU915 Sub Band Select #2
Comments
Hi @paulalting i'm facing the same problem when trying to connect the gateway to TTN (which uses the 2nd sub band), what did you edit in the global.conf file, i'm a bit confused about it. Thanks. |
Hi David, if you go to the link I gave above and find the correct sub band file and then use this to edit your own global.conf file, then that should work. It is confusing for sure, as there are many differences between the way it works in different countries. Do you the US915 or AU915 band over there ? |
Ok i got it, very useful files to keep at hand. Here the recomended band is AU915 but i'm having problems using it, with the node fixed 3 meters away from the gateway some messages arrive with very low rssi, some are simply lost and just a few arrive with the suposed rssi values. I faced the same situation when testing US915 but masking the channels to the 8 used by the gateway, it worked as expected. Tried it for AU915 but the problem is still there. So i guess is a channel match bug i can not figure it out. I read some about that Australian ACMA regulation, maybe that is the answer. |
Hi @davidgmoscoso did you have any further success ? See here for details: mcci-catena/arduino-lmic#340 |
After installing on RAK831 Pilot Gateway and configuring via gateway-config I noticed there was no way to configure the sub band as is possible with LoRaServer-OS direct from Orne Brocaar.
To get this gateway to work correctly I had to manually edit the global.conf file for the required sub band used here in Australia.
From Orne Broccar github you will notice AU/US 915MHz sub band config files:
An update to the gateway-config scripts to allow this functionality would be helpful.
The text was updated successfully, but these errors were encountered: