Skip to Content
Last modified by Mengting Qiu on 2025/06/18 15:53
From version 140.1
edited by Mengting Qiu
on 2025/03/08 11:35
Change comment: There is no comment for this version
To version 142.1
edited by Mengting Qiu
on 2025/06/16 10:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -997,25 +997,41 @@
997 997  [[image:image-20240820113015-60.png]]
998 998  
999 999  
1000 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
1000 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 (%%)What is the Downlink Command Format for CB Devices? ==
1001 1001  
1002 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1003 -=== UDP: ===
1004 1004  
1005 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1006 -Its downlink command is the same as the AT command, but brackets are required.
1007 -Example:
1003 +Firstly, it is recommended that users upgrade the firmware of the -CB 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.
1008 1008  
1009 -{AT+TDC=300}
1005 +=== **UDP Protocol:** ===
1010 1010  
1007 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
1011 1011  
1012 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1013 -=== MQTT: ===
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:
1010 +Downward format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1014 1014  
1015 -Json：
1012 +[[image:1750039871468-460.png||height="299" width="600"]]
1016 1016  
1017 -The Json format in MQTT mode needs to be configured with all commands.
1018 -If you have configurations that need to be changed, please change them in the template below.
1014 +=== **MQTT Protocol:** ===
1015 +
1016 +Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1017 +
1018 +//Example~:// For the S31-CB's uplink interval modification (AT+TDC=900):
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 {}.
1022 +
1023 +(% style="color:red" %)**Note:**
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.**
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.**
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.**
1030 +
1031 +
1032 +**Template for Batch Configuration:**
1033 +
1034 +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.
1019 1019  Template:
1020 1020  
1021 1021  {
... ... @@ -1041,16 +1041,18 @@
1041 1041  "AT+TEMPALARM3":"0"
1042 1042  }
1043 1043  
1044 -Hex：
1060 +**Instructions for Using the Template:**
1045 1045  
1046 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1062 +1. Modify the parameters for each AT command in the template as needed.
1063 +1. Send the entire template in one downlink command.
1047 1047  
1048 -The supported commands are consistent with LoRaWAN's hex commands.
1049 -Please refer to the following link to obtain the hex format:
1065 +(% style="color:red" %)**Note:**
1050 1050  
1051 -[[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/]]
1067 +* The template may vary depending on the device model.
1068 +* **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.
1052 1052  
1053 1053  
1071 +
1054 1054  == 7.4 What if the signal is good but the domain name resolution fails? ==
1055 1055  
1056 1056  
1750039871468-460.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +53.9 KB
Content