Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 223.1
edited by Edwin Chen
on 2025/01/21 23:55
Change comment: There is no comment for this version
To version 226.3
edited by Mengting Qiu
on 2025/06/13 19:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.ting
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+URL1=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 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
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+URL1=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 ===
... ... @@ -854,7 +854,7 @@
854 854  * (% style="color:#037691" %)**AT+CLIENT=NULL**
855 855  * (% style="color:#037691" %)**AT+UNAME=NULL**
856 856  * (% style="color:#037691" %)**AT+PWD=NULL**
857 -* (% style="color:#037691" %)**AT+TLSMOD=1,0**
848 +* (% style="color:#037691" %)**AT+TLSMOD=1,2**
858 858  
859 859  Test Uplink by click the button for 1~~3 seconds, the MQTT integration in ThingsEye allows you to view the data upstream from the device:
860 860  
... ... @@ -1033,18 +1033,18 @@
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 by the NB device?(%%) ==
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  
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 +
1039 1039  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1040 -=== UDP: ===
1033 +=== **UDP Protocol:** ===
1041 1041  
1035 +Only supports valid **HEX-format downlink commands** corresponding to AT command
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:
1037 +Example: For the S31-NB’s uplink interval modification command (AT+TDC), the downlink command should be:
1046 1046  
1047 -{AT+TDC=300}
1048 1048  
1049 1049  
1050 1050  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
... ... @@ -1111,7 +1111,6 @@
1111 1111  * **AT** **+GETLOG   ~-~-> Command to get the previous upstream log**
1112 1112  * **press the toggle button for 1 ~~2 seconds     ~-~-> Trigger a uplink**
1113 1113  
1114 -
1115 1115  Above are the output example for about three action:
1116 1116  
1117 1117  [[image:image-20250121235119-1.png||height="493" width="455"]]