Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 229.3
edited by Mengting Qiu
on 2025/06/16 09:07
Change comment: There is no comment for this version
To version 230.2
edited by Xiaoling
on 2025/06/17 15:10
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
... ... @@ -1035,19 +1035,35 @@
1035 1035  Only supports valid **HEX-format downlink commands** corresponding to AT command.
1036 1036  
1037 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 -01
1038 +Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1039 1039  
1040 1040  [[image:1750035991532-434.png||height="237" width="495"]]
1041 1041  
1042 1042  
1043 1043  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1044 -=== MQTT: ===
1044 +=== **MQTT Protocol:** ===
1045 1045  
1046 +Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1046 1046  
1047 -Json：
1048 +//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1048 1048  
1049 -The Json format in MQTT mode needs to be configured with all commands.
1050 -If you have configurations that need to be changed, please change them in the template below.
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 +(% style="color:red" %)**Note:**
1054 +
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.**
1056 +
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.**
1058 +
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.**
1060 +
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.
1051 1051  Template:
1052 1052  
1053 1053  {
... ... @@ -1073,27 +1073,18 @@
1073 1073  "AT+TEMPALARM3":"0"
1074 1074  }
1075 1075  
1076 -Hex：
1092 +**Instructions for Using the Template:**
1077 1077  
1078 -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.
1079 1079  
1080 -The supported commands are consistent with LoRaWAN's hex commands.
1081 -Please refer to the following link to obtain the hex format:
1082 -
1083 -[[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/]]
1084 -
1085 -
1086 1086  (% style="color:red" %)**Note:**
1087 1087  
1088 -(% 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.
1089 1089  
1090 -(% 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.**
1091 1091  
1092 -(% 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.**
1093 1093  
1094 -[[image:1750035004731-376.png||height="276" width="557"]]
1095 -
1096 -
1097 1097  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1098 1098  
1099 1099  
... ... @@ -1154,30 +1154,26 @@
1154 1154  
1155 1155  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:
1156 1156  
1157 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1158 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1159 -**Firmware version**
1160 -
1161 -**(without FDR1 function)**
1162 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1163 -**Firmware version**
1164 -
1165 -**(with FDR1 function)**
1164 +(% border="1" style="background-color:#f2f2f2; width:814px" %)
1165 +|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:313px" %)(((
1166 +**Firmware version (without FDR1 function)**
1167 +)))|(% style="background-color:#4f81bd; color:white; width:286px" %)(((
1168 +**Firmware version (with FDR1 function)**
1166 1166  )))
1167 1167  |(% style="width:210px" %)(((
1168 1168  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;
1169 -)))|(% style="width:150px" %)Before V1.2.1|(% style="width:150px" %)After V1.2.1 (including V1.2.1)
1172 +)))|(% style="width:313px" %)Before V1.2.1|(% style="width:286px" %)After V1.2.1 (including V1.2.1)
1170 1170  |(% style="width:210px" %)(((
1171 1171  WL03A-NB, SDI-12-NB;
1172 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1175 +)))|(% style="width:313px" %)Before V1.0.2|(% style="width:286px" %)(((
1173 1173  After V1.0.8 (including V1.0.2)
1174 1174  )))
1175 1175  |(% style="width:210px" %)(((
1176 1176  SW3L-NB, PS-NB;
1177 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1180 +)))|(% style="width:313px" %)Before V1.0.5|(% style="width:286px" %)(((
1178 1178  After V1.0.5 (including V1.0.5)
1179 1179  )))
1180 -|(% 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:210px" %)RS485-NB|(% style="width:313px" %)Before V1.0.8|(% style="width:286px" %)After V1.0.8 (including V1.0.8)
1181 1181  
1182 1182  === UART connection and firmware update methods ===
1183 1183