Skip to Content
Last modified by Mengting Qiu on 2025/07/17 10:51
From version 228.7
edited by Mengting Qiu
on 2025/06/16 09:05
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
... ... @@ -1034,14 +1034,36 @@
1034 1034  
1035 1035  Only supports valid **HEX-format downlink commands** corresponding to AT command.
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.
1039 +
1040 +[[image:1750035991532-434.png||height="237" width="495"]]
1041 +
1042 +
1037 1037  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1038 -=== MQTT: ===
1044 +=== **MQTT Protocol:** ===
1039 1039  
1046 +Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1040 1040  
1041 -Json：
1048 +//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1042 1042  
1043 -The Json format in MQTT mode needs to be configured with all commands.
1044 -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.
1045 1045  Template:
1046 1046  
1047 1047  {
... ... @@ -1067,27 +1067,18 @@
1067 1067  "AT+TEMPALARM3":"0"
1068 1068  }
1069 1069  
1070 -Hex：
1092 +**Instructions for Using the Template:**
1071 1071  
1072 -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.
1073 1073  
1074 -The supported commands are consistent with LoRaWAN's hex commands.
1075 -Please refer to the following link to obtain the hex format:
1076 -
1077 -[[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/]]
1078 -
1079 -
1080 1080  (% style="color:red" %)**Note:**
1081 1081  
1082 -(% 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.
1083 1083  
1084 -(% 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.**
1085 1085  
1086 -(% 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.**
1087 1087  
1088 -[[image:1750035004731-376.png||height="276" width="557"]]
1089 -
1090 -
1091 1091  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1092 1092  
1093 1093  
... ... @@ -1148,30 +1148,26 @@
1148 1148  
1149 1149  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:
1150 1150  
1151 -(% border="1" style="background-color:#f2f2f2; width:510px" %)
1152 -|(% style="background-color:#4f81bd; color:white; width:210px" %)**General Model**|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1153 -**Firmware version**
1154 -
1155 -**(without FDR1 function)**
1156 -)))|(% style="background-color:#4f81bd; color:white; width:150px" %)(((
1157 -**Firmware version**
1158 -
1159 -**(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)**
1160 1160  )))
1161 1161  |(% style="width:210px" %)(((
1162 1162  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;
1163 -)))|(% 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)
1164 1164  |(% style="width:210px" %)(((
1165 1165  WL03A-NB, SDI-12-NB;
1166 -)))|(% style="width:150px" %)Before V1.0.2|(% style="width:150px" %)(((
1175 +)))|(% style="width:313px" %)Before V1.0.2|(% style="width:286px" %)(((
1167 1167  After V1.0.8 (including V1.0.2)
1168 1168  )))
1169 1169  |(% style="width:210px" %)(((
1170 1170  SW3L-NB, PS-NB;
1171 -)))|(% style="width:150px" %)Before V1.0.5|(% style="width:150px" %)(((
1180 +)))|(% style="width:313px" %)Before V1.0.5|(% style="width:286px" %)(((
1172 1172  After V1.0.5 (including V1.0.5)
1173 1173  )))
1174 -|(% 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)
1175 1175  
1176 1176  === UART connection and firmware update methods ===
1177 1177  
1750035991532-434.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.4 KB
Content