Skip to Content

Changes for page Change Gateway Power

Last modified by Xiaoling on 2022/08/10 15:18
From version 8.1
edited by Edwin Chen
on 2022/06/23 09:42
Change comment: There is no comment for this version
To version 18.2
edited by Xiaoling
on 2022/07/22 15:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,18 +1,25 @@
1 1  (% class="wikigeneratedid" %)
2 -= Overview: =
2 +**Table of Contents:**
3 3  
4 -In LoRaWAN protocol, the gateway transmit packet use the output power base on the Power Index from LoRaWAN server downlink. for example: LoRaWAN server send downlink with this info "rf_power=14", gatewat 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 case, the LoRaWAN server might set the rf-power to a quite low value ( for example 0dB) which is not practical for use. In such case, User can manunal change the rf_power=0's rf settings to a higher power out. Below are the methods.
4 +{{toc/}}
5 5  
6 6  
7 -= Change Power for Semtech UDP Paket forward connection =
8 8  
9 -----
10 10  
11 -In LoRaWAN protocol, the gateway output power refer to the downstream packets sent by Gateway. This output power is controlled by LoRaWAN server.
9 += 1.  Overview =
12 12  
13 -Gateway maintain a power index in the file: /etc/lora/global_conf.json for example:
14 14  
12 +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.
15 15  
14 +
15 += 2.  Change Power for Semtech UDP Paket forward connection =
16 +
17 +
18 +In LoRaWAN protocol, the gateway output power refers to the downstream packets sent by Gateway. This output power is controlled by the LoRaWAN server.
19 +
20 +Gateway maintains a power index in the file: /etc/lora/global_conf.json for example:
21 +
22 +
16 16  (% class="box" %)
17 17  (((
18 18  "tx_lut_3": {
... ... @@ -30,15 +30,132 @@
30 30   "dig_gain": 0
31 31  )))
32 32  
33 -(% class="mark" %)Note: If when lorawan server specify a rf_power which is not list above. gateway will choose the closest power. profile.
34 34  
41 +(% style="color:red" %)**Note: If when lorawan server specifies a rf_power that is not listed above. gateway will choose the closest power. profile.**
35 35  
36 -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.
37 37  
38 -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 recommended, because this might break the regulator for specific country.
44 +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.
39 39  
40 -Please note, that the global_conf.json file will be overwritten by the match region files in /etc/lora/cfg-30x when changing settings in the web. So user needs to change the files in /etc/lora/cfg-cfg-30x instead of global_conf.json
46 +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.
41 41  
48 +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
42 42  
43 43  
44 -= Change Power for LoRaWAN Basic Station connection =
51 += 3.  Change Power for LoRaWAN Basic Station connection =
52 +
53 +
54 +First, you need to find out what is the chip module of the gateway?
55 +
56 +(% class="box infomessage" %)
57 +(((
58 +**cat /var/iot/chip **
59 +)))
60 +
61 +[[image:image-20220623140335-1.png||height="241" width="378"]]
62 +
63 +Gateways using the SX1301 LoRaWAN Concentrator are the [[LG308>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG308-LG301/&file=Datasheet_LG308_LoRaWAN_Gateway.pdf]] and [[DLOS8>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/DLOS8/&file=DLOS8_LoRaWAN_Gateway_User_Manual_v1.3.pdf]].
64 +
65 +
66 +(% style="color:blue" %)**SX1301 Change Power for LoRaWAN Basic Station Connection example:**
67 +
68 +Gateway maintains a power index in the file: /etc/station/station-sx1301.conf
69 +
70 +(% class="box" %)
71 +(((
72 +{
73 + /* If slave-X.conf present this acts as default settings */
74 + "SX1301_conf": { /* Actual channel plan is controlled by server */
75 + "lorawan_public": true, /* is default */
76 + "clksrc": 1, /* radio_1 provides clock to concentrator */
77 + /* path to the SPI device, un-comment if not specified on the command line e.g., RADIODEV=/dev/spidev0.0 */
78 + "device": "/dev/spidev1.0",
79 + /* freq/enable provided by LNS - only HW specific settings listed here */
80 +
81 + ~|<~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-(% style="color:red" %)Add parameters:"tx_gain_lut"  :  [ TX_GAIN_LUT, .. ]
82 +
83 + "radio_0": {
84 + "type": "SX1257",
85 + "rssi_offset": -166.0,
86 + "tx_enable": true,
87 + "antenna_gain": 0
88 + },
89 + "radio_1": {
90 + "type": "SX1257",
91 + "rssi_offset": -166.0,
92 + "tx_enable": false
93 + }
94 + /* chan_multiSF_X, chan_Lora_std, chan_FSK provided by LNS */
95 + },
96 +)))
97 +
98 +
99 +Add parameters:**"(% style="color:blue" %)tx_gain_lut": [ TX_GAIN_LUT, .. ](%%)**
100 +
101 +(% class="box" %)
102 +(((
103 +{
104 + /* If slave-X.conf present this acts as default settings */
105 + "SX1301_conf": { /* Actual channel plan is controlled by server */
106 + "lorawan_public": true, /* is default */
107 + "clksrc": 1, /* radio_1 provides clock to concentrator */
108 + /* path to the SPI device, un-comment if not specified on the command line e.g., RADIODEV=/dev/spidev0.0 */
109 + "device": "/dev/spidev1.0",
110 + /* freq/enable provided by LNS - only HW specific settings listed here */
111 + "tx_gain_lut":[
112 + {"rf_power": 12, "pa_gain": 2, "mix_gain": 11, "dig_gain": 2, "dac_gain": 3}, 
113 + {"rf_power": 13, "pa_gain": 2, "mix_gain": 10, "dig_gain": 0, "dac_gain": 3},
114 + {"rf_power": 14, "pa_gain": 2, "mix_gain": 12, "dig_gain": 2, "dac_gain": 3},
115 + {"rf_power": 15, "pa_gain": 2, "mix_gain": 13, "dig_gain": 2, "dac_gain": 3},
116 +
117 +/* Index 3 refer to rf_power: 15dB. device will set the pa_gain,mix_gain,dig_gain */
118 +
119 +/* to the value mentioned here so as to generate 15dB output power.*/
120 + {"rf_power": 16, "pa_gain": 2, "mix_gain": 13, "dig_gain": 1, "dac_gain": 3},
121 + {"rf_power": 17, "pa_gain": 2, "mix_gain": 14, "dig_gain": 1, "dac_gain": 3},
122 + {"rf_power": 18, "pa_gain": 2, "mix_gain": 15, "dig_gain": 2, "dac_gain": 3},
123 + {"rf_power": 19, "pa_gain": 2, "mix_gain": 15, "dig_gain": 1, "dac_gain": 3},
124 + {"rf_power": 20, "pa_gain": 2, "mix_gain": 15, "dig_gain": 1, "dac_gain": 3},
125 + {"rf_power": 21, "pa_gain": 3, "mix_gain": 9, "dig_gain": 0, "dac_gain": 3},
126 + {"rf_power": 22, "pa_gain": 3, "mix_gain": 10, "dig_gain": 0, "dac_gain": 3},
127 + {"rf_power": 23, "pa_gain": 3, "mix_gain": 11, "dig_gain": 1, "dac_gain": 3},
128 + {"rf_power": 24, "pa_gain": 3, "mix_gain": 12, "dig_gain": 0, "dac_gain": 3},
129 + {"rf_power": 25, "pa_gain": 3, "mix_gain": 14, "dig_gain": 0, "dac_gain": 3},
130 + {"rf_power": 26, "pa_gain": 3, "mix_gain": 14, "dig_gain": 0, "dac_gain": 3},
131 + {"rf_power": 27, "pa_gain": 3, "mix_gain": 14, "dig_gain": 0, "dac_gain": 3}
132 + ],
133 + "radio_0": {
134 + "type": "SX1257",
135 + "rssi_offset": -166.0,
136 + "tx_enable": true,
137 + "antenna_gain": 0
138 + },
139 + "radio_1": {
140 + "type": "SX1257",
141 + "rssi_offset": -166.0,
142 + "tx_enable": false
143 + }
144 + /* chan_multiSF_X, chan_Lora_std, chan_FSK provided by LNS */
145 + },
146 +)))
147 +
148 +See this link for more station configuration parameters: [[Concentrator Design (v1.5) - LoRa Basics™ StationLoRa Basics™ Station ~| DEVELOPER PORTAL (semtech.com)>>url:https://lora-developers.semtech.com/build/software/lora-basics/lora-basics-for-gateways/?url=gw_v1.5.html]]
149 +
150 +
151 +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.
152 +
153 +(% style="color:red" %)**Note: When the Settings are complete, click "Save&Apply" on the gateway's Web UI**
154 +
155 +
156 += 4.  Checking station Logs =
157 +
158 +
159 +Run the command:
160 +
161 +(% class="box infomessage" %)
162 +(((
163 +**tail -f /var/iot/station.log**
164 +)))
165 +
166 +[[image:image-20220623145437-2.png||height="501" width="694"]]
167 +
168 +
image-20220623140335-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20220623145437-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +195.4 KB
Content