Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:49
From version 140.1
edited by Mengting Qiu
on 2025/03/08 11:35
Change comment: There is no comment for this version
To version 144.13
edited by Mengting Qiu
on 2025/07/03 18:43
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -982,7 +982,7 @@
982 982  
983 983  * Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
984 984  * Do you configure the correct APN? [[Check here for APN settings>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
985 -* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
985 +* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>||anchor="H1.ConfigureFrequencyBand"]].
986 986  * Check if the device is attached to Carrier network but reject. (need to check with operator).
987 987  * Check if the antenna is connected firmly.
988 988  
... ... @@ -997,27 +997,42 @@
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 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? ==
1001 1001  
1002 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1003 -=== UDP: ===
1004 1004  
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:
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.
1008 1008  
1009 -{AT+TDC=300}
1005 +=== **UDP Protocol:** ===
1010 1010  
1007 +Only supports valid **HEX-format downlink commands** corresponding to AT command.
1011 1011  
1012 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1013 -=== 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.
1014 1014  
1015 -Json：
1012 +[[image:1750039871468-460.png||height="299" width="600"]]
1016 1016  
1017 -The Json format in MQTT mode needs to be configured with all commands.
1018 -If you have configurations that need to be changed, please change them in the template below.
1019 -Template:
1014 +=== **MQTT Protocol:** ===
1020 1020  
1016 +==== **1. HEX-format** ====
1017 +
1018 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1019 +
1020 +//Example~:// For the S31-CB's uplink interval modification (AT+TDC=900):
1021 +
1022 +Downlink command: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
1023 +
1024 +
1025 +==== **2. JSON-format ** ====
1026 +
1027 +===== **2. 1 JSON format template.** =====
1028 +
1029 +All -CB nodes support downlink configuration modification using (% style="color:blue" %)**JSON format templates.**
1030 +
1031 +We can 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.
1032 +Template.
1033 +
1034 +Take the template of DDS75-CB as an example:
1035 +
1021 1021  {
1022 1022  "AT+SERVADDR":"119.91.62.30,1882",
1023 1023  "AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
... ... @@ -1030,27 +1030,44 @@
1030 1030  "AT+APN":"NULL",
1031 1031  "AT+5VT":"0",
1032 1032  "AT+PRO":"3,5",
1033 -"AT+TR":"900",
1034 -"AT+NOUD":"0",
1048 +"AT+TR":"15",
1049 +"AT+NOUD":"8",
1035 1035  "AT+CSQTIME":"5",
1036 -"AT+DNSTIMER":"0",
1051 +"AT+GDNS":"0",
1037 1037  "AT+TLSMOD":"0,0",
1038 1038  "AT+MQOS":"0",
1039 -"AT+TEMPALARM1":"0",
1040 -"AT+TEMPALARM2":"10",
1041 -"AT+TEMPALARM3":"0"
1054 +"AT+IPTYPE":"0",
1055 +"AT+GTDC":"0",
1056 +"AT+GNSST":"10",
1057 +"AT+GPS":"0"
1042 1042  }
1043 1043  
1044 -Hex：
1060 +Explanations of two special commands in the template: AT+TR (set the detection interval: 0 ~~ 255 minutes) and AT+NOUD (set the number of groups) correspond to parameters in AT+CLOCKLOG.
1045 1045  
1046 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1062 +[[image:1751538862245-924.png]]
1047 1047  
1048 -The supported commands are consistent with LoRaWAN's hex commands.
1049 -Please refer to the following link to obtain the hex format:
1064 +**Instructions for Using the Template:**
1050 1050  
1051 -[[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/]]
1066 +1. Modify the parameters for each AT command in the template as needed.
1067 +1. Send the entire template in one downlink command.
1052 1052  
1069 +(% style="color:red" %)**Note:**
1053 1053  
1071 +* The template may vary depending on the device model.
1072 +* **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.
1073 +
1074 +
1075 +
1076 +===== **2.2 Support sending json format commands separately** =====
1077 +
1078 +Some models of nodes support sending json format commands separately：(% style="color:blue" %)**RS485-CB, LDS25-CB, CS01-CB, SDI-12-CB, SW3L-CB, WL03A-CB, PS-CB**
1079 +
1080 +//Example~:// For the PS-CB's uplink interval modification (AT+TDC=900):
1081 +
1082 +Downlink command:  (% 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 {}.
1083 +
1084 +
1085 +
1054 1054  == 7.4 What if the signal is good but the domain name resolution fails? ==
1055 1055  
1056 1056  
1750039871468-460.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +53.9 KB
Content
1751538862245-924.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +114.7 KB
Content