Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 83.1
edited by Xiaoling
on 2022/07/09 09:34
Change comment: Uploaded new attachment "1657330452568-615.png", version {1}
To version 108.11
edited by Xiaoling
on 2023/04/04 13:39
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,17 +83,16 @@
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
90 -* Max transmit power: 350mA@3.3v
102 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
91 91  
92 92  
93 93  
94 -
95 95  == ​1.4  Applications ==
96 96  
108 +
97 97  * Smart Buildings & Home Automation
98 98  * Logistics and Supply Chain Management
99 99  * Smart Metering
... ... @@ -105,7 +105,6 @@
105 105  ​
106 106  
107 107  
108 -
109 109  == 1.5  Pin Definitions ==
110 110  
111 111  
... ... @@ -112,12 +112,11 @@
112 112  [[image:1657328609906-564.png]]
113 113  
114 114  
115 -
116 -
117 117  = 2.  Use NDDS75 to communicate with IoT Server =
118 118  
119 119  == 2.1  How it works ==
120 120  
130 +
121 121  (((
122 122  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.
123 123  )))
... ... @@ -137,22 +137,21 @@
137 137  
138 138  )))
139 139  
140 -
141 141  == 2.2 ​ Configure the NDDS75 ==
142 142  
143 -
144 144  === 2.2.1 Test Requirement ===
145 145  
154 +
146 146  (((
147 147  To use NDDS75 in your city, make sure meet below requirements:
148 148  )))
149 149  
150 150  * Your local operator has already distributed a NB-IoT Network there.
151 -* The local NB-IoT network used the band that NSE01 supports.
160 +* The local NB-IoT network used the band that NDDS75 supports.
152 152  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
153 153  
154 154  (((
155 -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
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.
156 156  )))
157 157  
158 158  
... ... @@ -159,9 +159,9 @@
159 159  [[image:1657328756309-230.png]]
160 160  
161 161  
162 -
163 163  === 2.2.2 Insert SIM card ===
164 164  
173 +
165 165  (((
166 166  Insert the NB-IoT Card get from your provider.
167 167  )))
... ... @@ -174,9 +174,9 @@
174 174  [[image:1657328884227-504.png]]
175 175  
176 176  
177 -
178 178  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
179 179  
188 +
180 180  (((
181 181  (((
182 182  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.
... ... @@ -185,15 +185,16 @@
185 185  
186 186  [[image:image-20220709092052-2.png]]
187 187  
188 -**Connection:**
189 189  
190 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
198 +(% style="color:blue" %)**Connection:**
191 191  
192 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
200 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
193 193  
194 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
202 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
195 195  
204 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
196 196  
206 +
197 197  In the PC, use below serial tool settings:
198 198  
199 199  * Baud:  (% style="color:green" %)**9600**
... ... @@ -208,67 +208,82 @@
208 208  
209 209  [[image:1657329814315-101.png]]
210 210  
221 +
211 211  (((
212 -(% 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/]]
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]]**
213 213  )))
214 214  
215 215  
216 -
217 217  === 2.2.4 Use CoAP protocol to uplink data ===
218 218  
219 -(% 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/]]
220 220  
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/]]**
221 221  
232 +
233 +(((
222 222  **Use below commands:**
235 +)))
223 223  
224 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
225 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
226 -* (% 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
227 227  
246 +
247 +
248 +)))
249 +
250 +(((
228 228  For parameter description, please refer to AT command set
229 229  
230 -[[image:1657249793983-486.png]]
253 +
254 +)))
231 231  
256 +[[image:1657330452568-615.png]]
232 232  
233 -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.
234 234  
235 -[[image:1657249831934-534.png]]
236 236  
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.
237 237  
263 +
264 +)))
238 238  
239 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
266 +[[image:1657330472797-498.png]]
240 240  
241 -This feature is supported since firmware version v1.0.1
242 242  
269 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
243 243  
244 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
245 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
246 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
247 247  
248 -[[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
249 249  
276 +[[image:1657330501006-241.png]]
250 250  
251 -[[image:1657249930215-289.png]]
252 252  
279 +[[image:1657330533775-472.png]]
253 253  
254 254  
255 255  === 2.2.6 Use MQTT protocol to uplink data ===
256 256  
257 -This feature is supported since firmware version v110
258 258  
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
259 259  
260 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
261 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
262 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
263 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
264 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
265 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
266 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
267 -
268 268  [[image:1657249978444-674.png]]
269 269  
270 270  
271 -[[image:1657249990869-686.png]]
296 +[[image:1657330723006-866.png]]
272 272  
273 273  
274 274  (((
... ... @@ -276,75 +276,129 @@
276 276  )))
277 277  
278 278  
279 -
280 280  === 2.2.7 Use TCP protocol to uplink data ===
281 281  
282 -This feature is supported since firmware version v110
283 283  
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
284 284  
285 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
286 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
310 +[[image:image-20220709093918-1.png]]
287 287  
288 -[[image:1657250217799-140.png]]
289 289  
313 +[[image:image-20220709093918-2.png]]
290 290  
291 -[[image:1657250255956-604.png]]
292 292  
293 -
294 -
295 295  === 2.2.8 Change Update Interval ===
296 296  
318 +
297 297  User can use below command to change the (% style="color:green" %)**uplink interval**.
298 298  
299 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
321 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
300 300  
301 301  (((
324 +
325 +
326 +
302 302  (% style="color:red" %)**NOTE:**
303 -)))
304 304  
305 -(((
306 -(% 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:**
307 307  )))
308 308  
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).**
309 309  
310 310  
311 311  == 2.3  Uplink Payload ==
312 312  
313 -In this mode, uplink payload includes in total 18 bytes
339 +=== 2.3.1  Before Firmware v1.3.2 ===
314 314  
315 -(% 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" %)
316 316  |=(% style="width: 60px;" %)(((
317 317  **Size(bytes)**
318 -)))|=(% 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**
319 -|(% 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"]]
320 320  
321 321  (((
322 -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.
323 323  )))
324 324  
325 325  
326 -[[image:image-20220708111918-4.png]]
355 +[[image:1657331036973-987.png]]
327 327  
328 328  
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" style="background-color:#ffffcc; color:green; width:490px" %)
386 +|=(% 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**
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 +
329 329  The payload is ASCII string, representative same HEX:
330 330  
331 -0x72403155615900640c7817075e0a8c02f900 where:
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 (%%)**
332 332  
333 -* Device ID: 0x 724031556159 = 724031556159
334 -* Version: 0x0064=100=1.0.0
398 +**where:**
335 335  
336 -* BAT: 0x0c78 = 3192 mV = 3.192V
337 -* Singal: 0x17 = 23
338 -* Soil Moisture: 0x075e= 1886 = 18.86  %
339 -* Soil Temperature:0x0a8c =2700=27 °C
340 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
341 -* Interrupt: 0x00 = 0
400 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
342 342  
343 -== 2.4  Payload Explanation and Sensor Interface ==
402 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
344 344  
404 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
345 345  
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 +== 2.4  Payload Explanation and Sensor Interface ==
423 +
346 346  === 2.4.1  Device ID ===
347 347  
426 +
348 348  (((
349 349  By default, the Device ID equal to the last 6 bytes of IMEI.
350 350  )))
... ... @@ -351,10 +351,12 @@
351 351  
352 352  (((
353 353  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
433 +
434 +
354 354  )))
355 355  
356 356  (((
357 -**Example:**
438 +(% style="color:blue" %)**Example :**
358 358  )))
359 359  
360 360  (((
... ... @@ -362,28 +362,36 @@
362 362  )))
363 363  
364 364  (((
365 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
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.
366 366  )))
367 367  
368 368  
450 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
369 369  
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 +
370 370  === 2.4.2  Version Info ===
371 371  
464 +
372 372  (((
373 373  Specify the software version: 0x64=100, means firmware version 1.00.
374 374  )))
375 375  
376 376  (((
377 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
470 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
378 378  )))
379 379  
380 380  
381 -
382 382  === 2.4.3  Battery Info ===
383 383  
384 -(((
385 -Check the battery voltage for LSE01.
386 -)))
387 387  
388 388  (((
389 389  Ex1: 0x0B45 = 2885mV
... ... @@ -394,9 +394,9 @@
394 394  )))
395 395  
396 396  
397 -
398 398  === 2.4.4  Signal Strength ===
399 399  
488 +
400 400  (((
401 401  NB-IoT Network signal Strength.
402 402  )))
... ... @@ -426,77 +426,30 @@
426 426  )))
427 427  
428 428  
518 +=== 2.4.5  Distance ===
429 429  
430 -=== 2.4.5  Soil Moisture ===
431 431  
432 -(((
433 -(((
434 -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.
435 -)))
436 -)))
521 +Get the distance. Flat object range 280mm - 7500mm.
437 437  
438 438  (((
439 -(((
440 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
524 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
441 441  )))
442 -)))
443 443  
444 444  (((
445 -
446 -)))
447 -
448 448  (((
449 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
529 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
450 450  )))
451 -
452 -
453 -
454 -=== 2.4.6  Soil Temperature ===
455 -
456 -(((
457 -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
458 458  )))
459 459  
460 460  (((
461 -**Example**:
462 -)))
463 -
464 -(((
465 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
466 -)))
467 -
468 -(((
469 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
470 -)))
471 -
472 -
473 -
474 -=== 2.4.7  Soil Conductivity (EC) ===
475 -
476 -(((
477 -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).
478 -)))
479 -
480 -(((
481 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
482 -)))
483 -
484 -(((
485 -Generally, the EC value of irrigation water is less than 800uS / cm.
486 -)))
487 -
488 -(((
489 489  
490 490  )))
491 491  
492 -(((
493 -
494 -)))
537 +=== 2.4.6  Digital Interrupt ===
495 495  
496 -=== 2.4.8  Digital Interrupt ===
497 497  
498 498  (((
499 -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.
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.
500 500  )))
501 501  
502 502  (((
... ... @@ -504,7 +504,7 @@
504 504  )))
505 505  
506 506  (((
507 -(% 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]])**.**
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]])**.**
508 508  )))
509 509  
510 510  
... ... @@ -526,20 +526,24 @@
526 526  )))
527 527  
528 528  
571 +=== 2.4.7  ​+5V Output ===
529 529  
530 -=== 2.4.9  ​+5V Output ===
531 531  
532 532  (((
533 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
575 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
534 534  )))
535 535  
536 536  
537 537  (((
538 538  The 5V output time can be controlled by AT Command.
581 +
582 +
539 539  )))
540 540  
541 541  (((
542 542  (% style="color:blue" %)**AT+5VT=1000**
587 +
588 +
543 543  )))
544 544  
545 545  (((
... ... @@ -547,14 +547,14 @@
547 547  )))
548 548  
549 549  
550 -
551 551  == 2.5  Downlink Payload ==
552 552  
553 -By default, NSE01 prints the downlink payload to console port.
554 554  
555 -[[image:image-20220708133731-5.png]]
599 +By default, NDDS75 prints the downlink payload to console port.
556 556  
601 +[[image:image-20220709100028-1.png]]
557 557  
603 +
558 558  (((
559 559  (% style="color:blue" %)**Examples:**
560 560  )))
... ... @@ -588,7 +588,7 @@
588 588  )))
589 589  
590 590  (((
591 -If payload = 0x04FF, it will reset the NSE01
637 +If payload = 0x04FF, it will reset the NDDS75
592 592  )))
593 593  
594 594  
... ... @@ -599,239 +599,195 @@
599 599  )))
600 600  
601 601  
648 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
602 602  
603 -== 2.6  ​LED Indicator ==
604 604  
605 -(((
606 -The NSE01 has an internal LED which is to show the status of different state.
651 +(% style="color:blue" %)** ➢ AT Command:**
607 607  
653 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
608 608  
609 -* 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)
610 -* Then the LED will be on for 1 second means device is boot normally.
611 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
612 -* For each uplink probe, LED will be on for 500ms.
613 -)))
655 +² When min=0, and max≠0, Alarm higher than max
614 614  
657 +² When min≠0, and max=0, Alarm lower than min
615 615  
659 +² When min≠0 and max≠0, Alarm higher than max or lower than min
616 616  
617 617  
618 -== 2.7  Installation in Soil ==
662 +(% style="color:blue" %)** Example:**
619 619  
620 -__**Measurement the soil surface**__
664 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
621 621  
622 -(((
623 -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]]
624 -)))
625 625  
626 -[[image:1657259653666-883.png]] ​
667 +== 2.7  Set the number of data to be uploaded and the recording time ==
627 627  
628 628  
629 -(((
630 -
670 +(% style="color:blue" %)** ➢ AT Command:**
631 631  
632 -(((
633 -Dig a hole with diameter > 20CM.
634 -)))
672 +* (% 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)
673 +* (% 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.
635 635  
636 -(((
637 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
638 -)))
639 -)))
675 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
640 640  
641 -[[image:1654506665940-119.png]]
677 +[[image:image-20221009001114-1.png||height="687" width="955"]]
642 642  
643 -(((
644 -
645 -)))
646 646  
680 +== 2.8  Read or Clear cached data ==
647 647  
648 -== 2.8  ​Firmware Change Log ==
649 649  
683 +(% style="color:blue" %)** ➢ AT Command:**
650 650  
651 -Download URL & Firmware Change log
685 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
686 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
652 652  
653 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
688 +[[image:image-20220908175333-2.png]]
654 654  
655 655  
656 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
691 +== 2.9  ​LED Indicator ==
657 657  
658 658  
694 +The NDDS75 has an internal LED which is to show the status of different state.
659 659  
660 -== 2.9  ​Battery Analysis ==
661 661  
662 -=== 2.9.1  ​Battery Type ===
697 +* 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)
698 +* Then the LED will be on for 1 second means device is boot normally.
699 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
700 +* For each uplink probe, LED will be on for 500ms.
663 663  
664 -
665 665  (((
666 -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.
703 +
667 667  )))
668 668  
669 669  
670 -(((
671 -The battery is designed to last for several years depends on the actually use environment and update interval. 
672 -)))
707 +== 2.10  ​Firmware Change Log ==
673 673  
674 674  
675 675  (((
676 -The battery related documents as below:
711 +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]]
677 677  )))
678 678  
679 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
680 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
681 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
682 -
683 683  (((
684 -[[image:image-20220708140453-6.png]]
715 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
685 685  )))
686 686  
687 687  
719 +== 2.11 Battery & Power Consumption ==
688 688  
689 -=== 2.9.2  Power consumption Analyze ===
690 690  
691 -(((
692 -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.
693 -)))
722 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
694 694  
724 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
695 695  
696 -(((
697 -Instruction to use as below:
698 -)))
699 699  
700 -(((
701 -(% 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/]]
702 -)))
727 += 3. ​ Access NB-IoT Module =
703 703  
704 704  
705 705  (((
706 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
731 +Users can directly access the AT command set of the NB-IoT module.
707 707  )))
708 708  
709 -* (((
710 -Product Model
711 -)))
712 -* (((
713 -Uplink Interval
714 -)))
715 -* (((
716 -Working Mode
717 -)))
718 -
719 719  (((
720 -And the Life expectation in difference case will be shown on the right.
721 -)))
735 +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/]] 
722 722  
723 -[[image:image-20220708141352-7.jpeg]]
724 -
725 -
726 -
727 -=== 2.9.3  ​Battery Note ===
728 -
729 -(((
730 -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.
737 +
731 731  )))
732 732  
740 +[[image:1657333200519-600.png]]
733 733  
734 734  
735 -=== 2.9.4  Replace the battery ===
743 += 4.  Using the AT Commands =
736 736  
737 -(((
738 -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).
739 -)))
745 +== 4.1  Access AT Commands ==
740 740  
741 741  
748 +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]]
742 742  
743 -= 3. ​ Access NB-IoT Module =
744 744  
745 -(((
746 -Users can directly access the AT command set of the NB-IoT module.
747 -)))
751 +AT+<CMD>?  :  Help on <CMD>
748 748  
749 -(((
750 -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/]] 
751 -)))
753 +AT+<CMD>         :  Run <CMD>
752 752  
753 -[[image:1657261278785-153.png]]
755 +AT+<CMD>=<value> :  Set the value
754 754  
757 +AT+<CMD>=?  :  Get the value
755 755  
756 756  
757 -= 4.  Using the AT Commands =
760 +(% style="color:#037691" %)**General Commands**(%%)      
758 758  
759 -== 4.1  Access AT Commands ==
762 +AT  :  Attention       
760 760  
761 -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/]]
764 +AT?  :  Short Help     
762 762  
766 +ATZ  :  MCU Reset    
763 763  
764 -AT+<CMD>?  : Help on <CMD>
768 +AT+TDC  :  Application Data Transmission Interval
765 765  
766 -AT+<CMD>         : Run <CMD>
770 +AT+CFG  :  Print all configurations
767 767  
768 -AT+<CMD>=<value> : Set the value
772 +AT+CFGMOD           :  Working mode selection
769 769  
770 -AT+<CMD>=?  : Get the value
774 +AT+INTMOD            :  Set the trigger interrupt mode
771 771  
776 +AT+5VT  :  Set extend the time of 5V power  
772 772  
773 -(% style="color:#037691" %)**General Commands**(%%)      
778 +AT+PRO  :  Choose agreement
774 774  
775 -AT  : Attention       
780 +AT+WEIGRE  :  Get weight or set weight to 0
776 776  
777 -AT?  : Short Help     
782 +AT+WEIGAP  :  Get or Set the GapValue of weight
778 778  
779 -ATZ  : MCU Reset    
784 +AT+RXDL  :  Extend the sending and receiving time
780 780  
781 -AT+TDC  : Application Data Transmission Interval
786 +AT+CNTFAC  :  Get or set counting parameters
782 782  
783 -AT+CFG  : Print all configurations
788 +AT+SERVADDR  :  Server Address
784 784  
785 -AT+CFGMOD           : Working mode selection
790 +AT+TR  :  Get or Set record time"
786 786  
787 -AT+INTMOD            : Set the trigger interrupt mode
792 +AT+APN     :  Get or set the APN
788 788  
789 -AT+5VT  : Set extend the time of 5V power  
794 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
790 790  
791 -AT+PRO  : Choose agreement
796 +AT+DNSCFG  : Get or Set DNS Server
792 792  
793 -AT+WEIGRE  : Get weight or set weight to 0
798 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
794 794  
795 -AT+WEIGAP  : Get or Set the GapValue of weight
800 +AT+NOUD  :  Get or Set the number of data to be uploaded
796 796  
797 -AT+RXDL  : Extend the sending and receiving time
802 +AT+CDP     :  Read or Clear cached data
798 798  
799 -AT+CNTFAC  : Get or set counting parameters
804 +AT+LDDSALARM :  Get or Set alarm of distance
800 800  
801 -AT+SERVADDR  : Server Address
802 802  
803 -
804 804  (% style="color:#037691" %)**COAP Management**      
805 805  
806 -AT+URI            : Resource parameters
809 +AT+URI            :  Resource parameters
807 807  
808 808  
809 809  (% style="color:#037691" %)**UDP Management**
810 810  
811 -AT+CFM          : Upload confirmation mode (only valid for UDP)
814 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
812 812  
813 813  
814 814  (% style="color:#037691" %)**MQTT Management**
815 815  
816 -AT+CLIENT               : Get or Set MQTT client
819 +AT+CLIENT  :  Get or Set MQTT client
817 817  
818 -AT+UNAME  : Get or Set MQTT Username
821 +AT+UNAME  :  Get or Set MQTT Username
819 819  
820 -AT+PWD                  : Get or Set MQTT password
823 +AT+PWD  :  Get or Set MQTT password
821 821  
822 -AT+PUBTOPIC  : Get or Set MQTT publish topic
825 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
823 823  
824 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
827 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
825 825  
826 826  
827 827  (% style="color:#037691" %)**Information**          
828 828  
829 -AT+FDR  : Factory Data Reset
832 +AT+FDR  :  Factory Data Reset
830 830  
831 -AT+PWORD  : Serial Access Password
834 +AT+PWORD  :  Serial Access Password
832 832  
833 833  
834 -
835 835  = ​5.  FAQ =
836 836  
837 837  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -846,18 +846,10 @@
846 846  )))
847 847  
848 848  (((
849 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
851 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
850 850  )))
851 851  
852 852  
853 -
854 -== 5.2  Can I calibrate NSE01 to different soil types? ==
855 -
856 -(((
857 -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]].
858 -)))
859 -
860 -
861 861  = 6.  Trouble Shooting =
862 862  
863 863  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -872,13 +872,11 @@
872 872  
873 873  )))
874 874  
875 -
876 876  == 6.2  AT Command input doesn't work ==
877 877  
871 +
878 878  (((
879 879  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.
880 -
881 -
882 882  )))
883 883  
884 884  
... ... @@ -885,14 +885,9 @@
885 885  = 7. ​ Order Info =
886 886  
887 887  
888 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
880 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
889 889  
890 890  
891 -(% class="wikigeneratedid" %)
892 -(((
893 -
894 -)))
895 -
896 896  = 8.  Packing Info =
897 897  
898 898  (((
... ... @@ -900,7 +900,7 @@
900 900  
901 901  (% style="color:#037691" %)**Package Includes**:
902 902  
903 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
890 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
904 904  * External antenna x 1
905 905  )))
906 906  
... ... @@ -909,18 +909,20 @@
909 909  
910 910  (% style="color:#037691" %)**Dimension and weight**:
911 911  
912 -* Size: 195 x 125 x 55 mm
913 -* Weight:   420g
899 +* Device Size: 13.0 x 5 x 4.5 cm
900 +* Device Weight: 150g
901 +* Package Size / pcs : 15 x 12x 5.5 cm
902 +* Weight / pcs : 220g
914 914  )))
915 915  
916 916  (((
917 917  
918 918  
919 -
920 920  
921 921  )))
922 922  
923 923  = 9.  Support =
924 924  
913 +
925 925  * 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.
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]]
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-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