Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 181.1
edited by Mengting Qiu
on 2024/08/28 14:37
Change comment: There is no comment for this version
To version 157.1
edited by Mengting Qiu
on 2024/04/18 14:47
Change comment: Uploaded new attachment "image-20240418144714-2.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -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  
... ... @@ -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  
... ... @@ -284,7 +284,6 @@
284 284  
285 285  ==== 3.4.1.1 Create Device ====
286 286  
287 -
288 288  (% style="color:blue" %)**Add Device**(%%) in DataCake.
289 289  
290 290  [[image:image-20230808162301-1.png||height="453" width="952"]]
... ... @@ -355,11 +355,8 @@
355 355  
356 356  **Step6: Please add the decoder at the payload decoder of the device configuration.**
357 357  
358 -**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]]
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]]
359 359  
360 -**Due to version update, please use the following decoder for the new version firmware:**
361 -[[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]
362 -
363 363  [[image:image-20240129172056-7.png||height="457" width="816"]]
364 364  
365 365  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -541,88 +541,11 @@
541 541  [[image:image-20230802112413-43.png||height="407" width="825"]]
542 542  
543 543  
544 -== 3.7 ThingsBoard.Cloud (via COAP) ==
539 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
545 545  
546 -=== 3.7.1 Configure ThingsBoard ===
541 +=== 3.7.1 Create device & Get Credentials ===
547 547  
548 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
549 549  
550 -
551 -(% style="color:blue" %)**Uplink Converter**
552 -
553 -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.
554 -
555 -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.
556 -
557 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
558 -
559 -
560 -(% style="color:blue" %)**Downlink Converter**
561 -
562 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
563 -
564 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
565 -
566 -
567 -==== 3.7.1.2 COAP Integration Setup ====
568 -
569 -
570 -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" %);
571 -
572 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
573 -
574 -
575 -The next steps is to add the recently created uplink converters;
576 -
577 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
578 -
579 -
580 -==== 3.7.1.3 Add COAP Integration ====
581 -
582 -
583 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
584 -
585 -
586 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
587 -
588 -==== 3.7.2.1 Instruction Description ====
589 -
590 -
591 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
592 -* AT+SERVADDR=COAP Server Address,5683
593 -
594 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
595 -
596 -[[image:image-20240729172305-12.png||height="361" width="624"]]
597 -
598 -Note:The port for the COAP protocol has been fixed to 5683
599 -
600 -
601 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
602 -
603 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
604 -
605 -e.g.
606 -
607 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
608 -
609 -[[image:image-20240729172415-13.png||height="401" width="694"]]
610 -
611 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
612 -
613 -e.g.
614 -
615 -* AT+URL1=11, "i";  
616 -* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
617 -
618 -[[image:image-20240729172500-14.png||height="403" width="700"]]
619 -
620 -
621 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
622 -
623 -=== 3.8.1 Create device & Get Credentials ===
624 -
625 -
626 626  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.
627 627  
628 628  [[image:image-20230802112413-44.png]]
... ... @@ -671,7 +671,7 @@
671 671  
672 672  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
673 673  
674 -=== 3.8.2 Simulate with MQTT.fx ===
592 +=== 3.7.2 Simulate with MQTT.fx ===
675 675  
676 676  
677 677  [[image:image-20230802112413-52.png]]
... ... @@ -687,7 +687,7 @@
687 687  [[image:image-20230808105329-3.png]]
688 688  
689 689  
690 -=== 3.8.3 tago data ===
608 +=== 3.7.3 tago data ===
691 691  
692 692  
693 693  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -695,7 +695,7 @@
695 695  [[image:image-20230802112413-51.png||height="184" width="696"]]
696 696  
697 697  
698 -== 3.9 TCP Connection ==
616 +== 3.8 TCP Connection ==
699 699  
700 700  
701 701  (% style="color:blue" %)**AT command:**
... ... @@ -716,24 +716,19 @@
716 716  [[image:image-20230807233631-2.png]]
717 717  
718 718  
719 -== 3.10 AWS Connection ==
720 720  
721 721  
722 -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]]
723 -
724 -
725 725  = 4. MQTT/UDP/TCP downlink =
726 726  
727 727  == 4.1 MQTT (via MQTT.fx) ==
728 728  
729 -
730 730  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
731 731  
732 -**1.** Configure node MQTT connection (via MQTT.fx):
645 +**1.** **Configure node MQTT connection (via MQTT.fx):**
733 733  
734 734  (% style="color:blue" %)**AT command:**
735 735  
736 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
649 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
737 737  
738 738  * (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
739 739  
... ... @@ -743,30 +743,19 @@
743 743  
744 744  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
745 745  
746 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
659 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) **~/~/ to set MQTT server address and port**
747 747  
748 748  (% 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.**
749 749  
750 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
663 +[[image:image-20240417180145-2.png||height="545" width="737"]]
751 751  
665 +[[image:image-20240417180737-3.png||height="544" width="738"]]
752 752  
753 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
754 754  
755 -[[image:image-20240418144337-1.png||height="709" width="802"]]
756 756  
757 -**3. **The downlink command can be successfully sent only when the downlink port is open.
758 758  
759 - The downlink port is opened for about 3 seconds after uplink packets are sent.
760 760  
761 - 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.
762 762  
763 -[[image:image-20240418150435-3.png||height="582" width="659"]]
764 -
765 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
766 -
767 -(% 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.**
768 -
769 -
770 770  = 5. FAQ =
771 771  
772 772  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -867,182 +867,9 @@
867 867  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"]].
868 868  
869 869  
870 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
772 +== 6.4 Why sometime the AT Command is slow in reponse? ==
871 871  
872 872  
873 873  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.
874 874  
875 875  [[image:image-20240226111928-1.png]]
876 -
877 -
878 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
879 -
880 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
881 -=== UDP: ===
882 -
883 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
884 -Its downlink command is the same as the AT command, but brackets are required.
885 -Example:
886 -
887 -{AT+TDC=300}
888 -
889 -
890 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
891 -=== MQTT: ===
892 -
893 -Json：
894 -
895 -The Json format in MQTT mode needs to be configured with all commands.
896 -If you have configurations that need to be changed, please change them in the template below.
897 -Template:
898 -
899 -{
900 -"AT+SERVADDR":"119.91.62.30,1882",
901 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
902 -"AT+UNAME":"usenamedragino",
903 -"AT+PWD":"passworddragino",
904 -"AT+PUBTOPIC":"123",
905 -"AT+SUBTOPIC":"321",
906 -"AT+TDC":"7200",
907 -"AT+INTMOD":"0",
908 -"AT+APN":"NULL",
909 -"AT+5VT":"0",
910 -"AT+PRO":"3,5",
911 -"AT+TR":"900",
912 -"AT+NOUD":"0",
913 -"AT+CSQTIME":"5",
914 -"AT+DNSTIMER":"0",
915 -"AT+TLSMOD":"0,0",
916 -"AT+MQOS":"0",
917 -"AT+TEMPALARM1":"0",
918 -"AT+TEMPALARM2":"10",
919 -"AT+TEMPALARM3":"0"
920 -}
921 -
922 -Hex：
923 -
924 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
925 -
926 -The supported commands are consistent with LoRaWAN's hex commands.
927 -Please refer to the following link to obtain the hex format:
928 -
929 -[[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/]]
930 -
931 -
932 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
933 -
934 -
935 -* **AT Command: AT** **+GETLOG**
936 -
937 -This command can be used to query upstream logs of data packets.
938 -
939 -[[image:image-20240701114700-1.png]]
940 -
941 -
942 -== 6.7 How to find the AT Command Password if lost? ==
943 -
944 -
945 -== 6.7.1. Why can't the password access AT command after upgrade(-NB)? ==
946 -
947 -
948 -Because the new version of -NB firmware has updated the factory reset function, users can choose to restore all parameters to factory Settings, or keep the password to restore the rest of the parameters to factory Settings.
949 -
950 -This update changes the password address of the firmware, so the password will be invalid after the customer upgrades from the old version of firmware (without FDR1 function) to the new version of firmware (with FDR1 function).
951 -
952 -Two different restore factory Settings configurations.
953 -
954 -(% style="color:blue" %)**AT command:**
955 -
956 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
957 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
958 -
959 -== 6.7.2 Version Confirmation ==
960 -
961 -
962 -We are now dividing the **old firmware**(without FDR1 function) with the **new firmware**(with FDR1 function) by whether it contains FDR1 functionality. Please refer to the table:
963 -
964 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
965 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
966 -**Firmware version**
967 -
968 -**(without FDR1 function)**
969 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
970 -**Firmware version**
971 -
972 -**(with FDR1 function)**
973 -)))
974 -|(% style="width:210px" %)(((
975 -CPL03-NB, S31-NB, SN50V3-NB, TS01-NB, D20-NB, DS03A-NB, DDS04-NB, DDS45-NB, DDS20-NB, DDS75-NB, LDS12-NB, LDS40-NB, LMS01-NB, MDS120-NB,  MDS200-NB, SE01-NB, SPH01-NB;
976 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
977 -|(% style="width:210px" %)(((
978 -WL03A-NB, SDI-12-NB;
979 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
980 -After V1.0.8 (including V1.0.2)
981 -)))
982 -|(% style="width:210px" %)(((
983 -SW3L-NB, PS-NB;
984 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
985 -After V1.0.5 (including V1.0.5)
986 -)))
987 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
988 -
989 -
990 -== 6.7.3 UART connection and firmware update methods ==
991 -
992 -
993 -Users can query passwords only using the UART interface via the STM32CubeProgrammer.
994 -
995 -See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
996 -
997 -update firmware through UART TTL interface :** [[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
998 -
999 -
1000 -== 6.7.4 query the password via STM32CubeProgrammer ==
1001 -
1002 -
1003 -Users can use the password address to query the password through STM32CubeProgrammer.
1004 -
1005 -* The password address for old firmware(without FDR1 function) : **0x08019000**
1006 -* The password address for new firmware(with FDR1 function) : **0x08025D00**
1007 -
1008 -(% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1009 -
1010 -
1011 -**Procedure for querying the password(old firmware):**
1012 -
1013 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1014 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1015 -* Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1016 -* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1017 -
1018 -[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827171901-3.png?width=912&height=528&rev=1.1||alt="image-20240827171901-3.png"]]
1019 -
1020 -
1021 -**Procedure for querying the password(new firmware):**
1022 -
1023 -Refer to [[the old and new firmware division>>http://wiki.dragino.com/xwiki/bin/view/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/#H3.A0VersionConfirmation]] above, and run the firmware first after updating the firmware.
1024 -
1025 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1026 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1027 -* Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1028 -* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1029 -
1030 -[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827180414-1.png?width=910&height=527&rev=1.1||alt="image-20240827180414-1.png"]]
1031 -
1032 -
1033 -
1034 -== 6.7.5. Special case ==
1035 -
1036 -
1037 -If the user has never changed the password manually, the user cannot find the valid password through the above two password addresses. In this case, the valid password is still the original password on the node box label (**AT+PIN**).
1038 -
1039 -Invalid query screenshot example:
1040 -
1041 -
1042 -[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181447-4.png?width=889&height=519&rev=1.1||alt="image-20240827181447-4.png"]]
1043 -
1044 -[[image:http://wiki.dragino.com/xwiki/bin/download/Why%20can%27t%20the%20password%20access%20AT%20command%20after%20upgrade%28-NB%29%3F/WebHome/image-20240827181431-3.png?width=892&height=515&rev=1.1||alt="image-20240827181431-3.png"]]
1045 -
1046 -
1047 -
1048 -
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
image-20240729172500-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -48.6 KB
Content