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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual
Content
... ... @@ -1,10 +1,16 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220709085040-1.png||height="542" width="524"]]
2 +[[image:image-20220606151504-2.jpeg||height="554" width="554"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 +
9 +
10 +
11 +
12 +
13 +
8 8  **Table of Contents:**
9 9  
10 10  {{toc/}}
... ... @@ -14,65 +14,56 @@
14 14  
15 15  
16 16  
23 +
17 17  = 1.  Introduction =
18 18  
26 +== 1.1 ​ What is LoRaWAN Soil Moisture & EC Sensor ==
19 19  
20 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21 -
22 22  (((
23 23  
24 24  
25 25  (((
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.
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.
28 28  )))
29 29  
30 30  (((
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.
36 +It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
32 32  )))
33 33  
34 34  (((
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.
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.
36 36  )))
37 37  
38 38  (((
39 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
44 +NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.  
40 40  )))
41 41  
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)
47 +
44 44  )))
45 45  
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 -)))
50 +[[image:1654503236291-817.png]]
50 50  
51 -
52 -)))
53 53  
54 -[[image:1657327959271-447.png]]
53 +[[image:1657245163077-232.png]]
55 55  
56 56  
57 57  
58 58  == 1.2 ​ Features ==
59 59  
60 -
61 61  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
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
60 +* Monitor Soil Moisture
61 +* Monitor Soil Temperature
62 +* Monitor Soil Conductivity
67 67  * AT Commands to change parameters
68 68  * Uplink on periodically
69 69  * Downlink to change configure
70 70  * IP66 Waterproof Enclosure
67 +* Ultra-Low Power consumption
68 +* AT Commands to change parameters
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
74 74  
75 -
76 76  == 1.3  Specification ==
77 77  
78 78  
... ... @@ -83,102 +83,82 @@
83 83  
84 84  (% style="color:#037691" %)**NB-IoT Spec:**
85 85  
86 -* B1 @H-FDD: 2100MHz
87 -* B3 @H-FDD: 1800MHz
88 -* B8 @H-FDD: 900MHz
89 -* B5 @H-FDD: 850MHz
90 -* B20 @H-FDD: 800MHz
91 -* B28 @H-FDD: 700MHz
83 +* - B1 @H-FDD: 2100MHz
84 +* - B3 @H-FDD: 1800MHz
85 +* - B8 @H-FDD: 900MHz
86 +* - B5 @H-FDD: 850MHz
87 +* - B20 @H-FDD: 800MHz
88 +* - B28 @H-FDD: 700MHz
92 92  
93 -(% style="color:#037691" %)**Battery:**
90 +Probe(% style="color:#037691" %)** Specification:**
94 94  
95 -* Li/SOCI2 un-chargeable battery
96 -* Capacity: 8500mAh
97 -* Self Discharge: <1% / Year @ 25°C
98 -* Max continuously current: 130mA
99 -* Max boost current: 2A, 1 second
92 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
100 100  
101 -(% style="color:#037691" %)**Power Consumption**
94 +[[image:image-20220708101224-1.png]]
102 102  
103 -* STOP Mode: 10uA @ 3.3v
104 -* Max transmit power: 350mA@3.3v
105 105  
106 106  
107 -
108 108  == ​1.4  Applications ==
109 109  
110 -
111 -* Smart Buildings & Home Automation
112 -* Logistics and Supply Chain Management
113 -* Smart Metering
114 114  * Smart Agriculture
115 -* Smart Cities
116 -* Smart Factory
117 117  
118 118  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
119 119  ​
120 120  
121 -
122 -
123 123  == 1.5  Pin Definitions ==
124 124  
125 125  
126 -[[image:1657328609906-564.png]]
108 +[[image:1657246476176-652.png]]
127 127  
128 128  
129 129  
130 -= 2.  Use NDDS75 to communicate with IoT Server =
112 += 2.  Use NSE01 to communicate with IoT Server =
131 131  
132 -
133 133  == 2.1  How it works ==
134 134  
135 135  
136 136  (((
137 -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.
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.
138 138  )))
139 139  
140 140  
141 141  (((
142 -The diagram below shows the working flow in default firmware of NDDS75:
123 +The diagram below shows the working flow in default firmware of NSE01:
143 143  )))
144 144  
145 -(((
146 -
147 -)))
126 +[[image:image-20220708101605-2.png]]
148 148  
149 -[[image:1657328659945-416.png]]
150 -
151 151  (((
152 152  
153 153  )))
154 154  
155 155  
156 -== 2.2 ​ Configure the NDDS75 ==
157 157  
134 +== 2.2 ​ Configure the NSE01 ==
158 158  
136 +
159 159  === 2.2.1 Test Requirement ===
160 160  
161 161  
162 162  (((
163 -To use NDDS75 in your city, make sure meet below requirements:
141 +To use NSE01 in your city, make sure meet below requirements:
164 164  )))
165 165  
166 166  * Your local operator has already distributed a NB-IoT Network there.
167 -* The local NB-IoT network used the band that NDDS75 supports.
145 +* The local NB-IoT network used the band that NSE01 supports.
168 168  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
169 169  
170 170  (((
171 -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.
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
172 172  )))
173 173  
174 174  
175 -[[image:1657328756309-230.png]]
153 +[[image:1657249419225-449.png]]
176 176  
177 177  
178 178  
179 179  === 2.2.2 Insert SIM card ===
180 180  
181 -
182 182  (((
183 183  Insert the NB-IoT Card get from your provider.
184 184  )))
... ... @@ -188,31 +188,28 @@
188 188  )))
189 189  
190 190  
191 -[[image:1657328884227-504.png]]
168 +[[image:1657249468462-536.png]]
192 192  
193 193  
194 194  
195 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
172 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
196 196  
197 -
198 198  (((
199 199  (((
200 -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.
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.
201 201  )))
202 202  )))
203 203  
204 -[[image:image-20220709092052-2.png]]
205 205  
181 +**Connection:**
206 206  
207 -(% style="color:blue" %)**Connection:**
183 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
208 208  
209 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
185 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
210 210  
211 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
187 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
212 212  
213 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
214 214  
215 -
216 216  In the PC, use below serial tool settings:
217 217  
218 218  * Baud:  (% style="color:green" %)**9600**
... ... @@ -222,14 +222,13 @@
222 222  * Flow Control: (% style="color:green" %)**None**
223 223  
224 224  (((
225 -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.
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.
226 226  )))
227 227  
228 -[[image:1657329814315-101.png]]
202 +[[image:image-20220708110657-3.png]]
229 229  
230 -
231 231  (((
232 -(% 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]]**
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/]]
233 233  )))
234 234  
235 235  
... ... @@ -236,76 +236,59 @@
236 236  
237 237  === 2.2.4 Use CoAP protocol to uplink data ===
238 238  
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/]]
239 239  
240 -(% 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/]]**
241 241  
242 -
243 -(((
244 244  **Use below commands:**
245 -)))
246 246  
247 -* (((
248 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
249 -)))
250 -* (((
251 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
252 -)))
253 -* (((
254 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
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
255 255  
256 -
257 -
258 -)))
259 -
260 -(((
261 261  For parameter description, please refer to AT command set
262 262  
263 -
264 -)))
223 +[[image:1657249793983-486.png]]
265 265  
266 -[[image:1657330452568-615.png]]
267 267  
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.
268 268  
228 +[[image:1657249831934-534.png]]
269 269  
270 -(((
271 -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.
272 272  
273 -
274 -)))
275 275  
276 -[[image:1657330472797-498.png]]
277 -
278 -
279 -
280 280  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
281 281  
234 +This feature is supported since firmware version v1.0.1
282 282  
283 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
284 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
285 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
286 286  
287 -[[image:1657330501006-241.png]]
237 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
238 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
239 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
288 288  
241 +[[image:1657249864775-321.png]]
289 289  
290 -[[image:1657330533775-472.png]]
291 291  
244 +[[image:1657249930215-289.png]]
292 292  
293 293  
247 +
294 294  === 2.2.6 Use MQTT protocol to uplink data ===
295 295  
250 +This feature is supported since firmware version v110
296 296  
297 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
298 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
299 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
300 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
301 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
302 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
303 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
304 304  
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 +
305 305  [[image:1657249978444-674.png]]
306 306  
307 307  
308 -[[image:1657330723006-866.png]]
264 +[[image:1657249990869-686.png]]
309 309  
310 310  
311 311  (((
... ... @@ -316,240 +316,178 @@
316 316  
317 317  === 2.2.7 Use TCP protocol to uplink data ===
318 318  
275 +This feature is supported since firmware version v110
319 319  
320 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
321 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
322 322  
323 -[[image:image-20220709093918-1.png]]
278 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
279 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
324 324  
281 +[[image:1657250217799-140.png]]
325 325  
326 -[[image:image-20220709093918-2.png]]
327 327  
284 +[[image:1657250255956-604.png]]
328 328  
329 329  
287 +
330 330  === 2.2.8 Change Update Interval ===
331 331  
332 -
333 333  User can use below command to change the (% style="color:green" %)**uplink interval**.
334 334  
335 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
292 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
336 336  
337 337  (((
338 -
339 -
340 -
341 341  (% style="color:red" %)**NOTE:**
296 +)))
342 342  
343 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
344 -
345 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
298 +(((
299 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
346 346  )))
347 347  
348 -(% 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).**
349 349  
350 350  
351 -
352 352  == 2.3  Uplink Payload ==
353 353  
306 +In this mode, uplink payload includes in total 18 bytes
354 354  
355 -=== 2.3.1  Before Firmware v1.3.2 ===
356 -
357 -
358 -In this mode, uplink payload includes in total 14 bytes
359 -
360 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
308 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
361 361  |=(% style="width: 60px;" %)(((
362 362  **Size(bytes)**
363 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
364 -|(% 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"]]
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"]]
365 365  
366 -(((
367 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
368 -)))
314 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
369 369  
370 370  
371 -[[image:1657331036973-987.png]]
317 +[[image:image-20220708111918-4.png]]
372 372  
373 373  
320 +The payload is ASCII string, representative same HEX:
374 374  
375 -The payload is **ASCII** string, representative same HEX:
322 +0x72403155615900640c7817075e0a8c02f900 where:
376 376  
377 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
324 +* Device ID: 0x 724031556159 = 724031556159
325 +* Version: 0x0064=100=1.0.0
378 378  
379 -**where :**
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
380 380  
381 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
382 382  
383 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
335 +== 2.4  Payload Explanation and Sensor Interface ==
384 384  
385 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
386 386  
387 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
338 +=== 2.4.1  Device ID ===
388 388  
389 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
340 +By default, the Device ID equal to the last 6 bytes of IMEI.
390 390  
391 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
342 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
392 392  
344 +**Example:**
393 393  
346 +AT+DEUI=A84041F15612
394 394  
395 -=== 2.3.2  Since firmware v1.3.2 ===
348 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
396 396  
397 397  
398 -In this mode, uplink payload includes 69 bytes in total by default.
399 399  
400 -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.
352 +=== 2.4.2  Version Info ===
401 401  
402 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
403 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4**
404 -|=(% 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.......
354 +Specify the software version: 0x64=100, means firmware version 1.00.
405 405  
406 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
356 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
407 407  
408 -[[image:image-20220908175246-1.png]]
409 409  
410 410  
411 -The payload is ASCII string, representative same HEX:
360 +=== 2.4.3  Battery Info ===
412 412  
413 -**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
414 -
415 -**where:**
416 -
417 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
418 -
419 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
420 -
421 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
422 -
423 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
424 -
425 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
426 -
427 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
428 -
429 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
430 -
431 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
432 -
433 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
434 -
435 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
436 -
437 -
438 -== 2.4  Payload Explanation and Sensor Interface ==
439 -
440 -
441 -=== 2.4.1  Device ID ===
442 -
443 -
444 444  (((
445 -By default, the Device ID equal to the last 6 bytes of IMEI.
363 +Check the battery voltage for LSE01.
446 446  )))
447 447  
448 448  (((
449 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
450 -
451 -
367 +Ex1: 0x0B45 = 2885mV
452 452  )))
453 453  
454 454  (((
455 -(% style="color:blue" %)**Example :**
371 +Ex2: 0x0B49 = 2889mV
456 456  )))
457 457  
458 -(((
459 -AT+DEUI=A84041F15612
460 -)))
461 461  
462 -(((
463 -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.
464 -)))
465 465  
376 +=== 2.4.4  Signal Strength ===
466 466  
467 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
378 +NB-IoT Network signal Strength.
468 468  
469 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
380 +**Ex1: 0x1d = 29**
470 470  
471 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
382 +(% style="color:blue" %)**0**(%%)  -113dBm or less
472 472  
384 +(% style="color:blue" %)**1**(%%)  -111dBm
473 473  
474 -(% style="color:blue" %)**Example :**
386 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
475 475  
476 -AT+DEUI=868411056754138
388 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
477 477  
390 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
478 478  
479 479  
480 -=== 2.4.2  Version Info ===
481 481  
394 +=== 2.4.5  Soil Moisture ===
482 482  
483 483  (((
484 -Specify the software version: 0x64=100, means firmware version 1.00.
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 485  )))
486 486  
487 487  (((
488 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
401 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
489 489  )))
490 490  
491 -
492 -
493 -=== 2.4.3  Battery Info ===
494 -
495 -
496 496  (((
497 -Ex1: 0x0B45 = 2885mV
405 +
498 498  )))
499 499  
500 500  (((
501 -Ex2: 0x0B49 = 2889mV
409 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
502 502  )))
503 503  
504 504  
505 505  
506 -=== 2.4.4  Signal Strength ===
414 +=== 2.4.6  Soil Temperature ===
507 507  
508 -
509 509  (((
510 -NB-IoT Network signal Strength.
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 511  )))
512 512  
513 513  (((
514 -**Ex1: 0x1d = 29**
421 +**Example**:
515 515  )))
516 516  
517 517  (((
518 -(% style="color:blue" %)**0**(%%)  -113dBm or less
425 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
519 519  )))
520 520  
521 521  (((
522 -(% style="color:blue" %)**1**(%%)  -111dBm
429 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
523 523  )))
524 524  
525 -(((
526 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
527 -)))
528 528  
529 -(((
530 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
531 -)))
532 532  
434 +=== 2.4.7  Soil Conductivity (EC) ===
435 +
533 533  (((
534 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
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 535  )))
536 536  
537 -
538 -
539 -=== 2.4.5  Distance ===
540 -
541 -
542 -Get the distance. Flat object range 280mm - 7500mm.
543 -
544 544  (((
545 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
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 546  )))
547 547  
548 548  (((
549 -(((
550 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
445 +Generally, the EC value of irrigation water is less than 800uS / cm.
551 551  )))
552 -)))
553 553  
554 554  (((
555 555  
... ... @@ -559,75 +559,46 @@
559 559  
560 560  )))
561 561  
562 -=== 2.4.6  Digital Interrupt ===
456 +=== 2.4.8  Digital Interrupt ===
563 563  
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.
564 564  
565 -(((
566 -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.
567 -)))
568 -
569 -(((
570 570  The command is:
571 -)))
572 572  
573 -(((
574 -(% 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]])**.**
575 -)))
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 576  
577 577  
578 -(((
579 579  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.
580 -)))
581 581  
582 582  
583 -(((
584 584  Example:
585 -)))
586 586  
587 -(((
588 588  0x(00): Normal uplink packet.
589 -)))
590 590  
591 -(((
592 592  0x(01): Interrupt Uplink Packet.
593 -)))
594 594  
595 595  
596 596  
597 -=== 2.4.7  ​+5V Output ===
476 +=== 2.4.9  ​+5V Output ===
598 598  
478 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
599 599  
600 -(((
601 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
602 -)))
603 603  
604 -
605 -(((
606 606  The 5V output time can be controlled by AT Command.
607 607  
608 -
609 -)))
610 -
611 -(((
612 612  (% style="color:blue" %)**AT+5VT=1000**
613 613  
614 -
615 -)))
616 -
617 -(((
618 618  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
619 -)))
620 620  
621 621  
622 622  
623 623  == 2.5  Downlink Payload ==
624 624  
491 +By default, NSE01 prints the downlink payload to console port.
625 625  
626 -By default, NDDS75 prints the downlink payload to console port.
493 +[[image:image-20220708133731-5.png]]
627 627  
628 -[[image:image-20220709100028-1.png]]
629 629  
630 -
631 631  (((
632 632  (% style="color:blue" %)**Examples:**
633 633  )))
... ... @@ -661,115 +661,83 @@
661 661  )))
662 662  
663 663  (((
664 -If payload = 0x04FF, it will reset the NDDS75
529 +If payload = 0x04FF, it will reset the NSE01
665 665  )))
666 666  
667 667  
668 668  * (% style="color:blue" %)**INTMOD**
669 669  
670 -(((
671 671  Downlink Payload: 06000003, Set AT+INTMOD=3
672 -)))
673 673  
674 674  
675 675  
676 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
539 +== 2.6  ​LED Indicator ==
677 677  
541 +(((
542 +The NSE01 has an internal LED which is to show the status of different state.
678 678  
679 -(% style="color:blue" %)** ➢ AT Command:**
680 680  
681 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
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 682  
683 -² When min=0, and max≠0, Alarm higher than max
684 684  
685 -² When min≠0, and max=0, Alarm lower than min
686 686  
687 -² When min≠0 and max≠0, Alarm higher than max or lower than min
688 688  
554 +== 2.7  Installation in Soil ==
689 689  
690 -(% style="color:blue" %)** Example:**
556 +__**Measurement the soil surface**__
691 691  
692 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
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 693  
560 +[[image:1657259653666-883.png]] ​
694 694  
695 695  
696 -== 2.7  Set the number of data to be uploaded and the recording time ==
563 +(((
564 +
697 697  
566 +(((
567 +Dig a hole with diameter > 20CM.
568 +)))
698 698  
699 -(% style="color:blue" %)** ➢ AT Command:**
570 +(((
571 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
572 +)))
573 +)))
700 700  
701 -* (% 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)
702 -* (% 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.
575 +[[image:1654506665940-119.png]]
703 703  
704 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
705 -
706 -[[image:image-20221009001114-1.png||height="687" width="955"]]
707 -
708 -
709 -
710 -== 2.8  Read or Clear cached data ==
711 -
712 -
713 -(% style="color:blue" %)** ➢ AT Command:**
714 -
715 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
716 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
717 -
718 -[[image:image-20220908175333-2.png]]
719 -
720 -
721 -
722 -== 2.9  ​LED Indicator ==
723 -
724 -
725 -The NDDS75 has an internal LED which is to show the status of different state.
726 -
727 -
728 -* 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)
729 -* Then the LED will be on for 1 second means device is boot normally.
730 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
731 -* For each uplink probe, LED will be on for 500ms.
732 -
733 733  (((
734 734  
735 735  )))
736 736  
737 737  
582 +== 2.8  ​Firmware Change Log ==
738 738  
739 -== 2.10  ​Firmware Change Log ==
740 740  
585 +Download URL & Firmware Change log
741 741  
742 -(((
743 -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]]
744 -)))
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/]]
745 745  
746 -(((
747 -
748 -)))
749 749  
750 -(((
751 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
752 -)))
590 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
753 753  
754 754  
755 755  
756 -== 2.11  ​Battery Analysis ==
594 +== 2.9  ​Battery Analysis ==
757 757  
596 +=== 2.9.1  ​Battery Type ===
758 758  
759 -=== 2.11.1  ​Battery Type ===
760 760  
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.
761 761  
762 -(((
763 -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.
764 -)))
765 765  
766 -(((
767 767  The battery is designed to last for several years depends on the actually use environment and update interval. 
768 -)))
769 769  
770 -(((
604 +
771 771  The battery related documents as below:
772 -)))
773 773  
774 774  * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
775 775  * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
... ... @@ -776,14 +776,13 @@
776 776  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
777 777  
778 778  (((
779 -[[image:image-20220709101450-2.png]]
612 +[[image:image-20220708140453-6.png]]
780 780  )))
781 781  
782 782  
783 783  
784 -=== 2.11.2  Power consumption Analyze ===
617 +=== 2.9.2  Power consumption Analyze ===
785 785  
786 -
787 787  (((
788 788  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.
789 789  )))
... ... @@ -816,13 +816,12 @@
816 816  And the Life expectation in difference case will be shown on the right.
817 817  )))
818 818  
819 -[[image:image-20220709110451-3.png]]
651 +[[image:image-20220708141352-7.jpeg]]
820 820  
821 821  
822 822  
823 -=== 2.11.3  ​Battery Note ===
655 +=== 2.9.3  ​Battery Note ===
824 824  
825 -
826 826  (((
827 827  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.
828 828  )))
... ... @@ -829,11 +829,10 @@
829 829  
830 830  
831 831  
832 -=== 2.11.4  Replace the battery ===
663 +=== 2.9.4  Replace the battery ===
833 833  
834 -
835 835  (((
836 -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).
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 837  )))
838 838  
839 839  
... ... @@ -840,7 +840,6 @@
840 840  
841 841  = 3. ​ Access NB-IoT Module =
842 842  
843 -
844 844  (((
845 845  Users can directly access the AT command set of the NB-IoT module.
846 846  )))
... ... @@ -847,113 +847,92 @@
847 847  
848 848  (((
849 849  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/]] 
850 -
851 -
852 852  )))
853 853  
854 -[[image:1657333200519-600.png]]
681 +[[image:1657261278785-153.png]]
855 855  
856 856  
857 857  
858 858  = 4.  Using the AT Commands =
859 859  
860 -
861 861  == 4.1  Access AT Commands ==
862 862  
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/]]
863 863  
864 -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]]
865 865  
692 +AT+<CMD>?  : Help on <CMD>
866 866  
867 -AT+<CMD>?  :  Help on <CMD>
694 +AT+<CMD>         : Run <CMD>
868 868  
869 -AT+<CMD>         :  Run <CMD>
696 +AT+<CMD>=<value> : Set the value
870 870  
871 -AT+<CMD>=<value> :  Set the value
698 +AT+<CMD>=?  : Get the value
872 872  
873 -AT+<CMD>=?  :  Get the value
874 874  
875 -
876 876  (% style="color:#037691" %)**General Commands**(%%)      
877 877  
878 -AT  :  Attention       
703 +AT  : Attention       
879 879  
880 -AT?  :  Short Help     
705 +AT?  : Short Help     
881 881  
882 -ATZ  :  MCU Reset    
707 +ATZ  : MCU Reset    
883 883  
884 -AT+TDC  :  Application Data Transmission Interval
709 +AT+TDC  : Application Data Transmission Interval
885 885  
886 -AT+CFG  :  Print all configurations
711 +AT+CFG  : Print all configurations
887 887  
888 -AT+CFGMOD           :  Working mode selection
713 +AT+CFGMOD           : Working mode selection
889 889  
890 -AT+INTMOD            :  Set the trigger interrupt mode
715 +AT+INTMOD            : Set the trigger interrupt mode
891 891  
892 -AT+5VT  :  Set extend the time of 5V power  
717 +AT+5VT  : Set extend the time of 5V power  
893 893  
894 -AT+PRO  :  Choose agreement
719 +AT+PRO  : Choose agreement
895 895  
896 -AT+WEIGRE  :  Get weight or set weight to 0
721 +AT+WEIGRE  : Get weight or set weight to 0
897 897  
898 -AT+WEIGAP  :  Get or Set the GapValue of weight
723 +AT+WEIGAP  : Get or Set the GapValue of weight
899 899  
900 -AT+RXDL  :  Extend the sending and receiving time
725 +AT+RXDL  : Extend the sending and receiving time
901 901  
902 -AT+CNTFAC  :  Get or set counting parameters
727 +AT+CNTFAC  : Get or set counting parameters
903 903  
904 -AT+SERVADDR  :  Server Address
729 +AT+SERVADDR  : Server Address
905 905  
906 -AT+TR  :  Get or Set record time"
907 907  
908 -AT+APN     :  Get or set the APN
909 -
910 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
911 -
912 -AT+DNSCFG  : Get or Set DNS Server
913 -
914 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
915 -
916 -AT+NOUD  :  Get or Set the number of data to be uploaded
917 -
918 -AT+CDP     :  Read or Clear cached data
919 -
920 -AT+LDDSALARM :  Get or Set alarm of distance
921 -
922 -
923 923  (% style="color:#037691" %)**COAP Management**      
924 924  
925 -AT+URI            :  Resource parameters
734 +AT+URI            : Resource parameters
926 926  
927 927  
928 928  (% style="color:#037691" %)**UDP Management**
929 929  
930 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
739 +AT+CFM          : Upload confirmation mode (only valid for UDP)
931 931  
932 932  
933 933  (% style="color:#037691" %)**MQTT Management**
934 934  
935 -AT+CLIENT  :  Get or Set MQTT client
744 +AT+CLIENT               : Get or Set MQTT client
936 936  
937 -AT+UNAME  :  Get or Set MQTT Username
746 +AT+UNAME  : Get or Set MQTT Username
938 938  
939 -AT+PWD  :  Get or Set MQTT password
748 +AT+PWD                  : Get or Set MQTT password
940 940  
941 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
750 +AT+PUBTOPIC  : Get or Set MQTT publish topic
942 942  
943 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
752 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
944 944  
945 945  
946 946  (% style="color:#037691" %)**Information**          
947 947  
948 -AT+FDR  :  Factory Data Reset
757 +AT+FDR  : Factory Data Reset
949 949  
950 -AT+PWORD  :  Serial Access Password
759 +AT+PWORD  : Serial Access Password
951 951  
952 952  
953 953  
954 954  = ​5.  FAQ =
955 955  
956 -
957 957  == 5.1 ​ How to Upgrade Firmware ==
958 958  
959 959  
... ... @@ -966,7 +966,7 @@
966 966  )))
967 967  
968 968  (((
969 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
777 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
970 970  )))
971 971  
972 972  
... ... @@ -973,34 +973,28 @@
973 973  
974 974  = 6.  Trouble Shooting =
975 975  
976 -
977 977  == 6.1  ​Connection problem when uploading firmware ==
978 978  
979 979  
980 -(((
981 -**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]]
982 -)))
983 -
984 984  (% class="wikigeneratedid" %)
985 985  (((
986 -
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 987  )))
988 988  
989 989  
793 +
990 990  == 6.2  AT Command input doesn't work ==
991 991  
992 -
993 993  (((
994 994  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.
995 -
996 -
997 997  )))
998 998  
999 999  
801 +
1000 1000  = 7. ​ Order Info =
1001 1001  
1002 1002  
1003 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
805 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1004 1004  
1005 1005  
1006 1006  (% class="wikigeneratedid" %)
... ... @@ -1015,7 +1015,8 @@
1015 1015  
1016 1016  (% style="color:#037691" %)**Package Includes**:
1017 1017  
1018 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
820 +
821 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1019 1019  * External antenna x 1
1020 1020  )))
1021 1021  
... ... @@ -1022,13 +1022,11 @@
1022 1022  (((
1023 1023  
1024 1024  
1025 -
1026 1026  (% style="color:#037691" %)**Dimension and weight**:
1027 1027  
1028 -* Device Size: 13.0 x 5 x 4.5 cm
1029 -* Device Weight: 150g
1030 -* Package Size / pcs : 15 x 12x 5.5 cm
1031 -* Weight / pcs : 220g
830 +
831 +* Size: 195 x 125 x 55 mm
832 +* Weight:   420g
1032 1032  )))
1033 1033  
1034 1034  (((
... ... @@ -1040,6 +1040,5 @@
1040 1040  
1041 1041  = 9.  Support =
1042 1042  
1043 -
1044 1044  * 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.
1045 1045  * 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,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.5 KB
Content
1657327959271-447.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.3 KB
Content
1657328609906-564.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709084038-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084137-2.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084207-3.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.0 KB
Content
image-20220709084458-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -199.5 KB
Content
image-20220709085040-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -200.4 KB
Content
image-20220709092052-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -247.3 KB
Content
image-20220709093918-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -611.5 KB
Content
image-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content