Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 65.10
edited by Xiaoling
on 2022/07/08 15:43
Change comment: There is no comment for this version
To version 104.3
edited by Xiaoling
on 2022/09/09 11:50
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,93 +87,119 @@
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 +
179 +(((
159 159  Insert the NB-IoT Card get from your provider.
181 +)))
160 160  
183 +(((
161 161  User need to take out the NB-IoT module and insert the SIM card like below:
185 +)))
162 162  
163 163  
164 -[[image:1657249468462-536.png]]
188 +[[image:1657328884227-504.png]]
165 165  
166 166  
167 167  
168 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
192 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
169 169  
194 +
170 170  (((
171 171  (((
172 -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.
173 173  )))
174 174  )))
175 175  
201 +[[image:image-20220709092052-2.png]]
176 176  
203 +
177 177  **Connection:**
178 178  
179 179   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -192,70 +192,90 @@
192 192  * Flow Control: (% style="color:green" %)**None**
193 193  
194 194  (((
195 -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.
196 196  )))
197 197  
198 -[[image:image-20220708110657-3.png]]
225 +[[image:1657329814315-101.png]]
199 199  
200 -(% 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/]]
201 201  
228 +(((
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]]**
230 +)))
202 202  
203 203  
233 +
204 204  === 2.2.4 Use CoAP protocol to uplink data ===
205 205  
206 -(% 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/]]
207 207  
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/]]**
208 208  
239 +
240 +(((
209 209  **Use below commands:**
242 +)))
210 210  
211 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
212 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
213 -* (% 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
214 214  
253 +
254 +
255 +)))
256 +
257 +(((
215 215  For parameter description, please refer to AT command set
216 216  
217 -[[image:1657249793983-486.png]]
260 +
261 +)))
218 218  
263 +[[image:1657330452568-615.png]]
219 219  
220 -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.
221 221  
222 -[[image:1657249831934-534.png]]
223 223  
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.
224 224  
270 +
271 +)))
225 225  
226 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
273 +[[image:1657330472797-498.png]]
227 227  
228 -This feature is supported since firmware version v1.0.1
229 229  
230 230  
231 -* (% 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
232 232  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
233 -* (% 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
234 234  
235 -[[image:1657249864775-321.png]]
284 +[[image:1657330501006-241.png]]
236 236  
237 237  
238 -[[image:1657249930215-289.png]]
287 +[[image:1657330533775-472.png]]
239 239  
240 240  
241 241  
242 242  === 2.2.6 Use MQTT protocol to uplink data ===
243 243  
244 -This feature is supported since firmware version v110
245 245  
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
246 246  
247 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
248 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
249 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
250 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
251 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
252 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
253 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
254 -
255 255  [[image:1657249978444-674.png]]
256 256  
257 257  
258 -[[image:1657249990869-686.png]]
305 +[[image:1657330723006-866.png]]
259 259  
260 260  
261 261  (((
... ... @@ -266,178 +266,241 @@
266 266  
267 267  === 2.2.7 Use TCP protocol to uplink data ===
268 268  
269 -This feature is supported since firmware version v110
270 270  
271 -
272 272  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
273 273  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
274 274  
275 -[[image:1657250217799-140.png]]
320 +[[image:image-20220709093918-1.png]]
276 276  
277 277  
278 -[[image:1657250255956-604.png]]
323 +[[image:image-20220709093918-2.png]]
279 279  
280 280  
281 281  
282 282  === 2.2.8 Change Update Interval ===
283 283  
329 +
284 284  User can use below command to change the (% style="color:green" %)**uplink interval**.
285 285  
286 286  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
287 287  
288 288  (((
289 -(% style="color:red" %)**NOTE:**
290 -)))
335 +(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.**
291 291  
292 -(((
293 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
337 +
294 294  )))
295 295  
340 +(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:**
296 296  
342 +(% 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).**
297 297  
344 +
345 +
298 298  == 2.3  Uplink Payload ==
299 299  
300 -In this mode, uplink payload includes in total 18 bytes
301 301  
302 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
303 -|=(% style="width: 50px;" %)(((
349 +=== 2.3.1  Before Firmware 1.3.2 ===
350 +
351 +
352 +In this mode, uplink payload includes in total 14 bytes
353 +
354 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
355 +|=(% style="width: 60px;" %)(((
304 304  **Size(bytes)**
305 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1**
306 -|(% 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"]]
357 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
358 +|(% 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"]]
307 307  
308 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
360 +(((
361 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
362 +)))
309 309  
310 310  
311 -[[image:image-20220708111918-4.png]]
365 +[[image:1657331036973-987.png]]
312 312  
313 313  
314 -The payload is ASCII string, representative same HEX:
368 +(((
369 +The payload is **ASCII** string, representative same HEX:
370 +)))
315 315  
316 -0x72403155615900640c7817075e0a8c02f900 where:
372 +(((
373 +0x72403155615900640c6c19029200 where:
374 +)))
317 317  
318 -* Device ID: 0x 724031556159 = 724031556159
319 -* Version: 0x0064=100=1.0.0
376 +* (((
377 +Device ID: 0x724031556159 = 724031556159
378 +)))
379 +* (((
380 +Version:  0x0064=100=1.0.0
381 +)))
320 320  
321 -* BAT: 0x0c78 = 3192 mV = 3.192V
322 -* Singal: 0x17 = 23
323 -* Soil Moisture: 0x075e= 1886 = 18.86  %
324 -* Soil Temperature:0x0a8c =2700=27 °C
325 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
326 -* Interrupt: 0x00 = 0
383 +* (((
384 +BAT:  0x0c6c = 3180 mV = 3.180V
385 +)))
386 +* (((
387 +Signal: 0x19 = 25
388 +)))
389 +* (((
390 +Distance: 0x0292= 658 mm
391 +)))
392 +* (((
393 +Interrupt: 0x00 = 0
327 327  
328 328  
329 -== 2.4  Payload Explanation and Sensor Interface ==
330 330  
331 331  
332 -=== 2.4.1  Device ID ===
398 +
399 +)))
333 333  
334 -By default, the Device ID equal to the last 6 bytes of IMEI.
401 +=== **2.3.2  Since firmware v1.3.2** ===
335 335  
336 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
337 337  
338 -**Example:**
404 +In this mode, uplink payload includes 69 bytes in total by default.
339 339  
340 -AT+DEUI=A84041F15612
406 +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.
341 341  
342 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
408 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
409 +|(% 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
410 +|(% 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.......
343 343  
412 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
344 344  
414 +[[image:image-20220908175246-1.png]]
345 345  
346 -=== 2.4.2  Version Info ===
347 347  
348 -Specify the software version: 0x64=100, means firmware version 1.00.
417 +The payload is ASCII string, representative same HEX:
349 349  
350 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
419 +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:
351 351  
421 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
422 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
423 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
424 +* (% style="color:blue" %)Singal: 0x1e = 30
425 +* (% style="color:red" %)Mod: 0x01 = 1
426 +* Interrupt: 0x00= 0
427 +* Distance: 0x0039= 57 = 57
428 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
429 +* Distance,Time stamp : 00396319baf0
430 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
352 352  
353 353  
354 -=== 2.4.3  Battery Info ===
355 355  
434 +
435 +
436 +== 2.4  Payload Explanation and Sensor Interface ==
437 +
438 +
439 +=== 2.4.1  Device ID ===
440 +
441 +
356 356  (((
357 -Check the battery voltage for LSE01.
443 +By default, the Device ID equal to the last 6 bytes of IMEI.
358 358  )))
359 359  
360 360  (((
361 -Ex1: 0x0B45 = 2885mV
447 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
448 +
449 +
362 362  )))
363 363  
364 364  (((
365 -Ex2: 0x0B49 = 2889mV
453 +(% style="color:blue" %)**Example :**
366 366  )))
367 367  
456 +(((
457 +AT+DEUI=A84041F15612
458 +)))
368 368  
460 +(((
461 +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.
462 +)))
369 369  
370 -=== 2.4.4  Signal Strength ===
371 371  
372 -NB-IoT Network signal Strength.
465 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
373 373  
374 -**Ex1: 0x1d = 29**
467 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
375 375  
376 -(% style="color:blue" %)**0**(%%)  -113dBm or less
469 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
377 377  
378 -(% style="color:blue" %)**1**(%%)  -111dBm
379 379  
380 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
472 +(% style="color:blue" %)**Example :**
381 381  
382 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
474 +AT+DEUI=868411056754138
383 383  
384 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
385 385  
386 386  
478 +=== 2.4.2  Version Info ===
387 387  
388 -=== 2.4.5  Soil Moisture ===
389 389  
390 390  (((
391 -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.
482 +Specify the software version: 0x64=100, means firmware version 1.00.
392 392  )))
393 393  
394 394  (((
395 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
486 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
396 396  )))
397 397  
489 +
490 +
491 +=== 2.4.3  Battery Info ===
492 +
493 +
398 398  (((
399 -
495 +Ex1: 0x0B45 = 2885mV
400 400  )))
401 401  
402 402  (((
403 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
499 +Ex2: 0x0B49 = 2889mV
404 404  )))
405 405  
406 406  
407 407  
408 -=== 2.4.6  Soil Temperature ===
504 +=== 2.4.4  Signal Strength ===
409 409  
506 +
410 410  (((
411 - 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
508 +NB-IoT Network signal Strength.
412 412  )))
413 413  
414 414  (((
415 -**Example**:
512 +**Ex1: 0x1d = 29**
416 416  )))
417 417  
418 418  (((
419 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
516 +(% style="color:blue" %)**0**(%%)  -113dBm or less
420 420  )))
421 421  
422 422  (((
423 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
520 +(% style="color:blue" %)**1**(%%)  -111dBm
424 424  )))
425 425  
523 +(((
524 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
525 +)))
426 426  
527 +(((
528 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
529 +)))
427 427  
428 -=== 2.4.7  Soil Conductivity (EC) ===
429 -
430 430  (((
431 -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).
532 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
432 432  )))
433 433  
535 +
536 +
537 +=== 2.4.5  Distance ===
538 +
539 +
540 +Get the distance. Flat object range 280mm - 7500mm.
541 +
434 434  (((
435 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
543 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
436 436  )))
437 437  
438 438  (((
439 -Generally, the EC value of irrigation water is less than 800uS / cm.
547 +(((
548 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
440 440  )))
550 +)))
441 441  
442 442  (((
443 443  
... ... @@ -447,46 +447,75 @@
447 447  
448 448  )))
449 449  
450 -=== 2.4.8  Digital Interrupt ===
560 +=== 2.4.6  Digital Interrupt ===
451 451  
452 -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.
453 453  
563 +(((
564 +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.
565 +)))
566 +
567 +(((
454 454  The command is:
569 +)))
455 455  
571 +(((
456 456  (% 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]])**.**
573 +)))
457 457  
458 458  
576 +(((
459 459  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.
578 +)))
460 460  
461 461  
581 +(((
462 462  Example:
583 +)))
463 463  
585 +(((
464 464  0x(00): Normal uplink packet.
587 +)))
465 465  
589 +(((
466 466  0x(01): Interrupt Uplink Packet.
591 +)))
467 467  
468 468  
469 469  
470 -=== 2.4.9  ​+5V Output ===
595 +=== 2.4.7  ​+5V Output ===
471 471  
472 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
473 473  
598 +(((
599 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
600 +)))
474 474  
602 +
603 +(((
475 475  The 5V output time can be controlled by AT Command.
476 476  
606 +
607 +)))
608 +
609 +(((
477 477  (% style="color:blue" %)**AT+5VT=1000**
478 478  
612 +
613 +)))
614 +
615 +(((
479 479  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
617 +)))
480 480  
481 481  
482 482  
483 483  == 2.5  Downlink Payload ==
484 484  
485 -By default, NSE01 prints the downlink payload to console port.
486 486  
487 -[[image:image-20220708133731-5.png]]
624 +By default, NDDS75 prints the downlink payload to console port.
488 488  
626 +[[image:image-20220709100028-1.png]]
489 489  
628 +
490 490  (((
491 491  (% style="color:blue" %)**Examples:**
492 492  )))
... ... @@ -520,83 +520,115 @@
520 520  )))
521 521  
522 522  (((
523 -If payload = 0x04FF, it will reset the NSE01
662 +If payload = 0x04FF, it will reset the NDDS75
524 524  )))
525 525  
526 526  
527 527  * (% style="color:blue" %)**INTMOD**
528 528  
668 +(((
529 529  Downlink Payload: 06000003, Set AT+INTMOD=3
670 +)))
530 530  
531 531  
532 532  
533 -== 2.6  ​LED Indicator ==
674 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
534 534  
535 -(((
536 -The NSE01 has an internal LED which is to show the status of different state.
537 537  
677 +(% style="color:blue" %)** ➢ AT Command:**
538 538  
539 -* 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)
540 -* Then the LED will be on for 1 second means device is boot normally.
541 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
542 -* For each uplink probe, LED will be on for 500ms.
543 -)))
679 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
544 544  
681 +² When min=0, and max≠0, Alarm higher than max
545 545  
683 +² When min≠0, and max=0, Alarm lower than min
546 546  
685 +² When min≠0 and max≠0, Alarm higher than max or lower than min
547 547  
548 -== 2.7  Installation in Soil ==
549 549  
550 -__**Measurement the soil surface**__
688 +(% style="color:blue" %)** Example:**
551 551  
552 -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]]
690 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
553 553  
554 -[[image:1657259653666-883.png]] ​
555 555  
556 556  
557 -(((
558 -
694 +== 2.7  Set the number of data to be uploaded and the recording time ==
559 559  
560 -(((
561 -Dig a hole with diameter > 20CM.
562 -)))
563 563  
564 -(((
565 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
566 -)))
567 -)))
697 +(% style="color:blue" %)** ➢ AT Command:**
568 568  
569 -[[image:1654506665940-119.png]]
699 +(% 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)
570 570  
701 +(% 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.
702 +
703 +
704 +
705 +== 2.8  Read or Clear cached data ==
706 +
707 +
708 +(% style="color:blue" %)** ➢ AT Command:**
709 +
710 +(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
711 +
712 +
713 +[[image:image-20220908175333-2.png]]
714 +
715 +
716 +(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
717 +
718 +
719 +
720 +== 2.9  ​LED Indicator ==
721 +
722 +
723 +The NDDS75 has an internal LED which is to show the status of different state.
724 +
725 +
726 +* 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)
727 +* Then the LED will be on for 1 second means device is boot normally.
728 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
729 +* For each uplink probe, LED will be on for 500ms.
730 +
571 571  (((
572 572  
573 573  )))
574 574  
575 575  
576 -== 2.8  ​Firmware Change Log ==
577 577  
737 +== 2.10  ​Firmware Change Log ==
578 578  
579 -Download URL & Firmware Change log
580 580  
581 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
740 +(((
741 +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]]
742 +)))
582 582  
744 +(((
745 +
746 +)))
583 583  
584 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
748 +(((
749 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
750 +)))
585 585  
586 586  
587 587  
588 -== 2.9  ​Battery Analysis ==
754 +== 2.11  ​Battery Analysis ==
589 589  
590 -=== 2.9.1  ​Battery Type ===
591 591  
757 +=== 2.11.1  ​Battery Type ===
592 592  
593 -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.
594 594  
760 +(((
761 +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.
762 +)))
595 595  
764 +(((
596 596  The battery is designed to last for several years depends on the actually use environment and update interval. 
766 +)))
597 597  
598 -
768 +(((
599 599  The battery related documents as below:
770 +)))
600 600  
601 601  * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
602 602  * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
... ... @@ -603,13 +603,14 @@
603 603  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
604 604  
605 605  (((
606 -[[image:image-20220708140453-6.png]]
777 +[[image:image-20220709101450-2.png]]
607 607  )))
608 608  
609 609  
610 610  
611 -=== 2.9.2  Power consumption Analyze ===
782 +=== 2.11.2  Power consumption Analyze ===
612 612  
784 +
613 613  (((
614 614  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.
615 615  )))
... ... @@ -642,12 +642,13 @@
642 642  And the Life expectation in difference case will be shown on the right.
643 643  )))
644 644  
645 -[[image:image-20220708141352-7.jpeg]]
817 +[[image:image-20220709110451-3.png]]
646 646  
647 647  
648 648  
649 -=== 2.9.3  ​Battery Note ===
821 +=== 2.11.3  ​Battery Note ===
650 650  
823 +
651 651  (((
652 652  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.
653 653  )))
... ... @@ -654,10 +654,11 @@
654 654  
655 655  
656 656  
657 -=== 2.9.4  Replace the battery ===
830 +=== 2.11.4  Replace the battery ===
658 658  
832 +
659 659  (((
660 -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).
834 +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).
661 661  )))
662 662  
663 663  
... ... @@ -664,6 +664,7 @@
664 664  
665 665  = 3. ​ Access NB-IoT Module =
666 666  
841 +
667 667  (((
668 668  Users can directly access the AT command set of the NB-IoT module.
669 669  )))
... ... @@ -670,19 +670,23 @@
670 670  
671 671  (((
672 672  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/]] 
848 +
849 +
673 673  )))
674 674  
675 -[[image:1657261278785-153.png]]
852 +[[image:1657333200519-600.png]]
676 676  
677 677  
678 678  
679 679  = 4.  Using the AT Commands =
680 680  
858 +
681 681  == 4.1  Access AT Commands ==
682 682  
683 -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/]]
684 684  
862 +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]]
685 685  
864 +
686 686  AT+<CMD>?  : Help on <CMD>
687 687  
688 688  AT+<CMD>         : Run <CMD>
... ... @@ -722,7 +722,23 @@
722 722  
723 723  AT+SERVADDR  : Server Address
724 724  
904 +AT+TR      : Get or Set record time"
725 725  
906 +AT+APN     : Get or set the APN
907 +
908 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
909 +
910 +AT+DNSCFG  : Get or Set DNS Server
911 +
912 +AT+GETSENSORVALUE   : Returns the current sensor measurement
913 +
914 +AT+NOUD      : Get or Set the number of data to be uploaded
915 +
916 +AT+CDP     : Read or Clear cached data
917 +
918 +AT+LDDSALARM : Get or Set alarm of distance
919 +
920 +
726 726  (% style="color:#037691" %)**COAP Management**      
727 727  
728 728  AT+URI            : Resource parameters
... ... @@ -756,6 +756,7 @@
756 756  
757 757  = ​5.  FAQ =
758 758  
954 +
759 759  == 5.1 ​ How to Upgrade Firmware ==
760 760  
761 761  
... ... @@ -768,7 +768,7 @@
768 768  )))
769 769  
770 770  (((
771 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
967 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
772 772  )))
773 773  
774 774  
... ... @@ -775,28 +775,34 @@
775 775  
776 776  = 6.  Trouble Shooting =
777 777  
974 +
778 778  == 6.1  ​Connection problem when uploading firmware ==
779 779  
780 780  
978 +(((
979 +**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]]
980 +)))
981 +
781 781  (% class="wikigeneratedid" %)
782 782  (((
783 -(% 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;"]]
984 +
784 784  )))
785 785  
786 786  
787 -
788 788  == 6.2  AT Command input doesn't work ==
789 789  
990 +
790 790  (((
791 791  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.
993 +
994 +
792 792  )))
793 793  
794 794  
795 -
796 796  = 7. ​ Order Info =
797 797  
798 798  
799 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1001 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
800 800  
801 801  
802 802  (% class="wikigeneratedid" %)
... ... @@ -811,8 +811,7 @@
811 811  
812 812  (% style="color:#037691" %)**Package Includes**:
813 813  
814 -
815 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1016 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
816 816  * External antenna x 1
817 817  )))
818 818  
... ... @@ -819,11 +819,13 @@
819 819  (((
820 820  
821 821  
1023 +
822 822  (% style="color:#037691" %)**Dimension and weight**:
823 823  
824 -
825 -* Size: 195 x 125 x 55 mm
826 -* Weight:   420g
1026 +* Device Size: 13.0 x 5 x 4.5 cm
1027 +* Device Weight: 150g
1028 +* Package Size / pcs : 15 x 12x 5.5 cm
1029 +* Weight / pcs : 220g
827 827  )))
828 828  
829 829  (((
... ... @@ -835,5 +835,6 @@
835 835  
836 836  = 9.  Support =
837 837  
1041 +
838 838  * 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.
839 839  * 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