Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 81.2 >
edited by Xiaoling
on 2022/12/07 18:05
To version < 79.1 >
edited by Xiaoling
on 2022/12/07 17:40
>
Change comment: Uploaded new attachment "1670406036256-101.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -52,6 +52,7 @@
52 52  * 8500mAh Battery for long-term use
53 53  
54 54  
55 +
55 55  == 1.3 Radar probe specification ==
56 56  
57 57  
... ... @@ -66,6 +66,7 @@
66 66  
67 67  
68 68  
70 +
69 69  == 1.4  Storage Temperature ==
70 70  
71 71  
... ... @@ -90,6 +90,7 @@
90 90  * Bottom water level monitoring
91 91  
92 92  
95 +
93 93  == 1.6  Specification ==
94 94  
95 95  
... ... @@ -108,6 +108,7 @@
108 108  * B28 @H-FDD: 700MHz
109 109  
110 110  
114 +
111 111  == 1.7  Installation ==
112 112  
113 113  
... ... @@ -160,10 +160,10 @@
160 160  [[image:image-20221021110745-6.png]] ​
161 161  
162 162  
163 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
167 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
164 164  
165 165  
166 -User need to configure NMDS200 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NMDS200 support AT Commands, user can use a USB to TTL adapter to connect to NMDS200 and use AT Commands to configure it, as below.
170 +User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
167 167  
168 168  (% style="color:blue" %)**Connection:**
169 169  
... ... @@ -186,11 +186,11 @@
186 186  
187 187  * Flow Control: (% style="color:red" %)**None**
188 188  
189 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
193 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
190 190  
191 191  ​[[image:image-20221021110817-7.png]]
192 192  
193 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
197 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
194 194  
195 195  
196 196  (% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
... ... @@ -197,7 +197,7 @@
197 197  
198 198  
199 199  
200 -=== 2.2.3 Use CoAP protocol to uplink data ===
204 +=== 2.2.4 Use CoAP protocol to uplink data ===
201 201  
202 202  
203 203  (% style="color:red" %)**Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
... ... @@ -216,12 +216,12 @@
216 216  [[image:image-20221021110948-8.png]]
217 217  
218 218  
219 -After configuring the server address and (% style="color:green" %)**reset NMDS200**(%%) (via AT+ATZ ), NMDS200 will start to uplink sensor values to the CoAP server.
223 +After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
220 220  
221 -[[image:1670405841875-916.png]] ​
225 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
222 222  
223 223  
224 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
228 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
225 225  
226 226  
227 227  (% style="color:blue" %)**AT Commands:**
... ... @@ -239,7 +239,7 @@
239 239  
240 240  ​
241 241  
242 -=== 2.2.5 Use MQTT protocol to uplink data ===
246 +=== 2.2.6 Use MQTT protocol to uplink data ===
243 243  
244 244  
245 245  (% style="color:blue" %)**AT Commands:**
... ... @@ -261,7 +261,7 @@
261 261  ​ [[image:image-20221118103445-7.png]]
262 262  
263 263  
264 -[[image:1670405928926-116.png]]
268 +[[image:image-20221118103453-8.png||height="608" width="841"]]
265 265  
266 266  ​
267 267  
... ... @@ -268,7 +268,7 @@
268 268  MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
269 269  
270 270  
271 -=== 2.2.6 Use TCP protocol to uplink data ===
275 +=== 2.2.7 Use TCP protocol to uplink data ===
272 272  
273 273  
274 274  (% style="color:blue" %)**AT Commands:**
... ... @@ -277,19 +277,18 @@
277 277  
278 278  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
279 279  
280 -​ [[image:1670406036256-101.png||height="676" width="713"]]
284 +​ [[image:image-20221021111125-14.png]]
281 281  
282 -
283 283  [[image:image-20221021111131-15.png]]
284 284  
285 285  ​
286 286  
287 -=== 2.2.7 Change Update Interval ===
290 +=== 2.2.8 Change Update Interval ===
288 288  
289 289  
290 290  User can use below command to change the (% style="color:blue" %)**uplink interval**.
291 291  
292 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
295 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
293 293  
294 294  (% style="color:red" %)**NOTE:**
295 295  
... ... @@ -299,52 +299,70 @@
299 299  == 2.3  Uplink Payload ==
300 300  
301 301  
302 -The uplink payload includes 23 bytes in total by default.
305 +The uplink payload includes 26 bytes in total by default.
303 303  
304 304  Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
305 305  
309 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
306 306  
307 307  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
308 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:90px" %)**2**|(% style="width:100px" %)**2**
309 -|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) Distance 1 |(% style="width:93px" %) Distance  2
312 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
313 +|=(% style="width: 93px;" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
310 310  
311 311  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
312 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
316 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
313 313  **1-32 group**
314 314  )))
315 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
319 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
316 316  
317 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
321 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
318 318  
319 -[[image:1670406261143-723.png]]
320 320  
324 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
325 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
326 +|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
321 321  
322 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
328 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
329 +|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
330 +|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
323 323  
324 -**0x (% style="color:red" %)__f867787050471071__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0cc3__(% style="color:#00b0f0" %) 0__9__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00ef__(% style="color:#660066" %) (% style="color:#663300" %)__013d__ (% style="color:#d60093" %)__6390453d__(%%)**
332 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
333 +|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
334 +**1-32 group**
335 +)))
336 +|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
325 325  
338 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
339 +
340 +[[image:image-20221117145932-2.png]]
341 +
342 +
343 +The payload is ASCII string, representative same HEX:
344 +
345 +**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
346 +
326 326  **where:**
327 327  
328 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
349 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
329 329  
330 330  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
331 331  
332 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
353 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
333 333  
334 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
355 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
335 335  
336 336  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
337 337  
338 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
359 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
339 339  
340 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
361 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
341 341  
342 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
363 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
343 343  
344 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
365 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
345 345  
367 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
346 346  
347 -
348 348  == 2.4  Payload Explanation and Sensor Interface ==
349 349  
350 350  === 2.4.1  Device ID ===
... ... @@ -366,13 +366,13 @@
366 366  
367 367  Specify the software version: 0x64=100, which means firmware version 1.00.
368 368  
369 -For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
390 +For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
370 370  
371 371  
372 372  === 2.4.3  Battery Info ===
373 373  
374 374  
375 -Check the battery voltage for NMDS200.
396 +Check the battery voltage for NDS03A.
376 376  
377 377  Ex1: 0x0B45 = 2885mV
378 378  
... ... @@ -397,31 +397,34 @@
397 397  **99**    Not known or not detectable
398 398  
399 399  
400 -=== 2.4.5  Distance ===
421 +=== 2.4.5  Disalarm: (default: 0) ===
401 401  
402 402  
403 -[[image:1670407401682-959.png]]
424 +(% style="color:blue" %)**If Disalarm = 1**(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
404 404  
405 -**(% style="color:blue" %)Object1 Distance:**
426 +(% style="color:blue" %)**If Disalarm = 0**(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.
406 406  
407 -Distance between sensor probe to the first object. (unit: cm)
428 + (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
408 408  
409 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
410 410  
411 -**(% style="color:blue" %)0205(H) = 517 (D) = 517 cm.**
431 +=== 2.4.6  Keep Status & Keep Time ===
412 412  
413 413  
414 -**(% style="color:blue" %)Object2 Distance:**
434 +Shows the configure value of Alarm Base on Timeout Feature
415 415  
416 -Distance between sensor probe to the second object. (unit: cm)
417 417  
437 +=== 2.4.7  Timestamp ===
418 418  
419 -=== 2.4.6  Timestamp ===
420 420  
421 -
422 422  Timestamp : 0x6315537b =1662342011
423 423  
424 424  
443 +=== 2.4.8  Switch Dual Channel Mode ===
444 +
445 +
446 +NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
447 +
448 +
425 425  == 2.5  Downlink Payload ==
426 426  
427 427  
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
1670407401682-959.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.7 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0