Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 229.14
edited by Mengting Qiu
on 2025/06/16 09:19
Change comment: There is no comment for this version
To version 230.3
edited by Xiaoling
on 2025/06/17 15:11
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  
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.**
1057 1057  
1058 -The Json format in MQTT mode needs to be configured with all commands.
1059 -If you have configurations that need to be changed, please change them in the template below.
1061 +[[image:1750035004731-376.png||height="276" width="557"]]
1062 +
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,27 +1082,18 @@
1082 1082  "AT+TEMPALARM3":"0"
1083 1083  }
1084 1084  
1085 -Hex：
1092 +**Instructions for Using the Template:**
1086 1086  
1087 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1094 +1. Modify the parameters for each AT command in the template as needed.
1095 +1. Send the entire template in one downlink command.
1088 1088  
1089 -The supported commands are consistent with LoRaWAN's hex commands.
1090 -Please refer to the following link to obtain the hex format:
1091 -
1092 -[[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/]]
1093 -
1094 -
1095 1095  (% style="color:red" %)**Note:**
1096 1096  
1097 -(% 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.
1098 1098  
1099 -(% 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.**
1100 1100  
1101 -(% 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.**
1102 1102  
1103 -[[image:1750035004731-376.png||height="276" width="557"]]
1104 -
1105 -
1106 1106  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1107 1107  
1108 1108  
... ... @@ -1163,30 +1163,26 @@
1163 1163  
1164 1164  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:
1165 1165  
1166 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1167 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1168 -**Firmware version**
1169 -
1170 -**(without FDR1 function)**
1171 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1172 -**Firmware version**
1173 -
1174 -**(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)**
1175 1175  )))
1176 -|(% style="width:210px" %)(((
1170 +|(% style="width:306px" %)(((
1177 1177  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;
1178 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1179 -|(% 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" %)(((
1180 1180  WL03A-NB, SDI-12-NB;
1181 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1175 +)))|(% style="width:311px" %)Before V1.0.2|(% style="width:289px" %)(((
1182 1182  After V1.0.8 (including V1.0.2)
1183 1183  )))
1184 -|(% style="width:210px" %)(((
1178 +|(% style="width:306px" %)(((
1185 1185  SW3L-NB, PS-NB;
1186 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1180 +)))|(% style="width:311px" %)Before V1.0.5|(% style="width:289px" %)(((
1187 1187  After V1.0.5 (including V1.0.5)
1188 1188  )))
1189 -|(% 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)
1190 1190  
1191 1191  === UART connection and firmware update methods ===
1192 1192