Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 75.3
edited by Xiaoling
on 2022/07/09 08:58
Change comment: There is no comment for this version
To version 108.13
edited by Xiaoling
on 2023/04/24 10:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,6 +7,7 @@
7 7  
8 8  **Table of Contents:**
9 9  
10 +{{toc/}}
10 10  
11 11  
12 12  
... ... @@ -21,24 +21,37 @@
21 21  
22 22  
23 23  (((
25 +(((
24 24  The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
25 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
26 -\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
27 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
28 -\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
29 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
30 30  )))
31 31  
32 -
29 +(((
30 +The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
33 33  )))
34 34  
35 -[[image:1654503236291-817.png]]
33 +(((
34 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
35 +)))
36 36  
37 +(((
38 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
39 +)))
37 37  
38 -[[image:1657327959271-447.png]]
41 +(((
42 +NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
43 +)))
39 39  
45 +(((
46 +To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
47 +)))
48 +)))
40 40  
50 +
51 +)))
41 41  
53 +[[image:1657327959271-447.png]]
54 +
55 +
42 42  == 1.2 ​ Features ==
43 43  
44 44  
... ... @@ -67,14 +67,13 @@
67 67  
68 68  (% style="color:#037691" %)**NB-IoT Spec:**
69 69  
70 -* - B1 @H-FDD: 2100MHz
71 -* - B3 @H-FDD: 1800MHz
72 -* - B8 @H-FDD: 900MHz
73 -* - B5 @H-FDD: 850MHz
74 -* - B20 @H-FDD: 800MHz
75 -* - B28 @H-FDD: 700MHz
84 +* B1 @H-FDD: 2100MHz
85 +* B3 @H-FDD: 1800MHz
86 +* B8 @H-FDD: 900MHz
87 +* B5 @H-FDD: 850MHz
88 +* B20 @H-FDD: 800MHz
89 +* B28 @H-FDD: 700MHz
76 76  
77 -
78 78  (% style="color:#037691" %)**Battery:**
79 79  
80 80  * Li/SOCI2 un-chargeable battery
... ... @@ -83,7 +83,6 @@
83 83  * Max continuously current: 130mA
84 84  * Max boost current: 2A, 1 second
85 85  
86 -
87 87  (% style="color:#037691" %)**Power Consumption**
88 88  
89 89  * STOP Mode: 10uA @ 3.3v
... ... @@ -91,68 +91,74 @@
91 91  
92 92  
93 93  
94 -
95 95  == ​1.4  Applications ==
96 96  
108 +
109 +* Smart Buildings & Home Automation
110 +* Logistics and Supply Chain Management
111 +* Smart Metering
97 97  * Smart Agriculture
113 +* Smart Cities
114 +* Smart Factory
98 98  
99 99  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
100 100  ​
101 101  
119 +
102 102  == 1.5  Pin Definitions ==
103 103  
104 104  
105 -[[image:1657246476176-652.png]]
123 +[[image:1657328609906-564.png]]
106 106  
107 107  
126 += 2.  Use NDDS75 to communicate with IoT Server =
108 108  
109 -= 2.  Use NSE01 to communicate with IoT Server =
110 -
111 111  == 2.1  How it works ==
112 112  
113 113  
114 114  (((
115 -The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NSE01.
132 +The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
116 116  )))
117 117  
118 118  
119 119  (((
120 -The diagram below shows the working flow in default firmware of NSE01:
137 +The diagram below shows the working flow in default firmware of NDDS75:
121 121  )))
122 122  
123 -[[image:image-20220708101605-2.png]]
124 -
125 125  (((
126 126  
127 127  )))
128 128  
144 +[[image:1657328659945-416.png]]
129 129  
146 +(((
147 +
148 +)))
130 130  
131 -== 2.2 ​ Configure the NSE01 ==
150 +== 2.2 ​ Configure the NDDS75 ==
132 132  
133 -
134 134  === 2.2.1 Test Requirement ===
135 135  
136 136  
137 137  (((
138 -To use NSE01 in your city, make sure meet below requirements:
156 +To use NDDS75 in your city, make sure meet below requirements:
139 139  )))
140 140  
141 141  * Your local operator has already distributed a NB-IoT Network there.
142 -* The local NB-IoT network used the band that NSE01 supports.
160 +* The local NB-IoT network used the band that NDDS75 supports.
143 143  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
144 144  
145 145  (((
146 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
164 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
147 147  )))
148 148  
149 149  
150 -[[image:1657249419225-449.png]]
168 +[[image:1657328756309-230.png]]
151 151  
152 152  
153 -
154 154  === 2.2.2 Insert SIM card ===
155 155  
173 +
156 156  (((
157 157  Insert the NB-IoT Card get from your provider.
158 158  )))
... ... @@ -162,28 +162,30 @@
162 162  )))
163 163  
164 164  
165 -[[image:1657249468462-536.png]]
183 +[[image:1657328884227-504.png]]
166 166  
167 167  
186 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
168 168  
169 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
170 170  
171 171  (((
172 172  (((
173 -User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
191 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
174 174  )))
175 175  )))
176 176  
195 +[[image:image-20220709092052-2.png]]
177 177  
178 -**Connection:**
179 179  
180 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
198 +(% style="color:blue" %)**Connection:**
181 181  
182 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
200 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
183 183  
184 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
202 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
185 185  
204 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
186 186  
206 +
187 187  In the PC, use below serial tool settings:
188 188  
189 189  * Baud:  (% style="color:green" %)**9600**
... ... @@ -193,72 +193,87 @@
193 193  * Flow Control: (% style="color:green" %)**None**
194 194  
195 195  (((
196 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
216 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
197 197  )))
198 198  
199 -[[image:image-20220708110657-3.png]]
219 +[[image:1657329814315-101.png]]
200 200  
221 +
201 201  (((
202 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
223 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
203 203  )))
204 204  
205 205  
206 -
207 207  === 2.2.4 Use CoAP protocol to uplink data ===
208 208  
209 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
210 210  
230 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
211 211  
232 +
233 +(((
212 212  **Use below commands:**
235 +)))
213 213  
214 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
215 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
216 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
237 +* (((
238 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
239 +)))
240 +* (((
241 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
242 +)))
243 +* (((
244 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
217 217  
246 +
247 +
248 +)))
249 +
250 +(((
218 218  For parameter description, please refer to AT command set
219 219  
220 -[[image:1657249793983-486.png]]
253 +
254 +)))
221 221  
256 +[[image:1657330452568-615.png]]
222 222  
223 -After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
224 224  
225 -[[image:1657249831934-534.png]]
226 226  
260 +(((
261 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
227 227  
263 +
264 +)))
228 228  
229 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
266 +[[image:1657330472797-498.png]]
230 230  
231 -This feature is supported since firmware version v1.0.1
232 232  
269 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
233 233  
234 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
235 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
236 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
237 237  
238 -[[image:1657249864775-321.png]]
272 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
273 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
274 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
239 239  
276 +[[image:1657330501006-241.png]]
240 240  
241 -[[image:1657249930215-289.png]]
242 242  
279 +[[image:1657330533775-472.png]]
243 243  
244 244  
245 245  === 2.2.6 Use MQTT protocol to uplink data ===
246 246  
247 -This feature is supported since firmware version v110
248 248  
285 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
286 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
287 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
288 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
289 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
290 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
291 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
249 249  
250 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
251 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
252 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
253 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
254 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
255 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
256 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
257 -
258 258  [[image:1657249978444-674.png]]
259 259  
260 260  
261 -[[image:1657249990869-686.png]]
296 +[[image:1657330723006-866.png]]
262 262  
263 263  
264 264  (((
... ... @@ -266,75 +266,125 @@
266 266  )))
267 267  
268 268  
269 -
270 270  === 2.2.7 Use TCP protocol to uplink data ===
271 271  
272 -This feature is supported since firmware version v110
273 273  
307 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
274 274  
275 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
276 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
310 +[[image:image-20220709093918-1.png]]
277 277  
278 -[[image:1657250217799-140.png]]
279 279  
313 +[[image:image-20220709093918-2.png]]
280 280  
281 -[[image:1657250255956-604.png]]
282 282  
283 -
284 -
285 285  === 2.2.8 Change Update Interval ===
286 286  
318 +
287 287  User can use below command to change the (% style="color:green" %)**uplink interval**.
288 288  
289 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
321 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
290 290  
291 291  (((
324 +
325 +
326 +
292 292  (% style="color:red" %)**NOTE:**
293 -)))
294 294  
295 -(((
296 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
329 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
330 +
331 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
297 297  )))
298 298  
334 +(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
299 299  
300 300  
301 301  == 2.3  Uplink Payload ==
302 302  
303 -In this mode, uplink payload includes in total 18 bytes
339 +=== 2.3.1  Before Firmware v1.3.2 ===
304 304  
305 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
341 +
342 +In this mode, uplink payload includes in total 14 bytes
343 +
344 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
306 306  |=(% style="width: 60px;" %)(((
307 307  **Size(bytes)**
308 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1**
309 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
347 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
348 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
310 310  
311 311  (((
312 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
351 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
313 313  )))
314 314  
315 315  
316 -[[image:image-20220708111918-4.png]]
355 +[[image:1657331036973-987.png]]
317 317  
318 318  
358 +The payload is **ASCII** string, representative same HEX:
359 +
360 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
361 +
362 +**where :**
363 +
364 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
365 +
366 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
367 +
368 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
369 +
370 +* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
371 +
372 +* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
373 +
374 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
375 +
376 +=== 2.3.2  Since firmware v1.3.2 ===
377 +
378 +
379 +In this mode, uplink payload includes 69 bytes in total by default.
380 +
381 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
382 +
383 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
384 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4**
385 +|=(% style="width: 95px;" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
386 +
387 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
388 +
389 +[[image:image-20220908175246-1.png]]
390 +
391 +
319 319  The payload is ASCII string, representative same HEX:
320 320  
321 -0x72403155615900640c7817075e0a8c02f900 where:
394 +**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
322 322  
323 -* Device ID: 0x 724031556159 = 724031556159
324 -* Version: 0x0064=100=1.0.0
396 +**where:**
325 325  
326 -* BAT: 0x0c78 = 3192 mV = 3.192V
327 -* Singal: 0x17 = 23
328 -* Soil Moisture: 0x075e= 1886 = 18.86  %
329 -* Soil Temperature:0x0a8c =2700=27 °C
330 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
331 -* Interrupt: 0x00 = 0
398 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
332 332  
333 -== 2.4  Payload Explanation and Sensor Interface ==
400 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
334 334  
402 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
335 335  
404 +* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
405 +
406 +* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
407 +
408 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
409 +
410 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
411 +
412 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
413 +
414 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
415 +
416 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
417 +
418 +== 2.4  Payload Explanation and Sensor Interface ==
419 +
336 336  === 2.4.1  Device ID ===
337 337  
422 +
338 338  (((
339 339  By default, the Device ID equal to the last 6 bytes of IMEI.
340 340  )))
... ... @@ -341,10 +341,12 @@
341 341  
342 342  (((
343 343  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
429 +
430 +
344 344  )))
345 345  
346 346  (((
347 -**Example:**
434 +(% style="color:blue" %)**Example :**
348 348  )))
349 349  
350 350  (((
... ... @@ -352,28 +352,36 @@
352 352  )))
353 353  
354 354  (((
355 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
442 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
356 356  )))
357 357  
358 358  
446 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
359 359  
448 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
449 +
450 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
451 +
452 +
453 +(% style="color:blue" %)**Example :**
454 +
455 +AT+DEUI=868411056754138
456 +
457 +
360 360  === 2.4.2  Version Info ===
361 361  
460 +
362 362  (((
363 363  Specify the software version: 0x64=100, means firmware version 1.00.
364 364  )))
365 365  
366 366  (((
367 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
466 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
368 368  )))
369 369  
370 370  
371 -
372 372  === 2.4.3  Battery Info ===
373 373  
374 -(((
375 -Check the battery voltage for LSE01.
376 -)))
377 377  
378 378  (((
379 379  Ex1: 0x0B45 = 2885mV
... ... @@ -384,9 +384,9 @@
384 384  )))
385 385  
386 386  
387 -
388 388  === 2.4.4  Signal Strength ===
389 389  
484 +
390 390  (((
391 391  NB-IoT Network signal Strength.
392 392  )))
... ... @@ -416,77 +416,30 @@
416 416  )))
417 417  
418 418  
514 +=== 2.4.5  Distance ===
419 419  
420 -=== 2.4.5  Soil Moisture ===
421 421  
422 -(((
423 -(((
424 -Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
425 -)))
426 -)))
517 +Get the distance. Flat object range 280mm - 7500mm.
427 427  
428 428  (((
429 -(((
430 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
520 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
431 431  )))
432 -)))
433 433  
434 434  (((
435 -
436 -)))
437 -
438 438  (((
439 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
525 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
440 440  )))
441 -
442 -
443 -
444 -=== 2.4.6  Soil Temperature ===
445 -
446 -(((
447 -Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is
448 448  )))
449 449  
450 450  (((
451 -**Example**:
452 -)))
453 -
454 -(((
455 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
456 -)))
457 -
458 -(((
459 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
460 -)))
461 -
462 -
463 -
464 -=== 2.4.7  Soil Conductivity (EC) ===
465 -
466 -(((
467 -Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
468 -)))
469 -
470 -(((
471 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
472 -)))
473 -
474 -(((
475 -Generally, the EC value of irrigation water is less than 800uS / cm.
476 -)))
477 -
478 -(((
479 479  
480 480  )))
481 481  
482 -(((
483 -
484 -)))
533 +=== 2.4.6  Digital Interrupt ===
485 485  
486 -=== 2.4.8  Digital Interrupt ===
487 487  
488 488  (((
489 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
537 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
490 490  )))
491 491  
492 492  (((
... ... @@ -494,7 +494,7 @@
494 494  )))
495 495  
496 496  (((
497 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
545 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/  (more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
498 498  )))
499 499  
500 500  
... ... @@ -516,20 +516,24 @@
516 516  )))
517 517  
518 518  
567 +=== 2.4.7  ​+5V Output ===
519 519  
520 -=== 2.4.9  ​+5V Output ===
521 521  
522 522  (((
523 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
571 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
524 524  )))
525 525  
526 526  
527 527  (((
528 528  The 5V output time can be controlled by AT Command.
577 +
578 +
529 529  )))
530 530  
531 531  (((
532 532  (% style="color:blue" %)**AT+5VT=1000**
583 +
584 +
533 533  )))
534 534  
535 535  (((
... ... @@ -537,14 +537,14 @@
537 537  )))
538 538  
539 539  
540 -
541 541  == 2.5  Downlink Payload ==
542 542  
543 -By default, NSE01 prints the downlink payload to console port.
544 544  
545 -[[image:image-20220708133731-5.png]]
595 +By default, NDDS75 prints the downlink payload to console port.
546 546  
597 +[[image:image-20220709100028-1.png]]
547 547  
599 +
548 548  (((
549 549  (% style="color:blue" %)**Examples:**
550 550  )))
... ... @@ -578,7 +578,7 @@
578 578  )))
579 579  
580 580  (((
581 -If payload = 0x04FF, it will reset the NSE01
633 +If payload = 0x04FF, it will reset the NDDS75
582 582  )))
583 583  
584 584  
... ... @@ -589,239 +589,195 @@
589 589  )))
590 590  
591 591  
644 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
592 592  
593 -== 2.6  ​LED Indicator ==
594 594  
595 -(((
596 -The NSE01 has an internal LED which is to show the status of different state.
647 +(% style="color:blue" %)** ➢ AT Command:**
597 597  
649 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
598 598  
599 -* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
600 -* Then the LED will be on for 1 second means device is boot normally.
601 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
602 -* For each uplink probe, LED will be on for 500ms.
603 -)))
651 +² When min=0, and max≠0, Alarm higher than max
604 604  
653 +² When min≠0, and max=0, Alarm lower than min
605 605  
655 +² When min≠0 and max≠0, Alarm higher than max or lower than min
606 606  
607 607  
608 -== 2.7  Installation in Soil ==
658 +(% style="color:blue" %)** Example:**
609 609  
610 -__**Measurement the soil surface**__
660 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
611 611  
612 -(((
613 -Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
614 -)))
615 615  
616 -[[image:1657259653666-883.png]] ​
663 +== 2.7  Set the number of data to be uploaded and the recording time ==
617 617  
618 618  
619 -(((
620 -
666 +(% style="color:blue" %)** ➢ AT Command:**
621 621  
622 -(((
623 -Dig a hole with diameter > 20CM.
624 -)))
668 +* (% style="color:#037691" %)** AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
669 +* (% style="color:#037691" %)** AT+NOUD=8**             (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
625 625  
626 -(((
627 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
628 -)))
629 -)))
671 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
630 630  
631 -[[image:1654506665940-119.png]]
673 +[[image:image-20221009001114-1.png||height="687" width="955"]]
632 632  
633 -(((
634 -
635 -)))
636 636  
676 +== 2.8  Read or Clear cached data ==
637 637  
638 -== 2.8  ​Firmware Change Log ==
639 639  
679 +(% style="color:blue" %)** ➢ AT Command:**
640 640  
641 -Download URL & Firmware Change log
681 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
682 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
642 642  
643 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
684 +[[image:image-20220908175333-2.png]]
644 644  
645 645  
646 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
687 +== 2.9  ​LED Indicator ==
647 647  
648 648  
690 +The NDDS75 has an internal LED which is to show the status of different state.
649 649  
650 -== 2.9  ​Battery Analysis ==
651 651  
652 -=== 2.9.1  ​Battery Type ===
693 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
694 +* Then the LED will be on for 1 second means device is boot normally.
695 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
696 +* For each uplink probe, LED will be on for 500ms.
653 653  
654 -
655 655  (((
656 -The NSE01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
699 +
657 657  )))
658 658  
659 659  
660 -(((
661 -The battery is designed to last for several years depends on the actually use environment and update interval. 
662 -)))
703 +== 2.10  ​Firmware Change Log ==
663 663  
664 664  
665 665  (((
666 -The battery related documents as below:
707 +Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
667 667  )))
668 668  
669 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
670 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
671 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
672 -
673 673  (((
674 -[[image:image-20220708140453-6.png]]
711 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
675 675  )))
676 676  
677 677  
715 +== 2.11 Battery & Power Consumption ==
678 678  
679 -=== 2.9.2  Power consumption Analyze ===
680 680  
681 -(((
682 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
683 -)))
718 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
684 684  
720 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
685 685  
686 -(((
687 -Instruction to use as below:
688 -)))
689 689  
690 -(((
691 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
692 -)))
723 += 3. ​ Access NB-IoT Module =
693 693  
694 694  
695 695  (((
696 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
727 +Users can directly access the AT command set of the NB-IoT module.
697 697  )))
698 698  
699 -* (((
700 -Product Model
701 -)))
702 -* (((
703 -Uplink Interval
704 -)))
705 -* (((
706 -Working Mode
707 -)))
708 -
709 709  (((
710 -And the Life expectation in difference case will be shown on the right.
711 -)))
731 +The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
712 712  
713 -[[image:image-20220708141352-7.jpeg]]
714 -
715 -
716 -
717 -=== 2.9.3  ​Battery Note ===
718 -
719 -(((
720 -The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
733 +
721 721  )))
722 722  
736 +[[image:1657333200519-600.png]]
723 723  
724 724  
725 -=== 2.9.4  Replace the battery ===
739 += 4.  Using the AT Commands =
726 726  
727 -(((
728 -The default battery pack of NSE01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
729 -)))
741 +== 4.1  Access AT Commands ==
730 730  
731 731  
744 +See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
732 732  
733 -= 3. ​ Access NB-IoT Module =
734 734  
735 -(((
736 -Users can directly access the AT command set of the NB-IoT module.
737 -)))
747 +AT+<CMD>?  :  Help on <CMD>
738 738  
739 -(((
740 -The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
741 -)))
749 +AT+<CMD>         :  Run <CMD>
742 742  
743 -[[image:1657261278785-153.png]]
751 +AT+<CMD>=<value> :  Set the value
744 744  
753 +AT+<CMD>=?  :  Get the value
745 745  
746 746  
747 -= 4.  Using the AT Commands =
756 +(% style="color:#037691" %)**General Commands**(%%)      
748 748  
749 -== 4.1  Access AT Commands ==
758 +AT  :  Attention       
750 750  
751 -See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
760 +AT?  :  Short Help     
752 752  
762 +ATZ  :  MCU Reset    
753 753  
754 -AT+<CMD>?  : Help on <CMD>
764 +AT+TDC  :  Application Data Transmission Interval
755 755  
756 -AT+<CMD>         : Run <CMD>
766 +AT+CFG  :  Print all configurations
757 757  
758 -AT+<CMD>=<value> : Set the value
768 +AT+CFGMOD           :  Working mode selection
759 759  
760 -AT+<CMD>=?  : Get the value
770 +AT+INTMOD            :  Set the trigger interrupt mode
761 761  
772 +AT+5VT  :  Set extend the time of 5V power  
762 762  
763 -(% style="color:#037691" %)**General Commands**(%%)      
774 +AT+PRO  :  Choose agreement
764 764  
765 -AT  : Attention       
776 +AT+WEIGRE  :  Get weight or set weight to 0
766 766  
767 -AT?  : Short Help     
778 +AT+WEIGAP  :  Get or Set the GapValue of weight
768 768  
769 -ATZ  : MCU Reset    
780 +AT+RXDL  :  Extend the sending and receiving time
770 770  
771 -AT+TDC  : Application Data Transmission Interval
782 +AT+CNTFAC  :  Get or set counting parameters
772 772  
773 -AT+CFG  : Print all configurations
784 +AT+SERVADDR  :  Server Address
774 774  
775 -AT+CFGMOD           : Working mode selection
786 +AT+TR  :  Get or Set record time"
776 776  
777 -AT+INTMOD            : Set the trigger interrupt mode
788 +AT+APN     :  Get or set the APN
778 778  
779 -AT+5VT  : Set extend the time of 5V power  
790 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
780 780  
781 -AT+PRO  : Choose agreement
792 +AT+DNSCFG  : Get or Set DNS Server
782 782  
783 -AT+WEIGRE  : Get weight or set weight to 0
794 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
784 784  
785 -AT+WEIGAP  : Get or Set the GapValue of weight
796 +AT+NOUD  :  Get or Set the number of data to be uploaded
786 786  
787 -AT+RXDL  : Extend the sending and receiving time
798 +AT+CDP     :  Read or Clear cached data
788 788  
789 -AT+CNTFAC  : Get or set counting parameters
800 +AT+LDDSALARM :  Get or Set alarm of distance
790 790  
791 -AT+SERVADDR  : Server Address
792 792  
793 -
794 794  (% style="color:#037691" %)**COAP Management**      
795 795  
796 -AT+URI            : Resource parameters
805 +AT+URI            :  Resource parameters
797 797  
798 798  
799 799  (% style="color:#037691" %)**UDP Management**
800 800  
801 -AT+CFM          : Upload confirmation mode (only valid for UDP)
810 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
802 802  
803 803  
804 804  (% style="color:#037691" %)**MQTT Management**
805 805  
806 -AT+CLIENT               : Get or Set MQTT client
815 +AT+CLIENT  :  Get or Set MQTT client
807 807  
808 -AT+UNAME  : Get or Set MQTT Username
817 +AT+UNAME  :  Get or Set MQTT Username
809 809  
810 -AT+PWD                  : Get or Set MQTT password
819 +AT+PWD  :  Get or Set MQTT password
811 811  
812 -AT+PUBTOPIC  : Get or Set MQTT publish topic
821 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
813 813  
814 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
823 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
815 815  
816 816  
817 817  (% style="color:#037691" %)**Information**          
818 818  
819 -AT+FDR  : Factory Data Reset
828 +AT+FDR  :  Factory Data Reset
820 820  
821 -AT+PWORD  : Serial Access Password
830 +AT+PWORD  :  Serial Access Password
822 822  
823 823  
824 -
825 825  = ​5.  FAQ =
826 826  
827 827  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -836,18 +836,10 @@
836 836  )))
837 837  
838 838  (((
839 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
847 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
840 840  )))
841 841  
842 842  
843 -
844 -== 5.2  Can I calibrate NSE01 to different soil types? ==
845 -
846 -(((
847 -NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
848 -)))
849 -
850 -
851 851  = 6.  Trouble Shooting =
852 852  
853 853  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -862,27 +862,26 @@
862 862  
863 863  )))
864 864  
865 -
866 866  == 6.2  AT Command input doesn't work ==
867 867  
867 +
868 868  (((
869 869  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
870 -
871 -
872 872  )))
873 873  
874 874  
875 -= 7. ​ Order Info =
873 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
876 876  
877 877  
878 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
876 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
879 879  
880 880  
881 -(% class="wikigeneratedid" %)
882 -(((
883 -
884 -)))
879 += 7. ​ Order Info =
885 885  
881 +
882 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
883 +
884 +
886 886  = 8.  Packing Info =
887 887  
888 888  (((
... ... @@ -890,7 +890,7 @@
890 890  
891 891  (% style="color:#037691" %)**Package Includes**:
892 892  
893 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
892 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
894 894  * External antenna x 1
895 895  )))
896 896  
... ... @@ -899,18 +899,21 @@
899 899  
900 900  (% style="color:#037691" %)**Dimension and weight**:
901 901  
902 -* Size: 195 x 125 x 55 mm
903 -* Weight:   420g
901 +* Device Size: 13.0 x 5 x 4.5 cm
902 +* Device Weight: 150g
903 +* Package Size / pcs : 15 x 12x 5.5 cm
904 +* Weight / pcs : 220g
904 904  )))
905 905  
906 906  (((
907 907  
908 908  
909 -
910 910  
911 911  )))
912 912  
913 913  = 9.  Support =
914 914  
915 +
915 915  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
917 +
916 916  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1657328609906-564.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220709092052-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +247.3 KB
Content
image-20220709093918-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +611.5 KB
Content
image-20220908175246-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content