Skip to Content
Last modified by Mengting Qiu on 2025/06/18 15:53
From version 141.10
edited by Mengting Qiu
on 2025/06/16 10:14
Change comment: There is no comment for this version
To version 141.3
edited by Mengting Qiu
on 2025/06/16 10:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1006,7 +1006,7 @@
1006 1006  
1007 1007  Only supports valid **HEX-format downlink commands** corresponding to AT command.
1008 1008  
1009 -Take the AT+TDC command of S31-CB as an example, that is, only the valid HEX format downstream command corresponding to the AT+TDC command can be used:
1009 +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:
1010 1010  Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1011 1011  
1012 1012  [[image:1750039871468-460.png||height="299" width="600"]]
... ... @@ -1015,18 +1015,18 @@
1015 1015  
1016 1016  Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1017 1017  
1018 -//Example~:// For the S31-CB's uplink interval modification (AT+TDC=900):
1018 +//Example~:// For the S31-NB's uplink interval modification (AT+TDC=900):
1019 1019  
1020 -* HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1021 -* 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 {}.
1020 +* HEX format: **01000384**  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1021 +* JSON format: **{AT+TDC=900}       **~/~/ The correct format is **{AT Command}**. No extra characters other than valid AT commands can be added within {}.
1022 1022  
1023 -(% style="color:red" %)**Note:**
1023 +**Note:**
1024 1024  
1025 -(% 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.**
1025 +**~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.**
1026 1026  
1027 -(% 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.**
1027 +**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.**
1028 1028  
1029 -(% 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.**
1029 +**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.**
1030 1030  
1031 1031  
1032 1032