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