Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 102.1
edited by Edwin Chen
on 2023/08/16 20:21
Change comment: There is no comment for this version
To version 145.2
edited by Xiaoling
on 2024/03/01 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -16,13 +16,19 @@
16 16  
17 17  = 2. Attach Network =
18 18  
19 +== 2.1 General Configure to attach network ==
19 19  
21 +
20 20  To attache NB-IoT sensors to NB-IoT Network, You need to:
21 21  
22 22  1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
23 -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
24 24  1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
25 25  
30 +[[image:image-20240208102804-1.png||height="286" width="696"]]
31 +
26 26  [[image:image-20230808205045-1.png||height="293" width="438"]]
27 27  
28 28  After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
... ... @@ -39,7 +39,28 @@
39 39  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
40 40  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
41 41  
48 +== 2.2 Speed Up Network Attach time ==
42 42  
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 +
43 43  = 3. Configure to connect to different servers =
44 44  
45 45  == 3.1 General UDP Connection ==
... ... @@ -53,7 +53,7 @@
53 53  
54 54  We can use PC tool to simulate UDP connection to make sure server works ok.
55 55  
56 -[[image:image-20230802112413-1.png]]
83 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
57 57  
58 58  
59 59  === 3.1.2 Configure NB-IoT Sensor ===
... ... @@ -67,8 +67,6 @@
67 67  
68 68  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
69 69  
70 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
71 -
72 72  [[image:image-20230802112413-2.png]]
73 73  
74 74  
... ... @@ -139,7 +139,6 @@
139 139  
140 140  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
141 141  
142 -
143 143  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
144 144  
145 145  
... ... @@ -181,9 +181,9 @@
181 181  
182 182  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
183 183  
184 -
185 185  ==== 3.3.3.2 Uplink Examples ====
186 186  
210 +
187 187  [[image:image-20230816201942-1.png]]
188 188  
189 189  For SE01-NB
... ... @@ -242,7 +242,6 @@
242 242  |(% 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" %)
243 243  |(% 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" %)
244 244  
245 -
246 246  == 3.4 [[Datacake>>https://datacake.co/]] ==
247 247  
248 248  
... ... @@ -257,16 +257,16 @@
257 257  
258 258  * (% 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.
259 259  
283 +=== 3.4.1 For device Already has template ===
260 260  
261 -=== 3.4.1 Create device ===
285 +==== 3.4.1.1 Create Device ====
262 262  
263 -
264 264  (% style="color:blue" %)**Add Device**(%%) in DataCake.
265 265  
266 -[[image:image-20230808162301-1.png||height="473" width="994"]]
289 +[[image:image-20230808162301-1.png||height="453" width="952"]]
267 267  
268 268  
269 -[[image:image-20230808162342-2.png]]
292 +[[image:image-20230808162342-2.png||height="541" width="952"]]
270 270  
271 271  
272 272  (% style="color:blue" %)**Choose the correct model**(%%) from template.
... ... @@ -276,16 +276,18 @@
276 276  
277 277  (% 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.
278 278  
279 -[[image:image-20230808163612-7.png]]
302 +[[image:image-20230808163612-7.png||height="549" width="952"]]
280 280  
281 281  [[image:image-20230808163035-5.png]]
282 282  
283 -[[image:image-20230808163049-6.png]]
306 +[[image:image-20230808163049-6.png||height="544" width="926"]]
284 284  
285 285  
286 -=== 3.4.2 Scan QR code to obtain data ===
309 +=== 3.4.2 For Device already registered in DataCake before shipped ===
287 287  
311 +==== 3.4.2.1 Scan QR Code to get the device info ====
288 288  
313 +
289 289  Users can use their phones or computers to scan QR codes to obtain device data information.
290 290  
291 291  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -293,9 +293,69 @@
293 293  [[image:image-20230808170548-9.png]]
294 294  
295 295  
296 -=== 3.4.2 AT command for connecting to DataCake ===
321 +==== 3.4.2.2 Claim Device to User Account ====
297 297  
298 298  
324 +By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 +
326 +
327 +=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
328 +
329 +
330 +**Step1: Add a device**
331 +
332 +[[image:image-20240129170024-1.png||height="330" width="900"]]
333 +
334 +
335 +**Step2: Choose your device type,please select dragino NB-IOT device**
336 +
337 +[[image:image-20240129170216-2.png||height="534" width="643"]]
338 +
339 +
340 +**Step3: Choose to create a new device**
341 +
342 +[[image:image-20240129170539-3.png||height="459" width="646"]]
343 +
344 +
345 +**Step4: Fill in the device ID of your NB device**
346 +
347 +[[image:image-20240202111546-1.png||height="378" width="651"]]
348 +
349 +
350 +**Step5: Please select your device plan according to your needs and complete the creation of the device**
351 +
352 +[[image:image-20240129171236-6.png||height="450" width="648"]]
353 +
354 +
355 +**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 +
357 +**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]]
358 +
359 +[[image:image-20240129172056-7.png||height="457" width="816"]]
360 +
361 +[[image:image-20240129173116-9.png||height="499" width="814"]]
362 +
363 +
364 +**Step7: Add the output of the decoder as a field**
365 +
366 +[[image:image-20240129173541-10.png||height="592" width="968"]]
367 +
368 +
369 +**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 +
371 +[[image:image-20240129174518-11.png||height="147" width="1042"]]
372 +
373 +[[image:image-20240129174657-12.png||height="538" width="916"]]
374 +
375 +[[image:image-20240129174840-13.png||height="536" width="750"]]
376 +
377 +
378 +=== 3.4.4 For device have not configured to connect to DataCake ===
379 +
380 +
381 +(% class="lead" %)
382 +Use AT command for connecting to DataCake
383 +
299 299  (% style="color:blue" %)**AT+PRO=2,0**
300 300  
301 301  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
... ... @@ -324,7 +324,7 @@
324 324  
325 325  Please select the NB95S31B template.
326 326  
327 -[[image:image-20230809173310-5.png]]
412 +[[image:image-20230809173310-5.png||height="558" width="926"]]
328 328  
329 329  [[image:image-20230809173438-6.png]]
330 330  
... ... @@ -333,7 +333,7 @@
333 333  
334 334  Successfully imported template.
335 335  
336 -[[image:image-20230809173835-8.png]]
421 +[[image:image-20230809173835-8.png||height="515" width="860"]]
337 337  
338 338  
339 339  Users can set UDP port.
... ... @@ -348,16 +348,19 @@
348 348  
349 349  [[image:image-20230810083934-1.png]]
350 350  
351 -[[image:image-20230810084048-2.png]]
436 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
352 352  
438 +
353 353  === 3.5.3 Configure NB-IoT Sensors ===
354 354  
355 355  
356 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
442 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
443 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
444 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
445 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
446 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
447 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
357 357  
358 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
359 -
360 -
361 361  == 3.6 ThingsBoard.Cloud (via MQTT) ==
362 362  
363 363  === 3.6.1 Configure ThingsBoard ===
... ... @@ -367,7 +367,7 @@
367 367  
368 368  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
369 369  
370 -[[image:image-20230802112413-32.png]]
458 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
371 371  
372 372  
373 373  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
... ... @@ -379,7 +379,7 @@
379 379  
380 380  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.
381 381  
382 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
470 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
383 383  
384 384  
385 385  (% style="color:blue" %)**Downlink Converter**
... ... @@ -386,7 +386,7 @@
386 386  
387 387  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
388 388  
389 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
477 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
390 390  
391 391  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
392 392  
... ... @@ -396,23 +396,23 @@
396 396  
397 397  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**;
398 398  
399 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
487 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
400 400  
401 401  
402 402  * The next steps is to add the recently created uplink and downlink converters;
403 403  
404 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
492 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
405 405  
406 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
494 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
407 407  
408 408  
409 409  (% style="color:blue" %)**Add a topic filter:**
410 410  
411 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
499 +Consistent with the theme of the node setting.
412 412  
413 413  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
414 414  
415 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
503 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
416 416  
417 417  
418 418  === 3.6.2 Simulate with MQTT.fx ===
... ... @@ -420,7 +420,7 @@
420 420  
421 421  [[image:image-20230802112413-39.png]]
422 422  
423 -[[image:image-20230802112413-40.png]]
511 +[[image:image-20230802112413-40.png||height="525" width="980"]]
424 424  
425 425  
426 426  === 3.6.3 Configure NB-IoT Sensor ===
... ... @@ -442,11 +442,11 @@
442 442  
443 443  Test Uplink by click the button for 1 second
444 444  
445 -[[image:image-20230802112413-41.png]]
533 +[[image:image-20230802112413-41.png||height="496" width="828"]]
446 446  
447 447  [[image:image-20230802112413-42.png]]
448 448  
449 -[[image:image-20230802112413-43.png]]
537 +[[image:image-20230802112413-43.png||height="407" width="825"]]
450 450  
451 451  
452 452  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
... ... @@ -502,7 +502,6 @@
502 502  
503 503  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
504 504  
505 -
506 506  === 3.7.2 Simulate with MQTT.fx ===
507 507  
508 508  
... ... @@ -509,12 +509,12 @@
509 509  [[image:image-20230802112413-52.png]]
510 510  
511 511  
512 -[[image:image-20230808105300-2.png]]
599 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
513 513  
514 514  
515 515  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
516 516  
517 -[[image:image-20230808105217-1.png]]
604 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
518 518  
519 519  [[image:image-20230808105329-3.png]]
520 520  
... ... @@ -522,7 +522,7 @@
522 522  === 3.7.3 tago data ===
523 523  
524 524  
525 -[[image:image-20230802112413-50.png]]
612 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
526 526  
527 527  [[image:image-20230802112413-51.png||height="184" width="696"]]
528 528  
... ... @@ -546,3 +546,114 @@
546 546  (% style="color:blue" %)**See result in TCP Server:**
547 547  
548 548  [[image:image-20230807233631-2.png]]
636 +
637 +
638 += 4. FAQ =
639 +
640 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
641 +
642 +
643 +The NB series has the feature for Multi Sampling and one uplink. See one of them
644 +
645 +[[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]]
646 +
647 +User can use this feature for below purpose:
648 +
649 +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.
650 +1. Give more sampling data points.
651 +1. Increase reliable in transmission. For example. If user set
652 +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)
653 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
654 +1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
655 +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.
656 +
657 +
658 +
659 +== 4.2 Why the uplink JSON format is not standard? ==
660 +
661 +
662 +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.
663 +
664 +[[image:image-20240229233154-1.png]]
665 +
666 +
667 += 5. Trouble Shooting: =
668 +
669 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
670 +
671 +
672 +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.
673 +
674 +If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
675 +
676 +[[image:image-20240207002003-1.png]]
677 +
678 +
679 +If fail to attach network, it will shows signal 99. as below:
680 +
681 +[[image:image-20240207002129-2.png]]
682 +
683 +
684 +(% class="lead" %)
685 +When see this issue, below are the checklist:
686 +
687 +* 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.
688 +* 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]].
689 +* 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]].
690 +* Check if the device is attached to Carrier network but reject. (need to check with operator).
691 +* Check if the antenna is connected firmly.
692 +
693 +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.
694 +
695 +
696 +== 5.2 Issue: "NBIOT did not respond" ==
697 +
698 +
699 +(% class="box errormessage" %)
700 +(((
701 +11:24:22.397 [44596]NBIOT did not respond.
702 +11:24:24.315 [46530]NBIOT did not respond.
703 +11:24:26.256 [48464]NBIOT did not respond.
704 +11:24:28.196 [50398]NBIOT did not respond.
705 +11:24:30.115 [52332]NBIOT did not respond.
706 +11:24:32.127 [54266]NBIOT did not respond.
707 +11:24:32.127 [54299]Restart the module...
708 +11:24:39.181 [61332]No response when shutting down
709 +)))
710 +
711 +This issue might due to initiate issue for NB-IoT module. In this case, please try:
712 +
713 +1) Open Enclosure
714 +
715 +2) Power off device by pull out the power on Jumper
716 +
717 +3) Power on device by connect back the power jumper.
718 +
719 +4) push reset button.
720 +
721 +[[image:image-20240208001740-1.png]]
722 +
723 +
724 +== 5.3 Issue: "Failed to readI MSI number" ==
725 +
726 +
727 +(% class="box errormessage" %)
728 +(((
729 +[18170]Failed to read IMSI:1umber.
730 +[20109]Failed to read IMSI numoer.
731 +[22048]Failed to read IMSI number.
732 +[29842lRestart the module...
733 +)))
734 +
735 +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"]].
736 +
737 +
738 +== 5.4 Why sometime the AT Command is slow in reponse? ==
739 +
740 +
741 +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.
742 +
743 +[[image:image-20240226111928-1.png]]
744 +
745 +
746 +
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