Changes for page LoRaWAN Communication Debug
Last modified by Edwin Chen on 2025/01/29 20:30
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -195,23 +195,15 @@ 195 195 196 196 == 5.2 See Debug Info == 197 197 198 -((( 199 199 **For LoRaWAN Server** 200 -))) 201 201 202 -((( 203 203 We can check if there is downlink message for this end node, use TTN for example: 204 -))) 205 205 206 -((( 207 207 Configure a downstream to the end device 208 -))) 209 209 210 210 [[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]] 211 211 212 -((( 213 213 Set a downstream in TTN and see it is sent 214 -))) 215 215 216 216 217 217 ((( ... ... @@ -220,14 +220,10 @@ 220 220 221 221 [[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]] 222 222 223 -((( 224 224 Gateway Traffic can see this downstream info 225 -))) 226 226 227 227 228 -((( 229 229 **For LoRaWAN Gateway** 230 -))) 231 231 232 232 ((( 233 233 When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below: ... ... @@ -235,14 +235,10 @@ 235 235 236 236 [[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]] 237 237 238 -((( 239 239 Gateway Sent out this packet 240 -))) 241 241 242 242 243 -((( 244 244 **For End Node** 245 -))) 246 246 247 247 we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below: 248 248 ... ... @@ -253,51 +253,47 @@ 253 253 254 254 (% class="box infomessage" %) 255 255 ((( 256 - 240 + AT+RX2DR=3 ~-~--> The RX2 DataRate 257 257 ))) 258 258 259 259 (% class="box infomessage" %) 260 260 ((( 261 - 245 + AT+RX1DL=1000 ~-~--> Receive Delay 1 262 262 ))) 263 263 264 264 (% class="box infomessage" %) 265 265 ((( 266 - 250 + AT+RX2DL=2000 ~-~--> Receive Delay 2 267 267 ))) 268 268 269 - **when the device running, we can see below info:**253 +when the device running, we can see below info: 270 270 255 +(% class="box" %) 271 271 ((( 272 - 273 -))) 274 - 275 -{{{ [12502]***** UpLinkCounter= 0 ***** 257 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~** 276 276 [12503]TX on freq 868500000 Hz at DR 0 277 277 [13992]txDone 278 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone 279 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms) 280 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone 281 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}} 260 + [15022]RX on freq 868500000 Hz at DR 0 ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone 261 + [15222]rxTimeOut ~-~-> no packet arrive in RX1 window. (duration: 200ms) 262 + [15987]RX on freq 869525000 Hz at DR 3 ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone 263 + [16027]rxTimeOut ~-~-> no packet arrive in RX2 window. (duration: 40 ms) 264 +))) 282 282 266 +(% class="box" %) 283 283 ((( 284 - 268 + Another message: 269 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~** 270 + [12503]TX on freq 868100000 Hz at DR 0 271 + [13992]txDone 272 + [15022]RX on freq 868100000 Hz at DR 0 273 + [15222]rxTimeOut 274 + [15987]RX on freq 869525000 Hz at DR 3 275 + [16185]rxDone ~-~-> We have got the downstream packet. 276 + Rssi= -64 277 + Receive data 278 + 1:0012345678 285 285 ))) 286 286 287 -**Another message:** 288 - 289 -{{{ 290 - [12502]***** UpLinkCounter= 0 ***** 291 - [12503]TX on freq 868100000 Hz at DR 0 292 - [13992]txDone 293 - [15022]RX on freq 868100000 Hz at DR 0 294 - [15222]rxTimeOut 295 - [15987]RX on freq 869525000 Hz at DR 3 296 - [16185]rxDone --> We have got the downstream packet. 297 - Rssi= -64 298 - Receive data 299 - 1:0012345678}}} 300 - 301 301 == 5.3 If problem doesn’t solve == 302 302 303 303 **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:** ... ... @@ -309,29 +309,14 @@ 309 309 310 310 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 311 311 312 -((( 313 313 In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink. 314 -))) 315 315 316 -((( 317 - 318 -))) 319 - 320 -((( 321 321 So if the LoRaWAN server is an AS923 server which ask the gateway to transmit at 923.2Mhz frequency, but the gateway is IN868 frequency band (support 865~~867Mhz to transmit). In the gateway log it will show something like below: 322 -))) 323 323 324 -((( 325 -Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000) 326 -))) 296 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000) 297 +}}} 327 327 328 -((( 329 - 330 -))) 331 - 332 -((( 333 333 In this case, please double check the gateway frequency and the server frequency band. 334 -))) 335 335 336 336 337 337 = 7. Decrypt a LoRaWAN Packet =