Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 99.1
edited by Bei Jinggeng
on 2025/04/29 12:00
Change comment: There is no comment for this version
To version 4.4
edited by Xiaoling
on 2022/05/11 14:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
Content
... ... @@ -1,89 +1,77 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 += 1. OTAA Join Process Debug =
6 6  
7 -= 1. Join process page check =
8 -
9 -
10 10  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.
11 11  \\**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:**
12 12  
13 13  * End node console to show the Join freuqency and DR. (If possible)
14 -
15 15  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
16 -
17 17  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
18 -
19 19  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
20 -
21 21  * 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)
22 22  
23 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
17 +**~1. End Device Join Screen shot, we can check:**
24 24  
25 25  * If the device is sending join request to server?
26 -
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20240129142147-2.png||height="736" width="964"]]
22 +[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
30 30  
31 -Console Output from End device to see the transmit frequency.
24 +Console Output from End device to see the transmit frequency
32 32  
33 33  
34 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
27 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
35 35  
36 36  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
37 -
38 38  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
39 39  
40 -[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
32 +[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
41 41  
42 42  Console Output from Gateway to see packets between end node and server.
43 43  
44 44  
45 -(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
37 +**3. Gateway Traffic Page in LoRaWAN Server**
46 46  
47 -* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
48 -
49 -* Does the server send back a Join Accept for the Join Request? If not, check that the key from the device matches the key you put into the server, or try to choose a different server route for that end device.
50 -
39 +* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
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.
51 51  * 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.
52 52  
53 -[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
43 +[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
54 54  
55 -The Traffic for the End node in the server, use TTN as example.
45 +The Traffic for the End node in the server, use TTN as example
56 56  
57 57  
58 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
48 +**4. Data Page in LoRaWAN server**
59 59  
60 60  * 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.
61 61  
62 -[[image:image-20240129142557-3.png||height="488" width="1267"]]
52 +[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
63 63  
64 64  The data for the end device set in server
65 65  
56 +[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
66 66  
67 -[[image:image-20240129142631-4.png||height="637" width="1256"]]
58 +Check if OTAA Keys match the keys in device
68 68  
69 -Check if OTAA Keys match the keys in device.
70 70  
71 -
72 72  = 2. Notice of US915/CN470/AU915 Frequency band =
73 73  
74 -
75 75  (((
76 -If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
64 +If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
77 77  )))
78 78  
79 79  * (((
80 -What **sub-band** the server support?
68 +What **sub-band** the server support ?
81 81  )))
82 82  * (((
83 -What is the **sub-band** the gateway support?
71 +What is the **sub-band** the gateway support ?
84 84  )))
85 85  * (((
86 -What is the **sub-band** the end node is using?
74 +What is the **sub-band** the end node is using ?
87 87  )))
88 88  
89 89  (((
... ... @@ -95,7 +95,7 @@
95 95  )))
96 96  
97 97  (((
98 -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.
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.
99 99  )))
100 100  
101 101  (((
... ... @@ -103,25 +103,21 @@
103 103  )))
104 104  
105 105  (((
106 -Here are the frequency tables for these bands as reference:
94 +Here are the freuqency tables for these bands as reference:
107 107  )))
108 108  
109 -[[image:image-20220526163801-6.png]]
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"]]
110 110  
111 111  US915 Channels
112 112  
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"]]
113 113  
114 -[[image:image-20220526163926-7.png]]
115 -
116 116  AU915 Channels
117 117  
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"]]
118 118  
119 -[[image:image-20220526163941-8.png]]
120 -
121 121  (((
122 122  CN470 Channels
123 -
124 -
125 125  )))
126 126  
127 127  (((
... ... @@ -128,12 +128,10 @@
128 128  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.
129 129  )))
130 130  
131 -[[image:image-20240123151225-3.png||height="434" width="902"]]
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"]]
132 132  
133 133  (((
134 134  TTN FREQUENCY PLAN
135 -
136 -(% style="display:none" %) (%%)
137 137  )))
138 138  
139 139  (((
... ... @@ -140,23 +140,22 @@
140 140  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. )
141 141  )))
142 142  
143 -(% style="display:none" %) (%%)
144 144  
145 -= 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
126 += 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
146 146  
147 -
148 148  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:
149 149  
150 -* (% style="color:blue" %)**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.
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.
151 151  
152 -* (% style="color:blue" %)**Gateway** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
153 -
154 -* (% style="color:blue" %)**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.
155 -
156 156  (((
157 157  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.
158 158  )))
159 159  
138 +(((
139 +
140 +)))
160 160  
161 161  (((
162 162  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.
... ... @@ -163,545 +163,241 @@
163 163  )))
164 164  
165 165  
166 -= 4. Why i see packet lost =
147 += 4. Transmision on ABP Mode =
167 167  
168 -== **1. Signal problem** ==
149 +(((
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 +)))
169 169  
170 -
171 -1)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
172 -
173 -Reason:
174 -
175 -When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
176 -At this time, the server is at risk of losing uplink.
177 -
178 -
179 -Solution:
180 -
181 -Users can manually fix the DR value.
153 +(((
182 182  
183 -
184 -(% style="color:red" %)
185 -**Notice:**
186 -
187 -* User need to set Adaptive Data Rate(ADR)=0 first. otherwise device will respond to server's ADR command and change the DR according to server auto-adjustment.
188 -
189 -* Data Rate specifies Spreading Factor. The mapping varies in different frequency bands. User can check this link for detail. [[rp2-1.0.3-lorawan-regional-parameters.pdf>>https://lora-alliance.org/resource_hub/rp2-1-0-3-lorawan-regional-parameters/]]
190 -
191 -(% style="color:blue" %)**AT Command: AT+DR**
192 -
193 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:409px" %)
194 -|(% style="background-color:#4f81bd; color:white; width:156px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:147px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Response**
195 -|(% style="width:156px" %)AT+DR=?|(% style="width:147px" %)Get the Data Rate.|(% style="width:100px" %)5(((
196 -OK
197 197  )))
198 -|(% style="width:156px" %)AT+DR=2|(% style="width:147px" %)Set the Data Rate.|(% style="width:100px" %)OK(((
199 -
200 -)))
201 201  
202 -(% style="color:blue" %)**Downlink Command: 0x2200aaFF**
203 -
204 -If the downlink payload=220001FF, it means setting the data rate to 1, while type code is 22 00 aa FF.
205 -
206 -* **Example 1**: Downlink Payload: **220001FF**  ~/~/ Set AT+DR=1.
207 -
208 -* **Example 2**: Downlink Payload: **220000FF**  ~/~/ Set AT+DR=0.
209 -
210 -(% style="display:none" %) (%%)
211 -
212 -
213 -2)  (% style="color:blue" %)**Node antenna problem**
214 -
215 -Reason:
216 -
217 -Node antenna is loose
218 -
219 -
220 -Solution:
221 -
222 -Please check whether the antenna interface and module interface are detached
223 -
224 -[[image:image-20250429114526-1.png||height="429" width="303"]]
225 -
226 -
227 -
228 -3) (% style="color:blue" %)**Gateway antenna problem**
229 -
230 -Reason:
231 -Gateway uses antenna with wrong frequency band
232 -
233 -For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
234 -
235 -
236 -Solution:
237 -
238 -Please check whether the silk screen on the antenna conflicts with the frequency you set.
239 -
240 -[[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
241 -
242 -
243 -4) (% style="color:blue" %)**Gateway module problem**
244 -
245 -Reason:
246 -
247 -Gateway uses module with wrong frequency band
248 -For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
249 -
250 -
251 -Solution:
252 -
253 -Please check whether the silkscreen of the module conflicts with the frequency you set.
254 -
255 -[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429120030-6.png||height="284" width="378"]]
256 -
257 -
258 -== **2. Frequency point problem** ==
259 -
260 -The frequency point of the gateway or server is wrong or missing.
261 -
262 -
263 -== **3. Frequency band problem** ==
264 -
265 -When there are multiple gateways, the node cannot lock the frequency band.
266 -
267 -
268 -
269 -= 5. Transmision on ABP Mode =
270 -
271 -
272 272  (((
273 -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.
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.
274 274  )))
275 275  
276 276  (((
277 -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.
162 +
278 278  )))
279 279  
280 280  (((
281 281  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
282 -
283 -[[image:image-20240123161737-4.png||height="395" width="763"]]
284 284  )))
285 285  
286 -[[image:image-20240123161853-6.png||height="599" width="771"]]
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]]
287 287  
288 288  Disable Frame Counter Check in ABP Mode
289 289  
290 290  
291 -= 6. Downstream Debug =
174 += 5. Downstream Debug =
292 292  
293 -== 6.1 How it work ==
176 +== 5.1 How it work ==
294 294  
295 -
296 296  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.
297 297  
298 298  (((
299 -Depends on Class A or Class C, the receive windows will be a little difference. The main difference between Class A and Class C:
300 -
301 -* **Class A** : Suitable for Battery powered end node. Class A will save a lot of power but it can only receive downlink after each uplink
302 -* **Class C**: End node can receive downlink immediately but have higher power consumption.
303 -
304 -
181 +Depends on Class A or Class C, the receive windows will be a little difference,
305 305  )))
306 306  
307 -[[image:image-20220531161828-1.png]]
184 +[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
308 308  
309 309  receive windows for Class A and Class C
310 310  
311 -
312 312  Below are the requirement for the End Device to receive the packets.
313 313  
314 314  * The End Device must open the receive windows: RX1 or RX2
315 -
316 316  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
317 -
318 318  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
319 -
320 320  * 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.**
321 321  
322 -* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**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.**
196 +== 5.2 See Debug Info ==
323 323  
324 -== 6.2 See Debug Info ==
198 +**For LoRaWAN Server**
325 325  
326 -
327 -(((
328 -(% style="color:blue" %)**For LoRaWAN Server**
329 -)))
330 -
331 -(((
332 332  We can check if there is downlink message for this end node, use TTN for example:
333 -)))
334 334  
335 -(((
336 -Configure a downlink to the end device
202 +Configure a downstream to the end device
337 337  
338 -[[image:image-20240129152412-8.png||height="486" width="1206"]]
339 -)))
204 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
340 340  
341 -
342 -(((
343 343  Set a downstream in TTN and see it is sent
344 -)))
345 345  
346 -(% style="color:red" %)**Note: After the downlink command is successfully sent from the platform to the node, the downlink command is executed only after the platform receives the next uplink package from the node.**
347 347  
348 -
349 349  (((
350 -This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
210 +This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
351 351  )))
352 352  
353 -[[image:image-20240129152049-7.png||height="463" width="1166"]]
213 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
354 354  
355 -(((
356 -Gateway Traffic can see this downlink info
357 -)))
215 +Gateway Traffic can see this downstream info
358 358  
359 359  
218 +**For LoRaWAN Gateway**
360 360  
361 361  (((
362 -(% style="color:blue" %)**For LoRaWAN Gateway**
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:
363 363  )))
364 364  
365 -(((
366 -When the downlink packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragino Gateway, this can be checked by running "logread -f" in the SSH console. and see below:
367 -)))
224 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
368 368  
369 -[[image:image-20240129154321-9.png]]
370 -
371 -(((
372 372  Gateway Sent out this packet
373 -)))
374 374  
375 375  
229 +**For End Node**
376 376  
231 +we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
232 +
233 +(% class="box infomessage" %)
377 377  (((
378 -(% style="color:blue" %)**For End Node**
235 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
379 379  )))
380 380  
238 +(% class="box infomessage" %)
381 381  (((
382 -we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
240 + AT+RX2DR=3 ~-~--> The RX2 DataRate
383 383  )))
384 384  
243 +(% class="box infomessage" %)
385 385  (((
386 -* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
387 -
388 -* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
389 -
390 -* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
391 -
392 -* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
245 + AT+RX1DL=1000 ~-~--> Receive Delay 1
393 393  )))
394 394  
248 +(% class="box infomessage" %)
395 395  (((
396 -(% style="color:blue" %)**when the device running, we can see below info:**
250 + AT+RX2DL=2000 ~-~--> Receive Delay 2
397 397  )))
398 398  
399 -{{{ [12502]***** UpLinkCounter= 0 *****
400 - [12503]TX on freq 868500000 Hz at DR 0
401 - [13992]txDone
402 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
403 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
404 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
405 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
253 +when the device running, we can see below info:
406 406  
255 +(% class="box" %)
407 407  (((
408 -
409 -
410 -
257 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
258 + [12503]TX on freq 868500000 Hz at DR 0
259 + [13992]txDone
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)
411 411  )))
412 412  
266 +(% class="box" %)
413 413  (((
414 -(% style="color:blue" %)**Another message:**
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
415 415  )))
416 416  
417 -{{{ [12502]***** UpLinkCounter= 0 *****
418 - [12503]TX on freq 868100000 Hz at DR 0
419 - [13992]txDone
420 - [15022]RX on freq 868100000 Hz at DR 0
421 - [15222]rxTimeOut
422 - [15987]RX on freq 869525000 Hz at DR 3
423 - [16185]rxDone --> We have got the downstream packet.
424 - Rssi= -64
425 - Receive data
426 - 1:0012345678}}}
281 +== 5.3 If problem doesn’t solve ==
427 427  
283 +**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:**
428 428  
429 -== 6.3 If problem doesn't solve ==
430 -
431 -
432 -(% style="color:red" %)**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:**
433 -
434 434  * End node console to show the transmit freuqency and DR.
435 -
436 436  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
437 -
438 438  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
439 -
440 440  * End Node traffic (from server UI) to shows end node activity in server.
441 441  
442 -= 7. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
290 += 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
443 443  
292 +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.
444 444  
445 -(((
446 -In LoRaWAN, the gateway 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.
447 -)))
448 -
449 -(((
450 -
451 -)))
452 -
453 -(((
454 454  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:
455 -)))
456 456  
457 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
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 +}}}
458 458  
459 -(((
460 -
461 -)))
462 -
463 -(((
464 464  In this case, please double check the gateway frequency and the server frequency band.
465 -)))
466 466  
467 467  
468 -= 8. Decrypt a LoRaWAN Packet =
302 += 7. Decrypt a LoRaWAN Packet =
469 469  
304 +~1. LHT65 End device configure:
470 470  
471 -(% style="color:blue" %)**1. LHT65N End device configure:**
472 -
473 -**Change to ABP Mode:  AT+NJM=0**
474 -
475 -**Change to fix frequency:  ​​​​AT+CHE=1**
476 -
477 -
478 -**AT+CFG(Print configuration):**
479 -
480 -[[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
481 -
482 -
483 -
484 -**Configuration: **
485 -
486 -[[image:image-20240129164219-4.png||height="612" width="440"]]
487 -
488 -
489 -
490 -(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
491 -
492 -[[image:image-20240129164326-5.png||height="506" width="1114"]]
493 -
494 -
495 -In LPS8-v2 console, we can see the Base64 receive are:
496 -
497 -[[image:image-20240129170137-6.png||height="459" width="1116"]]
498 -
499 -
500 -
501 -(% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
502 -
503 -LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
504 -
505 -Then the instructions and format parsed in SecureCRT are:  ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
506 -
507 -
508 -**Step1: Open CMD, Enter the gateway IP and port.(ssh root@gateway IP -p 22)**
509 -
510 -[[image:image-20240129190752-17.png||height="338" width="901"]]
511 -
512 -[[image:image-20240129191937-21.png||height="450" width="901"]]
513 -
514 -
515 -**Step2: Enter the command to download the LoRa parsing package.(npm install lora-packet)**
516 -
517 -[[image:image-20240129192239-22.png||height="416" width="902"]]
518 -
519 -[[image:image-20240129192549-23.png||height="459" width="898"]]
520 -
521 -
522 -**Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
523 -
524 -
525 -
526 -
527 -[[image:image-20240129192908-24.png||height="477" width="907"]]
528 -
529 -
530 -[[image:image-20240129192954-25.png||height="485" width="916"]]
531 -
532 -
533 -
534 -
535 -
536 -
537 -
538 -= 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
539 -
540 -
541 -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.
542 -
543 -
544 -= 10. Why do I see a "MIC Mismatch" error message from the server? =
545 -
546 -
306 +(% class="box infomessage" %)
547 547  (((
548 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
308 +Change to ABP Mode: AT+NJM=0
549 549  )))
550 550  
311 +(% class="box infomessage" %)
551 551  (((
552 -It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
313 +Change to fix frequency: AT+CHS=904900000
553 553  )))
554 554  
555 -* (((
556 -Please note the distinction between "APPKEY" and "APPSKEY".
557 -)))
558 -
316 +(% class="box infomessage" %)
559 559  (((
560 -2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
318 +Change to fix DR: AT+DR=0
561 561  )))
562 562  
563 -(((
564 -The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
565 -)))
321 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
566 566  
567 -* (((
568 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
569 -)))
323 +2. In LG02 , configure to receive above message
570 570  
571 -(% class="wikigeneratedid" %)
572 -3）Wrong Regional Parameters version selected
573 - We generally use versions above 1.0.2
325 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
574 574  
575 -(% class="wikigeneratedid" %)
576 -[[image:image-20230322163227-1.png]]
327 +In LG02 console, we can see the hex receive are:
577 577  
578 -(% class="wikigeneratedid" %)
579 -4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
329 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
580 580  
331 +3. Decode the info in web
581 581  
582 -= 11. Why I got the payload only with "0x00" or "AA~=~="? =
333 +[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
583 583  
335 +Need these three fields:
584 584  
585 -(% style="color:blue" %)**Why sensor sends 0x00?**
337 +LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
586 586  
587 -For US915, AU915 or AS923 frequencies, the max payload lenght is 11 bytes for DR0. Some times sensor needs to send MAC command to server, because the payload is 11 bytes, The MAC command + Payload will exceed 11 bytes and LoRaWAN server will ignore the uplink. In this case, Sensor will send two uplinks together: one uplink is the payload without MAC command, another uplink is **0x00 payload + MAC Command.**  For the second uplink, in the server side, it will shows the payload is 0x00. Normally, there are several case this will happen.
339 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
588 588  
589 -**Possible Case 1**:
341 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
590 590  
591 -Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
343 +[[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]]
592 592  
345 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
593 593  
594 -**Possible Case 2:**
347 +The FRMPayload is the device payload.
595 595  
596 -For the sensor which has Datalog Feature enable, the sensor will send TimeRequest MAC Command to sync the time. This Time Request will be sent once Sensor Join Network and Every 10 days. While they send such command with DR=0, sensor will send this command with 0x00 payload.
597 597  
350 += 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
598 598  
599 -(% style="color:blue" %)**How to solve:**
352 +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.
600 600  
601 -Solution:
354 += 9. Why do I see a "MIC Mismatch" error message from the server? =
602 602  
603 -~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
356 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
604 604  
605 -2. Data rate changed from DR3 to DR5, increasing upload byte length
606 -AT+ADR=0
607 -AT+DR=3
358 +It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
608 608  
609 -Downlink：
360 +* Please note the distinction between "APPKEY" and "APPSKEY".
610 610  
611 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
362 +2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
612 612  
613 -Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
364 +The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
614 614  
366 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
615 615  
616 -= 12. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
368 += 10. Why i got the payload only with "0x00" or "AA~=~="? =
617 617  
370 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
618 618  
619 -(((
620 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
621 -)))
372 +When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
622 622  
623 -(((
624 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
625 -)))
374 +When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,
626 626  
627 -(((
628 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
629 -)))
376 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
630 630  
631 -(((
632 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
633 -)))
378 +so it will send a normal uplink packet, and an additional 00 data packet.
634 634  
635 -(((
636 -AT+APPEUI=00 00 00 00 00 00 00 00
637 -)))
380 +* Solution: Use the decoder to filter out this 00 packet.
381 +* 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
638 638  
639 -(((
383 +(% class="wikigeneratedid" id="H" %)
640 640  
641 -)))
642 -
643 -(((
644 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
645 -)))
646 -
647 -(((
648 -You can rewrites the keys by running commands in AT Console
649 -
650 -
651 -)))
652 -
653 -(((
654 -**For example：**
655 -)))
656 -
657 -(((
658 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
659 -)))
660 -
661 -(((
662 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
663 -)))
664 -
665 -(((
666 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
667 -)))
668 -
669 -(((
670 -AT+APPEUI=2C 45 47 E3 24 12 23 24
671 -)))
672 -
673 -(((
674 -(Any combination of 16 bit codes can be used）
675 -
676 -
677 -= 13. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
678 -)))
679 -
680 -
681 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
682 -
683 -
684 -= 14. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
685 -
686 -
687 -In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
688 -
689 -
690 -In Dragino Sensors old version firmware (before early 2022), the sub-band is fixed the sub-band to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
691 -
692 -We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, in this case, in this case, the end node can support LoRaWAN servers with different sub-bands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
693 -
694 -* (((
695 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
696 -)))
697 -* (((
698 -Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message (TTN v2 doesn't include).
699 -)))
700 -
701 -This change will make the activation time a little longer but make sure the device can be used in any sub-band.
702 -
703 -
704 -Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the sub-band he uses.
705 -
706 -
707 -[[image:image-20221215223215-1.png||height="584" width="1280"]]
image-20220526163523-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.3 KB
Content
image-20220526163926-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.4 KB
Content
image-20220526163941-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20220526164052-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.3 KB
Content
image-20220526164508-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -50.2 KB
Content
image-20220526164547-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.9 KB
Content
image-20220526164623-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 KB
Content
image-20220526164650-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -45.0 KB
Content
image-20220526164734-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -120.3 KB
Content
image-20220526164956-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content
image-20221215223215-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -183.6 KB
Content
image-20230322163227-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -43.1 KB
Content
image-20240123150720-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -119.9 KB
Content
image-20240123150943-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -161.5 KB
Content
image-20240123151225-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -136.1 KB
Content
image-20240123161737-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -83.0 KB
Content
image-20240123161806-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -71.5 KB
Content
image-20240123161853-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -60.6 KB
Content
image-20240123163307-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -123.3 KB
Content
image-20240123182345-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -108.0 KB
Content
image-20240129142110-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -126.9 KB
Content
image-20240129142147-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -116.1 KB
Content
image-20240129142557-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -125.7 KB
Content
image-20240129142631-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -189.0 KB
Content
image-20240129150821-5.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -129.2 KB
Content
image-20240129151608-6.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -318.1 KB
Content
image-20240129152049-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -148.3 KB
Content
image-20240129152412-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -133.6 KB
Content
image-20240129154321-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -99.5 KB
Content
image-20240129163533-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -80.8 KB
Content
image-20240129170137-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -115.2 KB
Content
image-20240129170603-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.2 KB
Content
image-20240129172956-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.2 KB
Content
image-20240129173810-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
image-20240129173932-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -73.6 KB
Content
image-20240129174125-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content
image-20240129174549-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.6 KB
Content
image-20240129174717-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.6 KB
Content
image-20240129174948-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20240129175037-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.8 KB
Content
image-20240129190344-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20240129190752-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20240129190840-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20240129191130-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -81.7 KB
Content
image-20240129191315-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.0 KB
Content
image-20240129191937-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -71.8 KB
Content
image-20240129192239-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -77.5 KB
Content
image-20240129192549-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -59.5 KB
Content
image-20240129192908-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -101.7 KB
Content
image-20240129192954-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -62.4 KB
Content
image-20250429114526-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -3.2 MB
Content
image-20250429115124-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -193.2 KB
Content
image-20250429115159-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1014.1 KB
Content
image-20250429115942-4.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -435.8 KB
Content
image-20250429115951-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content
image-20250429120030-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content