Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:49
From version 144.13
edited by Mengting Qiu
on 2025/07/03 18:43
Change comment: There is no comment for this version
To version 145.1
edited by Mengting Qiu
on 2025/07/03 18:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1081,8 +1081,15 @@
1081 1081  
1082 1082  Downlink command:  (% 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 {}.
1083 1083  
1084 +(% style="color:red" %)**Note:**
1084 1084  
1086 +(% 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 1085  
1088 +(% 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.**
1089 +
1090 +(% 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.**
1091 +
1092 +
1086 1086  == 7.4 What if the signal is good but the domain name resolution fails? ==
1087 1087  
1088 1088