Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:49
From version 141.10
edited by Mengting Qiu
on 2025/06/16 10:14
Change comment: There is no comment for this version
To version 143.7
edited by Mengting Qiu
on 2025/07/03 18:31
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  
... ... @@ -1013,12 +1013,14 @@
1013 1013  
1014 1014  === **MQTT Protocol:** ===
1015 1015  
1016 -Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1016 +==== **1. HEX-format** ====
1017 1017  
1018 +Supports **HEX-format** downlink commands (corresponding to AT commands).
1019 +
1018 1018  //Example~:// For the S31-CB's uplink interval modification (AT+TDC=900):
1019 1019  
1020 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 {}.
1023 +* 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 1022  
1023 1023  (% style="color:red" %)**Note:**
1024 1024  
... ... @@ -1029,13 +1029,14 @@
1029 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 1030  
1031 1031  
1034 +==== **2. JSON-format ** ====
1032 1032  
1036 +All -CB nodes support downlink configuration modification using JSON format templates.
1033 1033  
1034 -Json：
1038 +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.
1039 +Template.
1035 1035  
1036 -The Json format in MQTT mode needs to be configured with all commands.
1037 -If you have configurations that need to be changed, please change them in the template below.
1038 -Template:
1041 +Take the template of DDS75-CB as an example:
1039 1039  
1040 1040  {
1041 1041  "AT+SERVADDR":"119.91.62.30,1882",
... ... @@ -1049,27 +1049,32 @@
1049 1049  "AT+APN":"NULL",
1050 1050  "AT+5VT":"0",
1051 1051  "AT+PRO":"3,5",
1052 -"AT+TR":"900",
1053 -"AT+NOUD":"0",
1055 +"AT+TR":"15",
1056 +"AT+NOUD":"8",
1054 1054  "AT+CSQTIME":"5",
1055 -"AT+DNSTIMER":"0",
1058 +"AT+GDNS":"0",
1056 1056  "AT+TLSMOD":"0,0",
1057 1057  "AT+MQOS":"0",
1058 -"AT+TEMPALARM1":"0",
1059 -"AT+TEMPALARM2":"10",
1060 -"AT+TEMPALARM3":"0"
1061 +"AT+IPTYPE":"0",
1062 +"AT+GTDC":"0",
1063 +"AT+GNSST":"10",
1064 +"AT+GPS":"0"
1061 1061  }
1062 1062  
1063 -Hex：
1064 1064  
1065 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1066 1066  
1067 -The supported commands are consistent with LoRaWAN's hex commands.
1068 -Please refer to the following link to obtain the hex format:
1069 +**Instructions for Using the Template:**
1069 1069  
1070 -[[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/]]
1071 +1. Modify the parameters for each AT command in the template as needed.
1072 +1. Send the entire template in one downlink command.
1071 1071  
1074 +(% style="color:red" %)**Note:**
1072 1072  
1076 +* The template may vary depending on the device model.
1077 +* **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.
1078 +
1079 +
1080 +
1073 1073  == 7.4 What if the signal is good but the domain name resolution fails? ==
1074 1074  
1075 1075