Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 176.1
edited by kai
on 2024/07/29 17:24
Change comment: Uploaded new attachment "image-20240729172415-13.png", version {1}
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.kai
1 +XWiki.Edwin
Content
... ... @@ -25,7 +25,7 @@
25 25  1. Power Off End Node ( See below for the power off/on position)
26 26  1. Insert the SIM card to Sensor. ( See below for direction)
27 27  1. Power On End Node
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>), example AT+APN=iot.1nce.net
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 30  [[image:image-20240208102804-1.png||height="286" width="696"]]
31 31  
... ... @@ -40,8 +40,8 @@
40 40  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
41 41  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
42 42  
43 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
44 -)))|(% style="width:135px" %)UK: Band20
43 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
44 +)))|(% style="width:135px" %)
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,12 +48,13 @@
48 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.
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 52  
53 53  (% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
54 +
54 54  (% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
56 +
55 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**
57 57  
58 58  (% style="color:#037691" %)**Verizon**(%%)** ** AT+QBAND=1,13
59 59  (% style="color:#037691" %)**AT&T**(%%)           AT+QBAND=3,12,4,2
... ... @@ -62,7 +62,6 @@
62 62  
63 63  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64 64  
65 -By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
66 66  
67 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 68  
... ... @@ -310,7 +310,6 @@
310 310  
311 311  ==== 3.4.2.1 Scan QR Code to get the device info ====
312 312  
313 -
314 314  Users can use their phones or computers to scan QR codes to obtain device data information.
315 315  
316 316  [[image:image-20230808170051-8.png||height="255" width="259"]]
... ... @@ -320,40 +320,34 @@
320 320  
321 321  ==== 3.4.2.2 Claim Device to User Account ====
322 322  
323 -
324 324  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
325 325  
326 326  
325 +
327 327  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
328 328  
328 +**Step1:Add a device**
329 329  
330 -**Step1: Add a device**
331 -
332 332  [[image:image-20240129170024-1.png||height="330" width="900"]]
333 333  
332 +**Step2:Choose your device type,please select dragino NB-IOT device**
334 334  
335 -**Step2: Choose your device type,please select dragino NB-IOT device**
336 -
337 337  [[image:image-20240129170216-2.png||height="534" width="643"]]
338 338  
336 +**Step3:Choose to create a new device**
339 339  
340 -**Step3: Choose to create a new device**
341 -
342 342  [[image:image-20240129170539-3.png||height="459" width="646"]]
343 343  
340 +**Step4:Fill in the device ID of your NB device**
344 344  
345 -**Step4: Fill in the device ID of your NB device**
346 -
347 347  [[image:image-20240202111546-1.png||height="378" width="651"]]
348 348  
344 +**Step5:Please select your device plan according to your needs and complete the creation of the device**
349 349  
350 -**Step5: Please select your device plan according to your needs and complete the creation of the device**
351 -
352 352  [[image:image-20240129171236-6.png||height="450" width="648"]]
353 353  
348 +**Step6:Please add the decoder at the payload decoder of the device configuration.**
354 354  
355 -**Step6: Please add the decoder at the payload decoder of the device configuration.**
356 -
357 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 358  
359 359  [[image:image-20240129172056-7.png||height="457" width="816"]]
... ... @@ -360,14 +360,12 @@
360 360  
361 361  [[image:image-20240129173116-9.png||height="499" width="814"]]
362 362  
356 +**Step6:Add the output of the decoder as a field**
363 363  
364 -**Step7: Add the output of the decoder as a field**
365 -
366 366  [[image:image-20240129173541-10.png||height="592" width="968"]]
367 367  
360 +**Step7:Customize the dashboard and use fields as parameters of the dashboard**
368 368  
369 -**Step8: Customize the dashboard and use fields as parameters of the dashboard**
370 -
371 371  [[image:image-20240129174518-11.png||height="147" width="1042"]]
372 372  
373 373  [[image:image-20240129174657-12.png||height="538" width="916"]]
... ... @@ -377,7 +377,6 @@
377 377  
378 378  === 3.4.4 For device have not configured to connect to DataCake ===
379 379  
380 -
381 381  (% class="lead" %)
382 382  Use AT command for connecting to DataCake
383 383  
... ... @@ -537,67 +537,11 @@
537 537  [[image:image-20230802112413-43.png||height="407" width="825"]]
538 538  
539 539  
530 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
540 540  
541 -== 3.7 ThingsBoard.Cloud (via COAP) ==
532 +=== 3.7.1 Create device & Get Credentials ===
542 542  
543 -=== 3.7.1 Configure ThingsBoard ===
544 544  
545 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
546 -
547 -
548 -(% style="color:blue" %)**Uplink Converter**
549 -
550 -The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
551 -
552 -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" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
553 -
554 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
555 -
556 -
557 -(% style="color:blue" %)**Downlink Converter**
558 -
559 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
560 -
561 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
562 -
563 -
564 -==== 3.7.1.2 COAP Integration Setup ====
565 -
566 -
567 -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" %)**“CoAP Integration”**(%%), select type **COAP  **(% style="color:blue" %);
568 -
569 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
570 -
571 -
572 -The next steps is to add the recently created uplink converters;
573 -
574 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
575 -
576 -
577 -==== 3.7.1.3 Add COAP Integration ====
578 -
579 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
580 -
581 -
582 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
583 -
584 -==== 3.7.2.1 Instruction Description ====
585 -
586 -* AT+SERVADDR=COAP Server Address,5683
587 -
588 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
589 -
590 -Note:The port for the COAP protocol has been fixed to 5683
591 -
592 -AT+URL1=11,character length,""
593 -
594 -If the module used is BC660K, only one URL directive needs to be configured, e.g. AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
595 -
596 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
597 -
598 -=== 3.8.1 Create device & Get Credentials ===
599 -
600 -
601 601  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
602 602  
603 603  [[image:image-20230802112413-44.png]]
... ... @@ -646,7 +646,7 @@
646 646  
647 647  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
648 648  
649 -=== 3.8.2 Simulate with MQTT.fx ===
583 +=== 3.7.2 Simulate with MQTT.fx ===
650 650  
651 651  
652 652  [[image:image-20230802112413-52.png]]
... ... @@ -662,7 +662,7 @@
662 662  [[image:image-20230808105329-3.png]]
663 663  
664 664  
665 -=== 3.8.3 tago data ===
599 +=== 3.7.3 tago data ===
666 666  
667 667  
668 668  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -670,7 +670,7 @@
670 670  [[image:image-20230802112413-51.png||height="184" width="696"]]
671 671  
672 672  
673 -== 3.9 TCP Connection ==
607 +== 3.8 TCP Connection ==
674 674  
675 675  
676 676  (% style="color:blue" %)**AT command:**
... ... @@ -691,68 +691,10 @@
691 691  [[image:image-20230807233631-2.png]]
692 692  
693 693  
694 -== 3.10 AWS Connection ==
628 += 4. FAQ =
695 695  
630 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
696 696  
697 -Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
698 -
699 -
700 -
701 -
702 -= 4. MQTT/UDP/TCP downlink =
703 -
704 -== 4.1 MQTT (via MQTT.fx) ==
705 -
706 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
707 -
708 -**1.** Configure node MQTT connection (via MQTT.fx):
709 -
710 -(% style="color:blue" %)**AT command:**
711 -
712 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
713 -
714 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
715 -
716 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
717 -
718 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
719 -
720 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
721 -
722 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
723 -
724 -(% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**
725 -
726 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
727 -
728 -
729 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
730 -
731 -[[image:image-20240418144337-1.png||height="709" width="802"]]
732 -
733 -**3. **The downlink command can be successfully sent only when the downlink port is open.
734 -
735 - The downlink port is opened for about 3 seconds after uplink packets are sent.
736 -
737 - Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
738 -
739 -[[image:image-20240418150435-3.png||height="582" width="659"]]
740 -
741 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
742 -
743 -(% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
744 -
745 -
746 -
747 -
748 -
749 -
750 -
751 -= 5. FAQ =
752 -
753 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
754 -
755 -
756 756  The NB series has the feature for Multi Sampling and one uplink. See one of them
757 757  
758 758  [[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]]
... ... @@ -765,22 +765,20 @@
765 765  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)
766 766  1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
767 767  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
768 -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.
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.
769 769  
770 -== 5.2 Why the uplink JSON format is not standard? ==
771 771  
647 +== 4.2 Why the uplink JSON format is not standard? ==
772 772  
773 773  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.
774 774  
775 -The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
776 -
777 777  [[image:image-20240229233154-1.png]]
778 778  
779 779  
780 -= 6. Trouble Shooting: =
781 781  
782 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
655 += 5. Trouble Shooting: =
783 783  
657 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
784 784  
785 785  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.
786 786  
... ... @@ -806,9 +806,8 @@
806 806  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.
807 807  
808 808  
809 -== 6.2 Issue: "NBIOT did not respond" ==
683 +== 5.2 Issue: "NBIOT did not respond" ==
810 810  
811 -
812 812  (% class="box errormessage" %)
813 813  (((
814 814  11:24:22.397 [44596]NBIOT did not respond.
... ... @@ -834,9 +834,8 @@
834 834  [[image:image-20240208001740-1.png]]
835 835  
836 836  
837 -== 6.3 Issue: "Failed to readI MSI number" ==
710 +== 5.3 Issue: "Failed to readI MSI number" ==
838 838  
839 -
840 840  (% class="box errormessage" %)
841 841  (((
842 842  [18170]Failed to read IMSI:1umber.
... ... @@ -848,76 +848,11 @@
848 848  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"]].
849 849  
850 850  
851 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
723 +== 5.4 Why sometime the AT Command is slow in reponse? ==
852 852  
853 -
854 854  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.
855 855  
856 856  [[image:image-20240226111928-1.png]]
857 857  
858 858  
859 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
860 -
861 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
862 -=== UDP: ===
863 -
864 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
865 -Its downlink command is the same as the AT command, but brackets are required.
866 -Example:
867 -
868 -{AT+TDC=300}
869 -
870 -
871 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
872 -=== MQTT: ===
873 -
874 -Json：
875 -
876 -The Json format in MQTT mode needs to be configured with all commands.
877 -If you have configurations that need to be changed, please change them in the template below.
878 -Template:
879 -
880 -{
881 -"AT+SERVADDR":"119.91.62.30,1882",
882 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
883 -"AT+UNAME":"usenamedragino",
884 -"AT+PWD":"passworddragino",
885 -"AT+PUBTOPIC":"123",
886 -"AT+SUBTOPIC":"321",
887 -"AT+TDC":"7200",
888 -"AT+INTMOD":"0",
889 -"AT+APN":"NULL",
890 -"AT+5VT":"0",
891 -"AT+PRO":"3,5",
892 -"AT+TR":"900",
893 -"AT+NOUD":"0",
894 -"AT+CSQTIME":"5",
895 -"AT+DNSTIMER":"0",
896 -"AT+TLSMOD":"0,0",
897 -"AT+MQOS":"0",
898 -"AT+TEMPALARM1":"0",
899 -"AT+TEMPALARM2":"10",
900 -"AT+TEMPALARM3":"0"
901 -}
902 -
903 -Hex：
904 -
905 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
906 -
907 -The supported commands are consistent with LoRaWAN's hex commands.
908 -Please refer to the following link to obtain the hex format:
909 -
910 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
911 -
912 -
913 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
914 -
915 -* **AT Command: AT** **+GETLOG**
916 -
917 -This command can be used to query upstream logs of data packets.
918 -
919 -[[image:image-20240701114700-1.png]]
920 -
921 -
922 -
923 923  
image-20240417173549-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -70.3 KB
Content
image-20240417180145-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -59.7 KB
Content
image-20240418144337-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -103.4 KB
Content
image-20240701114700-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -166.8 KB
Content
image-20240729172234-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -57.8 KB
Content
image-20240729172305-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20240729172415-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -54.3 KB
Content