Skip to Content

Changes for page Change Gateway Power

Last modified by Xiaoling on 2022/08/10 15:18
From version 14.1
edited by Kilight Cao
on 2022/06/23 14:37
Change comment: There is no comment for this version
To version 1.8
edited by Xiaoling
on 2022/05/14 13:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
Content
... ... @@ -1,19 +1,16 @@
1 -= Overview: =
1 += Introduction =
2 2  
3 -In LoRaWAN protocol, the gateway transmit packet uses the output power base on the Power Index from the LoRaWAN server downlink. for example, the LoRaWAN server sends a downlink with this info "rf_power=14", gateway got this info and it will search the index for rf_power=14 and use the related rf setting to set output power. In some cases, the LoRaWAN server might set the rf-power to a quite low value ( for example 0dB) which is not practical for use. In such a case, the User can manually change the rf_power=0's rf settings to a higher power out. Below are the methods.
3 +(((
4 +In LoRaWAN protocol, the gateway output power refer to the downstream packets sent by Gateway. This output power is controlled by LoRaWAN server.
5 +)))
4 4  
7 +(((
8 +Gateway maintain a power index in the file: /etc/lora/global_conf.json for example:
9 +)))
5 5  
6 -= Change Power for Semtech UDP Paket forward connection =
7 -
8 -----
9 -
10 -In LoRaWAN protocol, the gateway output power refers to the downstream packets sent by Gateway. This output power is controlled by the LoRaWAN server.
11 -
12 -Gateway maintains a power index in the file: /etc/lora/global_conf.json for example:
13 -
14 -
15 15  (% class="box" %)
16 16  (((
13 +(((
17 17  "tx_lut_3": {
18 18   "desc": "TX gain table, index 3",        ~/~/ Index 3 refer to rf_power: 15dB. device will set the pa_gain,mix_gain,dig_gain 
19 19   "pa_gain": 2,                            ~/~/ to the value mentioned here so to generate 15dB output power.
... ... @@ -28,107 +28,24 @@
28 28   "rf_power": 16,
29 29   "dig_gain": 0
30 30  )))
28 +)))
31 31  
32 -(% class="mark" %)Note: If when lorawan server specifies a rf_power that is not listed above. gateway will choose the closest power. profile.
33 -
34 -
35 -When the LoRaWAN server sends a downlink stream, the server will also ask the gateway to use rf_power as output. So users don't need to consider controlling on the gateway side.
36 -
37 -If users want to always use a higher power or a lower power. Users can modify the pa_gain,mix_gain, and dig_gain to specify rf_power to achieve this purpose. This is not recommended, because this might break the regulator for a specific country.
38 -
39 -Please note, that the global_conf.json file will be overwritten by the match region files in /etc/lora/cfg-30x when changing settings on the web. So the user needs to change the files in /etc/lora/cfg-cfg-30x instead of global_conf.json
40 -
41 -
42 -= Change Power for LoRaWAN Basic Station connection =
43 -
44 -----
45 -
46 -First, you need to find out what is the chip module of the gateway?
47 -
48 -(% class="box infomessage" %)
49 49  (((
50 -cat /var/iot/chip
31 +When LoRaWAN server sends a downlink stream, server will also ask the gateway to use which rf_power as output. So user don't need to consider to control in the gateway side.
51 51  )))
52 52  
53 -[[image:image-20220623140335-1.png||height="241" width="378"]]
54 -
55 -Gateways using the SX1301 LoRaWAN Concentrator are the LG308 and DLOS8.
56 -
57 -
58 -**SX1301 Change Power for LoRaWAN Basic Station Connection example:**
59 -
60 -Gateway maintains a power index in the file: /etc/station/station-sx1301.conf for example:
61 -
62 -(% class="box" %)
63 63  (((
64 -{
65 - /* If slave-X.conf present this acts as default settings */
66 - "SX1301_conf": { /* Actual channel plan is controlled by server */
67 - "lorawan_public": true, /* is default */
68 - "clksrc": 1, /* radio_1 provides clock to concentrator */
69 - /* path to the SPI device, un-comment if not specified on the command line e.g., RADIODEV=/dev/spidev0.0 */
70 - "device": "/dev/spidev1.0",
71 - /* freq/enable provided by LNS - only HW specific settings listed here */
72 -
73 - ** |<~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-(% style="color:red" %)Add parameters:"tx_gain_lut"  :  [ TX_GAIN_LUT, .. ](%%)**
74 -
75 - "radio_0": {
76 - "type": "SX1257",
77 - "rssi_offset": -166.0,
78 - "tx_enable": true,
79 - "antenna_gain": 0
80 - },
81 - "radio_1": {
82 - "type": "SX1257",
83 - "rssi_offset": -166.0,
84 - "tx_enable": false
85 - }
86 - /* chan_multiSF_X, chan_Lora_std, chan_FSK provided by LNS */
87 - },
35 +
88 88  )))
89 89  
90 -(% class="box" %)
91 91  (((
92 -{
93 - /* If slave-X.conf present this acts as default settings */
94 - "SX1301_conf": { /* Actual channel plan is controlled by server */
95 - "lorawan_public": true, /* is default */
96 - "clksrc": 1, /* radio_1 provides clock to concentrator */
97 - /* path to the SPI device, un-comment if not specified on the command line e.g., RADIODEV=/dev/spidev0.0 */
98 - "device": "/dev/spidev1.0",
99 - /* freq/enable provided by LNS - only HW specific settings listed here */
100 - "tx_gain_lut":[
101 - {"rf_power": 12, "pa_gain": 2, "mix_gain": 11, "dig_gain": 2, "dac_gain": 3},
102 - {"rf_power": 13, "pa_gain": 2, "mix_gain": 10, "dig_gain": 0, "dac_gain": 3},
103 - {"rf_power": 14, "pa_gain": 2, "mix_gain": 12, "dig_gain": 2, "dac_gain": 3},
104 - {"rf_power": 15, "pa_gain": 2, "mix_gain": 13, "dig_gain": 2, "dac_gain": 3},
105 - {"rf_power": 16, "pa_gain": 2, "mix_gain": 13, "dig_gain": 1, "dac_gain": 3},
106 - {"rf_power": 17, "pa_gain": 2, "mix_gain": 14, "dig_gain": 1, "dac_gain": 3},
107 - {"rf_power": 18, "pa_gain": 2, "mix_gain": 15, "dig_gain": 2, "dac_gain": 3},
108 - {"rf_power": 19, "pa_gain": 2, "mix_gain": 15, "dig_gain": 1, "dac_gain": 3},
109 - {"rf_power": 20, "pa_gain": 2, "mix_gain": 15, "dig_gain": 1, "dac_gain": 3},
110 - {"rf_power": 21, "pa_gain": 3, "mix_gain": 9, "dig_gain": 0, "dac_gain": 3},
111 - {"rf_power": 22, "pa_gain": 3, "mix_gain": 10, "dig_gain": 0, "dac_gain": 3},
112 - {"rf_power": 23, "pa_gain": 3, "mix_gain": 11, "dig_gain": 1, "dac_gain": 3},
113 - {"rf_power": 24, "pa_gain": 3, "mix_gain": 12, "dig_gain": 0, "dac_gain": 3},
114 - {"rf_power": 25, "pa_gain": 3, "mix_gain": 14, "dig_gain": 0, "dac_gain": 3},
115 - {"rf_power": 26, "pa_gain": 3, "mix_gain": 14, "dig_gain": 0, "dac_gain": 3},
116 - {"rf_power": 27, "pa_gain": 3, "mix_gain": 14, "dig_gain": 0, "dac_gain": 3}
117 - ],
118 - "radio_0": {
119 - "type": "SX1257",
120 - "rssi_offset": -166.0,
121 - "tx_enable": true,
122 - "antenna_gain": 0
123 - },
124 - "radio_1": {
125 - "type": "SX1257",
126 - "rssi_offset": -166.0,
127 - "tx_enable": false
128 - }
129 - /* chan_multiSF_X, chan_Lora_std, chan_FSK provided by LNS */
130 - },
39 +If user want to always use a higher power or a lower power. User can modify the pa_gain,mix_gain,dig_gain for specify rf_power to achieve this purpose. This is not recommend, because this might break the regulator for specify country.
131 131  )))
132 -If users want to always use a higher power or a lower power. Users can modify the pa_gain,mix_gain, and dig_gain to specify rf_power to achieve this purpose. This is not recommended, because this might break the regulator for a specific country.
133 133  
42 +(((
134 134  
44 +)))
45 +
46 +(((
47 +Please note, the global_conf.json file will be overwrite by the match region files in /etc/lora/cfg-30x when change settings in the web. So user need to change the files in /etc/lora/cfg-cfg-30x instead of global_conf.json
48 +)))
image-20220623140335-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -14.9 KB
Content