Last modified by Mengting Qiu on 2025/03/08 11:33
<
From version < 203.2 >
edited by Mengting Qiu
on 2024/11/26 19:09
To version < 172.1 >
edited by kai
on 2024/07/29 16:08
>
Change comment: Uploaded new attachment "image-20240729160802-7.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.kai
Content
... ... @@ -45,10 +45,6 @@
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 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
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 -
52 52  == 2.2 Speed Up Network Attach time ==
53 53  
54 54  
... ... @@ -288,7 +288,6 @@
288 288  
289 289  ==== 3.4.1.1 Create Device ====
290 290  
291 -
292 292  (% style="color:blue" %)**Add Device**(%%) in DataCake.
293 293  
294 294  [[image:image-20230808162301-1.png||height="453" width="952"]]
... ... @@ -359,11 +359,8 @@
359 359  
360 360  **Step6: Please add the decoder at the payload decoder of the device configuration.**
361 361  
362 -**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 +**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]]
363 363  
364 -**Due to version update, please use the following decoder for the new version firmware:**
365 -[[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]]
366 -
367 367  [[image:image-20240129172056-7.png||height="457" width="816"]]
368 368  
369 369  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -545,88 +545,11 @@
545 545  [[image:image-20230802112413-43.png||height="407" width="825"]]
546 546  
547 547  
548 -== 3.7 ThingsBoard.Cloud (via COAP) ==
540 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
549 549  
550 -=== 3.7.1 Configure ThingsBoard ===
542 +=== 3.7.1 Create device & Get Credentials ===
551 551  
552 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
553 553  
554 -
555 -(% style="color:blue" %)**Uplink Converter**
556 -
557 -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.
558 -
559 -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.
560 -
561 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
562 -
563 -
564 -(% style="color:blue" %)**Downlink Converter**
565 -
566 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
567 -
568 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
569 -
570 -
571 -==== 3.7.1.2 COAP Integration Setup ====
572 -
573 -
574 -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" %);
575 -
576 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
577 -
578 -
579 -The next steps is to add the recently created uplink converters;
580 -
581 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
582 -
583 -
584 -==== 3.7.1.3 Add COAP Integration ====
585 -
586 -
587 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
588 -
589 -
590 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
591 -
592 -==== 3.7.2.1 Instruction Description ====
593 -
594 -
595 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
596 -* AT+SERVADDR=COAP Server Address,5683
597 -
598 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
599 -
600 -[[image:image-20240729172305-12.png||height="361" width="624"]]
601 -
602 -Note:The port for the COAP protocol has been fixed to 5683
603 -
604 -
605 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
606 -
607 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
608 -
609 -e.g.
610 -
611 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 -
613 -[[image:image-20240729172415-13.png||height="401" width="694"]]
614 -
615 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
616 -
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 -
625 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
626 -
627 -=== 3.8.1 Create device & Get Credentials ===
628 -
629 -
630 630  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.
631 631  
632 632  [[image:image-20230802112413-44.png]]
... ... @@ -675,7 +675,7 @@
675 675  
676 676  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
677 677  
678 -=== 3.8.2 Simulate with MQTT.fx ===
593 +=== 3.7.2 Simulate with MQTT.fx ===
679 679  
680 680  
681 681  [[image:image-20230802112413-52.png]]
... ... @@ -691,7 +691,7 @@
691 691  [[image:image-20230808105329-3.png]]
692 692  
693 693  
694 -=== 3.8.3 tago data ===
609 +=== 3.7.3 tago data ===
695 695  
696 696  
697 697  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -699,7 +699,7 @@
699 699  [[image:image-20230802112413-51.png||height="184" width="696"]]
700 700  
701 701  
702 -== 3.9 TCP Connection ==
617 +== 3.8 TCP Connection ==
703 703  
704 704  
705 705  (% style="color:blue" %)**AT command:**
... ... @@ -720,143 +720,18 @@
720 720  [[image:image-20230807233631-2.png]]
721 721  
722 722  
723 -== 3.10 AWS Connection ==
638 +== 3.9 AWS Connection ==
724 724  
725 725  
726 726  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]]
727 727  
728 728  
729 -== 3.11 ThingsEye (via MQTT) ==
730 730  
731 -(% class="wikigeneratedid" %)
732 -=== 3.11.1 Configure ThingsEye ===
733 733  
734 -
735 -==== 3.11.1.1 Create MQTT integration ====
736 -
737 -
738 -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**;
739 -
740 -
741 -[[image:image-20241126175509-1.png||height="518" width="1081"]]
742 -
743 -
744 -Next, directly select to create a new Uplink data converter and downlink data converter.
745 -
746 -[[image:image-20241126180135-2.png||height="535" width="1092"]]
747 -
748 -[[image:image-20241126180223-3.png||height="518" width="1093"]]
749 -
750 -
751 -(% style="color:blue" %)**Add a topic filter:**
752 -
753 -Consistent with the theme of the node setting.
754 -
755 -(% 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.**
756 -
757 -You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
758 -
759 -[[image:image-20241126181024-4.png||height="521" width="1081"]]
760 -
761 -
762 -==== 3.11.1.2 Add credentials to the MQTT integration ====
763 -
764 -
765 -Click on the MQTT integration you just created.
766 -
767 -[[image:image-20241126181837-5.png||height="365" width="1079"]]
768 -
769 -
770 -Click the edit icon in the upper right corner to enter the edit mode.
771 -
772 -[[image:image-20241126184523-13.png||height="330" width="1075"]]
773 -
774 -
775 -(% style="color:blue" %)**Add credential files.**
776 -
777 -Click this link to download the certificates.
778 -
779 -[[image:image-20241126183032-8.png||height="757" width="976"]]
780 -
781 -When the addition is complete, save the Settings.
782 -
783 -[[image:image-20241126184303-12.png||height="284" width="975"]]
784 -
785 -[[image:image-20241126184211-11.png||height="161" width="977"]]
786 -
787 -
788 -==== 3.11.1.2 Setup uplink and downlink converters ====
789 -
790 -
791 -First, you need to download the **MQTT uplink/downlink JS** **code**.
792 -
793 -* (% style="color:blue" %)**Uplink Converter**
794 -
795 -The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume.
796 -
797 -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.
798 -
799 -[[image:image-20241126184906-14.png||height="424" width="1100"]]
800 -
801 -Enter edit mode and apply **MQTT uplink JS code** to this uplink converter.
802 -
803 -[[image:image-20241126190131-15.png||height="542" width="1103"]]
804 -
805 -
806 -* (% style="color:blue" %)**Downlink Converter**
807 -
808 -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.
809 -
810 -[[image:image-20241126190251-16.png||height="372" width="1113"]]
811 -
812 -Enter edit mode and apply **MQTT downlink JS code** to this downlink converter.
813 -
814 -[[image:image-20241126190737-17.png||height="527" width="1114"]]
815 -
816 -
817 -=== 3.6.2 Simulate with MQTT.fx ===
818 -
819 -
820 -[[image:image-20230802112413-39.png]]
821 -
822 -[[image:image-20230802112413-40.png||height="525" width="980"]]
823 -
824 -
825 -=== 3.6.3 Configure NB-IoT Sensor ===
826 -
827 -
828 -(% style="color:blue" %)**AT Commands**
829 -
830 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
831 -
832 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
833 -
834 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
835 -
836 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
837 -
838 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
839 -
840 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
841 -
842 -Test Uplink by click the button for 1 second
843 -
844 -[[image:image-20230802112413-41.png||height="496" width="828"]]
845 -
846 -[[image:image-20230802112413-42.png]]
847 -
848 -[[image:image-20230802112413-43.png||height="407" width="825"]]
849 -
850 -
851 -
852 -
853 -
854 -
855 855  = 4. MQTT/UDP/TCP downlink =
856 856  
857 857  == 4.1 MQTT (via MQTT.fx) ==
858 858  
859 -
860 860  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
861 861  
862 862  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -897,6 +897,11 @@
897 897  (% 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.**
898 898  
899 899  
690 +
691 +
692 +
693 +
694 +
900 900  = 5. FAQ =
901 901  
902 902  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -1059,9 +1059,8 @@
1059 1059  [[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/]]
1060 1060  
1061 1061  
1062 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
857 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
1063 1063  
1064 -
1065 1065  * **AT Command: AT** **+GETLOG**
1066 1066  
1067 1067  This command can be used to query upstream logs of data packets.
... ... @@ -1069,108 +1069,5 @@
1069 1069  [[image:image-20240701114700-1.png]]
1070 1070  
1071 1071  
1072 -== 6.7 How to find the AT Command Password if lost? ==
1073 1073  
1074 -
1075 -=== Why can't the password access AT command after upgrade(-NB)? ===
1076 -
1077 -
1078 -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.
1079 -
1080 -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).
1081 -
1082 -Two different restore factory Settings configurations.
1083 -
1084 -(% style="color:blue" %)**AT command:**
1085 -
1086 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR**(%%)**       **~/~/ Reset Parameters to Factory Default.
1087 -* (% style="color:#037691; font-weight:bold" %)**AT+FDR1**(%%)**     **~/~/ Reset parameters to factory default values except for passwords.(new)
1088 -
1089 -=== Version Confirmation ===
1090 -
1091 -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:
1092 -
1093 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1094 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1095 -**Firmware version**
1096 -
1097 -**(without FDR1 function)**
1098 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1099 -**Firmware version**
1100 -
1101 -**(with FDR1 function)**
1102 -)))
1103 -|(% style="width:210px" %)(((
1104 -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;
1105 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1106 -|(% style="width:210px" %)(((
1107 -WL03A-NB, SDI-12-NB;
1108 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1109 -After V1.0.8 (including V1.0.2)
1110 -)))
1111 -|(% style="width:210px" %)(((
1112 -SW3L-NB, PS-NB;
1113 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1114 -After V1.0.5 (including V1.0.5)
1115 -)))
1116 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1117 -
1118 -=== UART connection and firmware update methods ===
1119 -
1120 -
1121 -Users can query passwords only using the UART interface via the STM32CubeProgrammer.
1122 -
1123 -See **[[UART Connection>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]]**.
1124 -
1125 -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]]**.
1126 -
1127 -
1128 -=== query the password via STM32CubeProgrammer ===
1129 -
1130 -
1131 -Users can use the password address to query the password through STM32CubeProgrammer.
1132 -
1133 -* The password address for old firmware(without FDR1 function) : **0x08019000**
1134 -* The password address for new firmware(with FDR1 function) : **0x08025D00**
1135 -
1136 -(% style="color:red" %)**Notice: The password can only be queried after the firmware is run once.**
1137 -
1138 -
1139 -**Procedure for querying the password(old firmware):**
1140 -
1141 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the firmware once**.
1142 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1143 -* Click "Device memory", enter **0x08019000** in "Address", and click "Read"
1144 -* Find the 0x08019000 address field and then read the current password as shown in the screenshot below.
1145 -
1146 -[[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"]]
1147 -
1148 -
1149 -**Procedure for querying the password(new firmware):**
1150 -
1151 -Refer to [[the old and new firmware division>>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/#HVersionConfirmation]] above, and run the firmware first after updating the firmware.
1152 -
1153 -* After the firmware upgrade is complete, switch back to the **FLASH** and reset the node to **run the new firmware once**.
1154 -* Then place the switch at the **ISP** and connect to the STM32CubeProgrammer (same as when burning the firmware).
1155 -* Click "Device memory", enter **0x08025D00** in "Address", and click "Read"
1156 -* Find the 0x08025D00 address field and then read the current password as shown in the screenshot below.
1157 -
1158 -[[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"]]
1159 -
1160 -
1161 -
1162 -=== Special case ===
1163 -
1164 -
1165 -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**).
1166 -
1167 -Invalid query screenshot example:
1168 -
1169 -
1170 -[[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"]]
1171 -
1172 -[[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"]]
1173 -
1174 -
1175 -
1176 1176  
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
image-20241126175509-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -241.0 KB
Content
image-20241126180135-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -192.8 KB
Content
image-20241126180223-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -213.1 KB
Content
image-20241126181024-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -238.8 KB
Content
image-20241126181837-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
image-20241126182007-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -136.3 KB
Content
image-20241126182135-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20241126183032-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -111.4 KB
Content
image-20241126183803-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20241126184136-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -15.7 KB
Content
image-20241126184211-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20241126184303-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -81.7 KB
Content
image-20241126184523-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -88.7 KB
Content
image-20241126184906-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -108.0 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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0