Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 137.1 >
edited by Edwin Chen
on 2024/02/08 10:28
To version < 101.1 >
edited by Edwin Chen
on 2023/08/16 20:20
>
Change comment: Uploaded new attachment "image-20230816201942-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -16,19 +16,13 @@
16 16  
17 17  = 2. Attach Network =
18 18  
19 -== 2.1 General Configure to attach network ==
20 20  
21 -
22 22  To attache NB-IoT sensors to NB-IoT Network, You need to:
23 23  
24 24  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
25 -1. Power Off End Node ( See below for the power off/on position)
26 -1. Insert the SIM card to Sensor. ( See below for direction)
27 -1. Power On End Node
23 +1. Insert the SIM card to Sensor
28 28  1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
29 29  
30 -[[image:image-20240208102804-1.png||height="286" width="696"]]
31 -
32 32  [[image:image-20230808205045-1.png||height="293" width="438"]]
33 33  
34 34  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -45,28 +45,8 @@
45 45  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
46 46  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 47  
48 -== 2.2 Speed Up Network Attach time ==
49 49  
50 50  
51 -BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show Signal Strenght:99. User can lock the band to specify band for its operator to make this faster.
52 -
53 -(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 -
55 -(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 -
57 -(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
58 -
59 -(% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
60 -(% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
61 -(% style="color:#037691" %)**Telstra**(%%)        AT+QBAND=1,28
62 -(% style="color:#037691" %)**Softband**(%%)     AT+QBAND=2,3,8
63 -
64 -After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
65 -
66 -
67 -See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
68 -
69 -
70 70  = 3. Configure to connect to different servers =
71 71  
72 72  == 3.1 General UDP Connection ==
... ... @@ -80,7 +80,7 @@
80 80  
81 81  We can use PC tool to simulate UDP connection to make sure server works ok.
82 82  
83 -[[image:image-20230802112413-1.png||height="468" width="1024"]]
57 +[[image:image-20230802112413-1.png]]
84 84  
85 85  
86 86  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -130,7 +130,7 @@
130 130  
131 131  [[image:image-20230802112413-4.png]]
132 132  
133 -[[image:image-20230802112413-5.png||height="530" width="987"]]
107 +[[image:image-20230802112413-5.png]]
134 134  
135 135  (% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink  period to a suitable interval.**
136 136  
... ... @@ -142,7 +142,7 @@
142 142  
143 143  [[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.
144 144  
145 -[[image:image-20230802112413-6.png||height="336" width="925"]]
119 +[[image:image-20230802112413-6.png]]
146 146  
147 147  [[image:image-20230802112413-7.png]]
148 148  
... ... @@ -166,6 +166,8 @@
166 166  
167 167  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
168 168  
143 +
144 +
169 169  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
170 170  
171 171  
... ... @@ -185,7 +185,7 @@
185 185  
186 186  (% style="color:blue" %)**Result: **
187 187  
188 -[[image:image-20230802112413-11.png||height="539" width="901"]]
164 +[[image:image-20230802112413-11.png]]
189 189  
190 190  
191 191  === 3.3.3 Configure NB-IoT Sensor for connection ===
... ... @@ -207,10 +207,12 @@
207 207  
208 208  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
209 209  
186 +
187 +
210 210  ==== 3.3.3.2 Uplink Examples ====
211 211  
212 212  
213 -[[image:image-20230816201942-1.png]]
191 +For S31-NB
214 214  
215 215  For SE01-NB
216 216  
... ... @@ -241,9 +241,9 @@
241 241  When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
242 242  
243 243  
244 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
222 +[[image:image-20230802112413-12.png]]
245 245  
246 -[[image:image-20230802112413-13.png||height="331" width="978"]]
224 +[[image:image-20230802112413-13.png]]
247 247  
248 248  
249 249  Below is the NB-IoT Product Table show the mapping.
... ... @@ -268,6 +268,8 @@
268 268  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
269 269  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
270 270  
249 +
250 +
271 271  == 3.4 [[Datacake>>https://datacake.co/]] ==
272 272  
273 273  
... ... @@ -282,16 +282,17 @@
282 282  
283 283  * (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
284 284  
285 -=== 3.4.1 For device Already has template ===
286 286  
287 -==== 3.4.1.1 Create Device ====
288 288  
267 +=== 3.4.1 Create device ===
268 +
269 +
289 289  (% style="color:blue" %)**Add Device**(%%) in DataCake.
290 290  
291 -[[image:image-20230808162301-1.png||height="453" width="952"]]
272 +[[image:image-20230808162301-1.png]]
292 292  
293 293  
294 -[[image:image-20230808162342-2.png||height="541" width="952"]]
275 +[[image:image-20230808162342-2.png]]
295 295  
296 296  
297 297  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -301,16 +301,15 @@
301 301  
302 302  (% style="color:blue" %)**Fill Device ID**(%%). The device ID needs to be filled in with IMEI, and a prefix of(% style="color:blue" %)** 'f' **(%%)needs to be added.
303 303  
304 -[[image:image-20230808163612-7.png||height="549" width="952"]]
285 +[[image:image-20230808163612-7.png]]
305 305  
306 306  [[image:image-20230808163035-5.png]]
307 307  
308 -[[image:image-20230808163049-6.png||height="544" width="926"]]
289 +[[image:image-20230808163049-6.png]]
309 309  
310 310  
311 -=== 3.4.2 For Device already registered in DataCake before shipped ===
292 +=== 3.4.2 Scan QR code to obtain data ===
312 312  
313 -==== 3.4.2.1 Scan QR Code to get the device info ====
314 314  
315 315  Users can use their phones or computers to scan QR codes to obtain device data information.
316 316  
... ... @@ -319,60 +319,9 @@
319 319  [[image:image-20230808170548-9.png]]
320 320  
321 321  
322 -==== 3.4.2.2 Claim Device to User Account ====
302 +=== 3.4.2 AT command for connecting to DataCake ===
323 323  
324 -By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 325  
326 -
327 -
328 -=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
329 -
330 -**Step1:Add a device**
331 -
332 -[[image:image-20240129170024-1.png||height="330" width="900"]]
333 -
334 -**Step2:Choose your device type,please select dragino NB-IOT device**
335 -
336 -[[image:image-20240129170216-2.png||height="534" width="643"]]
337 -
338 -**Step3:Choose to create a new device**
339 -
340 -[[image:image-20240129170539-3.png||height="459" width="646"]]
341 -
342 -**Step4:Fill in the device ID of your NB device**
343 -
344 -[[image:image-20240202111546-1.png||height="378" width="651"]]
345 -
346 -**Step5:Please select your device plan according to your needs and complete the creation of the device**
347 -
348 -[[image:image-20240129171236-6.png||height="450" width="648"]]
349 -
350 -**Step6:Please add the decoder at the payload decoder of the device configuration.**
351 -
352 -**Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
353 -
354 -[[image:image-20240129172056-7.png||height="457" width="816"]]
355 -
356 -[[image:image-20240129173116-9.png||height="499" width="814"]]
357 -
358 -**Step6:Add the output of the decoder as a field**
359 -
360 -[[image:image-20240129173541-10.png||height="592" width="968"]]
361 -
362 -**Step7:Customize the dashboard and use fields as parameters of the dashboard**
363 -
364 -[[image:image-20240129174518-11.png||height="147" width="1042"]]
365 -
366 -[[image:image-20240129174657-12.png||height="538" width="916"]]
367 -
368 -[[image:image-20240129174840-13.png||height="536" width="750"]]
369 -
370 -
371 -=== 3.4.4 For device have not configured to connect to DataCake ===
372 -
373 -(% class="lead" %)
374 -Use AT command for connecting to DataCake
375 -
376 376  (% style="color:blue" %)**AT+PRO=2,0**
377 377  
378 378  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -401,7 +401,7 @@
401 401  
402 402  Please select the NB95S31B template.
403 403  
404 -[[image:image-20230809173310-5.png||height="558" width="926"]]
333 +[[image:image-20230809173310-5.png]]
405 405  
406 406  [[image:image-20230809173438-6.png]]
407 407  
... ... @@ -410,7 +410,7 @@
410 410  
411 411  Successfully imported template.
412 412  
413 -[[image:image-20230809173835-8.png||height="515" width="860"]]
342 +[[image:image-20230809173835-8.png]]
414 414  
415 415  
416 416  Users can set UDP port.
... ... @@ -425,19 +425,17 @@
425 425  
426 426  [[image:image-20230810083934-1.png]]
427 427  
428 -[[image:image-20230810084048-2.png||height="535" width="1052"]]
357 +[[image:image-20230810084048-2.png]]
429 429  
430 -
431 431  === 3.5.3 Configure NB-IoT Sensors ===
432 432  
433 433  
434 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
435 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
436 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
437 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
438 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
439 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
362 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
440 440  
364 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
365 +
366 +
367 +
441 441  == 3.6 ThingsBoard.Cloud (via MQTT) ==
442 442  
443 443  === 3.6.1 Configure ThingsBoard ===
... ... @@ -447,7 +447,7 @@
447 447  
448 448  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
449 449  
450 -[[image:image-20230802112413-32.png||height="583" width="1066"]]
377 +[[image:image-20230802112413-32.png]]
451 451  
452 452  
453 453  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -459,7 +459,7 @@
459 459  
460 460  To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
461 461  
462 -[[image:image-20230802112413-33.png||height="597" width="1061"]]
389 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
463 463  
464 464  
465 465  (% style="color:blue" %)**Downlink Converter**
... ... @@ -466,7 +466,7 @@
466 466  
467 467  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
468 468  
469 -[[image:image-20230802112413-34.png||height="598" width="1063"]]
396 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
470 470  
471 471  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
472 472  
... ... @@ -476,23 +476,23 @@
476 476  
477 477  Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
478 478  
479 -[[image:image-20230802112413-35.png||height="597" width="1062"]]
406 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
480 480  
481 481  
482 482  * The next steps is to add the recently created uplink and downlink converters;
483 483  
484 -[[image:image-20230802112413-36.png||height="598" width="1062"]]
411 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
485 485  
486 -[[image:image-20230802112413-37.png||height="598" width="1064"]]
413 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
487 487  
488 488  
489 489  (% style="color:blue" %)**Add a topic filter:**
490 490  
491 -Consistent with the theme of the node setting.
418 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
492 492  
493 493  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
494 494  
495 -[[image:image-20230802112413-38.png||height="598" width="1064"]]
422 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
496 496  
497 497  
498 498  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -500,7 +500,7 @@
500 500  
501 501  [[image:image-20230802112413-39.png]]
502 502  
503 -[[image:image-20230802112413-40.png||height="525" width="980"]]
430 +[[image:image-20230802112413-40.png]]
504 504  
505 505  
506 506  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -522,11 +522,11 @@
522 522  
523 523  Test Uplink by click the button for 1 second
524 524  
525 -[[image:image-20230802112413-41.png||height="496" width="828"]]
452 +[[image:image-20230802112413-41.png]]
526 526  
527 527  [[image:image-20230802112413-42.png]]
528 528  
529 -[[image:image-20230802112413-43.png||height="407" width="825"]]
456 +[[image:image-20230802112413-43.png]]
530 530  
531 531  
532 532  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -582,6 +582,8 @@
582 582  
583 583  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
584 584  
512 +
513 +
585 585  === 3.7.2 Simulate with MQTT.fx ===
586 586  
587 587  
... ... @@ -588,12 +588,12 @@
588 588  [[image:image-20230802112413-52.png]]
589 589  
590 590  
591 -[[image:image-20230808105300-2.png||height="553" width="1026"]]
520 +[[image:image-20230808105300-2.png]]
592 592  
593 593  
594 594  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
595 595  
596 -[[image:image-20230808105217-1.png||height="556" width="1031"]]
525 +[[image:image-20230808105217-1.png]]
597 597  
598 598  [[image:image-20230808105329-3.png]]
599 599  
... ... @@ -601,7 +601,7 @@
601 601  === 3.7.3 tago data ===
602 602  
603 603  
604 -[[image:image-20230802112413-50.png||height="242" width="1037"]]
533 +[[image:image-20230802112413-50.png]]
605 605  
606 606  [[image:image-20230802112413-51.png||height="184" width="696"]]
607 607  
... ... @@ -625,76 +625,3 @@
625 625  (% style="color:blue" %)**See result in TCP Server:**
626 626  
627 627  [[image:image-20230807233631-2.png]]
628 -
629 -
630 -= 4. FAQ =
631 -
632 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
633 -
634 -The NB series has the feature for Multi Sampling and one uplink. See one of them
635 -
636 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
637 -
638 -User can use this feature for below purpose:
639 -
640 -1. **Reduce power consumption**. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.
641 -1. Give more sampling data points.
642 -1. Increase reliable in transmission. For example. If user set
643 -1*. **AT+TR=1800** ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
644 -1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
645 -1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
646 -1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn;t lost 6 continue data. There will not data lost.
647 -
648 -= 5. Trouble Shooting: =
649 -
650 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
651 -
652 -There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.
653 -
654 -If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
655 -
656 -[[image:image-20240207002003-1.png]]
657 -
658 -
659 -If fail to attach network, it will shows signal 99. as below:
660 -
661 -[[image:image-20240207002129-2.png]]
662 -
663 -
664 -(% class="lead" %)
665 -When see this issue, below are the checklist:
666 -
667 -* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
668 -* Do you configure the correct APN? [[Check here for APN settings>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
669 -* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
670 -* Check if the device is attached to Carrier network but reject. (need to check with operator).
671 -* Check if the antenna is connected firmly.
672 -
673 -If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.
674 -
675 -
676 -== 5.2 NBIOT did not respond issue. ==
677 -
678 -(% class="box errormessage" %)
679 -(((
680 -11:24:22.397 [44596]NBIOT did not respond.
681 -11:24:24.315 [46530]NBIOT did not respond.
682 -11:24:26.256 [48464]NBIOT did not respond.
683 -11:24:28.196 [50398]NBIOT did not respond.
684 -11:24:30.115 [52332]NBIOT did not respond.
685 -11:24:32.127 [54266]NBIOT did not respond.
686 -11:24:32.127 [54299]Restart the module...
687 -11:24:39.181 [61332]No response when shutting down
688 -)))
689 -
690 -This issue might due to initiate issue for NB-IoT module. In this case, please try:
691 -
692 -1) Open Enclosure
693 -
694 -2) Power off device by pull out the power on Jumper
695 -
696 -3) Power on device by connect back the power jumper.
697 -
698 -4) push reset button.
699 -
700 -[[image:image-20240208001740-1.png]]
image-20240129170024-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -507.6 KB
Content

Applications

Navigation

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