Last modified by Mengting Qiu on 2025/07/03 18:55

From version 228.6
edited by Mengting Qiu
on 2025/06/16 09:02
Change comment: There is no comment for this version
To version 229.1
edited by Mengting Qiu
on 2025/06/16 09:06
Change comment: Uploaded new attachment "1750035991532-434.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1028,22 +1028,14 @@
1028 1028  
1029 1029  
1030 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 -(% style="color:red" %)**Note:**
1032 1032  
1033 -(% 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.**
1034 -
1035 -(% 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.**
1036 -
1037 -(% 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.**
1038 -
1039 -[[image:1750035004731-376.png||height="346" width="698"]]
1040 -
1041 -
1042 1042  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1043 1043  === **UDP Protocol:** ===
1044 1044  
1045 -Only supports valid **HEX-format downlink commands** corresponding to AT command
1035 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
1046 1046  
1037 +
1038 +
1047 1047  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1048 1048  === MQTT: ===
1049 1049  
... ... @@ -1087,6 +1087,17 @@
1087 1087  [[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/]]
1088 1088  
1089 1089  
1082 +(% style="color:red" %)**Note:**
1083 +
1084 +(% 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.**
1085 +
1086 +(% 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.**
1087 +
1088 +(% 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.**
1089 +
1090 +[[image:1750035004731-376.png||height="276" width="557"]]
1091 +
1092 +
1090 1090  == (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to get the debug log for further analyze?(%%) ==
1091 1091  
1092 1092  
1750035991532-434.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.4 KB
Content