Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 1 removed)
  • image-20221016081725-1.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.Xiaoling

Content

...	...	@@ -10,9 +10,9 @@
10	10	In real-world deployment for LoRa, distance is a common topic. We always want to have the longest distance. This chapter shows some instructions for how to improve this.
11	11
12	12
13		-
14	14	= 2.  Analyze at the software side =
15	15
	15	+
16	16	== 2.1  LoRa parameters that effect distance ==
17	17
18	18
...	...	@@ -45,6 +45,7 @@
45	45	|(% style="width:134px" %)**AS923**|(% style="width:400px" %)14dBm|(% style="width:362px" %)SF=12|(% style="width:102px" %)125Khz
46	46
47	47
	48	+
48	48	== 2.2  Adaptive Data Rate (ADR) and set max distance ==
49	49
50	50
...	...	@@ -73,7 +73,7 @@
73	73	According to the above technology, if we have a problem on the distance, we can first check if the end node is trying to longest distance modulation already. We can see that from the LoRaWAN server. Below is an example from Chirpstack.
74	74
75	75
76		-We can see the traffic in gateway's page and know that the distance is SF12 / BW125. (note, server is not able to know Transmit Power settings from End Node)
	77	+We can see the traffic in gateway’s page and know that the distance is SF12 / BW125. (note, server is not able to know Transmit Power settings from End Node)
77	77
78	78
79	79	[[image:image-20221006185826-3.png]]
...	...	@@ -85,27 +85,18 @@
85	85
86	86	Below are the settings for longest distance transmission. ( will reduce battery life)
87	87
88		-* (% style="color:#037691" %)**AT+ADR=0**     (%%)~/~/  Disable ADR
89		-* (% style="color:#037691" %)**AT+DR=  0**     (%%)~/~/  Use the smallest DR
90		-* (% style="color:#037691" %)**AT+TXP=0**    (%%) ~/~/  Use max power.
	89	+* (% style="color:#037691" %)AT+ADR=0     (%%)~/~/  Disable ADR
	90	+* (% style="color:#037691" %)AT+DR=  0     (%%)~/~/  Use the smallest DR
	91	+* (% style="color:#037691" %)AT+TXP=0    (%%) ~/~/  Use max power.
91	91
92	92
93		-= 3.  Analyze at the hardware side =
94	94
95		-== 3.1  Check if the antenna path is good ~-~- For LSn50v2 series end node ==
	95	+= 3.  Installation Guidelines =
96	96
97		-a) Open Enclosure and Check if the antenna connection to module is good.
98	98
99		-b) check if the connector match.
	98	+== 3.1  Check the use environment ==
100	100
101		-[[image:image-20221016081725-1.png||height="426" width="706"]]
102	102
103		-
104		-= 4.  Installation Guidelines =
105		-
106		-== 4.1  Check the use environment ==
107		-
108		-
109	109	First , User should notice: Radio link quality and performances are highly dependent of the environment.
110	110
111	111	(% style="color:blue" %)**Better performances can be reached with:**
...	...	@@ -116,6 +116,7 @@
116	116	* At least 1 meter above the ground.
117	117
118	118
	111	+
119	119	(% style="color:blue" %)**Radio performances are degraded with:**
120	120
121	121	* Obstacles: buildings, trees...
...	...	@@ -124,18 +124,20 @@
124	124	* Radio communication are usually killed with bad topographic conditions. It is usually not possible to communicate through a hill, even very small.
125	125
126	126
127		-== 4.2  Improve the Antenna ==
128	128
	121	+== 3.2  Improve the Antenna ==
129	129
	123	+
130	130	In some case, we have to install the device inside the chamber or next to a metal case. So the signal between the antenna and the receiver (gateway) is blocked by the metal. This will greatly reduce the signal. In such case, we can consider using antenna extend cable to extend the antenna to a better position.
131	131
132	132
133	133
134		-= 5.  Some real-world case =
	128	+= 4.  Some real-world case =
135	135
136		-== 5.1  Server reason cause end node has problem on Join. ==
137	137
	131	+== 4.1  Server reason cause end node has problem on Join. ==
138	138
	133	+
139	139	In one case, the customer is using AWS IoT Core and gateway to connect to AWS via Basic Station Connection, Frequency Band is AU915 sub-band 2. For some unknown reason, AWS always set downlink power to 0dBm, which cause the gateway only emit a very low power and lead to a short distance for sensor.
140	140
141	141

image-20221016081725-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Edwin

Size

...	...	@@ -1,1 +1,0 @@
1		-569.8 KB

Content