Last modified by Mengting Qiu on 2025/07/03 18:55
From version 224.1
edited by Mengting Qiu
on 2025/02/21 09:34
on 2025/02/21 09:34
Change comment:
There is no comment for this version
To version 228.4
edited by Mengting Qiu
on 2025/06/16 08:57
on 2025/06/16 08:57
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -602,26 +602,17 @@ 602 602 Note:The port for the COAP protocol has been fixed to 5683 603 603 604 604 605 -* AT+UR L1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"605 +* AT+URI1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform", 606 606 607 - Ifthe moduleusedis(% style="color:red" %)**BC660K, only one**(%%)URLdirectiveneedstobeconfigured,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+UR L1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"611 +* AT+URI1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858" 612 612 613 613 [[image:image-20240729172415-13.png||height="401" width="694"]] 614 614 615 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands, 616 616 617 -e.g. 618 - 619 -* AT+URL1=11, "i" 620 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858" 621 - 622 -[[image:image-20240729172500-14.png||height="403" width="700"]] 623 - 624 - 625 625 == 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == 626 626 627 627 === 3.8.1 Create device & Get Credentials === ... ... @@ -1033,20 +1033,25 @@ 1033 1033 [[image:image-20240226111928-1.png]] 1034 1034 1035 1035 1036 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command bytheNBdevice?(%%)==1027 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 (%%)What is the Downlink Command Format for NB Devices? == 1037 1037 1038 1038 1039 - (%data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6"%)1040 - ===UDP:===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:** 1041 1041 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.** 1042 1042 1043 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %) 1044 -Its downlink command is the same as the AT command, but brackets are required. 1045 -Example: 1035 +(% style="color:red" %)**2. ** 1046 1046 1047 -{AT+TDC=300} 1048 1048 1038 +[[image:1750035004731-376.png]] 1049 1049 1040 + 1041 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1042 +=== **UDP Protocol:** === 1043 + 1044 +Only supports valid **HEX-format downlink commands** corresponding to AT command 1045 + 1050 1050 (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %) 1051 1051 === MQTT: === 1052 1052
- 1750035004731-376.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.ting - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.1 KB - Content