Last modified by Bei Jinggeng on 2024/05/31 09:53

From version 108.17
edited by Xiaoling
on 2023/05/17 18:20
Change comment: There is no comment for this version
To version 76.1
edited by Xiaoling
on 2022/07/09 09:03
Change comment: Uploaded new attachment "1657328609906-564.png", version {1}

Summary

Details

Page properties
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  )))
... ... @@ -176,30 +176,28 @@
176 176  )))
177 177  
178 178  
179 -[[image:1657328884227-504.png]]
172 +[[image:1657249468462-536.png]]
180 180  
181 181  
182 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
183 183  
176 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
184 184  
185 185  (((
186 186  (((
187 -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.
188 188  )))
189 189  )))
190 190  
191 -[[image:image-20220709092052-2.png]]
192 192  
185 +**Connection:**
193 193  
194 -(% style="color:blue" %)**Connection:**
187 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
195 195  
196 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
189 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
197 197  
198 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
191 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
199 199  
200 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
201 201  
202 -
203 203  In the PC, use below serial tool settings:
204 204  
205 205  * Baud:  (% style="color:green" %)**9600**
... ... @@ -209,87 +209,72 @@
209 209  * Flow Control: (% style="color:green" %)**None**
210 210  
211 211  (((
212 -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.
213 213  )))
214 214  
215 -[[image:1657329814315-101.png]]
206 +[[image:image-20220708110657-3.png]]
216 216  
217 -
218 218  (((
219 -(% 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/]]
220 220  )))
221 221  
222 222  
213 +
223 223  === 2.2.4 Use CoAP protocol to uplink data ===
224 224  
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/]]
225 225  
226 -(% 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/]]**
227 227  
228 -
229 -(((
230 230  **Use below commands:**
231 -)))
232 232  
233 -* (((
234 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
235 -)))
236 -* (((
237 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
238 -)))
239 -* (((
240 -(% 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
241 241  
242 -
243 -
244 -)))
245 -
246 -(((
247 247  For parameter description, please refer to AT command set
248 248  
249 -
250 -)))
227 +[[image:1657249793983-486.png]]
251 251  
252 -[[image:1657330452568-615.png]]
253 253  
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.
254 254  
232 +[[image:1657249831934-534.png]]
255 255  
256 -(((
257 -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.
258 258  
259 -
260 -)))
261 261  
262 -[[image:1657330472797-498.png]]
236 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
263 263  
238 +This feature is supported since firmware version v1.0.1
264 264  
265 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
266 266  
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
267 267  
268 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
269 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
270 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
245 +[[image:1657249864775-321.png]]
271 271  
272 -[[image:1657330501006-241.png]]
273 273  
248 +[[image:1657249930215-289.png]]
274 274  
275 -[[image:1657330533775-472.png]]
276 276  
277 277  
278 278  === 2.2.6 Use MQTT protocol to uplink data ===
279 279  
254 +This feature is supported since firmware version v110
280 280  
281 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
282 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
283 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
284 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
285 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
286 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
287 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
288 288  
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 +
289 289  [[image:1657249978444-674.png]]
290 290  
291 291  
292 -[[image:1657330723006-866.png]]
268 +[[image:1657249990869-686.png]]
293 293  
294 294  
295 295  (((
... ... @@ -297,125 +297,75 @@
297 297  )))
298 298  
299 299  
276 +
300 300  === 2.2.7 Use TCP protocol to uplink data ===
301 301  
279 +This feature is supported since firmware version v110
302 302  
303 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
304 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
305 305  
306 -[[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
307 307  
285 +[[image:1657250217799-140.png]]
308 308  
309 -[[image:image-20220709093918-2.png]]
310 310  
288 +[[image:1657250255956-604.png]]
311 311  
312 -=== 2.2.8 Change Update Interval ===
313 313  
314 314  
292 +=== 2.2.8 Change Update Interval ===
293 +
315 315  User can use below command to change the (% style="color:green" %)**uplink interval**.
316 316  
317 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
296 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
318 318  
319 319  (((
320 -
321 -
322 -
323 323  (% style="color:red" %)**NOTE:**
300 +)))
324 324  
325 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
326 -
327 -(% 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.
328 328  )))
329 329  
330 -(% 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).**
331 331  
332 332  
333 333  == 2.3  Uplink Payload ==
334 334  
335 -=== 2.3.1  Before Firmware v1.3.2 ===
310 +In this mode, uplink payload includes in total 18 bytes
336 336  
337 -
338 -In this mode, uplink payload includes in total 14 bytes
339 -
340 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %)
341 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)(((
312 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
313 +|=(% style="width: 60px;" %)(((
342 342  **Size(bytes)**
343 -)))|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**
344 -|(% 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"]]
345 345  
346 346  (((
347 -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.
348 348  )))
349 349  
350 350  
351 -[[image:1657331036973-987.png]]
323 +[[image:image-20220708111918-4.png]]
352 352  
353 353  
354 -The payload is **ASCII** string, representative same HEX:
355 -
356 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
357 -
358 -**where :**
359 -
360 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
361 -
362 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
363 -
364 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
365 -
366 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
367 -
368 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
369 -
370 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
371 -
372 -=== 2.3.2  Since firmware v1.3.2 ===
373 -
374 -
375 -In this mode, uplink payload includes 69 bytes in total by default.
376 -
377 -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.
378 -
379 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:490px" %)
380 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**4**
381 -|=(% 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.......
382 -
383 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
384 -
385 -[[image:image-20220908175246-1.png]]
386 -
387 -
388 388  The payload is ASCII string, representative same HEX:
389 389  
390 -**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:
391 391  
392 -**where:**
330 +* Device ID: 0x 724031556159 = 724031556159
331 +* Version: 0x0064=100=1.0.0
393 393  
394 -* (% 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
395 395  
396 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
397 -
398 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
399 -
400 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
401 -
402 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
403 -
404 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
405 -
406 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
407 -
408 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
409 -
410 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
411 -
412 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
413 -
414 414  == 2.4  Payload Explanation and Sensor Interface ==
415 415  
342 +
416 416  === 2.4.1  Device ID ===
417 417  
418 -
419 419  (((
420 420  By default, the Device ID equal to the last 6 bytes of IMEI.
421 421  )))
... ... @@ -422,12 +422,10 @@
422 422  
423 423  (((
424 424  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
425 -
426 -
427 427  )))
428 428  
429 429  (((
430 -(% style="color:blue" %)**Example :**
354 +**Example:**
431 431  )))
432 432  
433 433  (((
... ... @@ -435,36 +435,28 @@
435 435  )))
436 436  
437 437  (((
438 -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.
439 439  )))
440 440  
441 441  
442 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
443 443  
444 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
445 -
446 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
447 -
448 -
449 -(% style="color:blue" %)**Example :**
450 -
451 -AT+DEUI=868411056754138
452 -
453 -
454 454  === 2.4.2  Version Info ===
455 455  
456 -
457 457  (((
458 458  Specify the software version: 0x64=100, means firmware version 1.00.
459 459  )))
460 460  
461 461  (((
462 -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.
463 463  )))
464 464  
465 465  
378 +
466 466  === 2.4.3  Battery Info ===
467 467  
381 +(((
382 +Check the battery voltage for LSE01.
383 +)))
468 468  
469 469  (((
470 470  Ex1: 0x0B45 = 2885mV
... ... @@ -475,9 +475,9 @@
475 475  )))
476 476  
477 477  
394 +
478 478  === 2.4.4  Signal Strength ===
479 479  
480 -
481 481  (((
482 482  NB-IoT Network signal Strength.
483 483  )))
... ... @@ -507,30 +507,77 @@
507 507  )))
508 508  
509 509  
510 -=== 2.4.5  Distance ===
511 511  
427 +=== 2.4.5  Soil Moisture ===
512 512  
513 -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 +)))
514 514  
515 515  (((
516 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
436 +(((
437 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
517 517  )))
439 +)))
518 518  
519 519  (((
442 +
443 +)))
444 +
520 520  (((
521 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
446 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
522 522  )))
448 +
449 +
450 +
451 +=== 2.4.6  Soil Temperature ===
452 +
453 +(((
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
523 523  )))
524 524  
525 525  (((
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 +(((
526 526  
527 527  )))
528 528  
529 -=== 2.4.6  Digital Interrupt ===
489 +(((
490 +
491 +)))
530 530  
493 +=== 2.4.8  Digital Interrupt ===
531 531  
532 532  (((
533 -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.
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.
534 534  )))
535 535  
536 536  (((
... ... @@ -538,7 +538,7 @@
538 538  )))
539 539  
540 540  (((
541 -(% 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]])**.**
542 542  )))
543 543  
544 544  
... ... @@ -560,24 +560,20 @@
560 560  )))
561 561  
562 562  
563 -=== 2.4.7  ​+5V Output ===
564 564  
527 +=== 2.4.9  ​+5V Output ===
565 565  
566 566  (((
567 -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. 
568 568  )))
569 569  
570 570  
571 571  (((
572 572  The 5V output time can be controlled by AT Command.
573 -
574 -
575 575  )))
576 576  
577 577  (((
578 578  (% style="color:blue" %)**AT+5VT=1000**
579 -
580 -
581 581  )))
582 582  
583 583  (((
... ... @@ -585,19 +585,14 @@
585 585  )))
586 586  
587 587  
547 +
588 588  == 2.5  Downlink Payload ==
589 589  
550 +By default, NSE01 prints the downlink payload to console port.
590 590  
591 -By default, NDDS75 prints the downlink payload to console port.
552 +[[image:image-20220708133731-5.png]]
592 592  
593 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
594 -|(% style="width:208px;background-color:#D9E2F3;color:#0070C0" %)**Downlink Control Type**|(% style="width:56px;background-color:#D9E2F3;color:#0070C0" %)**FPort**|(% style="width:100px;background-color:#D9E2F3;color:#0070C0" %)**Type Code**|(% style="width:154px;background-color:#D9E2F3;color:#0070C0" %)**Downlink payload size(bytes)**
595 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
596 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
597 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
598 598  
599 -
600 -
601 601  (((
602 602  (% style="color:blue" %)**Examples:**
603 603  )))
... ... @@ -631,7 +631,7 @@
631 631  )))
632 632  
633 633  (((
634 -If payload = 0x04FF, it will reset the NDDS75
588 +If payload = 0x04FF, it will reset the NSE01
635 635  )))
636 636  
637 637  
... ... @@ -642,195 +642,239 @@
642 642  )))
643 643  
644 644  
645 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
646 646  
600 +== 2.6  ​LED Indicator ==
647 647  
648 -(% style="color:blue" %)** ➢ AT Command:**
602 +(((
603 +The NSE01 has an internal LED which is to show the status of different state.
649 649  
650 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
651 651  
652 -² 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 +)))
653 653  
654 -² When min≠0, and max=0, Alarm lower than min
655 655  
656 -² When min≠0 and max≠0, Alarm higher than max or lower than min
657 657  
658 658  
659 -(% style="color:blue" %)** Example:**
615 +== 2.7  Installation in Soil ==
660 660  
661 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
617 +__**Measurement the soil surface**__
662 662  
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 +)))
663 663  
664 -== 2.7  Set the number of data to be uploaded and the recording time ==
623 +[[image:1657259653666-883.png]]
665 665  
666 666  
667 -(% style="color:blue" %)** ➢ AT Command:**
626 +(((
627 +
668 668  
669 -* (% 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)
670 -* (% 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 +)))
671 671  
672 - 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 +)))
673 673  
674 -[[image:image-20221009001114-1.png||height="687" width="955"]]
638 +[[image:1654506665940-119.png]]
675 675  
640 +(((
641 +
642 +)))
676 676  
677 -== 2.8  Read or Clear cached data ==
678 678  
645 +== 2.8  ​Firmware Change Log ==
679 679  
680 -(% style="color:blue" %)** ➢ AT Command:**
681 681  
682 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
683 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
648 +Download URL & Firmware Change log
684 684  
685 -[[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/]]
686 686  
687 687  
688 -== 2.9  ​LED Indicator ==
653 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
689 689  
690 690  
691 -The NDDS75 has an internal LED which is to show the status of different state.
692 692  
657 +== 2.9  ​Battery Analysis ==
693 693  
694 -* 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)
695 -* Then the LED will be on for 1 second means device is boot normally.
696 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
697 -* For each uplink probe, LED will be on for 500ms.
659 +=== 2.9.1  ​Battery Type ===
698 698  
661 +
699 699  (((
700 -
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.
701 701  )))
702 702  
703 703  
704 -== 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 +)))
705 705  
706 706  
707 707  (((
708 -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:
709 709  )))
710 710  
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 +
711 711  (((
712 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
681 +[[image:image-20220708140453-6.png]]
713 713  )))
714 714  
715 715  
716 -== 2.11 Battery & Power Consumption ==
717 717  
686 +=== 2.9.2  Power consumption Analyze ===
718 718  
719 -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 +)))
720 720  
721 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
722 722  
693 +(((
694 +Instruction to use as below:
695 +)))
723 723  
724 -= 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 +)))
725 725  
726 726  
727 727  (((
728 -Users can directly access the AT command set of the NB-IoT module.
703 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
729 729  )))
730 730  
706 +* (((
707 +Product Model
708 +)))
709 +* (((
710 +Uplink Interval
711 +)))
712 +* (((
713 +Working Mode
714 +)))
715 +
731 731  (((
732 -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 +)))
733 733  
734 -
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.
735 735  )))
736 736  
737 -[[image:1657333200519-600.png]]
738 738  
739 739  
740 -= 4Using the AT Commands =
732 +=== 2.9.4  Replace the battery ===
741 741  
742 -== 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 +)))
743 743  
744 744  
745 -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]]
746 746  
740 += 3. ​ Access NB-IoT Module =
747 747  
748 -AT+<CMD>?  :  Help on <CMD>
742 +(((
743 +Users can directly access the AT command set of the NB-IoT module.
744 +)))
749 749  
750 -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 +)))
751 751  
752 -AT+<CMD>=<value> :  Set the value
750 +[[image:1657261278785-153.png]]
753 753  
754 -AT+<CMD>=?  :  Get the value
755 755  
756 756  
757 -(% style="color:#037691" %)**General Commands**(%%)      
754 += 4.  Using the AT Commands =
758 758  
759 -AT  :  Attention       
756 +== 4.1  Access AT Commands ==
760 760  
761 -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/]]
762 762  
763 -ATZ  :  MCU Reset    
764 764  
765 -AT+TDC  :  Application Data Transmission Interval
761 +AT+<CMD>?  : Help on <CMD>
766 766  
767 -AT+CFG  :  Print all configurations
763 +AT+<CMD>         : Run <CMD>
768 768  
769 -AT+CFGMOD           Working mode selection
765 +AT+<CMD>=<value> : Set the value
770 770  
771 -AT+INTMO           Set the trigger interrupt mode
767 +AT+<CMD>=?  : Get the value
772 772  
773 -AT+5VT  :  Set extend the time of 5V power  
774 774  
775 -AT+PRO  :  Choose agreement
770 +(% style="color:#037691" %)**General Commands**(%%)      
776 776  
777 -AT+WEIGRE  Get weight or set weight to 0
772 +AT  : Attention       
778 778  
779 -AT+WEIGAP  Get or Set the GapValue of weight
774 +AT?  : Short Help     
780 780  
781 -AT+RXDL  Extend the sending and receiving time
776 +ATZ  : MCU Reset    
782 782  
783 -AT+CNTFA Get or set counting parameters
778 +AT+TD: Application Data Transmission Interval
784 784  
785 -AT+SERVADDR  Server Address
780 +AT+CFG  : Print all configurations
786 786  
787 -AT+TR  :  Get or Set record time"
782 +AT+CFGMOD           : Working mode selection
788 788  
789 -AT+APN     :  Get or set the APN
784 +AT+INTMOD            : Set the trigger interrupt mode
790 790  
791 -AT+FBAND  Get or Set whether to automatically modify the frequency band
786 +AT+5VT  : Set extend the time of 5V power  
792 792  
793 -AT+DNSCFG  : Get or Set DNS Server
788 +AT+PRO  : Choose agreement
794 794  
795 -AT+GETSENSORVALU  Returns the current sensor measurement
790 +AT+WEIGRE  : Get weight or set weight to 0
796 796  
797 -AT+NOUD  Get or Set the number of data to be uploaded
792 +AT+WEIGAP  : Get or Set the GapValue of weight
798 798  
799 -AT+CDP     Read or Clear cached data
794 +AT+RXDL  : Extend the sending and receiving time
800 800  
801 -AT+LDDSALARM :  Get or Set alarm of distance
796 +AT+CNTFAC  : Get or set counting parameters
802 802  
798 +AT+SERVADDR  : Server Address
803 803  
800 +
804 804  (% style="color:#037691" %)**COAP Management**      
805 805  
806 -AT+URI            :  Resource parameters
803 +AT+URI            : Resource parameters
807 807  
808 808  
809 809  (% style="color:#037691" %)**UDP Management**
810 810  
811 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
808 +AT+CFM          : Upload confirmation mode (only valid for UDP)
812 812  
813 813  
814 814  (% style="color:#037691" %)**MQTT Management**
815 815  
816 -AT+CLIENT  :  Get or Set MQTT client
813 +AT+CLIENT               : Get or Set MQTT client
817 817  
818 -AT+UNAME  Get or Set MQTT Username
815 +AT+UNAME  : Get or Set MQTT Username
819 819  
820 -AT+PWD  :  Get or Set MQTT password
817 +AT+PWD                  : Get or Set MQTT password
821 821  
822 -AT+PUBTOPIC  Get or Set MQTT publish topic
819 +AT+PUBTOPIC  : Get or Set MQTT publish topic
823 823  
824 -AT+SUBTOPIC  Get or Set MQTT subscription topic
821 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
825 825  
826 826  
827 827  (% style="color:#037691" %)**Information**          
828 828  
829 -AT+FDR  :  Factory Data Reset
826 +AT+FDR  : Factory Data Reset
830 830  
831 -AT+PWORD  :  Serial Access Password
828 +AT+PWORD  : Serial Access Password
832 832  
833 833  
831 +
834 834  = ​5.  FAQ =
835 835  
836 836  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -845,10 +845,18 @@
845 845  )))
846 846  
847 847  (((
848 -(% 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.
849 849  )))
850 850  
851 851  
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 +
852 852  = 6.  Trouble Shooting =
853 853  
854 854  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -863,26 +863,27 @@
863 863  
864 864  )))
865 865  
872 +
866 866  == 6.2  AT Command input doesn't work ==
867 867  
868 -
869 869  (((
870 870  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 +
871 871  )))
872 872  
873 873  
874 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
875 -
876 -
877 -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]]//**.
878 -
879 -
880 880  = 7. ​ Order Info =
881 881  
882 882  
883 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
885 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
884 884  
885 885  
888 +(% class="wikigeneratedid" %)
889 +(((
890 +
891 +)))
892 +
886 886  = 8.  Packing Info =
887 887  
888 888  (((
... ... @@ -890,7 +890,7 @@
890 890  
891 891  (% style="color:#037691" %)**Package Includes**:
892 892  
893 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
900 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
894 894  * External antenna x 1
895 895  )))
896 896  
... ... @@ -899,21 +899,18 @@
899 899  
900 900  (% style="color:#037691" %)**Dimension and weight**:
901 901  
902 -* Device Size: 13.0 x 5 x 4.5 cm
903 -* Device Weight: 150g
904 -* Package Size / pcs : 15 x 12x 5.5 cm
905 -* Weight / pcs : 220g
909 +* Size: 195 x 125 x 55 mm
910 +* Weight:   420g
906 906  )))
907 907  
908 908  (((
909 909  
910 910  
916 +
911 911  
912 912  )))
913 913  
914 914  = 9.  Support =
915 915  
916 -
917 917  * 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.
918 -
919 919  * 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]]
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