Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 108.19
edited by Xiaoling
on 2023/05/17 18:23
Change comment: There is no comment for this version
To version 92.1
edited by Xiaoling
on 2022/07/09 10:00
Change comment: Uploaded new attachment "image-20220709100028-1.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -7,7 +7,6 @@
7 7  
8 8  **Table of Contents:**
9 9  
10 -{{toc/}}
11 11  
12 12  
13 13  
... ... @@ -22,37 +22,24 @@
22 22  
23 23  
24 24  (((
25 -(((
26 26  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.
27 27  )))
28 28  
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.
32 +
31 31  )))
32 32  
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 -)))
35 +[[image:1654503236291-817.png]]
36 36  
37 -(((
38 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
39 -)))
40 40  
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 -)))
44 -
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 -)))
49 -
50 -
51 -)))
52 -
53 53  [[image:1657327959271-447.png]]
54 54  
55 55  
41 +
56 56  == 1.2 ​ Features ==
57 57  
58 58  
... ... @@ -70,7 +70,6 @@
70 70  * 8500mAh Battery for long term use
71 71  
72 72  
73 -
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -81,12 +81,12 @@
81 81  
82 82  (% style="color:#037691" %)**NB-IoT Spec:**
83 83  
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
69 +* - B1 @H-FDD: 2100MHz
70 +* - B3 @H-FDD: 1800MHz
71 +* - B8 @H-FDD: 900MHz
72 +* - B5 @H-FDD: 850MHz
73 +* - B20 @H-FDD: 800MHz
74 +* - B28 @H-FDD: 700MHz
90 90  
91 91  (% style="color:#037691" %)**Battery:**
92 92  
... ... @@ -99,13 +99,12 @@
99 99  (% style="color:#037691" %)**Power Consumption**
100 100  
101 101  * STOP Mode: 10uA @ 3.3v
102 -* Max transmit power: 350mA@3.3v
87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
103 103  
104 104  
105 105  
106 106  == ​1.4  Applications ==
107 107  
108 -
109 109  * Smart Buildings & Home Automation
110 110  * Logistics and Supply Chain Management
111 111  * Smart Metering
... ... @@ -117,6 +117,7 @@
117 117  ​
118 118  
119 119  
104 +
120 120  == 1.5  Pin Definitions ==
121 121  
122 122  
... ... @@ -123,11 +123,11 @@
123 123  [[image:1657328609906-564.png]]
124 124  
125 125  
111 +
126 126  = 2.  Use NDDS75 to communicate with IoT Server =
127 127  
128 128  == 2.1  How it works ==
129 129  
130 -
131 131  (((
132 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.
133 133  )))
... ... @@ -147,21 +147,22 @@
147 147  
148 148  )))
149 149  
135 +
150 150  == 2.2 ​ Configure the NDDS75 ==
151 151  
138 +
152 152  === 2.2.1 Test Requirement ===
153 153  
154 -
155 155  (((
156 156  To use NDDS75 in your city, make sure meet below requirements:
157 157  )))
158 158  
159 159  * Your local operator has already distributed a NB-IoT Network there.
160 -* The local NB-IoT network used the band that NDDS75 supports.
146 +* The local NB-IoT network used the band that NSE01 supports.
161 161  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
162 162  
163 163  (((
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.
150 +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
165 165  )))
166 166  
167 167  
... ... @@ -168,9 +168,9 @@
168 168  [[image:1657328756309-230.png]]
169 169  
170 170  
157 +
171 171  === 2.2.2 Insert SIM card ===
172 172  
173 -
174 174  (((
175 175  Insert the NB-IoT Card get from your provider.
176 176  )))
... ... @@ -183,9 +183,9 @@
183 183  [[image:1657328884227-504.png]]
184 184  
185 185  
172 +
186 186  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
187 187  
188 -
189 189  (((
190 190  (((
191 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.
... ... @@ -194,16 +194,15 @@
194 194  
195 195  [[image:image-20220709092052-2.png]]
196 196  
183 +**Connection:**
197 197  
198 -(% style="color:blue" %)**Connection:**
185 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
199 199  
200 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
187 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
201 201  
202 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
189 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
203 203  
204 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
205 205  
206 -
207 207  In the PC, use below serial tool settings:
208 208  
209 209  * Baud:  (% style="color:green" %)**9600**
... ... @@ -218,60 +218,40 @@
218 218  
219 219  [[image:1657329814315-101.png]]
220 220  
221 -
222 222  (((
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]]**
207 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
224 224  )))
225 225  
226 226  
211 +
227 227  === 2.2.4 Use CoAP protocol to uplink data ===
228 228  
214 +(% 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/]]
229 229  
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/]]**
231 231  
232 -
233 -(((
234 234  **Use below commands:**
235 -)))
236 236  
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
219 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
220 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
221 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
245 245  
246 -
247 -
248 -)))
249 -
250 -(((
251 251  For parameter description, please refer to AT command set
252 252  
253 -
254 -)))
255 -
256 256  [[image:1657330452568-615.png]]
257 257  
258 258  
259 -
260 -(((
261 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.
262 262  
263 -
264 -)))
265 -
266 266  [[image:1657330472797-498.png]]
267 267  
268 268  
233 +
269 269  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
270 270  
271 271  
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
237 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
238 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
239 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
275 275  
276 276  [[image:1657330501006-241.png]]
277 277  
... ... @@ -279,16 +279,17 @@
279 279  [[image:1657330533775-472.png]]
280 280  
281 281  
247 +
282 282  === 2.2.6 Use MQTT protocol to uplink data ===
283 283  
284 284  
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
251 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
252 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
253 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
254 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
255 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
256 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
257 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
292 292  
293 293  [[image:1657249978444-674.png]]
294 294  
... ... @@ -301,11 +301,12 @@
301 301  )))
302 302  
303 303  
270 +
304 304  === 2.2.7 Use TCP protocol to uplink data ===
305 305  
306 306  
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 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
275 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
309 309  
310 310  [[image:image-20220709093918-1.png]]
311 311  
... ... @@ -313,117 +313,75 @@
313 313  [[image:image-20220709093918-2.png]]
314 314  
315 315  
283 +
316 316  === 2.2.8 Change Update Interval ===
317 317  
318 -
319 319  User can use below command to change the (% style="color:green" %)**uplink interval**.
320 320  
321 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
288 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
322 322  
323 323  (((
324 -
325 -
326 -
327 327  (% style="color:red" %)**NOTE:**
292 +)))
328 328  
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:**
294 +(((
295 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
332 332  )))
333 333  
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).**
335 335  
336 336  
337 337  == 2.3  Uplink Payload ==
338 338  
339 -=== 2.3.1  Before Firmware v1.3.2 ===
340 -
341 -
342 342  In this mode, uplink payload includes in total 14 bytes
343 343  
344 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %)
345 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)(((
304 +
305 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
306 +|=(% style="width: 60px;" %)(((
346 346  **Size(bytes)**
347 -)))|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**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"]]
308 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**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" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
349 349  
350 350  (((
351 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
312 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
352 352  )))
353 353  
354 354  
355 355  [[image:1657331036973-987.png]]
356 356  
357 -
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 -
377 -
378 -=== 2.3.2  Since firmware v1.3.2 ===
379 -
380 -
381 -In this mode, uplink payload includes 69 bytes in total by default.
382 -
383 -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.
384 -
385 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:490px" %)
386 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**4**
387 -|=(% 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.......
388 -
389 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
390 -
391 -[[image:image-20220908175246-1.png]]
392 -
393 -
318 +(((
394 394  The payload is ASCII string, representative same HEX:
320 +)))
395 395  
396 -**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 +(((
323 +0x72403155615900640c6c19029200 where:
324 +)))
397 397  
398 -**where:**
326 +* (((
327 +Device ID: 0x724031556159 = 724031556159
328 +)))
329 +* (((
330 +Version: 0x0064=100=1.0.0
331 +)))
399 399  
400 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
333 +* (((
334 +BAT: 0x0c6c = 3180 mV = 3.180V
335 +)))
336 +* (((
337 +Signal: 0x19 = 25
338 +)))
339 +* (((
340 +Distance: 0x0292= 658 mm
341 +)))
342 +* (((
343 +Interrupt: 0x00 = 0
344 +)))
401 401  
402 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
403 403  
404 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
405 -
406 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
407 -
408 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
409 -
410 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
411 -
412 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
413 -
414 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
415 -
416 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
417 -
418 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
419 -
420 -
421 -
422 422  == 2.4  Payload Explanation and Sensor Interface ==
423 423  
349 +
424 424  === 2.4.1  Device ID ===
425 425  
426 -
427 427  (((
428 428  By default, the Device ID equal to the last 6 bytes of IMEI.
429 429  )))
... ... @@ -430,12 +430,10 @@
430 430  
431 431  (((
432 432  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
433 -
434 -
435 435  )))
436 436  
437 437  (((
438 -(% style="color:blue" %)**Example :**
361 +**Example:**
439 439  )))
440 440  
441 441  (((
... ... @@ -443,25 +443,13 @@
443 443  )))
444 444  
445 445  (((
446 -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.
369 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
447 447  )))
448 448  
449 449  
450 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
451 451  
452 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
453 -
454 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455 -
456 -
457 -(% style="color:blue" %)**Example :**
458 -
459 -AT+DEUI=868411056754138
460 -
461 -
462 462  === 2.4.2  Version Info ===
463 463  
464 -
465 465  (((
466 466  Specify the software version: 0x64=100, means firmware version 1.00.
467 467  )))
... ... @@ -471,8 +471,12 @@
471 471  )))
472 472  
473 473  
385 +
474 474  === 2.4.3  Battery Info ===
475 475  
388 +(((
389 +Check the battery voltage for LSE01.
390 +)))
476 476  
477 477  (((
478 478  Ex1: 0x0B45 = 2885mV
... ... @@ -483,9 +483,9 @@
483 483  )))
484 484  
485 485  
401 +
486 486  === 2.4.4  Signal Strength ===
487 487  
488 -
489 489  (((
490 490  NB-IoT Network signal Strength.
491 491  )))
... ... @@ -515,14 +515,12 @@
515 515  )))
516 516  
517 517  
518 -=== 2.4.5  Distance ===
519 519  
434 +=== 2.4.5  Soil Moisture ===
520 520  
521 521  Get the distance. Flat object range 280mm - 7500mm.
522 522  
523 -(((
524 524  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
525 -)))
526 526  
527 527  (((
528 528  (((
... ... @@ -534,9 +534,12 @@
534 534  
535 535  )))
536 536  
450 +(((
451 +
452 +)))
453 +
537 537  === 2.4.6  Digital Interrupt ===
538 538  
539 -
540 540  (((
541 541  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.
542 542  )))
... ... @@ -546,7 +546,7 @@
546 546  )))
547 547  
548 548  (((
549 -(% 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]])**.**
465 +(% 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]])**.**
550 550  )))
551 551  
552 552  
... ... @@ -568,9 +568,9 @@
568 568  )))
569 569  
570 570  
487 +
571 571  === 2.4.7  ​+5V Output ===
572 572  
573 -
574 574  (((
575 575  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
576 576  )))
... ... @@ -578,14 +578,10 @@
578 578  
579 579  (((
580 580  The 5V output time can be controlled by AT Command.
581 -
582 -
583 583  )))
584 584  
585 585  (((
586 586  (% style="color:blue" %)**AT+5VT=1000**
587 -
588 -
589 589  )))
590 590  
591 591  (((
... ... @@ -593,18 +593,14 @@
593 593  )))
594 594  
595 595  
508 +
596 596  == 2.5  Downlink Payload ==
597 597  
511 +By default, NSE01 prints the downlink payload to console port.
598 598  
599 -By default, NDDS75 prints the downlink payload to console port.
513 +[[image:image-20220708133731-5.png]]
600 600  
601 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
602 -|(% style="background-color:#d9e2f3; color:#0070c0; width:208px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:56px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:154px" %)**Downlink payload size(bytes)**
603 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
604 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
605 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
606 606  
607 -
608 608  (((
609 609  (% style="color:blue" %)**Examples:**
610 610  )))
... ... @@ -638,7 +638,7 @@
638 638  )))
639 639  
640 640  (((
641 -If payload = 0x04FF, it will reset the NDDS75
549 +If payload = 0x04FF, it will reset the NSE01
642 642  )))
643 643  
644 644  
... ... @@ -649,195 +649,239 @@
649 649  )))
650 650  
651 651  
652 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
653 653  
561 +== 2.6  ​LED Indicator ==
654 654  
655 -(% style="color:blue" %)** ➢ AT Command:**
563 +(((
564 +The NSE01 has an internal LED which is to show the status of different state.
656 656  
657 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
658 658  
659 -² When min=0, and max≠0, Alarm higher than max
567 +* 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)
568 +* Then the LED will be on for 1 second means device is boot normally.
569 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
570 +* For each uplink probe, LED will be on for 500ms.
571 +)))
660 660  
661 -² When min≠0, and max=0, Alarm lower than min
662 662  
663 -² When min≠0 and max≠0, Alarm higher than max or lower than min
664 664  
665 665  
666 -(% style="color:blue" %)** Example:**
576 +== 2.7  Installation in Soil ==
667 667  
668 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
578 +__**Measurement the soil surface**__
669 669  
580 +(((
581 +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]]
582 +)))
670 670  
671 -== 2.7  Set the number of data to be uploaded and the recording time ==
584 +[[image:1657259653666-883.png]] ​
672 672  
673 673  
674 -(% style="color:blue" %)** ➢ AT Command:**
587 +(((
588 +
675 675  
676 -* (% 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)
677 -* (% 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.
590 +(((
591 +Dig a hole with diameter > 20CM.
592 +)))
678 678  
679 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
594 +(((
595 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
596 +)))
597 +)))
680 680  
681 -[[image:image-20221009001114-1.png||height="687" width="955"]]
599 +[[image:1654506665940-119.png]]
682 682  
601 +(((
602 +
603 +)))
683 683  
684 -== 2.8  Read or Clear cached data ==
685 685  
606 +== 2.8  ​Firmware Change Log ==
686 686  
687 -(% style="color:blue" %)** ➢ AT Command:**
688 688  
689 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
690 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
609 +Download URL & Firmware Change log
691 691  
692 -[[image:image-20220908175333-2.png]]
611 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
693 693  
694 694  
695 -== 2.9  ​LED Indicator ==
614 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
696 696  
697 697  
698 -The NDDS75 has an internal LED which is to show the status of different state.
699 699  
618 +== 2.9  ​Battery Analysis ==
700 700  
701 -* 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)
702 -* Then the LED will be on for 1 second means device is boot normally.
703 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
704 -* For each uplink probe, LED will be on for 500ms.
620 +=== 2.9.1  ​Battery Type ===
705 705  
622 +
706 706  (((
707 -
624 +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.
708 708  )))
709 709  
710 710  
711 -== 2.10  ​Firmware Change Log ==
628 +(((
629 +The battery is designed to last for several years depends on the actually use environment and update interval. 
630 +)))
712 712  
713 713  
714 714  (((
715 -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]]
634 +The battery related documents as below:
716 716  )))
717 717  
637 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
638 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
639 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
640 +
718 718  (((
719 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
642 +[[image:image-20220708140453-6.png]]
720 720  )))
721 721  
722 722  
723 -== 2.11 Battery & Power Consumption ==
724 724  
647 +=== 2.9.2  Power consumption Analyze ===
725 725  
726 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
649 +(((
650 +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.
651 +)))
727 727  
728 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
729 729  
654 +(((
655 +Instruction to use as below:
656 +)))
730 730  
731 -= 3. ​ Access NB-IoT Module =
658 +(((
659 +(% 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/]]
660 +)))
732 732  
733 733  
734 734  (((
735 -Users can directly access the AT command set of the NB-IoT module.
664 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
736 736  )))
737 737  
667 +* (((
668 +Product Model
669 +)))
670 +* (((
671 +Uplink Interval
672 +)))
673 +* (((
674 +Working Mode
675 +)))
676 +
738 738  (((
739 -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/]] 
678 +And the Life expectation in difference case will be shown on the right.
679 +)))
740 740  
741 -
681 +[[image:image-20220708141352-7.jpeg]]
682 +
683 +
684 +
685 +=== 2.9.3  ​Battery Note ===
686 +
687 +(((
688 +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.
742 742  )))
743 743  
744 -[[image:1657333200519-600.png]]
745 745  
746 746  
747 -= 4.  Using the AT Commands =
693 +=== 2.9.4  Replace the battery ===
748 748  
749 -== 4.1  Access AT Commands ==
695 +(((
696 +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).
697 +)))
750 750  
751 751  
752 -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]]
753 753  
701 += 3. ​ Access NB-IoT Module =
754 754  
755 -AT+<CMD>?  :  Help on <CMD>
703 +(((
704 +Users can directly access the AT command set of the NB-IoT module.
705 +)))
756 756  
757 -AT+<CMD>         :  Run <CMD>
707 +(((
708 +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/]] 
709 +)))
758 758  
759 -AT+<CMD>=<value> :  Set the value
711 +[[image:1657261278785-153.png]]
760 760  
761 -AT+<CMD>=?  :  Get the value
762 762  
763 763  
764 -(% style="color:#037691" %)**General Commands**(%%)      
715 += 4.  Using the AT Commands =
765 765  
766 -AT  :  Attention       
717 +== 4.1  Access AT Commands ==
767 767  
768 -AT?  :  Short Help     
719 +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/]]
769 769  
770 -ATZ  :  MCU Reset    
771 771  
772 -AT+TDC  :  Application Data Transmission Interval
722 +AT+<CMD>?  : Help on <CMD>
773 773  
774 -AT+CFG  :  Print all configurations
724 +AT+<CMD>         : Run <CMD>
775 775  
776 -AT+CFGMOD           :  Working mode selection
726 +AT+<CMD>=<value> : Set the value
777 777  
778 -AT+INTMOD            :  Set the trigger interrupt mode
728 +AT+<CMD>=?  : Get the value
779 779  
780 -AT+5VT  :  Set extend the time of 5V power  
781 781  
782 -AT+PRO  :  Choose agreement
731 +(% style="color:#037691" %)**General Commands**(%%)      
783 783  
784 -AT+WEIGRE  :  Get weight or set weight to 0
733 +AT  : Attention       
785 785  
786 -AT+WEIGAP  :  Get or Set the GapValue of weight
735 +AT?  : Short Help     
787 787  
788 -AT+RXDL  :  Extend the sending and receiving time
737 +ATZ  : MCU Reset    
789 789  
790 -AT+CNTFAC  :  Get or set counting parameters
739 +AT+TDC  : Application Data Transmission Interval
791 791  
792 -AT+SERVADDR  :  Server Address
741 +AT+CFG  : Print all configurations
793 793  
794 -AT+TR  :  Get or Set record time"
743 +AT+CFGMOD           : Working mode selection
795 795  
796 -AT+APN     :  Get or set the APN
745 +AT+INTMOD            : Set the trigger interrupt mode
797 797  
798 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
747 +AT+5VT  : Set extend the time of 5V power  
799 799  
800 -AT+DNSCFG  : Get or Set DNS Server
749 +AT+PRO  : Choose agreement
801 801  
802 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
751 +AT+WEIGRE  : Get weight or set weight to 0
803 803  
804 -AT+NOUD  :  Get or Set the number of data to be uploaded
753 +AT+WEIGAP  : Get or Set the GapValue of weight
805 805  
806 -AT+CDP     :  Read or Clear cached data
755 +AT+RXDL  : Extend the sending and receiving time
807 807  
808 -AT+LDDSALARM :  Get or Set alarm of distance
757 +AT+CNTFAC  : Get or set counting parameters
809 809  
759 +AT+SERVADDR  : Server Address
810 810  
761 +
811 811  (% style="color:#037691" %)**COAP Management**      
812 812  
813 -AT+URI            :  Resource parameters
764 +AT+URI            : Resource parameters
814 814  
815 815  
816 816  (% style="color:#037691" %)**UDP Management**
817 817  
818 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
769 +AT+CFM          : Upload confirmation mode (only valid for UDP)
819 819  
820 820  
821 821  (% style="color:#037691" %)**MQTT Management**
822 822  
823 -AT+CLIENT  :  Get or Set MQTT client
774 +AT+CLIENT               : Get or Set MQTT client
824 824  
825 -AT+UNAME  :  Get or Set MQTT Username
776 +AT+UNAME  : Get or Set MQTT Username
826 826  
827 -AT+PWD  :  Get or Set MQTT password
778 +AT+PWD                  : Get or Set MQTT password
828 828  
829 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
780 +AT+PUBTOPIC  : Get or Set MQTT publish topic
830 830  
831 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
782 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
832 832  
833 833  
834 834  (% style="color:#037691" %)**Information**          
835 835  
836 -AT+FDR  :  Factory Data Reset
787 +AT+FDR  : Factory Data Reset
837 837  
838 -AT+PWORD  :  Serial Access Password
789 +AT+PWORD  : Serial Access Password
839 839  
840 840  
792 +
841 841  = ​5.  FAQ =
842 842  
843 843  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -852,10 +852,18 @@
852 852  )))
853 853  
854 854  (((
855 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
807 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
856 856  )))
857 857  
858 858  
811 +
812 +== 5.2  Can I calibrate NSE01 to different soil types? ==
813 +
814 +(((
815 +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]].
816 +)))
817 +
818 +
859 859  = 6.  Trouble Shooting =
860 860  
861 861  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -870,26 +870,27 @@
870 870  
871 871  )))
872 872  
833 +
873 873  == 6.2  AT Command input doesn't work ==
874 874  
875 -
876 876  (((
877 877  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.
838 +
839 +
878 878  )))
879 879  
880 880  
881 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
882 -
883 -
884 -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]]//**.
885 -
886 -
887 887  = 7. ​ Order Info =
888 888  
889 889  
890 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
846 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
891 891  
892 892  
849 +(% class="wikigeneratedid" %)
850 +(((
851 +
852 +)))
853 +
893 893  = 8.  Packing Info =
894 894  
895 895  (((
... ... @@ -897,7 +897,7 @@
897 897  
898 898  (% style="color:#037691" %)**Package Includes**:
899 899  
900 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
861 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
901 901  * External antenna x 1
902 902  )))
903 903  
... ... @@ -906,21 +906,18 @@
906 906  
907 907  (% style="color:#037691" %)**Dimension and weight**:
908 908  
909 -* Device Size: 13.0 x 5 x 4.5 cm
910 -* Device Weight: 150g
911 -* Package Size / pcs : 15 x 12x 5.5 cm
912 -* Weight / pcs : 220g
870 +* Size: 195 x 125 x 55 mm
871 +* Weight:   420g
913 913  )))
914 914  
915 915  (((
916 916  
917 917  
877 +
918 918  
919 919  )))
920 920  
921 921  = 9.  Support =
922 922  
923 -
924 924  * 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.
925 -
926 926  * 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]]
1657332990863-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -611.5 KB
Content
image-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content