Summary

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

Details

Page properties

Author

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

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	+
13	13	= 2.  Analyze at the software side =
14	14
15		-
16	16	== 2.1  LoRa parameters that effect distance ==
17	17
18	18
...	...	@@ -45,7 +45,6 @@
45	45	|(% style="width:134px" %)**AS923**|(% style="width:400px" %)14dBm|(% style="width:362px" %)SF=12|(% style="width:102px" %)125Khz
46	46
47	47
48		-
49	49	== 2.2  Adaptive Data Rate (ADR) and set max distance ==
50	50
51	51
...	...	@@ -74,7 +74,7 @@
74	74	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.
75	75
76	76
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)
	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)
78	78
79	79
80	80	[[image:image-20221006185826-3.png]]
...	...	@@ -86,18 +86,27 @@
86	86
87	87	Below are the settings for longest distance transmission. ( will reduce battery life)
88	88
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.
	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.
92	92
93	93
	93	+= 3.  Analyze at the hardware side =
94	94
95		-= 3.  Installation Guidelines =
	95	+== 3.1  Check if the antenna path is good ~-~- For LSn50v2 series end node ==
96	96
	97	+a) Open Enclosure and Check if the antenna connection to module is good.
97	97
98		-== 3.1  Check the use environment ==
	99	+b) check if the connector match.
99	99
	101	+[[image:image-20221016081725-1.png||height="426" width="706"]]
100	100
	103	+
	104	+= 4.  Installation Guidelines =
	105	+
	106	+== 4.1  Check the use environment ==
	107	+
	108	+
101	101	First , User should notice: Radio link quality and performances are highly dependent of the environment.
102	102
103	103	(% style="color:blue" %)**Better performances can be reached with:**
...	...	@@ -108,7 +108,6 @@
108	108	* At least 1 meter above the ground.
109	109
110	110
111		-
112	112	(% style="color:blue" %)**Radio performances are degraded with:**
113	113
114	114	* Obstacles: buildings, trees...
...	...	@@ -117,20 +117,18 @@
117	117	* Radio communication are usually killed with bad topographic conditions. It is usually not possible to communicate through a hill, even very small.
118	118
119	119
	127	+== 4.2  Improve the Antenna ==
120	120
121		-== 3.2  Improve the Antenna ==
122	122
123		-
124	124	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.
125	125
126	126
127	127
128		-= 4.  Some real-world case =
	134	+= 5.  Some real-world case =
129	129
	136	+== 5.1  Server reason cause end node has problem on Join. ==
130	130
131		-== 4.1  Server reason cause end node has problem on Join. ==
132	132
133		-
134	134	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.
135	135
136	136

image-20221016081725-1.png

Author

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

Size

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

Content