Skip to Content
Last modified by Kilight Cao on 2025/07/23 16:27
From version 231.7
edited by Mengting Qiu
on 2025/07/03 18:53
Change comment: There is no comment for this version
To version 216.1
edited by Mengting Qiu
on 2024/11/26 19:42
Change comment: There is no comment for this version

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 ===
... ... @@ -721,11 +721,13 @@
721 721  
722 722  === 3.11.1 Configure ThingsEye ===
723 723  
733 +
724 724  ==== 3.11.1.1 Create MQTT integration ====
725 725  
726 726  
727 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 728  
739 +
729 729  [[image:image-20241126175509-1.png||height="518" width="1081"]]
730 730  
731 731  
... ... @@ -762,7 +762,7 @@
762 762  
763 763  (% style="color:blue" %)**Add credential files.**
764 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.
776 +Click this link to download the certificates.
766 766  
767 767  [[image:image-20241126183032-8.png||height="757" width="976"]]
768 768  
... ... @@ -773,10 +773,10 @@
773 773  [[image:image-20241126184211-11.png||height="161" width="977"]]
774 774  
775 775  
776 -==== 3.11.1.3 Setup uplink and downlink converters ====
787 +==== 3.11.1.2 Setup uplink and downlink converters ====
777 777  
778 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]].
790 +First, you need to download the **MQTT uplink/downlink JS** **code**.
780 780  
781 781  * (% style="color:blue" %)**Uplink Converter**
782 782  
... ... @@ -810,7 +810,7 @@
810 810  [[image:image-20241126193252-25.png||height="663" width="803"]]
811 811  
812 812  
813 -=== 3.11.3 Configure -NB node ===
824 +=== 3.6.3 Configure -NB node ===
814 814  
815 815  
816 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.
... ... @@ -819,10 +819,8 @@
819 819  
820 820  * Configuring the CA Certificate
821 821  
822 -[[image:image-20241126192009-19.png||height="431" width="697"]]
833 +[[image:image-20241126192009-19.png||height="431" width="697"]][[image:image-20241126192130-21.png||height="426" width="694"]]
823 823  
824 -[[image:image-20241126192130-21.png||height="426" width="694"]]
825 -
826 826  * Configure client certificate
827 827  
828 828  [[image:image-20241126192246-22.png||height="397" width="693"]][[image:image-20241126192315-23.png||height="402" width="645"]]
... ... @@ -839,14 +839,19 @@
839 839  (% style="color:blue" %)**AT Commands**
840 840  
841 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
851 +
852 +* (% style="color:#037691" %)**AT+SUBTOPIC=8899  **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
853 +
854 +* (% style="color:#037691" %)**AT+PUBTOPIC=8899  **(%%)~/~/Consistent with the Topic of MQTT integration created by ThingsEye
855 +
845 845  * (% style="color:#037691" %)**AT+CLIENT=NULL**
857 +
846 846  * (% style="color:#037691" %)**AT+UNAME=NULL**
859 +
847 847  * (% style="color:#037691" %)**AT+PWD=NULL**
848 -* (% style="color:#037691" %)**AT+TLSMOD=1,2**
849 849  
862 +* (% style="color:#037691" %)**AT+TLSMOD=1,0**
863 +
850 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 851  
852 852  [[image:image-20241126193458-26.png||height="375" width="1012"]]
... ... @@ -863,6 +863,7 @@
863 863  [[image:image-20241126194123-29.png||height="486" width="1073"]]
864 864  
865 865  
880 +
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.
941 +1*. **AT+NOUD=24** ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
942 +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,56 +1024,27 @@
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? ==
1034 +== (% 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:** ===
1037 +=== UDP: ===
1034 1034  
1035 -Only supports valid **HEX-format downlink commands** corresponding to AT command.
1039 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1040 +Its downlink command is the same as the AT command, but brackets are required.
1041 +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.
1043 +{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:** ===
1047 +=== MQTT: ===
1045 1045  
1046 -==== **1. HEX-format** ====
1049 +Json：
1047 1047  
1048 -Supports **HEX-format** downlink commands (corresponding to AT commands).
1051 +The Json format in MQTT mode needs to be configured with all commands.
1052 +If you have configurations that need to be changed, please change them in the template below.
1053 +Template:
1049 1049  
1050 -//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1051 -
1052 -* HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1053 -* 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 {}.
1054 -
1055 -(% style="color:red" %)**Note:**
1056 -
1057 -(% 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.**
1058 -
1059 -(% 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.**
1060 -
1061 -(% 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.**
1062 -
1063 -[[image:1750035004731-376.png||height="276" width="557"]]
1064 -
1065 -
1066 -==== **2. JSON-format ** ====
1067 -
1068 -===== **2. 1 JSON format template.** =====
1069 -
1070 -All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1071 -
1072 -We can 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.
1073 -Template.
1074 -
1075 -Take the template of D2x-CB as an example:
1076 -
1077 1077  {
1078 1078  "AT+SERVADDR":"119.91.62.30,1882",
1079 1079  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1097,73 +1097,26 @@
1097 1097  "AT+TEMPALARM3":"0"
1098 1098  }
1099 1099  
1100 -**Instructions for Using the Template:**
1078 +Hex：
1101 1101  
1102 -1. Modify the parameters for each AT command in the template as needed.
1103 -1. Send the entire template in one downlink command.
1080 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1104 1104  
1105 -(% style="color:red" %)**Note:**
1082 +The supported commands are consistent with LoRaWAN's hex commands.
1083 +Please refer to the following link to obtain the hex format:
1106 1106  
1107 -* The template may vary depending on the device model.
1108 -* **Currently, each specific template is being updated and tested**. If you need a template for your specific device, please contact **Dragino Technical Support** at [[support@dragino.com>>url:https://mailto:support@dragino.com/]] to request the latest downlink template.
1085 +[[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/]]
1109 1109  
1110 1110  
1088 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
1111 1111  
1112 -===== **2.2 Support sending json format commands separately** =====
1113 1113  
1114 -Some models of nodes support sending json format commands separately：(% style="color:blue" %)**J**(%%)**RS485-NB, LDS25-NB, CS01-NB, SDI-12-NB, SW3L-NB, WL03A-NB, PS-NB, LTC2-NB.**
1091 +* **AT Command: AT** **+GETLOG**
1115 1115  
1116 -//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
1093 +This command can be used to query upstream logs of data packets.
1117 1117  
1118 -Downlink command:  (% style="color:blue" %)**J**(%%)**       **~/~/ The correct format is (% style="color:blue" %)**J**(%%) **{AT Command}**. No extra characters other than valid AT commands can be added within {}.
1095 +[[image:image-20240701114700-1.png]]
1119 1119  
1120 -(% style="color:red" %)**Note:**
1121 1121  
1122 -(% 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.**
1123 -
1124 -(% 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.**
1125 -
1126 -(% 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.**
1127 -
1128 -
1129 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1130 -
1131 -
1132 -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.
1133 -
1134 -
1135 -(% class="lead" %)
1136 -Step1: Use Mobile Phone to connect device
1137 -
1138 -See this link: **[[how to connect via Mobile Phone:>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1UseDraginoDeviceTooltoconfigureorupgradefirmware]]**
1139 -
1140 -
1141 -(% class="lead" %)
1142 -Step2: Get Log by different commands.
1143 -
1144 -Use below three method to generate logs.
1145 -
1146 -* **AT+CFG       ~-~-> Command to show the current configuration**
1147 -* **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1148 -* **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1149 -
1150 -Above are the output example for about three action:
1151 -
1152 -[[image:image-20250121235119-1.png||height="493" width="455"]]
1153 -
1154 -[[image:image-20240207002129-2.png]]
1155 -
1156 -
1157 -(% class="lead" %)
1158 -Step3: Export Log
1159 -
1160 -[[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"]]
1161 -
1162 -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.
1163 -
1164 -[[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"]]
1165 -
1166 -
1167 1167  == 6.7 How to find the AT Command Password if lost? ==
1168 1168  
1169 1169  
... ... @@ -1183,29 +1183,32 @@
1183 1183  
1184 1184  === Version Confirmation ===
1185 1185  
1186 -
1187 1187  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:
1188 1188  
1189 -(% border="1" style="background-color:#f2f2f2; width:912px" %)
1190 -|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1191 -**Firmware version (without FDR1 function)**
1192 -)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1193 -**Firmware version (with FDR1 function)**
1119 +(% border="1" style="background-color:#f2f2f2; width:510px" %)
1120 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1121 +**Firmware version**
1122 +
1123 +**(without FDR1 function)**
1124 +)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1125 +**Firmware version**
1126 +
1127 +**(with FDR1 function)**
1194 1194  )))
1195 -|(% style="width:306px" %)(((
1129 +|(% style="width:210px" %)(((
1196 1196  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;
1197 -)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1198 -|(% style="width:306px" %)(((
1131 +)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1132 +|(% style="width:210px" %)(((
1199 1199  WL03A-NB, SDI-12-NB;
1200 -)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1134 +)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1201 1201  After V1.0.8 (including V1.0.2)
1202 1202  )))
1203 -|(% style="width:306px" %)(((
1137 +|(% style="width:210px" %)(((
1204 1204  SW3L-NB, PS-NB;
1205 -)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1139 +)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1206 1206  After V1.0.5 (including V1.0.5)
1207 1207  )))
1208 -|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1142 +|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1209 1209  
1210 1210  === UART connection and firmware update methods ===
1211 1211  
... ... @@ -1250,6 +1250,7 @@
1250 1250  [[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"]]
1251 1251  
1252 1252  
1187 +
1253 1253  === Special case ===
1254 1254  
1255 1255  
... ... @@ -1257,6 +1257,7 @@
1257 1257  
1258 1258  Invalid query screenshot example:
1259 1259  
1195 +
1260 1260  [[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"]]
1261 1261  
1262 1262  [[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"]]
... ... @@ -1263,11 +1263,4 @@
1263 1263  
1264 1264  
1265 1265  
1266 -== 6.8 ==
1267 -
1268 -
1269 -
1270 -
1271 -
1272 -
1273 1273  
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-20250121235119-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -145.4 KB
Content