Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual

Last modified by Mengting Qiu on 2024/04/02 17:03

From version < 81.4 >

edited by Xiaoling
on 2022/12/07 18:13

To version < 74.1 >

edited by Xiaoling
on 2022/12/07 17:12

Change comment: Uploaded new attachment "1670404362039-351.png", version {1}

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 7 removed)

Details

Page properties

Content

@@ -14,22 +14,39 @@
  (((
--The Dragino NMDS200 is a(% style="color:blue" %)** NB-IoT Microwave Radar distance sensor**(%%). It uses (% style="color:blue" %)**24Ghz Microwave**(%%) to detect the distance between sensor and different objects. Compare vs ultrasonic or Lidar measurement method, Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or thick dust on top of the sensor.
++The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
++)))
++(((
++The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
++)))
--The NMDS200 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
++(((
++NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
++)))
--NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
++(((
++NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
++)))
--NMDS200 (% style="color:blue" %)**supports Alarm Feature**(%%), user can set the NMDS200 to uplink data in a short interval when the distance is out of configured range.
++(((
++NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
++)))
++(((
  NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**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.
++)))
--NMDS200  (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
++(((
++NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
++)))
--NMDS200 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**,(%%) It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
++(((
++NDS03A is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
++)))
--To use NMDS200, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NMDS200 supports. If local operator support it, user needs to get a** (% style="color:blue" %)NB-IoT SIM card(%%)** from the operator and install into NMDS200 to get NB-IoT network connection.
++(((
++To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
  )))
@@ -38,9 +38,10 @@
  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
--* Short uplink interval for Distance Alarm
++* Open/Close detect
++* Open/Close statistics
  * Monitor Battery Level
--* Microwave Radar for distance detection
++* connect two door sensors
  * Datalog feature
  * Uplink periodically
  * Downlink to change configure
@@ -51,42 +51,33 @@
  * Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long-term use
--== 1.3  Radar probe specification ==
++== 1.3  Storage & Operation ==
--* Measuring Method: FMCW
--* Frequency: 24.000  24.500 GHz
--* Measurement output power: 6dBm
--* Measure range: 0.5  20m
--* Accuracy: ±0.1m
--* Resolution: 0.01m
--* Horizontal Angel: 78°
--* Vertical Angel: 23°
++Temperature -40°C to +85°C
--== 1.4  Storage Temperature ==
++== 1.4  Mechanical ==
-- -40°C to +85°C
++[[image:image-20221117114937-4.png]]
++[[image:image-20221117114949-5.png]]
++[[image:image-20221117115010-6.png]]
++
++
++
  == 1.5  Applications ==
++[[image:image-20221117114842-3.png]]
--* 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
++
  == 1.6  Specification ==
@@ -93,7 +93,7 @@
  (% style="color:blue" %)**Common DC Characteristics:**
  * Supply Voltage: 2.1v ~~ 3.6v
--* Operating Temperature: 0 ~~ 70°C
++* Operating Temperature: -40 ~~ 85°C
  (% style="color:blue" %)**NB-IoT Spec:**
@@ -104,49 +104,86 @@
  * B20 @H-FDD: 800MHz
  * B28 @H-FDD: 700MHz
--== 1.7  Installation ==
++== 1.7  Pin Definitions and Switch ==
--Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
++[[image:image-20221021110429-4.png]]
--[[image:image-20221207170748-1.png]]   [[image:image-20221207170748-2.png||height="366" width="672"]]
++=== 1.7.1  Pin Definition ===
--== 1.8  Pin Definitions and Switch ==
++The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
--[[image:1670404362039-351.png]]
++=== 1.7.2  Jumper JP2(Power ON/OFF) ===
--= 2.  Use NMDS200 to communicate with IoT Server =
++Power on Device when putting this jumper.
++
++=== 1.7.3  BOOT MODE / SW1 ===
++
++
++1)  ISP:   upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
++
++2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
++
++
++=== 1.7.4  Reset Button ===
++
++
++Press to reboot the device.
++
++
++=== 1.7.5  LED ===
++
++
++The LED will blink when :
++
++1.  Boot the device in flash mode
++
++2.  Send an uplink packet
++
++
++== 1.8  Magnet Distance ==
++
++
++(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
++
++(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
++
++
++= 2.  Use NDS03A to communicate with IoT Server =
++
  == 2.1  How it works ==
--The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
++In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
--The diagram below shows the working flow in the default firmware of NMDS200:
++The diagram below shows the working flow in the default firmware of NDS03A:
  [[image:image-20221021110615-5.png]]
--== 2.2  Configure NMDS200 ==
++== 2.2  Configure NDS03A ==
++=== 2.2.1  Test Requirement ===
--To use NMDS200 in your city, make sure to meet below requirements:
++To use NDS03A in your city, make sure to meet below requirements:
++
  * Your local operator has already distributed an NB-IoT Network.
--* The local NB-IoT network used the band that NMDS200 supports.
++* The local NB-IoT network used the band that NDS03A supports.
  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
--Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NMDS200 will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
++Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A will use** (% style="color:red" %)CoAP(120.24.4.116:5683)(%%)** or raw (% style="color:red" %)**UDP(120.24.4.116:5601) **(%%)or (% style="color:red" %)**MQTT(120.24.4.116:1883) **(%%)or (% style="color:red" %)**TCP(120.24.4.116:5600)protocol**(%%) to send data to the test server.
--[[image:image-20221207173300-4.png]]
++[[image:image-20221117142300-1.png]]
--=== 2.2.1  Insert NB-IoT SIM card ===
++=== 2.2.2  Insert NB-IoT SIM card ===
  Insert the NB-IoT Card get from your provider.
@@ -156,10 +156,10 @@
  [[image:image-20221021110745-6.png]]
--=== 2.2.2  Connect USB – TTL to NMDS200 and configure it ===
++=== 2.2.3  Connect USB – TTL to NDS03A and configure it ===
--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.
++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.
  (% style="color:blue" %)**Connection:**
@@ -182,11 +182,11 @@
  * Flow Control: (% style="color:red" %)**None**
--Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
++Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
  [[image:image-20221021110817-7.png]]
--NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
++NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
  (% 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 @@
--=== 2.2.3  Use CoAP protocol to uplink data ===
++=== 2.2.4  Use CoAP protocol to uplink data ===
  (% 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 @@
  [[image:image-20221021110948-8.png]]
--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.
++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.
--[[image:1670405841875-916.png]]
++[[image:image-20221118103547-9.png||height="605" width="837"]]
--=== 2.2.4  Use UDP protocol to uplink data(Default protocol) ===
++=== 2.2.5  Use UDP protocol to uplink data(Default protocol) ===
  (% style="color:blue" %)**AT Commands:**
@@ -235,7 +235,7 @@
--=== 2.2.5  Use MQTT protocol to uplink data ===
++=== 2.2.6  Use MQTT protocol to uplink data ===
  (% style="color:blue" %)**AT Commands:**
@@ -257,7 +257,7 @@
   [[image:image-20221118103445-7.png]]
--[[image:1670405928926-116.png]]
++[[image:image-20221118103453-8.png||height="608" width="841"]]
@@ -264,7 +264,7 @@
  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.
--=== 2.2.6  Use TCP protocol to uplink data ===
++=== 2.2.7  Use TCP protocol to uplink data ===
  (% style="color:blue" %)**AT Commands:**
@@ -273,19 +273,18 @@
  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   **   (%%) ~/~/  Set TCP server address and port
-- [[image:1670406036256-101.png||height="676" width="713"]]
++ [[image:image-20221021111125-14.png]]
--
  [[image:image-20221021111131-15.png]]
--=== 2.2.7  Change Update Interval ===
++=== 2.2.8  Change Update Interval ===
  User can use below command to change the (% style="color:blue" %)**uplink interval**.
--* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
++* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
  (% style="color:red" %)**NOTE:**
@@ -295,51 +295,71 @@
  == 2.3  Uplink Payload ==
--The uplink payload includes 23 bytes in total by default.
++The uplink payload includes 26 bytes in total by default.
  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.
++(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
--|=(% 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**
--|=(% 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
++|=(% 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**
++|=(% 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)
  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
--|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
++|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
  **1-32 group**
  )))
--|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
++|(% 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" %)...
--If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
++(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
--[[image:1670406261143-723.png]]
++(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
++|=(% 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**
++|=(% 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)
--The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00  00ef  013d  6390453d
++(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
++|(% 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**
++|(% 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)
--**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__(%%)**
++(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
++|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
++**1-32 group**
++)))
++|(% 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" %)......
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
++
++[[image:image-20221117145932-2.png]]
++
++
++The payload is ASCII string, representative same HEX:
++
++**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__(%%)**
++
  **where:**
--* (% style="color:#037691" %)**Device ID:**(%%) 0x  f867787050471071 =  f867787050471071
++* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
  * (% style="color:#037691" %)**Version:**(%%)    0x0064=100=1.0.0
--* (% style="color:#037691" %)**BAT :**(%%)    0x0cc3 = 3267 mV = 3.267V
++* (% style="color:#037691" %)**BAT :**(%%)    0x0ccf = 3279 mV = 3.279V
--* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
++* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
  * (% style="color:#037691" %)**Mod:**(%%)   0x01 = 1
--* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
++* (% style="color:#037691" %)**Door Status:**(%%)   0x00=0
--* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
++* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
--* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
++* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
--* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
++* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
++* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
++
  == 2.4  Payload Explanation and Sensor Interface ==
  === 2.4.1  Device ID ===
@@ -361,13 +361,13 @@
  Specify the software version: 0x64=100, which means firmware version 1.00.
--For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
++For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
  === 2.4.3  Battery Info ===
--Check the battery voltage for NMDS200.
++Check the battery voltage for NDS03A.
  Ex1: 0x0B45 = 2885mV
@@ -392,35 +392,38 @@
  **99**      Not known or not detectable
--=== 2.4.5  Distance ===
++=== 2.4.5  Disalarm: (default: 0) ===
--[[image:1670407401682-959.png]]
++(% 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.
--(% style="color:blue" %)**Object1 Distance:**
++(% 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.
--Distance between sensor probe to the first object.  (unit: cm)
++ (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
--For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is
--(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.**
++=== 2.4.6  Keep Status & Keep Time ===
--(% style="color:blue" %)**Object2 Distance:**
++Shows the configure value of Alarm Base on Timeout Feature
--Distance between sensor probe to the second object.  (unit: cm)
++=== 2.4.7  Timestamp ===
--=== 2.4.6  Timestamp ===
--
  Timestamp : 0x6315537b =1662342011
++=== 2.4.8  Switch Dual Channel Mode ===
++
++
++NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
++
++
  == 2.5  Downlink Payload ==
--By default, NMDS200 prints the downlink payload to console port.
++By default, NDS03A prints the downlink payload to console port.
  [[image:image-20221021111414-18.png]]
@@ -437,7 +437,7 @@
  * (% style="color:#037691" %)**Reset**
--If payload = 0x04FF, it will reset the NMDS200
++If payload = 0x04FF, it will reset the NDS03A
  * (% style="color:#037691" %)**INTMOD**
@@ -447,7 +447,7 @@
  == 2.6  LED Indicator ==
--The NMDS200 has an internal LED which is to show the status of different states.
++The NDS03A has an internal LED which is to show the status of different states.
  * When the device starts normally, the LED will light up for 1 second.
  * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
@@ -454,24 +454,44 @@
  * For each uplink probe, LED will be on for 500ms.
++== 2.7  Alarm Base on Timeout ==
--== 2.7  Distance alarm function ==
++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:
--(% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
--**Example 1:**
++(% style="color:blue" %)**1. Keep Status: Status to be monitor**
--AT+ ALARM1 =60,200           ~/~/ Alarm when moisture lower than 60.
++Keep Status = 1: Monitor Close to Open event
--AT+ ALARM2 =min,max
++Keep Status = 0: Monitor Open to Close event
--**Example 2:**
++(% style="color:blue" %)**2. Keep Time: Timeout to send an Alarm**
--AT+ ALARM2 =200,1500      ~/~/ Alarm when temperature lower than 1500
++Range 0 ~~ 65535(0xFFFF) seconds.
++If keep time = 0, Disable Alarm Base on Timeout feature.
++If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
++
++
++(% style="color:blue" %)**AT Command to configure:**
++
++(% style="color:blue" %)**PB14 PIN:**
++
++(% 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.
++
++(% style="color:#037691" %)**AT+TTRIG=0,0 **  (%%)    **~-~->** Default Value, disable timeout Alarm.
++
++
++(% style="color:blue" %)**PB15 PIN:**
++
++(% style="color:#037691" %)**AT+TTRIG2=1,30**
++
++(% style="color:#037691" %)**AT+TTRIG2=0,0 **
++
++
  == 2.8  Set debug mode ==
@@ -758,6 +758,7 @@
  * NDS03A Open/Close Door Sensor x 1
++
  = 9.  Support =

1670405841875-916.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-76.1 KB

Content

1670405928926-116.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-76.7 KB

Content

1670406036256-101.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-181.0 KB

Content

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

image-20221207173200-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-76.7 KB

Content

image-20221207173300-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-77.0 KB

Content

Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual

Summary

Details

Applications

Navigation