<
From version < 8.1 >
edited by Edwin Chen
on 2022/06/23 09:42
To version < 12.1 >
edited by Kilight Cao
on 2022/06/23 14:18
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Kilight
Content
... ... @@ -1,7 +2,6 @@
1 -(% class="wikigeneratedid" %)
2 2  = Overview: =
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.
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.
5 5  
6 6  
7 7  = Change Power for Semtech UDP Paket forward connection =
... ... @@ -8,9 +8,9 @@
8 8  
9 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.
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.
12 12  
13 -Gateway maintain a power index in the file: /etc/lora/global_conf.json for example:
12 +Gateway maintains a power index in the file: /etc/lora/global_conf.json for example:
14 14  
15 15  
16 16  (% class="box" %)
... ... @@ -30,15 +30,72 @@
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.
32 +(% class="mark" %)Note: If when lorawan server specifies a rf_power that is not listed above. gateway will choose the closest power. profile.
34 34  
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.
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.
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.
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.
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
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
41 41  
42 42  
43 -
44 44  = 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 +(((
50 +cat /var/iot/chip
51 +)))
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 +(% class="box" %)
62 +(((
63 +{
64 + /* If slave-X.conf present this acts as default settings */
65 + "SX1301_conf": { /* Actual channel plan is controlled by server */
66 + "lorawan_public": true, /* is default */
67 + "clksrc": 1, /* radio_1 provides clock to concentrator */
68 + /* path to the SPI device, un-comment if not specified on the command line e.g., RADIODEV=/dev/spidev0.0 */
69 + "device": "/dev/spidev1.0",
70 + /* freq/enable provided by LNS - only HW specific settings listed here */
71 + "radio_0": {
72 + "type": "SX1257",
73 + "rssi_offset": -166.0,
74 + "tx_enable": true,
75 + "antenna_gain": 0
76 + },
77 + "radio_1": {
78 + "type": "SX1257",
79 + "rssi_offset": -166.0,
80 + "tx_enable": false
81 + }
82 + /* chan_multiSF_X, chan_Lora_std, chan_FSK provided by LNS */
83 + },
84 + "station_conf": {
85 + "routerid": "a84041ffff1ec39f",
86 + "radio_init": "rinit.sh",
87 + "RADIO_INIT_WAIT": "5s",
88 + "RX_POLL_INTV": "10ms",
89 + "TC_TIMEOUT": "360s",
90 + "log_file": "stderr",
91 + "log_level": "DEBUG", /* XDEBUG,DEBUG,VERBOSE,INFO,NOTICE,WARNING,ERROR,CRITICAL */
92 + "log_size": 10000000,
93 + "log_rotate": 3,
94 + "CUPS_RESYNC_INTV": "1s"
95 + }
96 +}
97 +)))
98 +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.
99 +
100 +
image-20220623140335-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0