Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 65.12
edited by Xiaoling
on 2022/07/08 15:49
Change comment: There is no comment for this version
To version 104.4
edited by Xiaoling
on 2022/09/09 11:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual
1 +NDDS75 NB-IoT Distance Detect Sensor User Manual
Content
... ... @@ -1,16 +1,10 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220606151504-2.jpeg||height="554" width="554"]]
2 +[[image:image-20220709085040-1.png||height="542" width="524"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -
9 -
10 -
11 -
12 -
13 -
14 14  **Table of Contents:**
15 15  
16 16  {{toc/}}
... ... @@ -20,56 +20,63 @@
20 20  
21 21  
22 22  
23 -
24 24  = 1.  Introduction =
25 25  
26 -== 1.1 ​ What is LoRaWAN Soil Moisture & EC Sensor ==
27 27  
20 +== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21 +
28 28  (((
29 29  
30 30  
31 31  (((
32 -Dragino NSE01 is an (% style="color:blue" %)**NB-IOT soil moisture & EC sensor**(%%) for agricultural IoT. Used to measure the soil moisture of saline-alkali soil and loam. The soil sensor uses the FDR method to calculate soil moisture and compensates it with soil temperature and electrical conductivity. It has also been calibrated for mineral soil types at the factory.
26 +(((
27 +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.
33 33  )))
34 34  
35 35  (((
36 -It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
31 +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.
37 37  )))
38 38  
39 39  (((
40 -The wireless technology used in NSE01 allows the device to send data at a low data rate and reach ultra-long distances, providing ultra-long-distance spread spectrum Communication.
35 +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.
41 41  )))
42 42  
43 43  (((
44 -NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.  
39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
45 45  )))
46 46  
47 -
42 +(((
43 +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)
48 48  )))
49 49  
50 -[[image:1654503236291-817.png]]
46 +(((
47 +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.
48 +)))
49 +)))
51 51  
51 +
52 +)))
52 52  
53 -[[image:1657245163077-232.png]]
54 +[[image:1657327959271-447.png]]
54 54  
55 55  
56 56  
57 57  == 1.2 ​ Features ==
58 58  
60 +
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 -* Monitor Soil Moisture
61 -* Monitor Soil Temperature
62 -* Monitor Soil Conductivity
62 +* Ultra low power consumption
63 +* Distance Detection by Ultrasonic technology
64 +* Flat object range 280mm - 7500mm
65 +* Accuracy: ±(1cm+S*0.3%) (S: Distance)
66 +* Cable Length: 25cm
63 63  * AT Commands to change parameters
64 64  * Uplink on periodically
65 65  * Downlink to change configure
66 66  * IP66 Waterproof Enclosure
67 -* Ultra-Low Power consumption
68 -* AT Commands to change parameters
69 69  * Micro SIM card slot for NB-IoT SIM
70 70  * 8500mAh Battery for long term use
71 71  
72 -
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -87,75 +87,94 @@
87 87  * - B20 @H-FDD: 800MHz
88 88  * - B28 @H-FDD: 700MHz
89 89  
90 -Probe(% style="color:#037691" %)** Specification:**
91 +(% style="color:#037691" %)**Battery:**
91 91  
92 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
93 +* Li/SOCI2 un-chargeable battery
94 +* Capacity: 8500mAh
95 +* Self Discharge: <1% / Year @ 25°C
96 +* Max continuously current: 130mA
97 +* Max boost current: 2A, 1 second
93 93  
94 -[[image:image-20220708101224-1.png]]
99 +(% style="color:#037691" %)**Power Consumption**
95 95  
101 +* STOP Mode: 10uA @ 3.3v
102 +* Max transmit power: 350mA@3.3v
96 96  
97 -
98 98  == ​1.4  Applications ==
99 99  
106 +
107 +* Smart Buildings & Home Automation
108 +* Logistics and Supply Chain Management
109 +* Smart Metering
100 100  * Smart Agriculture
111 +* Smart Cities
112 +* Smart Factory
101 101  
102 102  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
103 103  ​
104 104  
117 +
118 +
119 +
105 105  == 1.5  Pin Definitions ==
106 106  
107 107  
108 -[[image:1657246476176-652.png]]
123 +[[image:1657328609906-564.png]]
109 109  
110 110  
111 111  
112 -= 2.  Use NSE01 to communicate with IoT Server =
127 += 2.  Use NDDS75 to communicate with IoT Server =
113 113  
129 +
114 114  == 2.1  How it works ==
115 115  
116 116  
117 117  (((
118 -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.
134 +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.
119 119  )))
120 120  
121 121  
122 122  (((
123 -The diagram below shows the working flow in default firmware of NSE01:
139 +The diagram below shows the working flow in default firmware of NDDS75:
124 124  )))
125 125  
126 -[[image:image-20220708101605-2.png]]
127 -
128 128  (((
129 129  
130 130  )))
131 131  
146 +[[image:1657328659945-416.png]]
132 132  
148 +(((
149 +
150 +)))
133 133  
134 -== 2.2 ​ Configure the NSE01 ==
135 135  
153 +== 2.2 ​ Configure the NDDS75 ==
136 136  
155 +
137 137  === 2.2.1 Test Requirement ===
138 138  
139 139  
140 140  (((
141 -To use NSE01 in your city, make sure meet below requirements:
160 +To use NDDS75 in your city, make sure meet below requirements:
142 142  )))
143 143  
144 144  * Your local operator has already distributed a NB-IoT Network there.
145 -* The local NB-IoT network used the band that NSE01 supports.
164 +* The local NB-IoT network used the band that NDDS75 supports.
146 146  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
147 147  
148 148  (((
149 -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
168 +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 150  )))
151 151  
152 152  
153 -[[image:1657249419225-449.png]]
172 +[[image:1657328756309-230.png]]
154 154  
155 155  
156 156  
157 157  === 2.2.2 Insert SIM card ===
158 158  
178 +
159 159  (((
160 160  Insert the NB-IoT Card get from your provider.
161 161  )))
... ... @@ -165,19 +165,22 @@
165 165  )))
166 166  
167 167  
168 -[[image:1657249468462-536.png]]
188 +[[image:1657328884227-504.png]]
169 169  
170 170  
171 171  
172 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
192 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
173 173  
194 +
174 174  (((
175 175  (((
176 -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.
197 +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.
177 177  )))
178 178  )))
179 179  
201 +[[image:image-20220709092052-2.png]]
180 180  
203 +
181 181  **Connection:**
182 182  
183 183   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -196,13 +196,14 @@
196 196  * Flow Control: (% style="color:green" %)**None**
197 197  
198 198  (((
199 -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.
222 +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.
200 200  )))
201 201  
202 -[[image:image-20220708110657-3.png]]
225 +[[image:1657329814315-101.png]]
203 203  
227 +
204 204  (((
205 -(% 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/]]
229 +(% 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]]**
206 206  )))
207 207  
208 208  
... ... @@ -209,59 +209,76 @@
209 209  
210 210  === 2.2.4 Use CoAP protocol to uplink data ===
211 211  
212 -(% 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/]]
213 213  
237 +(% 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/]]**
214 214  
239 +
240 +(((
215 215  **Use below commands:**
242 +)))
216 216  
217 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
218 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
219 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
244 +* (((
245 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
246 +)))
247 +* (((
248 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
249 +)))
250 +* (((
251 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
220 220  
253 +
254 +
255 +)))
256 +
257 +(((
221 221  For parameter description, please refer to AT command set
222 222  
223 -[[image:1657249793983-486.png]]
260 +
261 +)))
224 224  
263 +[[image:1657330452568-615.png]]
225 225  
226 -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.
227 227  
228 -[[image:1657249831934-534.png]]
229 229  
267 +(((
268 +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.
230 230  
270 +
271 +)))
231 231  
232 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
273 +[[image:1657330472797-498.png]]
233 233  
234 -This feature is supported since firmware version v1.0.1
235 235  
236 236  
237 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
277 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
278 +
279 +
280 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
238 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
282 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
240 240  
241 -[[image:1657249864775-321.png]]
284 +[[image:1657330501006-241.png]]
242 242  
243 243  
244 -[[image:1657249930215-289.png]]
287 +[[image:1657330533775-472.png]]
245 245  
246 246  
247 247  
248 248  === 2.2.6 Use MQTT protocol to uplink data ===
249 249  
250 -This feature is supported since firmware version v110
251 251  
294 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
295 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
296 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
297 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
298 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
299 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
300 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
252 252  
253 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
254 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
255 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
256 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
257 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
258 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
259 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
260 -
261 261  [[image:1657249978444-674.png]]
262 262  
263 263  
264 -[[image:1657249990869-686.png]]
305 +[[image:1657330723006-866.png]]
265 265  
266 266  
267 267  (((
... ... @@ -272,178 +272,244 @@
272 272  
273 273  === 2.2.7 Use TCP protocol to uplink data ===
274 274  
275 -This feature is supported since firmware version v110
276 276  
277 -
278 278  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
279 279  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
280 280  
281 -[[image:1657250217799-140.png]]
320 +[[image:image-20220709093918-1.png]]
282 282  
283 283  
284 -[[image:1657250255956-604.png]]
323 +[[image:image-20220709093918-2.png]]
285 285  
286 286  
287 287  
288 288  === 2.2.8 Change Update Interval ===
289 289  
329 +
290 290  User can use below command to change the (% style="color:green" %)**uplink interval**.
291 291  
292 292  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
293 293  
294 294  (((
335 +
336 +
337 +
295 295  (% style="color:red" %)**NOTE:**
296 -)))
297 297  
298 -(((
299 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
340 +(% style="color:red" %)**1: By default, the device will send an uplink message every 1 hour.**
341 +
342 +(% style="color:red" %)**2: When the firmware version is v1.3.2 and later firmware:**
300 300  )))
301 301  
345 +(% 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).**
302 302  
303 303  
348 +
304 304  == 2.3  Uplink Payload ==
305 305  
306 -In this mode, uplink payload includes in total 18 bytes
307 307  
308 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
352 +=== 2.3.1  Before Firmware 1.3.2 ===
353 +
354 +
355 +In this mode, uplink payload includes in total 14 bytes
356 +
357 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
309 309  |=(% style="width: 60px;" %)(((
310 310  **Size(bytes)**
311 -)))|=(% 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**
312 -|(% 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"]]
360 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
361 +|(% 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"]]
313 313  
314 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
363 +(((
364 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
365 +)))
315 315  
316 316  
317 -[[image:image-20220708111918-4.png]]
368 +[[image:1657331036973-987.png]]
318 318  
319 319  
320 -The payload is ASCII string, representative same HEX:
371 +(((
372 +The payload is **ASCII** string, representative same HEX:
373 +)))
321 321  
322 -0x72403155615900640c7817075e0a8c02f900 where:
375 +(((
376 +0x72403155615900640c6c19029200 where:
377 +)))
323 323  
324 -* Device ID: 0x 724031556159 = 724031556159
325 -* Version: 0x0064=100=1.0.0
379 +* (((
380 +Device ID: 0x724031556159 = 724031556159
381 +)))
382 +* (((
383 +Version:  0x0064=100=1.0.0
384 +)))
326 326  
327 -* BAT: 0x0c78 = 3192 mV = 3.192V
328 -* Singal: 0x17 = 23
329 -* Soil Moisture: 0x075e= 1886 = 18.86  %
330 -* Soil Temperature:0x0a8c =2700=27 °C
331 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
332 -* Interrupt: 0x00 = 0
386 +* (((
387 +BAT:  0x0c6c = 3180 mV = 3.180V
388 +)))
389 +* (((
390 +Signal: 0x19 = 25
391 +)))
392 +* (((
393 +Distance: 0x0292= 658 mm
394 +)))
395 +* (((
396 +Interrupt: 0x00 = 0
333 333  
334 334  
335 -== 2.4  Payload Explanation and Sensor Interface ==
336 336  
337 337  
338 -=== 2.4.1  Device ID ===
401 +
402 +)))
339 339  
340 -By default, the Device ID equal to the last 6 bytes of IMEI.
404 +=== **2.3.2  Since firmware v1.3.2** ===
341 341  
342 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
343 343  
344 -**Example:**
407 +In this mode, uplink payload includes 69 bytes in total by default.
345 345  
346 -AT+DEUI=A84041F15612
409 +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.
347 347  
348 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
411 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
412 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
413 +|(% 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.......
349 349  
415 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
350 350  
417 +[[image:image-20220908175246-1.png]]
351 351  
352 -=== 2.4.2  Version Info ===
353 353  
354 -Specify the software version: 0x64=100, means firmware version 1.00.
420 +The payload is ASCII string, representative same HEX:
355 355  
356 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
422 +0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
357 357  
424 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
425 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
426 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
427 +* (% style="color:blue" %)Singal: 0x1e = 30
428 +* (% style="color:red" %)Mod: 0x01 = 1
429 +* Interrupt: 0x00= 0
430 +* Distance: 0x0039= 57 = 57
431 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
432 +* Distance,Time stamp : 00396319baf0
433 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
358 358  
359 359  
360 -=== 2.4.3  Battery Info ===
361 361  
437 +
438 +
439 +== 2.4  Payload Explanation and Sensor Interface ==
440 +
441 +
442 +=== 2.4.1  Device ID ===
443 +
444 +
362 362  (((
363 -Check the battery voltage for LSE01.
446 +By default, the Device ID equal to the last 6 bytes of IMEI.
364 364  )))
365 365  
366 366  (((
367 -Ex1: 0x0B45 = 2885mV
450 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
451 +
452 +
368 368  )))
369 369  
370 370  (((
371 -Ex2: 0x0B49 = 2889mV
456 +(% style="color:blue" %)**Example :**
372 372  )))
373 373  
459 +(((
460 +AT+DEUI=A84041F15612
461 +)))
374 374  
463 +(((
464 +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.
465 +)))
375 375  
376 -=== 2.4.4  Signal Strength ===
377 377  
378 -NB-IoT Network signal Strength.
468 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
379 379  
380 -**Ex1: 0x1d = 29**
470 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
381 381  
382 -(% style="color:blue" %)**0**(%%)  -113dBm or less
472 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
383 383  
384 -(% style="color:blue" %)**1**(%%)  -111dBm
385 385  
386 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
475 +(% style="color:blue" %)**Example :**
387 387  
388 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
477 +AT+DEUI=868411056754138
389 389  
390 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
391 391  
392 392  
481 +=== 2.4.2  Version Info ===
393 393  
394 -=== 2.4.5  Soil Moisture ===
395 395  
396 396  (((
397 -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.
485 +Specify the software version: 0x64=100, means firmware version 1.00.
398 398  )))
399 399  
400 400  (((
401 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
489 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
402 402  )))
403 403  
492 +
493 +
494 +=== 2.4.3  Battery Info ===
495 +
496 +
404 404  (((
405 -
498 +Ex1: 0x0B45 = 2885mV
406 406  )))
407 407  
408 408  (((
409 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
502 +Ex2: 0x0B49 = 2889mV
410 410  )))
411 411  
412 412  
413 413  
414 -=== 2.4.6  Soil Temperature ===
507 +=== 2.4.4  Signal Strength ===
415 415  
509 +
416 416  (((
417 - 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
511 +NB-IoT Network signal Strength.
418 418  )))
419 419  
420 420  (((
421 -**Example**:
515 +**Ex1: 0x1d = 29**
422 422  )))
423 423  
424 424  (((
425 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
519 +(% style="color:blue" %)**0**(%%)  -113dBm or less
426 426  )))
427 427  
428 428  (((
429 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
523 +(% style="color:blue" %)**1**(%%)  -111dBm
430 430  )))
431 431  
526 +(((
527 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
528 +)))
432 432  
530 +(((
531 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
532 +)))
433 433  
434 -=== 2.4.7  Soil Conductivity (EC) ===
435 -
436 436  (((
437 -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).
535 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
438 438  )))
439 439  
538 +
539 +
540 +=== 2.4.5  Distance ===
541 +
542 +
543 +Get the distance. Flat object range 280mm - 7500mm.
544 +
440 440  (((
441 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
546 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
442 442  )))
443 443  
444 444  (((
445 -Generally, the EC value of irrigation water is less than 800uS / cm.
550 +(((
551 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
446 446  )))
553 +)))
447 447  
448 448  (((
449 449  
... ... @@ -453,46 +453,75 @@
453 453  
454 454  )))
455 455  
456 -=== 2.4.8  Digital Interrupt ===
563 +=== 2.4.6  Digital Interrupt ===
457 457  
458 -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.
459 459  
566 +(((
567 +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.
568 +)))
569 +
570 +(((
460 460  The command is:
572 +)))
461 461  
574 +(((
462 462  (% 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]])**.**
576 +)))
463 463  
464 464  
579 +(((
465 465  The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
581 +)))
466 466  
467 467  
584 +(((
468 468  Example:
586 +)))
469 469  
588 +(((
470 470  0x(00): Normal uplink packet.
590 +)))
471 471  
592 +(((
472 472  0x(01): Interrupt Uplink Packet.
594 +)))
473 473  
474 474  
475 475  
476 -=== 2.4.9  ​+5V Output ===
598 +=== 2.4.7  ​+5V Output ===
477 477  
478 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
479 479  
601 +(((
602 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
603 +)))
480 480  
605 +
606 +(((
481 481  The 5V output time can be controlled by AT Command.
482 482  
609 +
610 +)))
611 +
612 +(((
483 483  (% style="color:blue" %)**AT+5VT=1000**
484 484  
615 +
616 +)))
617 +
618 +(((
485 485  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
620 +)))
486 486  
487 487  
488 488  
489 489  == 2.5  Downlink Payload ==
490 490  
491 -By default, NSE01 prints the downlink payload to console port.
492 492  
493 -[[image:image-20220708133731-5.png]]
627 +By default, NDDS75 prints the downlink payload to console port.
494 494  
629 +[[image:image-20220709100028-1.png]]
495 495  
631 +
496 496  (((
497 497  (% style="color:blue" %)**Examples:**
498 498  )))
... ... @@ -526,83 +526,115 @@
526 526  )))
527 527  
528 528  (((
529 -If payload = 0x04FF, it will reset the NSE01
665 +If payload = 0x04FF, it will reset the NDDS75
530 530  )))
531 531  
532 532  
533 533  * (% style="color:blue" %)**INTMOD**
534 534  
671 +(((
535 535  Downlink Payload: 06000003, Set AT+INTMOD=3
673 +)))
536 536  
537 537  
538 538  
539 -== 2.6  ​LED Indicator ==
677 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
540 540  
541 -(((
542 -The NSE01 has an internal LED which is to show the status of different state.
543 543  
680 +(% style="color:blue" %)** ➢ AT Command:**
544 544  
545 -* 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)
546 -* Then the LED will be on for 1 second means device is boot normally.
547 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
548 -* For each uplink probe, LED will be on for 500ms.
549 -)))
682 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
550 550  
684 +² When min=0, and max≠0, Alarm higher than max
551 551  
686 +² When min≠0, and max=0, Alarm lower than min
552 552  
688 +² When min≠0 and max≠0, Alarm higher than max or lower than min
553 553  
554 -== 2.7  Installation in Soil ==
555 555  
556 -__**Measurement the soil surface**__
691 +(% style="color:blue" %)** Example:**
557 557  
558 -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]]
693 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
559 559  
560 -[[image:1657259653666-883.png]] ​
561 561  
562 562  
563 -(((
564 -
697 +== 2.7  Set the number of data to be uploaded and the recording time ==
565 565  
566 -(((
567 -Dig a hole with diameter > 20CM.
568 -)))
569 569  
570 -(((
571 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
572 -)))
573 -)))
700 +(% style="color:blue" %)** ➢ AT Command:**
574 574  
575 -[[image:1654506665940-119.png]]
702 +(% 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)
576 576  
704 +(% 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.
705 +
706 +
707 +
708 +== 2.8  Read or Clear cached data ==
709 +
710 +
711 +(% style="color:blue" %)** ➢ AT Command:**
712 +
713 +(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
714 +
715 +
716 +[[image:image-20220908175333-2.png]]
717 +
718 +
719 +(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
720 +
721 +
722 +
723 +== 2.9  ​LED Indicator ==
724 +
725 +
726 +The NDDS75 has an internal LED which is to show the status of different state.
727 +
728 +
729 +* 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)
730 +* Then the LED will be on for 1 second means device is boot normally.
731 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
732 +* For each uplink probe, LED will be on for 500ms.
733 +
577 577  (((
578 578  
579 579  )))
580 580  
581 581  
582 -== 2.8  ​Firmware Change Log ==
583 583  
740 +== 2.10  ​Firmware Change Log ==
584 584  
585 -Download URL & Firmware Change log
586 586  
587 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
743 +(((
744 +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]]
745 +)))
588 588  
747 +(((
748 +
749 +)))
589 589  
590 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
751 +(((
752 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
753 +)))
591 591  
592 592  
593 593  
594 -== 2.9  ​Battery Analysis ==
757 +== 2.11  ​Battery Analysis ==
595 595  
596 -=== 2.9.1  ​Battery Type ===
597 597  
760 +=== 2.11.1  ​Battery Type ===
598 598  
599 -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.
600 600  
763 +(((
764 +The NDDS75 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.
765 +)))
601 601  
767 +(((
602 602  The battery is designed to last for several years depends on the actually use environment and update interval. 
769 +)))
603 603  
604 -
771 +(((
605 605  The battery related documents as below:
773 +)))
606 606  
607 607  * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
608 608  * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
... ... @@ -609,13 +609,14 @@
609 609  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
610 610  
611 611  (((
612 -[[image:image-20220708140453-6.png]]
780 +[[image:image-20220709101450-2.png]]
613 613  )))
614 614  
615 615  
616 616  
617 -=== 2.9.2  Power consumption Analyze ===
785 +=== 2.11.2  Power consumption Analyze ===
618 618  
787 +
619 619  (((
620 620  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.
621 621  )))
... ... @@ -648,12 +648,13 @@
648 648  And the Life expectation in difference case will be shown on the right.
649 649  )))
650 650  
651 -[[image:image-20220708141352-7.jpeg]]
820 +[[image:image-20220709110451-3.png]]
652 652  
653 653  
654 654  
655 -=== 2.9.3  ​Battery Note ===
824 +=== 2.11.3  ​Battery Note ===
656 656  
826 +
657 657  (((
658 658  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.
659 659  )))
... ... @@ -660,10 +660,11 @@
660 660  
661 661  
662 662  
663 -=== 2.9.4  Replace the battery ===
833 +=== 2.11.4  Replace the battery ===
664 664  
835 +
665 665  (((
666 -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).
837 +The default battery pack of NDDS75 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).
667 667  )))
668 668  
669 669  
... ... @@ -670,6 +670,7 @@
670 670  
671 671  = 3. ​ Access NB-IoT Module =
672 672  
844 +
673 673  (((
674 674  Users can directly access the AT command set of the NB-IoT module.
675 675  )))
... ... @@ -676,19 +676,23 @@
676 676  
677 677  (((
678 678  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/]] 
851 +
852 +
679 679  )))
680 680  
681 -[[image:1657261278785-153.png]]
855 +[[image:1657333200519-600.png]]
682 682  
683 683  
684 684  
685 685  = 4.  Using the AT Commands =
686 686  
861 +
687 687  == 4.1  Access AT Commands ==
688 688  
689 -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/]]
690 690  
865 +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]]
691 691  
867 +
692 692  AT+<CMD>?  : Help on <CMD>
693 693  
694 694  AT+<CMD>         : Run <CMD>
... ... @@ -728,7 +728,23 @@
728 728  
729 729  AT+SERVADDR  : Server Address
730 730  
907 +AT+TR      : Get or Set record time"
731 731  
909 +AT+APN     : Get or set the APN
910 +
911 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
912 +
913 +AT+DNSCFG  : Get or Set DNS Server
914 +
915 +AT+GETSENSORVALUE   : Returns the current sensor measurement
916 +
917 +AT+NOUD      : Get or Set the number of data to be uploaded
918 +
919 +AT+CDP     : Read or Clear cached data
920 +
921 +AT+LDDSALARM : Get or Set alarm of distance
922 +
923 +
732 732  (% style="color:#037691" %)**COAP Management**      
733 733  
734 734  AT+URI            : Resource parameters
... ... @@ -762,6 +762,7 @@
762 762  
763 763  = ​5.  FAQ =
764 764  
957 +
765 765  == 5.1 ​ How to Upgrade Firmware ==
766 766  
767 767  
... ... @@ -774,7 +774,7 @@
774 774  )))
775 775  
776 776  (((
777 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
970 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
778 778  )))
779 779  
780 780  
... ... @@ -781,28 +781,34 @@
781 781  
782 782  = 6.  Trouble Shooting =
783 783  
977 +
784 784  == 6.1  ​Connection problem when uploading firmware ==
785 785  
786 786  
981 +(((
982 +**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
983 +)))
984 +
787 787  (% class="wikigeneratedid" %)
788 788  (((
789 -(% style="font-size:14px" %)**Please see: **(%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting||style="background-color: rgb(255, 255, 255); font-size: 14px;"]]
987 +
790 790  )))
791 791  
792 792  
793 -
794 794  == 6.2  AT Command input doesn't work ==
795 795  
993 +
796 796  (((
797 797  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.
996 +
997 +
798 798  )))
799 799  
800 800  
801 -
802 802  = 7. ​ Order Info =
803 803  
804 804  
805 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1004 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
806 806  
807 807  
808 808  (% class="wikigeneratedid" %)
... ... @@ -817,8 +817,7 @@
817 817  
818 818  (% style="color:#037691" %)**Package Includes**:
819 819  
820 -
821 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1019 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
822 822  * External antenna x 1
823 823  )))
824 824  
... ... @@ -825,11 +825,13 @@
825 825  (((
826 826  
827 827  
1026 +
828 828  (% style="color:#037691" %)**Dimension and weight**:
829 829  
830 -
831 -* Size: 195 x 125 x 55 mm
832 -* Weight:   420g
1029 +* Device Size: 13.0 x 5 x 4.5 cm
1030 +* Device Weight: 150g
1031 +* Package Size / pcs : 15 x 12x 5.5 cm
1032 +* Weight / pcs : 220g
833 833  )))
834 834  
835 835  (((
... ... @@ -841,5 +841,6 @@
841 841  
842 842  = 9.  Support =
843 843  
1044 +
844 844  * 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.
845 845  * 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]]
1657271519014-786.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +71.5 KB
Content
1657327959271-447.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.3 KB
Content
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-20220709084038-1.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.0 KB
Content
image-20220709084137-2.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.0 KB
Content
image-20220709084207-3.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.0 KB
Content
image-20220709084458-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +199.5 KB
Content
image-20220709085040-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +200.4 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