Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 105.1
edited by Edwin Chen
on 2023/11/05 08:49
Change comment: There is no comment for this version
To version 147.1
edited by Edwin Chen
on 2024/03/03 16:50
Change comment: There is no comment for this version

Summary

Details

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