Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 76.1
edited by Xiaoling
on 2022/07/09 09:03
Change comment: Uploaded new attachment "1657328609906-564.png", version {1}
To version 108.10
edited by Xiaoling
on 2023/04/04 12:01
Change comment: There is no comment for this version

Summary

Details

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