RAK7289 CV2 16 Channels - AS923 Bug with overlapping channels

tobyICT · December 1, 2024, 1:01am

Hi All,

Recently we have a job to configure a RAK7289 CV2 we purchased.
I’ve been reading through documentation both LoRa Alliance and partial help from TTNv3.
This is our first 16x channel gateway, where we have had experience with 50+ 8channel ones before.

Just to note, I see the same issue described below on both firmware versions:
WisGateOS2_2.2.6
&
WisGateOS2_2.2.8
Plan references are:

github.com

TheThingsNetwork/lorawan-frequency-plans/blob/master/AS_920_923.yml

band-id: AS_923
sub-bands:
- min-frequency: 922000000
  max-frequency: 923400000
uplink-channels:
- frequency: 923200000
  min-data-rate: 0
  max-data-rate: 5
  radio: 0
- frequency: 923400000
  min-data-rate: 0
  max-data-rate: 5
  radio: 0
- frequency: 922200000
  min-data-rate: 0
  max-data-rate: 5
  radio: 1
- frequency: 922400000
  min-data-rate: 0
  max-data-rate: 5

This file has been truncated. show original

github.com

TheThingsNetwork/lorawan-frequency-plans/blob/master/AS_920_923_TTN_AU.yml

sub-bands:
- min-frequency: 915000000
  max-frequency: 928000000
  duty-cycle: 1
dwell-time:
  uplinks: false
  downlinks: false
max-eirp: 30

github.com

TheThingsNetwork/lorawan-frequency-plans/blob/master/AS_923_925.yml

band-id: AS_923
sub-bands:
- min-frequency: 923200000
  max-frequency: 924600000
uplink-channels:
- frequency: 923200000
  min-data-rate: 0
  max-data-rate: 5
  radio: 0
- frequency: 923400000
  min-data-rate: 0
  max-data-rate: 5
  radio: 0
- frequency: 923600000
  min-data-rate: 0
  max-data-rate: 5
  radio: 0
- frequency: 923800000
  min-data-rate: 0
  max-data-rate: 5

This file has been truncated. show original

github.com

TheThingsNetwork/lorawan-frequency-plans/blob/master/AS_923_925_TTN_AU.yml

sub-bands:
- min-frequency: 915000000
  max-frequency: 928000000
  duty-cycle: 1
dwell-time:
  uplinks: false
  downlinks: false
max-eirp: 30

I’ve configured for Australia / AS923-1 plan use when doing initial setup, which shifts the plans higher up around the actual 923Mhz range instead of AS923-2,3,4 which are actually much lower in the 915Mhz area (which are also not advisable for use in Australia is my understanding.)

Note too, using Semtech Legacy Packet forwarder - as that has been the most reliable for us over the years for installs, customer of this gateway will however be using CUPS once we confirm working on TTNv3.

To make the best use of the 16channels I will be making the first and second concentrator AS1 and AS2, aka the Australian 920-923Mhz plan, and the 2nd concentrator the 923-925Mhz secondary plan (this will be done on purpose to load share by registering half end devices on primary plan and other half on 2nd plan, see links above for the primary channel plans + local Australia min/max and dwell time (not sure how dwell time is done at gateway level - assume is done at TTN/lora server level/application level as noted in past).
Something I wasn’t expecting but now I know now that the Gateway only has one EUI even though it has two concentrators - work around is configure TTN endpoint as two plans (but unsure how that will affect future LoRaWAN integration - plan is to use AWS IoT core AS923-1 server I believe, but haven’t got that far yet.)
The built in AS923 drop down selection you get by first having “confirm to LoRaWAN” ticked, doesn’t actually give you the correct bands - the bands are almost all wrong and do not allow for easy matching of the plan to say Australian AS923 “AS1” plan, so I have opted always when doing Asia / 923 to manual set the concentrators.

What I have run into however and unsure if a bug or I am not reading it correctly where the GUI doesn’t make mention/logical sense.
When I try to setup 1st and 2nd concentrator matching the below channels I get a warning about duplicate channels, it appears to be detecting this as a false positive.
The channels it is treating as duplicates are with AS1 and AS2 are the standard channels that overlap between the plans which allows for OTAA joining / channel plan selection, which I believe are 922000000 and 923400000

It appears that even though the concentrators are separate hardware that the firmware on the gateway is treating the configuration as mixed/shared (which to my understanding they should be treated separate.

Please see screenshot, it gets an “internal error message” too I believe.
Also the min/max range functions/exacting bands seem to be very glitched where channel set numbers will reset even if forced/saved, and these bugs also appear to reset my settings on the second concentrator.

Any help would be appreciated, or any knowledge of Beta firmware to correct it IF it is a bug.

Regards

Toby
ICT International