Skip to Content
Last modified by Mengting Qiu on 2025/06/18 15:53
From version 138.1
edited by Xiaoling
on 2025/01/13 11:31
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -54,7 +54,6 @@
54 54  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:406px" %)China Mainland, HongKong|(% style="width:351px" %) |(% style="width:120px" %)
55 55  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:406px" %)China Mainland|(% style="width:351px" %) |(% style="width:120px" %)
56 56  
57 -
58 58  == 2.2 Speed Up Network Attach time ==
59 59  
60 60  
... ... @@ -724,8 +724,8 @@
724 724  Note:The port for the COAP protocol has been fixed to 5683
725 725  
726 726  
727 -* AT+URL1=11,"i"
728 -* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
726 +* AT+URI1=11,"i"
727 +* AT+URI2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
729 729  *
730 730  
731 731  -CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
... ... @@ -732,8 +732,8 @@
732 732  
733 733  e.g.
734 734  
735 -* AT+URL1=11, "i"
736 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
734 +* AT+URI1=11, "i"
735 +* AT+URI2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
737 737  
738 738  [[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172500-14.png?width=700&height=403&rev=1.1||alt="image-20240729172500-14.png" height="413" width="718"]]
739 739  
... ... @@ -998,25 +998,41 @@
998 998  [[image:image-20240820113015-60.png]]
999 999  
1000 1000  
1001 -== (% 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? ==
1002 1002  
1003 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1004 -=== UDP: ===
1005 1005  
1006 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
1007 -Its downlink command is the same as the AT command, but brackets are required.
1008 -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.
1009 1009  
1010 -{AT+TDC=300}
1005 +=== **UDP Protocol:** ===
1011 1011  
1007 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
1012 1012  
1013 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1014 -=== 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.
1015 1015  
1016 -Json：
1012 +[[image:1750039871468-460.png||height="299" width="600"]]
1017 1017  
1018 -The Json format in MQTT mode needs to be configured with all commands.
1019 -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.
1020 1020  Template:
1021 1021  
1022 1022  {
... ... @@ -1042,16 +1042,18 @@
1042 1042  "AT+TEMPALARM3":"0"
1043 1043  }
1044 1044  
1045 -Hex：
1060 +**Instructions for Using the Template:**
1046 1046  
1047 -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.
1048 1048  
1049 -The supported commands are consistent with LoRaWAN's hex commands.
1050 -Please refer to the following link to obtain the hex format:
1065 +(% style="color:red" %)**Note:**
1051 1051  
1052 -[[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.
1053 1053  
1054 1054  
1071 +
1055 1055  == 7.4 What if the signal is good but the domain name resolution fails? ==
1056 1056  
1057 1057  
... ... @@ -1189,4 +1189,13 @@
1189 1189  AT+IPTYPE can only be configured as 1 or 2.
1190 1190  If it is configured otherwise, this error will occur**
1191 1191  
1209 +
1210 +== 7.7 How to get the debug log for further analyze? ==
1211 +
1212 +
1213 +CB model use the same debug instruction as NB model. Please check this link:
1214 +
1215 +**[[How to Get Full Log>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H6.6Howtogetthedebuglogforfurtheranalyze3F]]**?
1216 +
1217 +
1192 1192  
1750039871468-460.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +53.9 KB
Content