Changes for page General Manual for -CB , -CS models
Last modified by Mengting Qiu on 2025/06/18 15:53
From version 141.4
edited by Mengting Qiu
on 2025/06/16 10:12
on 2025/06/16 10:12
Change comment:
There is no comment for this version
To version 140.1
edited by Mengting Qiu
on 2025/03/08 11:35
on 2025/03/08 11:35
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -997,40 +997,21 @@ 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 CommandFormatforCBDevices? ==1000 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) == 1001 1001 1002 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1003 +=== UDP: === 1002 1002 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. 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: 1004 1004 1005 - === **UDP Protocol:**===1009 +{AT+TDC=300} 1006 1006 1007 -Only supports valid **HEX-format downlink commands** corresponding to AT command. 1008 1008 1009 - Takethe AT+TDC commandof S31-CB asanexample,thatis, only the validHEXformat downstreamcommandcorresponding to the AT+TDC commandcan be used:1010 - Downward format: (% style="color:blue" %)**01000384**(%%) ~/~/ There are no Spaces. 0x0384(H)=900(D),that is, modifyTDCto 900 seconds.1012 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1013 +=== MQTT: === 1011 1011 1012 -[[image:1750039871468-460.png||height="299" width="600"]] 1013 - 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: **{AT+TDC=900} **~/~/ The correct format is **{AT Command}**. No extra characters other than valid AT commands can be added within {}. 1022 - 1023 -**Note:** 1024 - 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 - 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 - 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 - 1031 - 1032 - 1033 - 1034 1034 Json: 1035 1035 1036 1036 The Json format in MQTT mode needs to be configured with all commands.
- 1750039871468-460.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -53.9 KB - Content