Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 229.15
edited by Mengting Qiu
on 2025/06/16 09:25
Change comment: There is no comment for this version
To version 231.1
edited by Xiaoling
on 2025/06/17 15:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -1050,13 +1050,20 @@
1050 1050  * HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1051 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 1052  
1053 +(% style="color:red" %)**Note:**
1053 1053  
1055 +(% 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.**
1054 1054  
1055 -**Template for Batch Configuration:**
1057 +(% 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.**
1056 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.
1059 +(% 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.**
1058 1058  
1061 +[[image:1750035004731-376.png||height="276" width="557"]]
1059 1059  
1063 +
1064 +**Template for Batch Configuration:**
1065 +
1066 +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.
1060 1060  Template:
1061 1061  
1062 1062  {
... ... @@ -1082,21 +1082,18 @@
1082 1082  "AT+TEMPALARM3":"0"
1083 1083  }
1084 1084  
1092 +**Instructions for Using the Template:**
1085 1085  
1086 -[[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/]]
1094 +1. Modify the parameters for each AT command in the template as needed.
1095 +1. Send the entire template in one downlink command.
1087 1087  
1088 -
1089 1089  (% style="color:red" %)**Note:**
1090 1090  
1091 -(% 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.**
1099 +* The template may vary depending on the device model.
1100 +* **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.
1092 1092  
1093 -(% 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.**
1094 1094  
1095 -(% 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.**
1096 1096  
1097 -[[image:1750035004731-376.png||height="276" width="557"]]
1098 -
1099 -
1100 1100  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1101 1101  
1102 1102  
... ... @@ -1157,30 +1157,26 @@
1157 1157  
1158 1158  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:
1159 1159  
1160 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1161 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1162 -**Firmware version**
1163 -
1164 -**(without FDR1 function)**
1165 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1166 -**Firmware version**
1167 -
1168 -**(with FDR1 function)**
1164 +(% border="1" style="background-color:#f2f2f2; width:912px" %)
1165 +|(% style="background-color:#4f81bd; color:white; width:306px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:311px" %)(((
1166 +**Firmware version (without FDR1 function)**
1167 +)))|(% style="background-color:#4f81bd; color:white; width:289px" %)(((
1168 +**Firmware version (with FDR1 function)**
1169 1169  )))
1170 -|(% style="width:210px" %)(((
1170 +|(% style="width:306px" %)(((
1171 1171  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;
1172 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1173 -|(% style="width:210px" %)(((
1172 +)))|(% style="width:311px" %)Before V1.2.1|(% style="width:289px" %)After V1.2.1 (including V1.2.1)
1173 +|(% style="width:306px" %)(((
1174 1174  WL03A-NB, SDI-12-NB;
1175 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1175 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1176 1176  After V1.0.8 (including V1.0.2)
1177 1177  )))
1178 -|(% style="width:210px" %)(((
1178 +|(% style="width:306px" %)(((
1179 1179  SW3L-NB, PS-NB;
1180 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1180 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1181 1181  After V1.0.5 (including V1.0.5)
1182 1182  )))
1183 -|(% style="width:210px" %)RS485-NB|(% style="width:150px" %)Before V1.0.8|(% style="width:150px" %)After V1.0.8 (including V1.0.8)
1183 +|(% style="width:306px" %)RS485-NB|(% style="width:311px" %)Before V1.0.8|(% style="width:289px" %)After V1.0.8 (including V1.0.8)
1184 1184  
1185 1185  === UART connection and firmware update methods ===
1186 1186