Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 229.16
edited by Mengting Qiu
on 2025/06/16 09:25
Change comment: There is no comment for this version
To version 200.1
edited by Mengting Qiu
on 2024/11/26 18:49
Change comment: Uploaded new attachment "image-20241126184906-14.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -46,8 +46,8 @@
46 46  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 47  
48 48  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
49 -|(% style="background-color:#4f81bd; color:white; width:152px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:169px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:427px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
50 -|(% style="width:152px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:169px" %)iot.1nce.net/xxx|(% style="width:427px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
49 +|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+QCGDEFCONT=**|(% style="background-color:#4f81bd; color:white; width:474px" %)**Command Explanation**|(% style="background-color:#4f81bd; color:white; width:135px" %)**Comments**
50 +|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]/[[NB card purchased by the customer>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net/xxx|(% style="width:474px" %)This command sets the PSD connection settings for PDN connection on power-up. When the MT attaches to the NB-IoT network on power-on, a PDN connection setup is performed. Therefore, PDN connection settings are stored in NVRAM so that they can be used by the modem during the attachment.|(% style="width:135px" %)
51 51  
52 52  == 2.2 Speed Up Network Attach time ==
53 53  
... ... @@ -513,6 +513,7 @@
513 513  
514 514  === 3.6.2 Simulate with MQTT.fx ===
515 515  
516 +
516 516  [[image:image-20230802112413-39.png]]
517 517  
518 518  [[image:image-20230802112413-40.png||height="525" width="980"]]
... ... @@ -583,8 +583,7 @@
583 583  ==== 3.7.1.3 Add COAP Integration ====
584 584  
585 585  
586 -(% class="wikigeneratedid" id="H" %)
587 -[[image:image-20240729161543-9.png||height="500" width="1009"]]
587 +==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
588 588  
589 589  
590 590  === 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
... ... @@ -602,17 +602,26 @@
602 602  Note:The port for the COAP protocol has been fixed to 5683
603 603  
604 604  
605 -* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
605 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
606 606  
607 --NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
607 +If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
608 608  
609 609  e.g.
610 610  
611 -* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
611 +* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 612  
613 613  [[image:image-20240729172415-13.png||height="401" width="694"]]
614 614  
615 +If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
615 615  
617 +e.g.
618 +
619 +* AT+URL1=11, "i"
620 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
621 +
622 +[[image:image-20240729172500-14.png||height="403" width="700"]]
623 +
624 +
616 616  == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
617 617  
618 618  === 3.8.1 Create device & Get Credentials ===
... ... @@ -717,152 +717,6 @@
717 717  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]]
718 718  
719 719  
720 -== 3.11 ThingsEye (via MQTT) ==
721 -
722 -=== 3.11.1 Configure ThingsEye ===
723 -
724 -==== 3.11.1.1 Create MQTT integration ====
725 -
726 -
727 -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_NB”**(%%), select type (% style="color:blue" %)**MQTT**;
728 -
729 -[[image:image-20241126175509-1.png||height="518" width="1081"]]
730 -
731 -
732 -Next, directly select to create a new Uplink data converter and downlink data converter.
733 -
734 -[[image:image-20241126180135-2.png||height="535" width="1092"]]
735 -
736 -[[image:image-20241126180223-3.png||height="518" width="1093"]]
737 -
738 -
739 -(% style="color:blue" %)**Add a topic filter:**
740 -
741 -Consistent with the theme of the node setting.
742 -
743 -(% style="color:red" %)**Note: Recommended MQTT broker: lns1.thingseye.io 8883, fixed use. Topic can be changed on their own, but it need to be consistent with the node's publish and subscribe topic.**
744 -
745 -You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
746 -
747 -[[image:image-20241126181024-4.png||height="521" width="1081"]]
748 -
749 -
750 -==== 3.11.1.2 Add credentials to the MQTT integration ====
751 -
752 -
753 -Click on the MQTT integration you just created.
754 -
755 -[[image:image-20241126181837-5.png||height="365" width="1079"]]
756 -
757 -
758 -Click the edit icon in the upper right corner to enter the edit mode.
759 -
760 -[[image:image-20241126184523-13.png||height="330" width="1075"]]
761 -
762 -
763 -(% style="color:blue" %)**Add credential files.**
764 -
765 -Click this [[link>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]] to download the certificates.
766 -
767 -[[image:image-20241126183032-8.png||height="757" width="976"]]
768 -
769 -When the addition is complete, save the Settings.
770 -
771 -[[image:image-20241126184303-12.png||height="284" width="975"]]
772 -
773 -[[image:image-20241126184211-11.png||height="161" width="977"]]
774 -
775 -
776 -==== 3.11.1.3 Setup uplink and downlink converters ====
777 -
778 -
779 -First, you need to download the [[**MQTT uplink/downlink JS** **code**>>https://www.dropbox.com/scl/fo/d5s1wf36f4syv30a8laup/AK8FjVpNXYXCWodRnnQ1Hig?rlkey=jrz1ip0f0xwwq5z2m2gu1tuij&e=1&st=kl4caub0&dl=0]].
780 -
781 -* (% style="color:blue" %)**Uplink Converter**
782 -
783 -The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
784 -
785 -Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT uplink converter that was newly created when the integration was created.
786 -
787 -[[image:image-20241126184906-14.png||height="424" width="1100"]]
788 -
789 -Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
790 -
791 -[[image:image-20241126190131-15.png||height="542" width="1103"]]
792 -
793 -
794 -* (% style="color:blue" %)**Downlink Converter**
795 -
796 -Go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page, and find that MQTT downlink converter that was newly created when the integration was created.
797 -
798 -[[image:image-20241126190251-16.png||height="372" width="1113"]]
799 -
800 -Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
801 -
802 -[[image:image-20241126190737-17.png||height="527" width="1114"]]
803 -
804 -
805 -=== 3.11.2 Simulate with MQTT.fx ===
806 -
807 -
808 -[[image:image-20241126191118-18.png||height="605" width="835"]]
809 -
810 -[[image:image-20241126193252-25.png||height="663" width="803"]]
811 -
812 -
813 -=== 3.11.3 Configure -NB node ===
814 -
815 -
816 -First you need to configure the certificate to the -NB node. Follow the instructions in this **[[link>>https://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H4.1.2Configurecertificate]]** to configure the certificate.
817 -
818 -Screenshot of successful certificate configuration:
819 -
820 -* Configuring the CA Certificate
821 -
822 -[[image:image-20241126192009-19.png||height="431" width="697"]]
823 -
824 -[[image:image-20241126192130-21.png||height="426" width="694"]]
825 -
826 -* Configure client certificate
827 -
828 -[[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
829 -
830 -* Configure client private key
831 -
832 -[[image:image-20241126192415-24.png||height="435" width="737"]]
833 -
834 -
835 -When the certificate is configured, burn the boot program, burn the working firmware, and then restart the device.
836 -
837 -Then configure the -NB node to connect to the ThingsEye platform:
838 -
839 -(% style="color:blue" %)**AT Commands**
840 -
841 -* (% style="color:#037691" %)**AT+PRO=3,5  **(%%)** **~/~/ Use MQTT Connection & Json Payload
842 -* (% style="color:#037691" %)**AT+SERVADDR=lns1.thingseye.io,8883**
843 -* (% style="color:#037691" %)**AT+SUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
844 -* (% style="color:#037691" %)**AT+PUBTOPIC=8899     **(%%)~/~/ Consistent with the Topic of MQTT integration created by ThingsEye
845 -* (% style="color:#037691" %)**AT+CLIENT=NULL**
846 -* (% style="color:#037691" %)**AT+UNAME=NULL**
847 -* (% style="color:#037691" %)**AT+PWD=NULL**
848 -* (% style="color:#037691" %)**AT+TLSMOD=1,2**
849 -
850 -Test Uplink by click the button for 1~~3 seconds, the MQTT integration in ThingsEye allows you to view the data upstream from the device:
851 -
852 -[[image:image-20241126193458-26.png||height="375" width="1012"]]
853 -
854 -[[image:image-20241126193609-27.png||height="424" width="1014"]]
855 -
856 -
857 -Go to (% style="color:blue" %)**"Device" **(%%) -> (% style="color:blue" %)** "Search Device"**(%%), enter the (% style="color:blue" %)** IMEI**(%%) of the device to find the device.
858 -
859 -[[image:image-20241126194018-28.png||height="318" width="1076"]]
860 -
861 -You can view the data that has just been uplink on the device:
862 -
863 -[[image:image-20241126194123-29.png||height="486" width="1073"]]
864 -
865 -
866 866  = 4. MQTT/UDP/TCP downlink =
867 867  
868 868  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -923,8 +923,8 @@
923 923  1. Give more sampling data points.
924 924  1. Increase reliable in transmission. For example. If user set
925 925  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)
926 -1*. **AT+NOUD=24**  ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
927 -1*. **AT+TDC=7200**  ~/~/  Uplink every 2 hours.
789 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
790 +1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
928 928  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.
929 929  
930 930  == 5.2 Why the uplink JSON format is not standard? ==
... ... @@ -937,14 +937,6 @@
937 937  [[image:image-20240229233154-1.png]]
938 938  
939 939  
940 -== 5.3 What is the data consumption for different transfer mode？ ==
941 -
942 -
943 -For the data consumption of NB-IoT End node in different transfer mode, reference link:
944 -
945 -[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20~~-~~-%20NBCB/>>https://wiki.dragino.com/xwiki/bin/view/Main/Traffic%20Statistics%20--%20NBCB/]]
946 -
947 -
948 948  = 6. Trouble Shooting: =
949 949  
950 950  == 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
... ... @@ -1024,39 +1024,25 @@
1024 1024  [[image:image-20240226111928-1.png]]
1025 1025  
1026 1026  
1027 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
882 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1028 1028  
1029 -
1030 -Firstly, it is recommended that users upgrade the firmware of the -NB node to the latest version, as the processing method for downlink commands varies depending on the firmware version. Below, we will introduce the latest downlink command format.
1031 -
1032 1032  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1033 -=== **UDP Protocol:** ===
885 +=== UDP: ===
1034 1034  
1035 -Only supports valid **HEX-format downlink commands** corresponding to AT command.
887 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
888 +Its downlink command is the same as the AT command, but brackets are required.
889 +Example:
1036 1036  
1037 -Take the AT+TDC command of S31-NB as an example, that is, only the valid HEX format downstream command corresponding to the AT+TDC command can be used:
1038 -Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
891 +{AT+TDC=300}
1039 1039  
1040 -[[image:1750035991532-434.png||height="237" width="495"]]
1041 1041  
1042 -
1043 1043  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1044 -=== **MQTT Protocol:** ===
895 +=== MQTT: ===
1045 1045  
1046 -Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
897 +Json：
1047 1047  
1048 -//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1049 -
1050 -* HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1051 -* JSON format: (% style="color:blue" %)**{AT+TDC=900}  **(%%)~/~/ The correct format is (% style="color:blue" %)**{AT Command}**(%%). No extra characters other than valid AT commands can be added within {}.
1052 -
1053 -
1054 -
1055 -**Template for Batch Configuration:**
1056 -
1057 -We can also use templates to configure multiple commands AT once. Users only need to modify the parameters of the required AT commands in the correct template for each device.
1058 -
1059 -
899 +The Json format in MQTT mode needs to be configured with all commands.
900 +If you have configurations that need to be changed, please change them in the template below.
1060 1060  Template:
1061 1061  
1062 1062  {
... ... @@ -1082,62 +1082,26 @@
1082 1082  "AT+TEMPALARM3":"0"
1083 1083  }
1084 1084  
1085 -**Instructions for Using the Template:**
926 +Hex：
1086 1086  
1087 -1. Modify the parameters for each AT command in the template as needed.
1088 -1. Send the entire template in one downlink command.
928 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1089 1089  
930 +The supported commands are consistent with LoRaWAN's hex commands.
931 +Please refer to the following link to obtain the hex format:
1090 1090  
933 +[[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/]]
1091 1091  
1092 -(% style="color:red" %)**Note:**
1093 1093  
1094 -(% style="color:red" %)**1. Only when the correct and valid download command is used and the format is correct can the device be configured through the download command. Invalid download content cannot be processed by the device and will be automatically restarted.**
936 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1095 1095  
1096 -(% style="color:red" %)**2. Devices designed with downlink commands can utilize different downlink formats (e.g., JSON or HEX) for configuration. However, regardless of the format, the functionality is strictly limited to the downlink command specifications described in the user manual's AT command explanation.**
1097 1097  
1098 -(% style="color:red" %)**For example, the HEX-format downlink command corresponding to AT+TDC can only be used to configure TDC and cannot be used for queries. There is no HEX-format downlink command equivalent to AT+TDC=? , so querying TDC via downlink is not supported.**
939 +* **AT Command: AT** **+GETLOG**
1099 1099  
1100 -[[image:1750035004731-376.png||height="276" width="557"]]
941 +This command can be used to query upstream logs of data packets.
1101 1101  
943 +[[image:image-20240701114700-1.png]]
1102 1102  
1103 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1104 1104  
1105 -
1106 -If user is not able to solve the connection issue, user can use below method and get the device log and send to Dragino (Support@dragino.cc) for further analyze.
1107 -
1108 -
1109 -(% class="lead" %)
1110 -Step1: Use Mobile Phone to connect device
1111 -
1112 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1113 -
1114 -
1115 -(% class="lead" %)
1116 -Step2: Get Log by different commands.
1117 -
1118 -Use below three method to generate logs.
1119 -
1120 -* **AT+CFG       ~-~-> Command to show the current configuration**
1121 -* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1122 -* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1123 -
1124 -Above are the output example for about three action:
1125 -
1126 -[[image:image-20250121235119-1.png||height="493" width="455"]]
1127 -
1128 -[[image:image-20240207002129-2.png]]
1129 -
1130 -
1131 -(% class="lead" %)
1132 -Step3: Export Log
1133 -
1134 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155425-16.png?width=330&height=85&rev=1.1||alt="image-20241230155425-16.png" height="85" width="330"]]
1135 -
1136 -select the log you want to export, then click the share icon on the far right to enter the document that comes with your phone and choose to export it.
1137 -
1138 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/image-20241230155528-17.png?width=327&height=324&rev=1.1||alt="image-20241230155528-17.png" height="324" width="327"]]
1139 -
1140 -
1141 1141  == 6.7 How to find the AT Command Password if lost? ==
1142 1142  
1143 1143  
... ... @@ -1157,7 +1157,6 @@
1157 1157  
1158 1158  === Version Confirmation ===
1159 1159  
1160 -
1161 1161  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:
1162 1162  
1163 1163  (% border="1" style="background-color:#f2f2f2; width:510px" %)
... ... @@ -1228,6 +1228,7 @@
1228 1228  [[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"]]
1229 1229  
1230 1230  
1035 +
1231 1231  === Special case ===
1232 1232  
1233 1233  
... ... @@ -1235,6 +1235,7 @@
1235 1235  
1236 1236  Invalid query screenshot example:
1237 1237  
1043 +
1238 1238  [[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"]]
1239 1239  
1240 1240  [[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"]]
1750035004731-376.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -55.1 KB
Content
1750035991532-434.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.4 KB
Content
image-20241126190131-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -267.9 KB
Content
image-20241126190251-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -94.2 KB
Content
image-20241126190737-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -253.7 KB
Content
image-20241126191118-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -61.4 KB
Content
image-20241126192009-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -113.6 KB
Content
image-20241126192122-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -105.2 KB
Content
image-20241126192130-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -105.2 KB
Content
image-20241126192246-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -87.7 KB
Content
image-20241126192315-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -99.0 KB
Content
image-20241126192415-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -88.2 KB
Content
image-20241126193252-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -64.2 KB
Content
image-20241126193458-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -144.3 KB
Content
image-20241126193609-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -167.5 KB
Content
image-20241126194018-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -63.5 KB
Content
image-20241126194123-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -126.7 KB
Content
image-20250121235119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -145.4 KB
Content