Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:49
From version 143.4
edited by Mengting Qiu
on 2025/07/03 18:27
Change comment: There is no comment for this version
To version 141.9
edited by Mengting Qiu
on 2025/06/16 10:14
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>>||anchor="H1.ConfigureFrequencyBand"]].
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]].
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,30 +1013,22 @@
1013 1013  
1014 1014  === **MQTT Protocol:** ===
1015 1015  
1016 -==== **1. HEX-format** ====
1016 +Supports both **JSON-format** and **HEX-format** downlink commands (corresponding to AT commands).
1017 1017  
1018 -Supports **HEX-format** downlink commands (corresponding to AT commands).
1019 -
1020 1020  //Example~:// For the S31-CB's uplink interval modification (AT+TDC=900):
1021 1021  
1022 1022  * HEX format: (% style="color:blue" %)**01000384**(%%)  ~/~/ There are no Spaces. 0x0384(H)=900(D), that is, modify TDC to 900 seconds.
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 {}.
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 {}.
1024 1024  
1025 1025  (% style="color:red" %)**Note:**
1026 1026  
1027 -(% 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.**
1028 1028  
1029 -(% 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.**
1030 1030  
1031 -(% 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.**
1032 1032  
1028 +Json：
1033 1033  
1034 -
1035 -==== 2. **JSON-format** ====
1036 -
1037 -**Template for Batch Configuration:**
1038 -
1039 -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.
1030 +The Json format in MQTT mode needs to be configured with all commands.
1031 +If you have configurations that need to be changed, please change them in the template below.
1040 1040  Template:
1041 1041  
1042 1042  {
... ... @@ -1062,18 +1062,16 @@
1062 1062  "AT+TEMPALARM3":"0"
1063 1063  }
1064 1064  
1065 -**Instructions for Using the Template:**
1057 +Hex：
1066 1066  
1067 -1. Modify the parameters for each AT command in the template as needed.
1068 -1. Send the entire template in one downlink command.
1059 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
1069 1069  
1070 -(% style="color:red" %)**Note:**
1061 +The supported commands are consistent with LoRaWAN's hex commands.
1062 +Please refer to the following link to obtain the hex format:
1071 1071  
1072 -* The template may vary depending on the device model.
1073 -* **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.
1064 +[[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/]]
1074 1074  
1075 1075  
1076 -
1077 1077  == 7.4 What if the signal is good but the domain name resolution fails? ==
1078 1078  
1079 1079