Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 228.5
edited by Mengting Qiu
on 2025/06/16 09:01
Change comment: There is no comment for this version
To version 225.1
edited by Mengting Qiu
on 2025/03/08 11:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -602,13 +602,13 @@
602 602  Note:The port for the COAP protocol has been fixed to 5683
603 603  
604 604  
605 -* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
605 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform",
606 606  
607 607  -NB/NS products use the (% style="color:red" %)**BC660K**(%%) module, only need to configure (% style="color:red" %)**only one URL**(%%) command.
608 608  
609 609  e.g.
610 610  
611 -* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
611 +* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
612 612  
613 613  [[image:image-20240729172415-13.png||height="401" width="694"]]
614 614  
... ... @@ -1024,27 +1024,20 @@
1024 1024  [[image:image-20240226111928-1.png]]
1025 1025  
1026 1026  
1027 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? ==
1027 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
1028 1028  
1029 1029  
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:**
1030 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1031 +=== UDP: ===
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 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.**
1034 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1035 +Its downlink command is the same as the AT command, but brackets are required.
1036 +Example:
1036 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 +{AT+TDC=300}
1038 1038  
1039 1039  
1040 -[[image:1750035004731-376.png]]
1041 -
1042 -
1043 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1044 -=== **UDP Protocol:** ===
1045 -
1046 -Only supports valid **HEX-format downlink commands** corresponding to AT command
1047 -
1048 1048  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1049 1049  === MQTT: ===
1050 1050  
1750035004731-376.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -55.1 KB
Content