Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 104.5
edited by Xiaoling
on 2023/10/07 10:56
Change comment: There is no comment for this version
To version 145.1
edited by Edwin Chen
on 2024/02/29 23:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -22,9 +22,13 @@
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. Insert the SIM card to Sensor
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
26 26  1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
27 27  
30 +[[image:image-20240208102804-1.png||height="286" width="696"]]
31 +
28 28  [[image:image-20230808205045-1.png||height="293" width="438"]]
29 29  
30 30  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -41,20 +41,28 @@
41 41  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
42 42  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
43 43  
48 +== 2.2 Speed Up Network Attach time ==
44 44  
45 45  
46 -== 2.2 Speed Up Network Attach time ==
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.
47 47  
53 +(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
48 48  
49 -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. User can lock the band to specify band for its operator to make this faster.
55 +(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
50 50  
51 -(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
57 +(% style="color:#037691" %)**Europe General**(%%) **AT+QBAND=2,8,20 ** ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
52 52  
53 -(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
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
54 54  
55 -(% style="color:#037691" %)**AT+QBAND=2,8,20**  (%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
64 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
56 56  
57 57  
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 +
58 58  = 3. Configure to connect to different servers =
59 59  
60 60  == 3.1 General UDP Connection ==
... ... @@ -68,7 +68,7 @@
68 68  
69 69  We can use PC tool to simulate UDP connection to make sure server works ok.
70 70  
71 -[[image:image-20230802112413-1.png]]
83 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
72 72  
73 73  
74 74  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -82,8 +82,6 @@
82 82  
83 83  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
84 84  
85 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
86 -
87 87  [[image:image-20230802112413-2.png]]
88 88  
89 89  
... ... @@ -154,8 +154,6 @@
154 154  
155 155  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
156 156  
157 -
158 -
159 159  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
160 160  
161 161  
... ... @@ -197,8 +197,6 @@
197 197  
198 198  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
199 199  
200 -
201 -
202 202  ==== 3.3.3.2 Uplink Examples ====
203 203  
204 204  
... ... @@ -260,8 +260,6 @@
260 260  |(% 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" %)
261 261  |(% 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" %)
262 262  
263 -
264 -
265 265  == 3.4 [[Datacake>>https://datacake.co/]] ==
266 266  
267 267  
... ... @@ -276,17 +276,16 @@
276 276  
277 277  * (% 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.
278 278  
283 +=== 3.4.1 For device Already has template ===
279 279  
285 +==== 3.4.1.1 Create Device ====
280 280  
281 -=== 3.4.1 Create device ===
282 -
283 -
284 284  (% style="color:blue" %)**Add Device**(%%) in DataCake.
285 285  
286 -[[image:image-20230808162301-1.png||height="473" width="994"]]
289 +[[image:image-20230808162301-1.png||height="453" width="952"]]
287 287  
288 288  
289 -[[image:image-20230808162342-2.png]]
292 +[[image:image-20230808162342-2.png||height="541" width="952"]]
290 290  
291 291  
292 292  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -296,15 +296,16 @@
296 296  
297 297  (% 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.
298 298  
299 -[[image:image-20230808163612-7.png]]
302 +[[image:image-20230808163612-7.png||height="549" width="952"]]
300 300  
301 301  [[image:image-20230808163035-5.png]]
302 302  
303 -[[image:image-20230808163049-6.png]]
306 +[[image:image-20230808163049-6.png||height="544" width="926"]]
304 304  
305 305  
306 -=== 3.4.2 Scan QR code to obtain data ===
309 +=== 3.4.2 For Device already registered in DataCake before shipped ===
307 307  
311 +==== 3.4.2.1 Scan QR Code to get the device info ====
308 308  
309 309  Users can use their phones or computers to scan QR codes to obtain device data information.
310 310  
... ... @@ -313,9 +313,60 @@
313 313  [[image:image-20230808170548-9.png]]
314 314  
315 315  
316 -=== 3.4.2 AT command for connecting to DataCake ===
320 +==== 3.4.2.2 Claim Device to User Account ====
317 317  
322 +By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
318 318  
324 +
325 +
326 +=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
327 +
328 +**Step1:Add a device**
329 +
330 +[[image:image-20240129170024-1.png||height="330" width="900"]]
331 +
332 +**Step2:Choose your device type,please select dragino NB-IOT device**
333 +
334 +[[image:image-20240129170216-2.png||height="534" width="643"]]
335 +
336 +**Step3:Choose to create a new device**
337 +
338 +[[image:image-20240129170539-3.png||height="459" width="646"]]
339 +
340 +**Step4:Fill in the device ID of your NB device**
341 +
342 +[[image:image-20240202111546-1.png||height="378" width="651"]]
343 +
344 +**Step5:Please select your device plan according to your needs and complete the creation of the device**
345 +
346 +[[image:image-20240129171236-6.png||height="450" width="648"]]
347 +
348 +**Step6:Please add the decoder at the payload decoder of the device configuration.**
349 +
350 +**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]]
351 +
352 +[[image:image-20240129172056-7.png||height="457" width="816"]]
353 +
354 +[[image:image-20240129173116-9.png||height="499" width="814"]]
355 +
356 +**Step6:Add the output of the decoder as a field**
357 +
358 +[[image:image-20240129173541-10.png||height="592" width="968"]]
359 +
360 +**Step7:Customize the dashboard and use fields as parameters of the dashboard**
361 +
362 +[[image:image-20240129174518-11.png||height="147" width="1042"]]
363 +
364 +[[image:image-20240129174657-12.png||height="538" width="916"]]
365 +
366 +[[image:image-20240129174840-13.png||height="536" width="750"]]
367 +
368 +
369 +=== 3.4.4 For device have not configured to connect to DataCake ===
370 +
371 +(% class="lead" %)
372 +Use AT command for connecting to DataCake
373 +
319 319  (% style="color:blue" %)**AT+PRO=2,0**
320 320  
321 321  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -344,7 +344,7 @@
344 344  
345 345  Please select the NB95S31B template.
346 346  
347 -[[image:image-20230809173310-5.png]]
402 +[[image:image-20230809173310-5.png||height="558" width="926"]]
348 348  
349 349  [[image:image-20230809173438-6.png]]
350 350  
... ... @@ -353,7 +353,7 @@
353 353  
354 354  Successfully imported template.
355 355  
356 -[[image:image-20230809173835-8.png]]
411 +[[image:image-20230809173835-8.png||height="515" width="860"]]
357 357  
358 358  
359 359  Users can set UDP port.
... ... @@ -368,17 +368,19 @@
368 368  
369 369  [[image:image-20230810083934-1.png]]
370 370  
371 -[[image:image-20230810084048-2.png]]
426 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
372 372  
428 +
373 373  === 3.5.3 Configure NB-IoT Sensors ===
374 374  
375 375  
376 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
432 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
433 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
434 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
435 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
436 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
437 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
377 377  
378 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
379 -
380 -
381 -
382 382  == 3.6 ThingsBoard.Cloud (via MQTT) ==
383 383  
384 384  === 3.6.1 Configure ThingsBoard ===
... ... @@ -388,7 +388,7 @@
388 388  
389 389  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
390 390  
391 -[[image:image-20230802112413-32.png]]
448 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
392 392  
393 393  
394 394  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -400,7 +400,7 @@
400 400  
401 401  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.
402 402  
403 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
460 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
404 404  
405 405  
406 406  (% style="color:blue" %)**Downlink Converter**
... ... @@ -407,7 +407,7 @@
407 407  
408 408  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
409 409  
410 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
467 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
411 411  
412 412  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
413 413  
... ... @@ -417,23 +417,23 @@
417 417  
418 418  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**;
419 419  
420 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
477 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
421 421  
422 422  
423 423  * The next steps is to add the recently created uplink and downlink converters;
424 424  
425 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
482 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
426 426  
427 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
484 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
428 428  
429 429  
430 430  (% style="color:blue" %)**Add a topic filter:**
431 431  
432 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
489 +Consistent with the theme of the node setting.
433 433  
434 434  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
435 435  
436 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
493 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
437 437  
438 438  
439 439  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -441,7 +441,7 @@
441 441  
442 442  [[image:image-20230802112413-39.png]]
443 443  
444 -[[image:image-20230802112413-40.png]]
501 +[[image:image-20230802112413-40.png||height="525" width="980"]]
445 445  
446 446  
447 447  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -463,11 +463,11 @@
463 463  
464 464  Test Uplink by click the button for 1 second
465 465  
466 -[[image:image-20230802112413-41.png]]
523 +[[image:image-20230802112413-41.png||height="496" width="828"]]
467 467  
468 468  [[image:image-20230802112413-42.png]]
469 469  
470 -[[image:image-20230802112413-43.png]]
527 +[[image:image-20230802112413-43.png||height="407" width="825"]]
471 471  
472 472  
473 473  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -523,8 +523,6 @@
523 523  
524 524  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
525 525  
526 -
527 -
528 528  === 3.7.2 Simulate with MQTT.fx ===
529 529  
530 530  
... ... @@ -531,12 +531,12 @@
531 531  [[image:image-20230802112413-52.png]]
532 532  
533 533  
534 -[[image:image-20230808105300-2.png]]
589 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
535 535  
536 536  
537 537  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
538 538  
539 -[[image:image-20230808105217-1.png]]
594 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
540 540  
541 541  [[image:image-20230808105329-3.png]]
542 542  
... ... @@ -544,7 +544,7 @@
544 544  === 3.7.3 tago data ===
545 545  
546 546  
547 -[[image:image-20230802112413-50.png]]
602 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
548 548  
549 549  [[image:image-20230802112413-51.png||height="184" width="696"]]
550 550  
... ... @@ -568,3 +568,108 @@
568 568  (% style="color:blue" %)**See result in TCP Server:**
569 569  
570 570  [[image:image-20230807233631-2.png]]
626 +
627 +
628 += 4. FAQ =
629 +
630 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
631 +
632 +The NB series has the feature for Multi Sampling and one uplink. See one of them
633 +
634 +[[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]]
635 +
636 +User can use this feature for below purpose:
637 +
638 +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.
639 +1. Give more sampling data points.
640 +1. Increase reliable in transmission. For example. If user set
641 +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)
642 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
643 +1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
644 +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.
645 +
646 +
647 +== 4.2 Why the uplink JSON format is not standard? ==
648 +
649 +The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
650 +
651 +[[image:image-20240229233154-1.png]]
652 +
653 +
654 +
655 += 5. Trouble Shooting: =
656 +
657 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
658 +
659 +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.
660 +
661 +If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
662 +
663 +[[image:image-20240207002003-1.png]]
664 +
665 +
666 +If fail to attach network, it will shows signal 99. as below:
667 +
668 +[[image:image-20240207002129-2.png]]
669 +
670 +
671 +(% class="lead" %)
672 +When see this issue, below are the checklist:
673 +
674 +* 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.
675 +* 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]].
676 +* 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]].
677 +* Check if the device is attached to Carrier network but reject. (need to check with operator).
678 +* Check if the antenna is connected firmly.
679 +
680 +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.
681 +
682 +
683 +== 5.2 Issue: "NBIOT did not respond" ==
684 +
685 +(% class="box errormessage" %)
686 +(((
687 +11:24:22.397 [44596]NBIOT did not respond.
688 +11:24:24.315 [46530]NBIOT did not respond.
689 +11:24:26.256 [48464]NBIOT did not respond.
690 +11:24:28.196 [50398]NBIOT did not respond.
691 +11:24:30.115 [52332]NBIOT did not respond.
692 +11:24:32.127 [54266]NBIOT did not respond.
693 +11:24:32.127 [54299]Restart the module...
694 +11:24:39.181 [61332]No response when shutting down
695 +)))
696 +
697 +This issue might due to initiate issue for NB-IoT module. In this case, please try:
698 +
699 +1) Open Enclosure
700 +
701 +2) Power off device by pull out the power on Jumper
702 +
703 +3) Power on device by connect back the power jumper.
704 +
705 +4) push reset button.
706 +
707 +[[image:image-20240208001740-1.png]]
708 +
709 +
710 +== 5.3 Issue: "Failed to readI MSI number" ==
711 +
712 +(% class="box errormessage" %)
713 +(((
714 +[18170]Failed to read IMSI:1umber.
715 +[20109]Failed to read IMSI numoer.
716 +[22048]Failed to read IMSI number.
717 +[29842lRestart the module...
718 +)))
719 +
720 +Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
721 +
722 +
723 +== 5.4 Why sometime the AT Command is slow in reponse? ==
724 +
725 +When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
726 +
727 +[[image:image-20240226111928-1.png]]
728 +
729 +
730 +
image-20240129170024-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +49.8 KB
Content
image-20240129172056-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +69.8 KB
Content
image-20240129172136-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +80.4 KB
Content
image-20240129173116-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +110.8 KB
Content
image-20240129173541-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +95.4 KB
Content
image-20240129174518-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +23.2 KB
Content
image-20240129174657-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +141.9 KB
Content
image-20240129174840-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +92.9 KB
Content
image-20240202111546-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +33.3 KB
Content
image-20240207002003-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20240207002129-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +17.9 KB
Content
image-20240208001740-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +487.1 KB
Content
image-20240208102804-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +507.6 KB
Content
image-20240226111928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +52.0 KB
Content
image-20240229233154-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +39.5 KB
Content