Changes for page LoRaWAN Communication Debug
Last modified by Xiaoling on 2025/05/05 08:51
From version 101.1
edited by Bei Jinggeng
on 2025/04/29 13:57
on 2025/04/29 13:57
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - Content
-
... ... @@ -63,7 +63,6 @@ 63 63 64 64 The data for the end device set in server 65 65 66 - 67 67 [[image:image-20240129142631-4.png||height="637" width="1256"]] 68 68 69 69 Check if OTAA Keys match the keys in device. ... ... @@ -168,15 +168,15 @@ 168 168 == **1. Signal problem** == 169 169 170 170 171 -1) (% style="color:blue" %)**ADR automatic adjustment** (%%) 170 +(% style="color:blue" %)**1)**(%%) (% style="color:blue" %)**ADR automatic adjustment** (%%) 172 172 173 -Reason: 172 +**Reason:** 174 174 175 175 When the signal is at a critical value, the server may configure the node to adjust to a lower power DR. 176 176 At this time, the server is at risk of losing uplink. 177 177 178 178 179 -Solution: 178 +**Solution:** 180 180 181 181 Users can manually fix the DR value. 182 182 ... ... @@ -210,14 +210,14 @@ 210 210 (% style="display:none" %) (%%) 211 211 212 212 213 -2) (% style="color:blue" %)**Node antenna problem** 212 +(% style="color:blue" %)**2)**(%%) (% style="color:blue" %)**Node antenna problem** 214 214 215 -Reason: 214 +**Reason:** 216 216 217 217 Node antenna is loose 218 218 219 219 220 -Solution: 219 +**Solution:** 221 221 222 222 Please check whether the antenna interface and module interface are detached 223 223 ... ... @@ -225,15 +225,15 @@ 225 225 226 226 227 227 228 -3) 227 +(% style="color:blue" %)**3) **(%%) (% style="color:blue" %)**Gateway antenna problem** 229 229 230 -Reason: 229 +**Reason:** 231 231 Gateway uses antenna with wrong frequency band 232 232 233 233 For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced 234 234 235 235 236 -Solution: 235 +**Solution:** 237 237 238 238 Please check whether the silk screen on the antenna conflicts with the frequency you set. 239 239 ... ... @@ -240,15 +240,15 @@ 240 240 [[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]] 241 241 242 242 243 -4) 242 +(% style="color:blue" %)**4) **(%%) (% style="color:blue" %)**Gateway module problem** 244 244 245 -Reason: 244 +**Reason:** 246 246 247 247 Gateway uses module with wrong frequency band 248 248 For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced 249 249 250 250 251 -Solution: 250 +**Solution:** 252 252 253 253 Please check whether the silkscreen of the module conflicts with the frequency you set. 254 254 ... ... @@ -257,14 +257,15 @@ 257 257 258 258 == **2. Frequency point problem** == 259 259 260 -Reason: 261 261 260 +**Reason:** 261 + 262 262 There are multiple frequency configurations in AS923/US915/AU915/CN470. 263 263 264 264 The frequency point of the gateway or server is wrong or missing. 265 265 266 266 267 -Solution: 267 +**Solution:** 268 268 269 269 Users need to check whether the server or gateway configuration is missing or has an incorrect frequency. 270 270 ... ... @@ -273,12 +273,13 @@ 273 273 274 274 == **3. Frequency band problem** == 275 275 276 -Reason: 277 277 277 +**Reason:** 278 + 278 278 When there are multiple gateways, the node cannot lock the frequency band. 279 279 280 280 281 -Solution: 282 +**Solution:** 282 282 283 283 ((( 284 284 By default, the frequency bands US915, AU915, CN470 work in 72 frequencies. Many gateways are 8 channel gateways, and in this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies. ... ... @@ -570,7 +570,6 @@ 570 570 [[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]] 571 571 572 572 573 - 574 574 **Configuration: ** 575 575 576 576 [[image:image-20240129164219-4.png||height="612" width="440"]] ... ... @@ -587,7 +587,6 @@ 587 587 [[image:image-20240129170137-6.png||height="459" width="1116"]] 588 588 589 589 590 - 591 591 (% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)** 592 592 593 593 LoRa packet Base64 format: QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)** ... ... @@ -611,20 +611,11 @@ 611 611 612 612 **Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)** 613 613 614 - 615 - 616 - 617 617 [[image:image-20240129192908-24.png||height="477" width="907"]] 618 618 619 - 620 620 [[image:image-20240129192954-25.png||height="485" width="916"]] 621 621 622 622 623 - 624 - 625 - 626 - 627 - 628 628 = 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware = 629 629 630 630