Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 108.24
edited by Xiaoling
on 2024/01/19 17:51
Change comment: There is no comment for this version
To version 75.4
edited by Xiaoling
on 2022/07/09 09:02
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 +NDDS75 NB-IoT Distance Detect Sensor User Manual
Content
... ... @@ -7,7 +7,6 @@
7 7  
8 8  **Table of Contents:**
9 9  
10 -{{toc/}}
11 11  
12 12  
13 13  
... ... @@ -22,37 +22,24 @@
22 22  
23 23  
24 24  (((
25 -(((
26 26  The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
25 +\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
26 +\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
27 +\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
28 +\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
29 +\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
27 27  )))
28 28  
29 -(((
30 -The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
32 +
31 31  )))
32 32  
33 -(((
34 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
35 -)))
35 +[[image:1654503236291-817.png]]
36 36  
37 -(((
38 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
39 -)))
40 40  
41 -(((
42 -NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
43 -)))
44 -
45 -(((
46 -To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
47 -)))
48 -)))
49 -
50 -
51 -)))
52 -
53 53  [[image:1657327959271-447.png]]
54 54  
55 55  
41 +
56 56  == 1.2 ​ Features ==
57 57  
58 58  
... ... @@ -69,6 +69,8 @@
69 69  * Micro SIM card slot for NB-IoT SIM
70 70  * 8500mAh Battery for long term use
71 71  
58 +
59 +
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -79,13 +79,14 @@
79 79  
80 80  (% style="color:#037691" %)**NB-IoT Spec:**
81 81  
82 -* B1 @H-FDD: 2100MHz
83 -* B3 @H-FDD: 1800MHz
84 -* B8 @H-FDD: 900MHz
85 -* B5 @H-FDD: 850MHz
86 -* B20 @H-FDD: 800MHz
87 -* B28 @H-FDD: 700MHz
70 +* - B1 @H-FDD: 2100MHz
71 +* - B3 @H-FDD: 1800MHz
72 +* - B8 @H-FDD: 900MHz
73 +* - B5 @H-FDD: 850MHz
74 +* - B20 @H-FDD: 800MHz
75 +* - B28 @H-FDD: 700MHz
88 88  
77 +
89 89  (% style="color:#037691" %)**Battery:**
90 90  
91 91  * Li/SOCI2 un-chargeable battery
... ... @@ -94,14 +94,17 @@
94 94  * Max continuously current: 130mA
95 95  * Max boost current: 2A, 1 second
96 96  
86 +
97 97  (% style="color:#037691" %)**Power Consumption**
98 98  
99 99  * STOP Mode: 10uA @ 3.3v
100 100  * Max transmit power: 350mA@3.3v
101 101  
102 -== ​1.4  Applications ==
103 103  
104 104  
94 +
95 +== ​1.4  Applications ==
96 +
105 105  * Smart Buildings & Home Automation
106 106  * Logistics and Supply Chain Management
107 107  * Smart Metering
... ... @@ -113,60 +113,61 @@
113 113  ​
114 114  
115 115  
108 +
116 116  == 1.5  Pin Definitions ==
117 117  
118 118  
119 -[[image:1657328609906-564.png]]
112 +[[image:1657246476176-652.png]]
120 120  
121 121  
122 -= 2.  Use NDDS75 to communicate with IoT Server =
123 123  
116 += 2.  Use NSE01 to communicate with IoT Server =
117 +
124 124  == 2.1  How it works ==
125 125  
126 126  
127 127  (((
128 -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.
122 +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.
129 129  )))
130 130  
131 131  
132 132  (((
133 -The diagram below shows the working flow in default firmware of NDDS75:
127 +The diagram below shows the working flow in default firmware of NSE01:
134 134  )))
135 135  
130 +[[image:image-20220708101605-2.png]]
131 +
136 136  (((
137 137  
138 138  )))
139 139  
140 -[[image:1657328659945-416.png]]
141 141  
142 -(((
143 -
144 -)))
145 145  
146 -== 2.2 ​ Configure the NDDS75 ==
138 +== 2.2 ​ Configure the NSE01 ==
147 147  
140 +
148 148  === 2.2.1 Test Requirement ===
149 149  
150 150  
151 151  (((
152 -To use NDDS75 in your city, make sure meet below requirements:
145 +To use NSE01 in your city, make sure meet below requirements:
153 153  )))
154 154  
155 155  * Your local operator has already distributed a NB-IoT Network there.
156 -* The local NB-IoT network used the band that NDDS75 supports.
149 +* The local NB-IoT network used the band that NSE01 supports.
157 157  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
158 158  
159 159  (((
160 -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.
153 +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
161 161  )))
162 162  
163 163  
164 -[[image:1657328756309-230.png]]
157 +[[image:1657249419225-449.png]]
165 165  
166 166  
160 +
167 167  === 2.2.2 Insert SIM card ===
168 168  
169 -
170 170  (((
171 171  Insert the NB-IoT Card get from your provider.
172 172  )))
... ... @@ -175,30 +175,29 @@
175 175  User need to take out the NB-IoT module and insert the SIM card like below:
176 176  )))
177 177  
178 -[[image:1657328884227-504.png]]
179 179  
172 +[[image:1657249468462-536.png]]
180 180  
181 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
182 182  
183 183  
176 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
177 +
184 184  (((
185 185  (((
186 -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.
180 +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.
187 187  )))
188 188  )))
189 189  
190 -[[image:image-20220709092052-2.png]]
191 191  
185 +**Connection:**
192 192  
193 -(% style="color:blue" %)**Connection:**
187 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
194 194  
195 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
189 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
196 196  
197 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
191 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
198 198  
199 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
200 200  
201 -
202 202  In the PC, use below serial tool settings:
203 203  
204 204  * Baud:  (% style="color:green" %)**9600**
... ... @@ -208,83 +208,72 @@
208 208  * Flow Control: (% style="color:green" %)**None**
209 209  
210 210  (((
211 -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.
203 +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.
212 212  )))
213 213  
214 -[[image:1657329814315-101.png]]
206 +[[image:image-20220708110657-3.png]]
215 215  
216 -
217 217  (((
218 -(% 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]]**
209 +(% 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/]]
219 219  )))
220 220  
221 221  
213 +
222 222  === 2.2.4 Use CoAP protocol to uplink data ===
223 223  
216 +(% 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/]]
224 224  
225 -(% 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/]]**
226 226  
227 -
228 -(((
229 229  **Use below commands:**
230 -)))
231 231  
232 -* (((
233 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
234 -)))
235 -* (((
236 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
237 -)))
238 -* (((
239 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
221 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
222 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
223 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
240 240  
241 -
242 -)))
243 -
244 -(((
245 245  For parameter description, please refer to AT command set
246 246  
247 -
248 -)))
227 +[[image:1657249793983-486.png]]
249 249  
250 -[[image:1657330452568-615.png]]
251 251  
230 +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.
252 252  
253 -(((
254 -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.
255 -)))
232 +[[image:1657249831934-534.png]]
256 256  
257 -[[image:1657330472797-498.png]]
258 258  
259 259  
260 260  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
261 261  
238 +This feature is supported since firmware version v1.0.1
262 262  
263 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
264 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
265 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
266 266  
267 -[[image:1657330501006-241.png]]
241 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
242 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
243 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
268 268  
245 +[[image:1657249864775-321.png]]
269 269  
270 -[[image:1657330533775-472.png]]
271 271  
248 +[[image:1657249930215-289.png]]
272 272  
250 +
251 +
273 273  === 2.2.6 Use MQTT protocol to uplink data ===
274 274  
254 +This feature is supported since firmware version v110
275 275  
276 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
277 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
278 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
279 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
280 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
281 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
282 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
283 283  
257 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
258 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
259 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
260 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
261 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
262 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
263 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
264 +
284 284  [[image:1657249978444-674.png]]
285 285  
286 286  
287 -[[image:1657330723006-866.png]]
268 +[[image:1657249990869-686.png]]
288 288  
289 289  
290 290  (((
... ... @@ -292,124 +292,75 @@
292 292  )))
293 293  
294 294  
276 +
295 295  === 2.2.7 Use TCP protocol to uplink data ===
296 296  
279 +This feature is supported since firmware version v110
297 297  
298 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
299 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
300 300  
301 -[[image:image-20220709093918-1.png]]
282 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
283 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
302 302  
285 +[[image:1657250217799-140.png]]
303 303  
304 -[[image:image-20220709093918-2.png]]
305 305  
288 +[[image:1657250255956-604.png]]
306 306  
307 -=== 2.2.8 Change Update Interval ===
308 308  
309 309  
292 +=== 2.2.8 Change Update Interval ===
293 +
310 310  User can use below command to change the (% style="color:green" %)**uplink interval**.
311 311  
312 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
296 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
313 313  
314 314  (((
315 -
316 -
317 317  (% style="color:red" %)**NOTE:**
300 +)))
318 318  
319 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
320 -
321 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
302 +(((
303 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
322 322  )))
323 323  
324 -(% 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).**
325 325  
326 326  
327 327  == 2.3  Uplink Payload ==
328 328  
329 -=== 2.3.1  Before Firmware v1.3.2 ===
310 +In this mode, uplink payload includes in total 18 bytes
330 330  
331 -
332 -In this mode, uplink payload includes in total 14 bytes
333 -
334 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %)
335 -|=(% style="width: 61px;background-color:#4F81BD;color:white" %)(((
312 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
313 +|=(% style="width: 60px;" %)(((
336 336  **Size(bytes)**
337 -)))|=(% style="width: 61px;background-color:#4F81BD;color:white" %)**6**|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2|=(% style="width: 37px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 82px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 102px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**
338 -|(% 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"]]
315 +)))|=(% 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**
316 +|(% 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"]]
339 339  
340 340  (((
341 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
319 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
342 342  )))
343 343  
344 344  
345 -[[image:1657331036973-987.png]]
323 +[[image:image-20220708111918-4.png]]
346 346  
347 347  
348 -The payload is **ASCII** string, representative same HEX:
349 -
350 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
351 -
352 -**where :**
353 -
354 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
355 -
356 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
357 -
358 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
359 -
360 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
361 -
362 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
363 -
364 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
365 -
366 -=== 2.3.2  Since firmware v1.3.2 ===
367 -
368 -
369 -In this mode, uplink payload includes 69 bytes in total by default.
370 -
371 -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.
372 -
373 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)
374 -|(% style="background-color:#4F81BD;color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4F81BD;color:white; width:40px" %)**8**|(% style="background-color:#4F81BD;color:white; width:25px" %)**2**|(% style="background-color:#4F81BD;color:white; width:25px" %)**2**|(% style="background-color:#4F81BD;color:white; width:60px" %)**1**|(% style="background-color:#4F81BD;color:white; width:25px" %)**1**|(% style="background-color:#4F81BD;color:white; width:40px" %)**1**|(% style="background-color:#4F81BD;color:white; width:40px" %)**2**|(% style="background-color:#4F81BD;color:white; width:70px" %)**4**|(% style="background-color:#4F81BD;color:white; width:40px" %)**2**|(% style="background-color:#4F81BD;color:white; width:65px" %)**4**
375 -|(% 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.......
376 -
377 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
378 -
379 -[[image:image-20220908175246-1.png]]
380 -
381 -
382 382  The payload is ASCII string, representative same HEX:
383 383  
384 -**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 (%%)**
328 +0x72403155615900640c7817075e0a8c02f900 where:
385 385  
386 -**where:**
330 +* Device ID: 0x 724031556159 = 724031556159
331 +* Version: 0x0064=100=1.0.0
387 387  
388 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
333 +* BAT: 0x0c78 = 3192 mV = 3.192V
334 +* Singal: 0x17 = 23
335 +* Soil Moisture: 0x075e= 1886 = 18.86  %
336 +* Soil Temperature:0x0a8c =2700=27 °C
337 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
338 +* Interrupt: 0x00 = 0
389 389  
390 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
391 -
392 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
393 -
394 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
395 -
396 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
397 -
398 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
399 -
400 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
401 -
402 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
403 -
404 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
405 -
406 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
407 -
408 408  == 2.4  Payload Explanation and Sensor Interface ==
409 409  
342 +
410 410  === 2.4.1  Device ID ===
411 411  
412 -
413 413  (((
414 414  By default, the Device ID equal to the last 6 bytes of IMEI.
415 415  )))
... ... @@ -416,12 +416,10 @@
416 416  
417 417  (((
418 418  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
419 -
420 -
421 421  )))
422 422  
423 423  (((
424 -(% style="color:blue" %)**Example :**
354 +**Example:**
425 425  )))
426 426  
427 427  (((
... ... @@ -429,36 +429,28 @@
429 429  )))
430 430  
431 431  (((
432 -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.
362 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
433 433  )))
434 434  
435 435  
436 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
437 437  
438 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
439 -
440 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
441 -
442 -
443 -(% style="color:blue" %)**Example :**
444 -
445 -AT+DEUI=868411056754138
446 -
447 -
448 448  === 2.4.2  Version Info ===
449 449  
450 -
451 451  (((
452 452  Specify the software version: 0x64=100, means firmware version 1.00.
453 453  )))
454 454  
455 455  (((
456 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
374 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
457 457  )))
458 458  
459 459  
378 +
460 460  === 2.4.3  Battery Info ===
461 461  
381 +(((
382 +Check the battery voltage for LSE01.
383 +)))
462 462  
463 463  (((
464 464  Ex1: 0x0B45 = 2885mV
... ... @@ -469,9 +469,9 @@
469 469  )))
470 470  
471 471  
394 +
472 472  === 2.4.4  Signal Strength ===
473 473  
474 -
475 475  (((
476 476  NB-IoT Network signal Strength.
477 477  )))
... ... @@ -501,32 +501,85 @@
501 501  )))
502 502  
503 503  
504 -=== 2.4.5  Distance ===
505 505  
427 +=== 2.4.5  Soil Moisture ===
506 506  
507 -Get the distance. Flat object range 280mm - 7500mm.
429 +(((
430 +(((
431 +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.
432 +)))
433 +)))
508 508  
509 509  (((
510 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
436 +(((
437 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
511 511  )))
439 +)))
512 512  
513 513  (((
514 514  
515 515  )))
516 516  
517 -=== 2.4.6  Digital Interrupt ===
445 +(((
446 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
447 +)))
518 518  
519 519  
450 +
451 +=== 2.4.6  Soil Temperature ===
452 +
520 520  (((
521 -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.
454 +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
522 522  )))
523 523  
524 524  (((
458 +**Example**:
459 +)))
460 +
461 +(((
462 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
463 +)))
464 +
465 +(((
466 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
467 +)))
468 +
469 +
470 +
471 +=== 2.4.7  Soil Conductivity (EC) ===
472 +
473 +(((
474 +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).
475 +)))
476 +
477 +(((
478 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
479 +)))
480 +
481 +(((
482 +Generally, the EC value of irrigation water is less than 800uS / cm.
483 +)))
484 +
485 +(((
486 +
487 +)))
488 +
489 +(((
490 +
491 +)))
492 +
493 +=== 2.4.8  Digital Interrupt ===
494 +
495 +(((
496 +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.
497 +)))
498 +
499 +(((
525 525  The command is:
526 526  )))
527 527  
528 528  (((
529 -(% 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]])**.**
504 +(% 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]])**.**
530 530  )))
531 531  
532 532  
... ... @@ -534,8 +534,9 @@
534 534  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.
535 535  )))
536 536  
512 +
537 537  (((
538 -**Example:**
514 +Example:
539 539  )))
540 540  
541 541  (((
... ... @@ -547,13 +547,14 @@
547 547  )))
548 548  
549 549  
550 -=== 2.4.7  ​+5V Output ===
551 551  
527 +=== 2.4.9  ​+5V Output ===
552 552  
553 553  (((
554 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
530 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
555 555  )))
556 556  
533 +
557 557  (((
558 558  The 5V output time can be controlled by AT Command.
559 559  )))
... ... @@ -567,16 +567,13 @@
567 567  )))
568 568  
569 569  
547 +
570 570  == 2.5  Downlink Payload ==
571 571  
550 +By default, NSE01 prints the downlink payload to console port.
572 572  
573 -By default, NDDS75 prints the downlink payload to console port.
552 +[[image:image-20220708133731-5.png]]
574 574  
575 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:520px" %)
576 -|(% style="background-color:#4F81BD;color:white; width:208px" %)**Downlink Control Type**|(% style="background-color:#4F81BD;color:white; width:56px" %)**FPort**|(% style="background-color:#4F81BD;color:white; width:100px" %)**Type Code**|(% style="background-color:#4F81BD;color:white; width:154px" %)**Downlink payload size(bytes)**
577 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
578 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
579 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
580 580  
581 581  (((
582 582  (% style="color:blue" %)**Examples:**
... ... @@ -611,7 +611,7 @@
611 611  )))
612 612  
613 613  (((
614 -If payload = 0x04FF, it will reset the NDDS75
588 +If payload = 0x04FF, it will reset the NSE01
615 615  )))
616 616  
617 617  
... ... @@ -622,195 +622,239 @@
622 622  )))
623 623  
624 624  
625 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
626 626  
600 +== 2.6  ​LED Indicator ==
627 627  
628 -(% style="color:blue" %)** ➢ AT Command:**
602 +(((
603 +The NSE01 has an internal LED which is to show the status of different state.
629 629  
630 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
631 631  
632 -² When min=0, and max≠0, Alarm higher than max
606 +* 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)
607 +* Then the LED will be on for 1 second means device is boot normally.
608 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
609 +* For each uplink probe, LED will be on for 500ms.
610 +)))
633 633  
634 -² When min≠0, and max=0, Alarm lower than min
635 635  
636 -² When min≠0 and max≠0, Alarm higher than max or lower than min
637 637  
638 638  
639 -(% style="color:blue" %)** Example:**
615 +== 2.7  Installation in Soil ==
640 640  
641 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
617 +__**Measurement the soil surface**__
642 642  
619 +(((
620 +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]]
621 +)))
643 643  
644 -== 2.7  Set the number of data to be uploaded and the recording time ==
623 +[[image:1657259653666-883.png]] ​
645 645  
646 646  
647 -(% style="color:blue" %)** ➢ AT Command:**
626 +(((
627 +
648 648  
649 -* (% 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)
650 -* (% 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.
629 +(((
630 +Dig a hole with diameter > 20CM.
631 +)))
651 651  
652 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
633 +(((
634 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
635 +)))
636 +)))
653 653  
654 -[[image:image-20221009001114-1.png||height="687" width="955"]]
638 +[[image:1654506665940-119.png]]
655 655  
640 +(((
641 +
642 +)))
656 656  
657 -== 2.8  Read or Clear cached data ==
658 658  
645 +== 2.8  ​Firmware Change Log ==
659 659  
660 -(% style="color:blue" %)** ➢ AT Command:**
661 661  
662 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
663 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
648 +Download URL & Firmware Change log
664 664  
665 -[[image:image-20220908175333-2.png]]
650 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
666 666  
667 667  
668 -== 2.9  ​LED Indicator ==
653 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
669 669  
670 670  
671 -The NDDS75 has an internal LED which is to show the status of different state.
672 672  
657 +== 2.9  ​Battery Analysis ==
673 673  
674 -* 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)
675 -* Then the LED will be on for 1 second means device is boot normally.
676 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
677 -* For each uplink probe, LED will be on for 500ms.
659 +=== 2.9.1  ​Battery Type ===
678 678  
661 +
679 679  (((
680 -
663 +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.
681 681  )))
682 682  
683 683  
684 -== 2.10  ​Firmware Change Log ==
667 +(((
668 +The battery is designed to last for several years depends on the actually use environment and update interval. 
669 +)))
685 685  
686 686  
687 687  (((
688 -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]]
673 +The battery related documents as below:
689 689  )))
690 690  
676 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
677 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
678 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
679 +
691 691  (((
692 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
681 +[[image:image-20220708140453-6.png]]
693 693  )))
694 694  
695 695  
696 -== 2.11 Battery & Power Consumption ==
697 697  
686 +=== 2.9.2  Power consumption Analyze ===
698 698  
699 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
688 +(((
689 +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.
690 +)))
700 700  
701 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
702 702  
693 +(((
694 +Instruction to use as below:
695 +)))
703 703  
704 -= 3. ​ Access NB-IoT Module =
697 +(((
698 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
699 +)))
705 705  
706 706  
707 707  (((
708 -Users can directly access the AT command set of the NB-IoT module.
703 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
709 709  )))
710 710  
706 +* (((
707 +Product Model
708 +)))
709 +* (((
710 +Uplink Interval
711 +)))
712 +* (((
713 +Working Mode
714 +)))
715 +
711 711  (((
712 -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/]] 
717 +And the Life expectation in difference case will be shown on the right.
718 +)))
713 713  
714 -
720 +[[image:image-20220708141352-7.jpeg]]
721 +
722 +
723 +
724 +=== 2.9.3  ​Battery Note ===
725 +
726 +(((
727 +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.
715 715  )))
716 716  
717 -[[image:1657333200519-600.png]]
718 718  
719 719  
720 -= 4.  Using the AT Commands =
732 +=== 2.9.4  Replace the battery ===
721 721  
722 -== 4.1  Access AT Commands ==
734 +(((
735 +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).
736 +)))
723 723  
724 724  
725 -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]]
726 726  
740 += 3. ​ Access NB-IoT Module =
727 727  
728 -AT+<CMD>?  :  Help on <CMD>
742 +(((
743 +Users can directly access the AT command set of the NB-IoT module.
744 +)))
729 729  
730 -AT+<CMD>         :  Run <CMD>
746 +(((
747 +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/]] 
748 +)))
731 731  
732 -AT+<CMD>=<value> :  Set the value
750 +[[image:1657261278785-153.png]]
733 733  
734 -AT+<CMD>=?  :  Get the value
735 735  
736 736  
737 -(% style="color:#037691" %)**General Commands**(%%)      
754 += 4.  Using the AT Commands =
738 738  
739 -AT  :  Attention       
756 +== 4.1  Access AT Commands ==
740 740  
741 -AT?  :  Short Help     
758 +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/]]
742 742  
743 -ATZ  :  MCU Reset    
744 744  
745 -AT+TDC  :  Application Data Transmission Interval
761 +AT+<CMD>?  : Help on <CMD>
746 746  
747 -AT+CFG  :  Print all configurations
763 +AT+<CMD>         : Run <CMD>
748 748  
749 -AT+CFGMOD           :  Working mode selection
765 +AT+<CMD>=<value> : Set the value
750 750  
751 -AT+INTMOD            :  Set the trigger interrupt mode
767 +AT+<CMD>=?  : Get the value
752 752  
753 -AT+5VT  :  Set extend the time of 5V power  
754 754  
755 -AT+PRO  :  Choose agreement
770 +(% style="color:#037691" %)**General Commands**(%%)      
756 756  
757 -AT+WEIGRE  :  Get weight or set weight to 0
772 +AT  : Attention       
758 758  
759 -AT+WEIGAP  :  Get or Set the GapValue of weight
774 +AT?  : Short Help     
760 760  
761 -AT+RXDL  :  Extend the sending and receiving time
776 +ATZ  : MCU Reset    
762 762  
763 -AT+CNTFAC  :  Get or set counting parameters
778 +AT+TDC  : Application Data Transmission Interval
764 764  
765 -AT+SERVADDR  :  Server Address
780 +AT+CFG  : Print all configurations
766 766  
767 -AT+TR  :  Get or Set record time"
782 +AT+CFGMOD           : Working mode selection
768 768  
769 -AT+APN     :  Get or set the APN
784 +AT+INTMOD            : Set the trigger interrupt mode
770 770  
771 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
786 +AT+5VT  : Set extend the time of 5V power  
772 772  
773 -AT+DNSCFG  : Get or Set DNS Server
788 +AT+PRO  : Choose agreement
774 774  
775 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
790 +AT+WEIGRE  : Get weight or set weight to 0
776 776  
777 -AT+NOUD  :  Get or Set the number of data to be uploaded
792 +AT+WEIGAP  : Get or Set the GapValue of weight
778 778  
779 -AT+CDP     :  Read or Clear cached data
794 +AT+RXDL  : Extend the sending and receiving time
780 780  
781 -AT+LDDSALARM :  Get or Set alarm of distance
796 +AT+CNTFAC  : Get or set counting parameters
782 782  
798 +AT+SERVADDR  : Server Address
783 783  
800 +
784 784  (% style="color:#037691" %)**COAP Management**      
785 785  
786 -AT+URI            :  Resource parameters
803 +AT+URI            : Resource parameters
787 787  
788 788  
789 789  (% style="color:#037691" %)**UDP Management**
790 790  
791 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
808 +AT+CFM          : Upload confirmation mode (only valid for UDP)
792 792  
793 793  
794 794  (% style="color:#037691" %)**MQTT Management**
795 795  
796 -AT+CLIENT  :  Get or Set MQTT client
813 +AT+CLIENT               : Get or Set MQTT client
797 797  
798 -AT+UNAME  :  Get or Set MQTT Username
815 +AT+UNAME  : Get or Set MQTT Username
799 799  
800 -AT+PWD  :  Get or Set MQTT password
817 +AT+PWD                  : Get or Set MQTT password
801 801  
802 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
819 +AT+PUBTOPIC  : Get or Set MQTT publish topic
803 803  
804 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
821 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
805 805  
806 806  
807 807  (% style="color:#037691" %)**Information**          
808 808  
809 -AT+FDR  :  Factory Data Reset
826 +AT+FDR  : Factory Data Reset
810 810  
811 -AT+PWORD  :  Serial Access Password
828 +AT+PWORD  : Serial Access Password
812 812  
813 813  
831 +
814 814  = ​5.  FAQ =
815 815  
816 816  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -825,10 +825,18 @@
825 825  )))
826 826  
827 827  (((
828 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
846 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
829 829  )))
830 830  
831 831  
850 +
851 +== 5.2  Can I calibrate NSE01 to different soil types? ==
852 +
853 +(((
854 +NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
855 +)))
856 +
857 +
832 832  = 6.  Trouble Shooting =
833 833  
834 834  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -843,26 +843,27 @@
843 843  
844 844  )))
845 845  
872 +
846 846  == 6.2  AT Command input doesn't work ==
847 847  
848 -
849 849  (((
850 850  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.
877 +
878 +
851 851  )))
852 852  
853 853  
854 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
855 -
856 -
857 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
858 -
859 -
860 860  = 7. ​ Order Info =
861 861  
862 862  
863 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
885 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
864 864  
865 865  
888 +(% class="wikigeneratedid" %)
889 +(((
890 +
891 +)))
892 +
866 866  = 8.  Packing Info =
867 867  
868 868  (((
... ... @@ -870,7 +870,7 @@
870 870  
871 871  (% style="color:#037691" %)**Package Includes**:
872 872  
873 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
900 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
874 874  * External antenna x 1
875 875  )))
876 876  
... ... @@ -879,21 +879,18 @@
879 879  
880 880  (% style="color:#037691" %)**Dimension and weight**:
881 881  
882 -* Device Size: 13.0 x 5 x 4.5 cm
883 -* Device Weight: 150g
884 -* Package Size / pcs : 15 x 12x 5.5 cm
885 -* Weight / pcs : 220g
909 +* Size: 195 x 125 x 55 mm
910 +* Weight:   420g
886 886  )))
887 887  
888 888  (((
889 889  
890 890  
916 +
891 891  
892 892  )))
893 893  
894 894  = 9.  Support =
895 895  
896 -
897 897  * 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.
898 -
899 899  * 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]]
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-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