Frequency plan for Uzbekistan

Gateways
1

Hi I am from Uzbekistan, I tried make gateway with OrangePi one Ebyte e106 915MHZ SX1302 module, and I tried Uzbekistan frequency plan in frequency plan list I registered it, it connected to TTN but I use US915 configuration in source code of gateway and end node (ra-08h kit, asr6601) source code also configured with US915. I am looking for gateway and end node configuration for Uzbekistan freq plan.
This is piece of code: {
“SX130x_conf”: {
“com_type”: “SPI”,
“com_path”: “/dev/spidev0.0”,
“lorawan_public”: true,
“clksrc”: 0,
“antenna_gain”: 0, /* antenna gain, in dBi /
“full_duplex”: false,
“fine_timestamp”: {
“enable”: false,
“mode”: “all_sf” / high_capacity or all_sf /
},
“lbt”: {
“enable”: false / LBT for 500 Khz channels is not supported /
}
},
“radio_0”: {
“enable”: true,
“type”: “SX1250”,
“freq”: 904300000,
“rssi_offset”: -215.4,
“rssi_tcomp”: {“coeff_a”: 0, “coeff_b”: 0, “coeff_c”: 20.41, “coeff_d”: 2162.56, “coeff_e”: 0},
“tx_enable”: true,
“tx_freq_min”: 923000000,
“tx_freq_max”: 928000000,
“tx_gain_lut”:[
{“rf_power”: 12, “pa_gain”: 0, “pwr_idx”: 15},
{“rf_power”: 13, “pa_gain”: 0, “pwr_idx”: 16},
{“rf_power”: 14, “pa_gain”: 0, “pwr_idx”: 17},
{“rf_power”: 15, “pa_gain”: 0, “pwr_idx”: 19},
{“rf_power”: 16, “pa_gain”: 0, “pwr_idx”: 20},
{“rf_power”: 17, “pa_gain”: 0, “pwr_idx”: 22},
{“rf_power”: 18, “pa_gain”: 1, “pwr_idx”: 1},
{“rf_power”: 19, “pa_gain”: 1, “pwr_idx”: 2},
{“rf_power”: 20, “pa_gain”: 1, “pwr_idx”: 3},
{“rf_power”: 21, “pa_gain”: 1, “pwr_idx”: 4},
{“rf_power”: 22, “pa_gain”: 1, “pwr_idx”: 5},
{“rf_power”: 23, “pa_gain”: 1, “pwr_idx”: 6},
{“rf_power”: 24, “pa_gain”: 1, “pwr_idx”: 7},
{“rf_power”: 25, “pa_gain”: 1, “pwr_idx”: 9},
{“rf_power”: 26, “pa_gain”: 1, “pwr_idx”: 11},
{“rf_power”: 27, “pa_gain”: 1, “pwr_idx”: 14}
]
},
“radio_1”: {
“enable”: true,
“type”: “SX1250”,
“freq”: 905000000,
“rssi_offset”: -215.4,
“rssi_tcomp”: {“coeff_a”: 0, “coeff_b”: 0, “coeff_c”: 20.41, “coeff_d”: 2162.56, “coeff_e”: 0},
“tx_enable”: false
},
“chan_multiSF_All”: {“spreading_factor_enable”: [ 5, 6, 7, 8, 9, 10, 11, 12 ]},
“chan_multiSF_0”: {“enable”: true, “radio”: 0, “if”: -400000}, / Freq : 903.9 MHz*/
“chan_multiSF_1”: {“enable”: true, “radio”: 0, “if”: -200000}, /* Freq : 904.1 MHz*/
“chan_multiSF_2”: {“enable”: true, “radio”: 0, “if”: 0}, /* Freq : 904.3 MHz*/
“chan_multiSF_3”: {“enable”: true, “radio”: 0, “if”: 200000}, /* Freq : 904.5 MHz*/
“chan_multiSF_4”: {“enable”: true, “radio”: 1, “if”: -300000}, /* Freq : 904.7 MHz*/
“chan_multiSF_5”: {“enable”: true, “radio”: 1, “if”: -100000}, /* Freq : 904.9 MHz*/
“chan_multiSF_6”: {“enable”: true, “radio”: 1, “if”: 100000}, /* Freq : 905.1 MHz*/
“chan_multiSF_7”: {“enable”: true, “radio”: 1, “if”: 300000}, /* Freq : 905.3 MHz*/
“chan_Lora_std”: {“enable”: true, “radio”: 0, “if”: 300000, “bandwidth”: 500000, “spread_factor”: 8, /* Freq : 904.6 MHz*/
“implicit_hdr”: false, “implicit_payload_length”: 17, “implicit_crc_en”: false, “implicit_coderate”: 1},
“chan_FSK”: {“enable”: false, “radio”: 1, “if”: 300000, “bandwidth”: 125000, “datarate”: 50000} /* Freq : 868.8 MHz*/
},

"gateway_conf": {
    "gateway_ID": "-----------------",
    /* change with default server address/ports */
    "server_address": "au1.cloud.thethings.network",
    "serv_port_up": 1700,
    "serv_port_down": 1700,
    /* adjust the following parameters for your network */
    "keepalive_interval": 10,
    "stat_interval": 30,
    "push_timeout_ms": 100,
    /* forward only valid packets */
    "forward_crc_valid": true,
    "forward_crc_error": false,
    "forward_crc_disabled": false,
    /* GPS configuration */
    "gps_tty_path": "/dev/ttyS0",
    /* GPS reference coordinates */
    "ref_latitude": 0.0,
    "ref_longitude": 0.0,
    "ref_altitude": 0,
    /* Beaconing parameters */
    "beacon_period": 0, /* disable class B beacon */
    "beacon_freq_hz": 869525000,
    "beacon_datarate": 9,
    "beacon_bw_hz": 125000,
    "beacon_power": 14,
    "beacon_infodesc": 0
},

"debug_conf": {
    "ref_payload":[
        {"id": "0xCAFE1234"},
        {"id": "0xCAFE2345"}
    ],
    "log_file": "loragw_hal.log"
}

}

2

Why? Given even a cursory search would show (per LoRa-Alliance RP’s):

image

Whilst 862-868 Mhz and 905-915+Mhz modules can sometimes be bent to cover the alternate bands -usually with significant RF attenuation - such a step is all but guaranteed to fail with 433Mhz, unless module engineered for such use!

But if you look through the rest of your post you see it littered with some AS923, some US/AU? 915 and even some EU 868 freq settings. Besides not working likely you are also transmitting illegally in territory (IANAL!) recommend you stop & start afresh with correct hardware and settings ASAP.

3

image
image1164×898 152 KB

4

And we would know this how? Bit blunt, not the politest way of letting us know.

You still have the two three issues of using a 915MHz concentrator card for 868 or 927 and the wholesale misconfiguration of mixed frequencies and transmitting on 915MHz isn’t legal for you.

Screen shots are fine, but please crop them to size.

5

That appears to be local RA doc vs anything from L-A. In terms of LoRaWAN specifically vs ISM band generally, we would normally take advice from L-A, who publish and manage the associated recomended frequency plan(s). Note the doc allows for ‘bands’ of spectrum, it says nothing how how they may be used and channelised or what duty cycles etc (or other limits/constraints might apply - dwell times? LBT? SF limits, payload sizes, etc. - appears likely implied as a potential requirement or mitigation but no details shown) which is where you then get into the weeds of how it might be implemented (L-A guidance required here).

Whilst I keep a local copy of the L-A RP’s on laptops, field service machines and my servers for quick reference (as used for the image I posted), if in doubt or where looking for something new I go to the L-A resources directly. Before responding to you I did just that and the last public RP appears to be to (c)2022 RP v …-04, which I quoted. (As you might expect - as a volunteer providing limited guidance - I would not normally go trawling through specific local Regulatory Authority details for new updates in a specific case…will leave that to others with more experience/access in the specific territory, if any to be found on the Forum) Perhaps L-A have a new update for your territory and others pending release?..perhaps you might approach them for guidance? Not sure if they will be represented at the upcoming TTConference in Amsterdam, if so if you attend you might ask them directly? To attempt to use the RF spectrum without fullsome guidance and details of the (local) regs is invite potential interop/compatability problems as a minimum, and possible legal response up to and including substantial fines and even jail time in extremis…your choice :slight_smile: (Again IANAL!)

6

Thanks for your feedback everyone on this!