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

Correct AU915 #19

Merged
merged 1 commit into from
Jul 26, 2021
Merged

Correct AU915 #19

merged 1 commit into from
Jul 26, 2021

Conversation

lthiery
Copy link
Member

@lthiery lthiery commented Jul 26, 2021

miner/sys.config presents:

'AU915' => [916.8, 917.0, 917.2, 917.4, 917.5, 917.6, 917.8, 918.0, 918.2],

Meanwhile, prior to this PR, the results from analysis with sx13xx-conf:

sx13xx-conf ~/sx1302_hal/packet_forwarder/global_conf.json.sx1250.AU915 AU915
1        916.8 MHz
2        917 MHz
3        917.2 MHz
4        917.4 MHz
5        917.6 MHz
6        917.8 MHz
7        918 MHz
8        918.2 MHz
Fat LoRa 917.5 MHz, BW 500 KHz
FSK      Disabled
Channel 4 mismatch! Expected 917500000, but got 917600000
Channel 5 mismatch! Expected 917600000, but got 917800000
Channel 6 mismatch! Expected 917800000, but got 918000000
Channel 7 mismatch! Expected 918000000, but got 918200000
Channel 8 mismatch! Expected 918200000, but got 917500000

Some corrections were made, including the centering of the radio0 range. The analysis now claims a match to miner/sys.config:

sx13xx-conf ~/sx1302_hal/packet_forwarder/global_conf.json.sx1250.AU915 AU915
1        916.8 MHz
2        917 MHz
3        917.2 MHz
4        917.4 MHz
5        917.5 MHz
6        917.6 MHz
7        917.8 MHz
8        918 MHz
Fat LoRa 918.2 MHz, BW 500 KHz
FSK      Disabled

@lthiery lthiery changed the base branch from master to helium/hotspot July 26, 2021 22:36
@JayKickliter JayKickliter merged commit bcc18e9 into helium/hotspot Jul 26, 2021
@JayKickliter JayKickliter deleted the lthiery/correct-AU915 branch July 26, 2021 22:40
shawaj added a commit to NebraLtd/hm-pktfwd that referenced this pull request Aug 25, 2021
shawaj added a commit to NebraLtd/hm-pktfwd that referenced this pull request Aug 26, 2021
fix au915

Relates-to: helium/sx1302_hal#19
Closes: #38
shawaj added a commit to NebraLtd/hm-pktfwd that referenced this pull request Aug 26, 2021
- add as923_4
- rename as923_1, _2 and _3
- correct au915

Closes: #19
Relates-to: helium/sx1302_hal#19
shawaj added a commit to NebraLtd/hm-pktfwd that referenced this pull request Aug 26, 2021
- add as923_4
- rename as923_1, _2 and _3
- correct au915
- correct us915, kr920, in865

Closes: #19
Relates-to: helium/sx1302_hal#19
shawaj added a commit to NebraLtd/hm-pktfwd that referenced this pull request Aug 26, 2021
fix au915 for sx1301 and sx1302

Relates-to: helium/sx1302_hal#19
Closes: #38
@mdaviesnz
Copy link

mdaviesnz commented Aug 28, 2021

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:

8	916.8
9	917
10	917.2
11	917.4
12	917.6
13	917.8
14	918
15	918.2

Upstream channels 64 to 71 are 500 kHz wide and incremented by 1.6 MHz from 915.9 to 927.1:

64	915.9
65	917.5 <--
66	919.1
67	920.7
68	922.3
69	923.9
70	925.5
71	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:

0	923.3
1	923.9
2	924.5
3	925.1
4	925.7
5	926.3
6	926.9
7	927.5

I'm new to this so I might be on the wrong track, just thought I'd call out an inconsistency that I noticed.

@mdaviesnz
Copy link

@lthiery @JayKickliter Not sure if you get a notification about this since it's merged already.

@shawaj
Copy link

shawaj commented Sep 3, 2021

@mdaviesnz your are correct and in fact on the sx1301 it breaks things.

See NebraLtd/hm-pktfwd#48

@shawaj shawaj mentioned this pull request Sep 3, 2021
@lthiery
Copy link
Member Author

lthiery commented Sep 3, 2021

@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?

@shawaj
Copy link

shawaj commented Sep 3, 2021

@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

@lthiery
Copy link
Member Author

lthiery commented Sep 3, 2021

Sorry I misread. We need to simply revert this change it seems? And then update the test analysis software to be the following

pub const AU915_UPLINK_FREQUENCIES: [usize; 9] = [
    916_800_000,
    917_000_000,
    917_200_000,
    917_400_000,
    917_600_000,
    917_800_000,
    918_000_000,
    918_200_000,
    917_500_000, // fat channel
];

@shawaj
Copy link

shawaj commented Sep 3, 2021

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

@mdaviesnz
Copy link

Thanks for looking at this.
I expect reverting this would fix in the short term. Maybe needs to be stored as an ordered list, or indexed by channel number, perhaps with bandwidth details too, to avoid this in the future (or with other band plans).

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

Successfully merging this pull request may close these issues.

None yet

4 participants