Last modified by Edwin Chen on 2025/01/29 20:30
From version < 4.5 >
edited by Xiaoling
on 2022/05/11 14:46
To version 1.1 >
edited by Xiaoling
on 2022/05/11 13:43
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -**~ Contents:**
1 +
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -6,7 +6,7 @@
6 6  = 1. OTAA Join Process Debug =
7 7  
8 8  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
9 -\\**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:**
9 +\\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:
10 10  
11 11  * End node console to show the Join freuqency and DR. (If possible)
12 12  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
... ... @@ -14,12 +14,13 @@
14 14  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
15 15  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
16 16  
17 +
17 17  **~1. End Device Join Screen shot, we can check:**
18 18  
19 19  * If the device is sending join request to server?
20 20  * What frequency the device is sending?
21 21  
22 -[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
23 +[[~[~[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg~|~|height="316" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:OTAA_Join-1.jpg]]
23 23  
24 24  Console Output from End device to see the transmit frequency
25 25  
... ... @@ -29,7 +29,7 @@
29 29  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
30 30  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
31 31  
32 -[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
33 +[[~[~[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png~|~|height="325" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:OTAA_Join-2.png]]
33 33  
34 34  Console Output from Gateway to see packets between end node and server.
35 35  
... ... @@ -40,7 +40,7 @@
40 40  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
41 41  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
44 +[[~[~[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png~|~|height="301" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:OTAA_Join-3.png]]
44 44  
45 45  The Traffic for the End node in the server, use TTN as example
46 46  
... ... @@ -49,122 +49,70 @@
49 49  
50 50  * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
51 51  
52 -[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
53 +[[~[~[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png~|~|height="181" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:OTAA_Join-4.png]]
53 53  
54 54  The data for the end device set in server
55 55  
56 -[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
57 +[[~[~[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png~|~|height="166" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:OTAA_Join-5.png]]
57 57  
58 58  Check if OTAA Keys match the keys in device
59 59  
60 60  
61 -= 2. Notice of US915/CN470/AU915 Frequency band =
62 += Notice of US915/CN470/AU915 Frequency band =
62 62  
63 -(((
64 64  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
65 -)))
66 66  
67 -* (((
68 -What **sub-band** the server support ?
69 -)))
70 -* (((
71 -What is the **sub-band** the gateway support ?
72 -)))
73 -* (((
74 -What is the **sub-band** the end node is using ?
75 -)))
66 +* What sub-band the server support ?
67 +* What is the sub-band the gateway support ?
68 +* What is the sub-band the end node is using ?
76 76  
77 -(((
78 78  All of above should match so End Node can properly Join the server and don't have packet lost.
79 -)))
80 80  
81 -(((
82 -
83 -)))
84 -
85 -(((
86 86  In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn,t support.
87 -)))
88 88  
89 -(((
90 -
91 -)))
92 -
93 -(((
94 94  Here are the freuqency tables for these bands as reference:
95 -)))
96 96  
97 -[[image:https://wiki.dragino.com/images/thumb/3/3f/US915_FRE_BAND-1.png/600px-US915_FRE_BAND-1.png||height="170" width="600"]]
76 +[[~[~[image:https://wiki.dragino.com/images/thumb/3/3f/US915_FRE_BAND-1.png/600px-US915_FRE_BAND-1.png~|~|height="170" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:US915_FRE_BAND-1.png]]
98 98  
99 99  US915 Channels
100 100  
101 -[[image:https://wiki.dragino.com/images/thumb/8/8a/AU915_FRE_BAND-1.png/600px-AU915_FRE_BAND-1.png||height="167" width="600"]]
80 +[[~[~[image:https://wiki.dragino.com/images/thumb/8/8a/AU915_FRE_BAND-1.png/600px-AU915_FRE_BAND-1.png~|~|height="167" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:AU915_FRE_BAND-1.png]]
102 102  
103 103  AU915 Channels
104 104  
105 -[[image:https://wiki.dragino.com/images/thumb/3/3a/CN470_FRE_BAND-1.png/600px-CN470_FRE_BAND-1.png||height="205" width="600"]]
84 +[[~[~[image:https://wiki.dragino.com/images/thumb/3/3a/CN470_FRE_BAND-1.png/600px-CN470_FRE_BAND-1.png~|~|height="205" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:CN470_FRE_BAND-1.png]]
106 106  
107 -(((
108 108  CN470 Channels
109 -)))
110 110  
111 -(((
112 112  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
113 -)))
114 114  
115 -[[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
90 +[[~[~[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png~|~|height="288" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:US915_FRE_BAND-2.png]]
116 116  
117 -(((
118 118  TTN FREQUENCY PLAN
119 -)))
120 120  
121 -(((
122 122  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
123 -)))
124 124  
125 125  
126 -= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
97 += Why i see data lost/unperiocially uplink data? Even the signal strength is good =
127 127  
128 128  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
129 129  
130 -* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
131 -* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
132 -* **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
101 +* End node ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
102 +* Gateway ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
103 +* LoRaWAN server ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
133 133  
134 -(((
135 135  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
136 -)))
137 137  
138 -(((
139 -
140 -)))
141 -
142 -(((
143 143  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
144 -)))
145 145  
146 146  
147 -= 4. Transmision on ABP Mode =
110 += Transmision on ABP Mode =
148 148  
149 -(((
150 150  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
151 -)))
152 152  
153 -(((
154 -
155 -)))
156 -
157 -(((
158 158  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
159 -)))
160 160  
161 -(((
162 -
163 -)))
164 -
165 -(((
166 166  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
167 -)))
168 168  
169 169  [[~[~[image:https://wiki.dragino.com/images/thumb/1/19/ABP_Issue-1.jpg/600px-ABP_Issue-1.jpg~|~|height="340" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:ABP_Issue-1.jpg]]
170 170  
... ... @@ -171,17 +171,15 @@
171 171  Disable Frame Counter Check in ABP Mode
172 172  
173 173  
174 -= 5. Downstream Debug =
123 += Downstream Debug =
175 175  
176 -== 5.1 How it work ==
125 +== How it work ==
177 177  
178 178  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
179 179  
180 -(((
181 181  Depends on Class A or Class C, the receive windows will be a little difference,
182 -)))
183 183  
184 -[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
131 +[[~[~[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png~|~|height="590" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:Downstream_LoRaWAN-1.png]]
185 185  
186 186  receive windows for Class A and Class C
187 187  
... ... @@ -191,164 +191,115 @@
191 191  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
192 192  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
193 193  * This packet must match the frequency of the RX1 or RX2 window.
194 -* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
141 +* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.
195 195  
196 -== 5.2 See Debug Info ==
197 197  
198 -**For LoRaWAN Server**
144 +== See Debug Info ==
199 199  
146 +For LoRaWAN Server
147 +
200 200  We can check if there is downlink message for this end node, use TTN for example:
201 201  
202 202  Configure a downstream to the end device
203 203  
204 -[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
152 +[[~[~[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png~|~|height="217" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:Downstream_debug_1.png]]
205 205  
206 206  Set a downstream in TTN and see it is sent
207 207  
208 208  
209 -(((
210 210  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
211 -)))
212 212  
213 -[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
159 +[[~[~[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png~|~|height="245" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:Downstream_debug_2.png]]
214 214  
215 215  Gateway Traffic can see this downstream info
216 216  
217 217  
218 -**For LoRaWAN Gateway**
164 +For LoRaWAN Gateway
219 219  
220 -(((
221 221  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:
222 -)))
223 223  
224 -[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
168 +[[~[~[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png~|~|height="195" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:Downstream_debug_3.png]]
225 225  
226 226  Gateway Sent out this packet
227 227  
228 228  
229 -**For End Node**
173 +For End Node
230 230  
231 231  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
232 232  
233 -(% class="box infomessage" %)
234 -(((
235 - AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
236 -)))
177 +{{{AT+RX2FQ=869525000 ---> The RX2 Window frequency
178 +AT+RX2DR=3 ---> The RX2 DataRate
179 +AT+RX1DL=1000 ---> Receive Delay 1
180 +AT+RX2DL=2000 ---> Receive Delay 2
181 +}}}
237 237  
238 -(% class="box infomessage" %)
239 -(((
240 - AT+RX2DR=3 ~-~--> The RX2 DataRate
241 -)))
183 +when the device running, we can see below info:
242 242  
243 -(% class="box infomessage" %)
244 -(((
245 - AT+RX1DL=1000 ~-~--> Receive Delay 1
246 -)))
185 +{{{[12502]***** UpLinkCounter= 0 *****
186 +[12503]TX on freq 868500000 Hz at DR 0
187 +[13992]txDone
188 +[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
189 +[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
190 +[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
191 +[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)
192 +}}}
247 247  
248 -(% class="box infomessage" %)
249 -(((
250 - AT+RX2DL=2000 ~-~--> Receive Delay 2
251 -)))
194 +{{{Another message:
195 +[12502]***** UpLinkCounter= 0 *****
196 +[12503]TX on freq 868100000 Hz at DR 0
197 +[13992]txDone
198 +[15022]RX on freq 868100000 Hz at DR 0
199 +[15222]rxTimeOut
200 +[15987]RX on freq 869525000 Hz at DR 3
201 +[16185]rxDone --> We have got the downstream packet.
202 +Rssi= -64
203 +Receive data
204 +1:0012345678
205 +}}}
252 252  
253 -(((
254 -**when the device running, we can see below info:**
255 -)))
207 +== If problem doesn’t solve ==
256 256  
257 -(((
258 -
259 -)))
209 +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:
260 260  
261 -(% class="box" %)
262 -(((
263 - [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
264 - [12503]TX on freq 868500000 Hz at DR 0
265 - [13992]txDone
266 - [15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
267 - [15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
268 - [15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
269 - [16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
270 -)))
271 -
272 -(((
273 -
274 -)))
275 -
276 -(((
277 -**Another message:**
278 -)))
279 -
280 -
281 - [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
282 - [12503]TX on freq 868100000 Hz at DR 0
283 - [13992]txDone
284 - [15022]RX on freq 868100000 Hz at DR 0
285 - [15222]rxTimeOut
286 - [15987]RX on freq 869525000 Hz at DR 3
287 - [16185]rxDone                              ~-~-> We have got the downstream packet.
288 - Rssi= -64
289 - Receive data
290 - 1:0012345678
291 -
292 -== 5.3 If problem doesn’t solve ==
293 -
294 -**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:**
295 -
296 296  * End node console to show the transmit freuqency and DR.
297 297  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
298 298  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
299 299  * End Node traffic (from server UI) to shows end node activity in server.
300 300  
301 -= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
302 302  
303 -(((
304 -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.
305 -)))
306 306  
307 -(((
308 -
309 -)))
218 += Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310 310  
311 -(((
220 +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.
221 +
312 312  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:
313 -)))
314 314  
315 -(((
316 -Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
317 -)))
224 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
225 +}}}
318 318  
319 -(((
320 320  In this case, please double check the gateway frequency and the server frequency band.
321 -)))
322 322  
323 323  
324 -= 7. Decrypt a LoRaWAN Packet =
325 325  
231 += Decrypt a LoRaWAN Packet =
232 +
326 326  ~1. LHT65 End device configure:
327 327  
328 -(% class="box infomessage" %)
329 -(((
330 330  Change to ABP Mode: AT+NJM=0
331 -)))
332 332  
333 -(% class="box infomessage" %)
334 -(((
335 335  Change to fix frequency: AT+CHS=904900000
336 -)))
337 337  
338 -(% class="box infomessage" %)
339 -(((
340 340  Change to fix DR: AT+DR=0
341 -)))
342 342  
343 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
241 +[[~[~[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg~|~|alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"~]~]>>url:https://wiki.dragino.com/index.php/File:Decrypt_a_LoRaWAN_Packet1.jpg]]
344 344  
345 345  2. In LG02 , configure to receive above message
346 346  
347 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
245 +[[~[~[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg~|~|alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"~]~]>>url:https://wiki.dragino.com/index.php/File:Decrypt_a_LoRaWAN_Packet2.jpg]]
348 348  
349 349  In LG02 console, we can see the hex receive are:
350 350  
351 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
249 +[[~[~[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg~|~|alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"~]~]>>url:https://wiki.dragino.com/index.php/File:Decrypt_a_LoRaWAN_Packet3.jpg]]
352 352  
353 353  3. Decode the info in web
354 354  
... ... @@ -364,16 +364,16 @@
364 364  
365 365  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
366 366  
367 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
265 +[[~[~[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png~|~|alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"~]~]>>url:https://wiki.dragino.com/index.php/File:Decrypt_a_LoRaWAN_Packet4.png]]
368 368  
369 369  The FRMPayload is the device payload.
370 370  
371 371  
372 -= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
270 += Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
373 373  
374 374  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
375 375  
376 -= 9. Why do I see a "MIC Mismatch" error message from the server? =
274 += Why do I see a "MIC Mismatch" error message from the server? =
377 377  
378 378  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
379 379  
... ... @@ -387,7 +387,7 @@
387 387  
388 388  * If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
389 389  
390 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
288 += Why i got the payload only with "0x00" or "AA~=~="? =
391 391  
392 392  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
393 393  
... ... @@ -402,5 +402,4 @@
402 402  * Solution: Use the decoder to filter out this 00 packet.
403 403  * Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to david.huang@dragino.cc
404 404  
405 -(% class="wikigeneratedid" id="H" %)
406 -
303 +== ==

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0