Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 82.2 >
edited by Xiaoling
on 2022/12/07 18:18
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
... ... @@ -51,6 +51,8 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 +
55 +
54 54  == 1.3 Radar probe specification ==
55 55  
56 56  
... ... @@ -64,6 +64,8 @@
64 64  * Vertical Angel: 23°
65 65  
66 66  
69 +
70 +
67 67  == 1.4  Storage Temperature ==
68 68  
69 69  
... ... @@ -87,6 +87,8 @@
87 87  * Sewer
88 88  * Bottom water level monitoring
89 89  
94 +
95 +
90 90  == 1.6  Specification ==
91 91  
92 92  
... ... @@ -104,6 +104,8 @@
104 104  * B20 @H-FDD: 800MHz
105 105  * B28 @H-FDD: 700MHz
106 106  
113 +
114 +
107 107  == 1.7  Installation ==
108 108  
109 109  
... ... @@ -156,10 +156,10 @@
156 156  [[image:image-20221021110745-6.png]] ​
157 157  
158 158  
159 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
167 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
160 160  
161 161  
162 -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.
163 163  
164 164  (% style="color:blue" %)**Connection:**
165 165  
... ... @@ -182,11 +182,11 @@
182 182  
183 183  * Flow Control: (% style="color:red" %)**None**
184 184  
185 -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**(%%).
186 186  
187 187  ​[[image:image-20221021110817-7.png]]
188 188  
189 -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.
190 190  
191 191  
192 192  (% 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]]
... ... @@ -193,7 +193,7 @@
193 193  
194 194  
195 195  
196 -=== 2.2.3 Use CoAP protocol to uplink data ===
204 +=== 2.2.4 Use CoAP protocol to uplink data ===
197 197  
198 198  
199 199  (% 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/]]
... ... @@ -212,12 +212,12 @@
212 212  [[image:image-20221021110948-8.png]]
213 213  
214 214  
215 -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.
216 216  
217 -[[image:1670405841875-916.png]] ​
225 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
218 218  
219 219  
220 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
228 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
221 221  
222 222  
223 223  (% style="color:blue" %)**AT Commands:**
... ... @@ -235,7 +235,7 @@
235 235  
236 236  ​
237 237  
238 -=== 2.2.5 Use MQTT protocol to uplink data ===
246 +=== 2.2.6 Use MQTT protocol to uplink data ===
239 239  
240 240  
241 241  (% style="color:blue" %)**AT Commands:**
... ... @@ -257,7 +257,7 @@
257 257  ​ [[image:image-20221118103445-7.png]]
258 258  
259 259  
260 -[[image:1670405928926-116.png]]
268 +[[image:image-20221118103453-8.png||height="608" width="841"]]
261 261  
262 262  ​
263 263  
... ... @@ -264,7 +264,7 @@
264 264  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.
265 265  
266 266  
267 -=== 2.2.6 Use TCP protocol to uplink data ===
275 +=== 2.2.7 Use TCP protocol to uplink data ===
268 268  
269 269  
270 270  (% style="color:blue" %)**AT Commands:**
... ... @@ -273,19 +273,18 @@
273 273  
274 274  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
275 275  
276 -​ [[image:1670406036256-101.png||height="676" width="713"]]
284 +​ [[image:image-20221021111125-14.png]]
277 277  
278 -
279 279  [[image:image-20221021111131-15.png]]
280 280  
281 281  ​
282 282  
283 -=== 2.2.7 Change Update Interval ===
290 +=== 2.2.8 Change Update Interval ===
284 284  
285 285  
286 286  User can use below command to change the (% style="color:blue" %)**uplink interval**.
287 287  
288 -* (% 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)
289 289  
290 290  (% style="color:red" %)**NOTE:**
291 291  
... ... @@ -295,50 +295,69 @@
295 295  == 2.3  Uplink Payload ==
296 296  
297 297  
298 -The uplink payload includes 23 bytes in total by default.
305 +The uplink payload includes 26 bytes in total by default.
299 299  
300 300  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.
301 301  
309 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
302 302  
303 303  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
304 -|=(% 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**
305 -|=(% 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)
306 306  
307 307  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
308 -|(% 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" %)(((
309 309  **1-32 group**
310 310  )))
311 -|(% 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" %)...
312 312  
313 -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:**
314 314  
315 -[[image:1670406261143-723.png]]
316 316  
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)
317 317  
318 -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)
319 319  
320 -**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" %)......
321 321  
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 +
322 322  **where:**
323 323  
324 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
349 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
325 325  
326 326  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
327 327  
328 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
353 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
329 329  
330 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
355 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
331 331  
332 332  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
333 333  
334 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
359 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
335 335  
336 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
361 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
337 337  
338 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
363 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
339 339  
340 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
365 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
341 341  
367 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
342 342  
343 343  == 2.4  Payload Explanation and Sensor Interface ==
344 344  
... ... @@ -361,13 +361,13 @@
361 361  
362 362  Specify the software version: 0x64=100, which means firmware version 1.00.
363 363  
364 -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.
365 365  
366 366  
367 367  === 2.4.3  Battery Info ===
368 368  
369 369  
370 -Check the battery voltage for NMDS200.
396 +Check the battery voltage for NDS03A.
371 371  
372 372  Ex1: 0x0B45 = 2885mV
373 373  
... ... @@ -392,35 +392,38 @@
392 392  **99**    Not known or not detectable
393 393  
394 394  
395 -=== 2.4.5  Distance ===
421 +=== 2.4.5  Disalarm: (default: 0) ===
396 396  
397 397  
398 -[[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.
399 399  
400 -(% 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.
401 401  
402 -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.
403 403  
404 -For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
405 405  
406 -(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
431 +=== 2.4.6  Keep Status & Keep Time ===
407 407  
408 408  
409 -(% style="color:blue" %)**Object2 Distance:**
434 +Shows the configure value of Alarm Base on Timeout Feature
410 410  
411 -Distance between sensor probe to the second object. (unit: cm)
412 412  
437 +=== 2.4.7  Timestamp ===
413 413  
414 -=== 2.4.6  Timestamp ===
415 415  
416 -
417 417  Timestamp : 0x6315537b =1662342011
418 418  
419 419  
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 +
420 420  == 2.5  Downlink Payload ==
421 421  
422 422  
423 -By default, NMDS200 prints the downlink payload to console port.
452 +By default, NDS03A prints the downlink payload to console port.
424 424  
425 425  [[image:image-20221021111414-18.png]] ​
426 426  
... ... @@ -437,7 +437,7 @@
437 437  
438 438  * (% style="color:#037691" %)**Reset**
439 439  
440 -If payload = 0x04FF, it will reset the NMDS200
469 +If payload = 0x04FF, it will reset the NDS03A
441 441  
442 442  * (% style="color:#037691" %)**INTMOD**
443 443  
... ... @@ -447,34 +447,112 @@
447 447  == 2.6  ​LED Indicator ==
448 448  
449 449  
450 -The NMDS200 has an internal LED which is to show the status of different states.
479 +The NDS03A has an internal LED which is to show the status of different states.
451 451  
452 452  * When the device starts normally, the LED will light up for 1 second.
453 453  * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
454 454  * For each uplink probe, LED will be on for 500ms.
455 455  
485 +== 2.7  Alarm Base on Timeout ==
456 456  
457 457  
458 -== 2.7  Distance alarm function ==
488 +NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
459 459  
460 460  
461 -(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
491 +(% style="color:blue" %)**1. Keep Status: Status to be monitor**
462 462  
463 -**Example 1:**
493 +Keep Status = 1: Monitor Close to Open event
464 464  
465 -AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
495 +Keep Status = 0: Monitor Open to Close event
466 466  
467 -AT+ ALARM2 =min,max
468 468  
498 +(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
469 469  
470 -**Example 2:**
500 +Range 0 ~~ 65535(0xFFFF) seconds.
471 471  
472 -AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
502 +If keep time = 0, Disable Alarm Base on Timeout feature.
473 473  
504 +If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
474 474  
475 -== 2.8  Set the number of data to be uploaded and the recording time ==
476 476  
507 +(% style="color:blue" %)**AT Command to configure:**
477 477  
509 +(% style="color:blue" %)**PB14 PIN:**
510 +
511 +(% style="color:#037691" %)**AT+TTRIG=1,30** (%%) **~-~->**  When the **Keep Status** change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
512 +
513 +(% style="color:#037691" %)**AT+TTRIG=0,0 ** (%%) **~-~->** Default Value, disable timeout Alarm.
514 +
515 +
516 +(% style="color:blue" %)**PB15 PIN:**
517 +
518 +(% style="color:#037691" %)**AT+TTRIG2=1,30**
519 +
520 +(% style="color:#037691" %)**AT+TTRIG2=0,0 **
521 +
522 +
523 +== 2.8  Set debug mode ==
524 +
525 +
526 +Feature: Enable or Disable debug mode
527 +
528 +(% style="color:blue" %)**AT Command: AT+DEBUG**
529 +
530 +[[image:image-20221021111629-21.png]]
531 +
532 +
533 +
534 +== 2.9  Clear Flash Record ==
535 +
536 +
537 +Feature: Clear flash storage for data log feature.
538 +
539 +(% style="color:blue" %)**AT Command: AT+CLRDTA**
540 +
541 +[[image:image-20221021111527-19.png]]
542 +
543 +
544 +== 2.10  Count Mod ==
545 +
546 +
547 +(% style="color:blue" %)**AT Command: AT+COUNTMOD**
548 +
549 +[[image:image-20221118092935-1.png]]
550 +
551 +
552 +== 2.11  Interrupt Pin Channel Mod ==
553 +
554 +
555 +(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
556 +
557 +[[image:image-20221118093144-2.png]]
558 +
559 +
560 +== 2.12 TTRIG1/2 timeout status alarm ==
561 +
562 +
563 +It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
564 +
565 +(% style="color:blue" %)**AT Command: AT+TTRALARM**
566 +
567 +[[image:image-20221118093512-3.png]]
568 +
569 +
570 +== 2.13  Select counting mode ==
571 +
572 +
573 +(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
574 +
575 +When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
576 +
577 +When (% style="color:red" %)**b=0**(%%), it is the last door open duration, and when (% style="color:red" %)**b=1**(%%),the last door close duration.
578 +
579 +[[image:image-20221118093658-4.png]]
580 +
581 +
582 +== 2.14  Set the number of data to be uploaded and the recording time ==
583 +
584 +
478 478  (% style="color:blue" %)**AT Command:**
479 479  
480 480  (% 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)
... ... @@ -482,7 +482,7 @@
482 482  (% style="color:#037691" %)**AT+NOUD=8**(%%)** ** ~/~/  The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
483 483  
484 484  
485 -== 2.9  Read or Clear cached data ==
592 +== 2.15  Read or Clear cached data ==
486 486  
487 487  
488 488  (% style="color:blue" %)**AT Command:**
... ... @@ -491,10 +491,10 @@
491 491  
492 492  (% style="color:#037691" %)**AT+CDP=0**  (%%) ~/~/ Clear cached data ​
493 493  
494 -[[image:1670408172929-569.png]]
601 +[[image:image-20221118094227-5.png]]
495 495  
496 496  
497 -== 2.10  ​Firmware Change Log ==
604 +== 2.16  ​Firmware Change Log ==
498 498  
499 499  
500 500  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
... ... @@ -502,12 +502,12 @@
502 502  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
503 503  
504 504  
505 -== 2.11  ​Battery Analysis ==
612 +== 2.17  ​Battery Analysis ==
506 506  
507 -=== 2.11.1  ​Battery Type ===
614 +=== 2.17.1  ​Battery Type ===
508 508  
509 509  
510 -The NMDS200 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-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.
617 +The NDS03A battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-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.
511 511  
512 512  The battery is designed to last for several years depends on the actual use environment and update interval. 
513 513  
... ... @@ -522,7 +522,7 @@
522 522  [[image:image-20221021111911-26.png]] ​
523 523  
524 524  
525 -=== 2.11.2  Power consumption Analyze ===
632 +=== 2.17.2  Power consumption Analyze ===
526 526  
527 527  
528 528  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.
... ... @@ -544,16 +544,16 @@
544 544  [[image:1666596205057-567.png]] ​
545 545  
546 546  
547 -=== 2.11.3  ​Battery Note ===
654 +=== 2.17.3  ​Battery Note ===
548 548  
549 549  
550 550  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.
551 551  
552 552  
553 -=== 2.11.4  Replace the battery ===
660 +=== 2.17.4  Replace the battery ===
554 554  
555 555  
556 -The default battery pack of NMDS200 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).
663 +The default battery pack of NDS03A 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).
557 557  
558 558  
559 559  = 3. ​ Access NB-IoT Module =
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
1670408172929-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -211.8 KB
Content

Applications

Navigation

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