-
Notifications
You must be signed in to change notification settings - Fork 44
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
Correct AU915 #19
Correct AU915 #19
Conversation
relates to helium/sx1302_hal#19
fix au915 Relates-to: helium/sx1302_hal#19 Closes: #38
- add as923_4 - rename as923_1, _2 and _3 - correct au915 Closes: #19 Relates-to: helium/sx1302_hal#19
- add as923_4 - rename as923_1, _2 and _3 - correct au915 - correct us915, kr920, in865 Closes: #19 Relates-to: helium/sx1302_hal#19
fix au915 for sx1301 and sx1302 Relates-to: helium/sx1302_hal#19 Closes: #38
Looking at this because I was going to add AU915 to the Frequency Plans page in the docs, went down the rabbit hole, and I'm wondering if this was actually originally correct and miners/sys.config was misleading. Looking at RP2-1.0.3 LoRaWAN Regional Parameters upstream channels 0 through 63 are 125 kHz wide and incremented linearly by 200kHz from 915.2 MHz to 927.8 MHz so channels 8 through 15 are:
Upstream channels 64 to 71 are 500 kHz wide and incremented by 1.6 MHz from 915.9 to 927.1:
So I suspect the 500 kHz channel is intended to be 65, rather than 918.2 as it looks has been changed here. Looks like this comes from the numerical sorting of the frequencies in sys.config which doesn't correspond to the actual channels. Otherwise as per that LoraWAN doc the downstream channels are all 500kHz wide with 600 kHz increments between 923.3 and 927.5, but I don't know enough about this to see where that fits in with this config:
I'm new to this so I might be on the wrong track, just thought I'd call out an inconsistency that I noticed. |
@lthiery @JayKickliter Not sure if you get a notification about this since it's merged already. |
@mdaviesnz your are correct and in fact on the sx1301 it breaks things. |
@shawaj @mdaviesnz if we are going to correct the AU915 configuration here, we must first fix it in miner/sys.config. But based on my reading, I think your corrections are right. @mdaviesnz would you care to open a PR against Miner presenting your findings? |
@lthiery what is wrong in sys.config? all of the frequencies from the initial config are present there https://github.com/helium/miner/blob/a5a99c355b12dd312603913c7cb938cba3750ab4/config/sys.config#L114 |
Sorry I misread. We need to simply revert this change it seems? And then update the test analysis software to be the following
|
Just for future reference also, the SX1257 has a bandwidth of 1MHz, so using std with 500kHz bandwidth and IF of 400kHz puts this beyond the range ... 400kHz + (500kHZ / 2) = 650kHZ which is higher than 550kHZ ( = 1.1MHz / 2) which is the usable bandwidth for 500kHz channels. Which is why it fails to work. For SX1250 not sure if this is the same |
Thanks for looking at this. |
miner/sys.config
presents:Meanwhile, prior to this PR, the results from analysis with sx13xx-conf:
Some corrections were made, including the centering of the radio0 range. The analysis now claims a match to
miner/sys.config
: