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 < 80.2 >

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

To version < 58.1 >

edited by Xiaoling
on 2022/11/17 11:50

Change comment: Uploaded new attachment "image-20221117115010-6.png", version {1}

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 22 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
++NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual

Content

@@ -1,7 +1,12 @@
  (% style="text-align:center" %)
--[[image:LMDS200_10.jpg]]
++[[image:image-20221117105556-1.png]]
++
++
++
++
++
  **Table of Contents：**
@@ -10,37 +10,54 @@
  = 1.  Introduction =
--== 1.1  What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
++== 1.1  What is NDS03A NB-IoT Open/Close Door Sensor ==
++
  (((
--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.
++(((
++NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)**standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
++)))
--NMDS200  (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
++(((
++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)
++)))
--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)
--
--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.
  )))
++
++
  == 1.2  Features ==
  * 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
++* Uplink on periodically and open/close event
  * Datalog feature
  * Uplink periodically
  * Downlink to change configure
@@ -51,108 +51,132 @@
  * Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long-term use
++== 1.3  Specification ==
--== 1.3  Radar probe specification ==
++(% style="color:blue" %)**Common DC Characteristics:**
--* 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°
++* Supply Voltage: 2.1v ~~ 3.6v
++* Operating Temperature: -40 ~~ 85°C
++(% style="color:blue" %)**NB-IoT Spec:**
++* - B1 @H-FDD: 2100MHz
++* - B3 @H-FDD: 1800MHz
++* - B8 @H-FDD: 900MHz
++* - B5 @H-FDD: 850MHz
++* - B20 @H-FDD: 800MHz
++* - B28 @H-FDD: 700MHz
--== 1.4  Storage Temperature ==
++== 1.4  Installation ==
-- -40°C to +85°C
++Connect CPN01 to an Open Close sensor like below. So it can detect the Open/Close event.
++[[image:image-20221021110329-1.png]]
++[[image:image-20221022234602-2.png||height="288" width="922"]]
++
  == 1.5  Applications ==
++* Open/Close Detection
++* Pulse meter application
++* Dry Contact Detection
--* 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  Mechanical ==
--== 1.6  Specification ==
++[[image:image-20221021110415-3.png]]
--(% style="color:blue" %)**Common DC Characteristics:**
--* Supply Voltage: 2.1v ~~ 3.6v
--* Operating Temperature: 0 ~~ 70°C
++== 1.7  Pin Definitions and Switch ==
--(% style="color:blue" %)**NB-IoT Spec:**
--* B1 @H-FDD: 2100MHz
--* B3 @H-FDD: 1800MHz
--* B8 @H-FDD: 900MHz
--* B5 @H-FDD: 850MHz
--* B20 @H-FDD: 800MHz
--* B28 @H-FDD: 700MHz
++[[image:image-20221021110429-4.png]]
--== 1.7  Installation ==
++=== 1.7.1  Pin Definition ===
--Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
++CPN01 is pre-configured to connect to two external wires. The other pins are not used. If user wants to know more about other pins, please refer to the **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.
--[[image:image-20221207170748-1.png]]   [[image:image-20221207170748-2.png||height="366" width="672"]]
++=== 1.7.2  Jumper JP2(Power ON/OFF) ===
--== 1.8  Pin Definitions and Switch ==
++Power on Device when putting this jumper.
--[[image:1670404362039-351.png]]
++=== 1.7.3  BOOT MODE / SW1 ===
--= 2.  Use NMDS200 to communicate with IoT Server =
++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
++
++
++
++= 2.  Use CPN01 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.
++The CPN01 is equipped with an NB-IoT module, the pre-loaded firmware in CPN01 will get (% style="color:blue" %)**Open/Close Event or Count**(%%) from sensor and send the value to the NB-IoT network. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.
--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 CPN01:
  [[image:image-20221021110615-5.png]]
--== 2.2  Configure NMDS200 ==
++== 2.2  Configure CPN01 ==
--To use NMDS200 in your city, make sure to meet below requirements:
++=== 2.2.1  Test Requirement ===
++
++
++To use CPN01 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 CPN01 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 CPN01 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-20221023000439-3.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.
  User needs to take out the NB-IoT module and insert the SIM card like below:
@@ -160,11 +160,12 @@
  [[image:image-20221021110745-6.png]]
--=== 2.2.2  Connect USB – TTL to NMDS200 and configure it ===
++=== 2.2.3  Connect USB – TTL to CPN01 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 CPN01 via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.
++
  (% style="color:blue" %)**Connection:**
  (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
@@ -186,11 +186,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 CPN01 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.
++CPN01 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]]
@@ -197,13 +197,13 @@
--=== 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/]]
--(% style="color:blue" %)**Use below commands in NDS03A:**
++(% style="color:blue" %)**Use below commands in CPN01:**
  * (% style="color:#037691" %)**AT+PRO=1**                (%%)                                ~/~/ Set to use CoAP protocol to uplink
@@ -216,14 +216,15 @@
  [[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 CPN01**(%%) (via AT+ATZ ), CPN01 will start to uplink sensor values to the CoAP server.
--[[image:1670405841875-916.png]]
++[[image:image-20221021110956-9.png]]
--=== 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:**
  * (% style="color:#037691" %)**AT+PRO=2   **  (%%) ~/~/  Set to use UDP protocol to uplink
@@ -239,9 +239,10 @@
--=== 2.2.5  Use MQTT protocol to uplink data ===
++=== 2.2.6  Use MQTT protocol to uplink data ===
++
  (% style="color:blue" %)**AT Commands:**
  * (% style="color:#037691" %)**AT+PRO=3   **                (%%)                              ~/~/  Set to use MQTT protocol to uplink
@@ -258,10 +258,10 @@
  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          **   (%%)       ~/~/  Set the subscription topic of MQTT
-- [[image:image-20221118103445-7.png]]
++ [[image:image-20221021111058-12.png]]
--[[image:1670405928926-116.png]]
++[[image:image-20221021111201-16.png||height="472" width="653"]]
@@ -268,9 +268,10 @@
  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:**
  * (% style="color:#037691" %)**AT+PRO=4   **                          (%%)                  ~/~/  Set to use TCP protocol to uplink
@@ -277,76 +277,82 @@
  * (% 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=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hours)
  (% style="color:red" %)**NOTE:**
--1.  By default, the device will send an uplink message every 4 hour.
++1.  By default, the device will send an uplink message every 1 hour.
++
  == 2.3  Uplink Payload ==
--The uplink payload includes 23 bytes in total by default.
++The uplink payload includes 123 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.
++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.
--(% 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
++(% border="1.5" style="background-color:#ffffcc; color:green; width:510px" %)
++|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:40px" %)**1**|(% style="width:60px" %)**3**
++|=(% style="width: 96px;" %)**Value**|(% style="width:84px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:44px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:121px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:52px" %)MOD|(% style="width:84px" %)[[ Calculate Flag>>||anchor="H2.4.5A0CalculateFlag"]]|(% style="width:116px" %)[[Contact Status>>||anchor="H2.4.7A0ContactStatus"]]|(% style="width:57px" %)[[Alarm>>||anchor="H2.4.6A0Alarm"]]|(% style="width:91px" %)[[Total pulse>>||anchor="H2.4.8A0Totalpulse"]]
--(% 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" %)(((
--**1-32 group**
--)))
--|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
++(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
++|(% style="width:100px" %)**3**|(% style="width:50px" %)**4**|(% style="width:70px" %)**1**|(% style="width:50px" %)**3**|(% style="width:100px" %)**3**|(% style="width:80px" %)4|(% style="width:50px" %)**8 group**
++|(% style="width:176px" %)[[The last open duration>>||anchor="H2.4.9A0Thelastopenduration"]]|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.10A0Timestamp"]]|(% style="width:115px" %)Contact Status|(% style="width:92px" %)Total pulse|(% style="width:169px" %)The last open duration|(% style="width:97px" %)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.
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.
--[[image:1670406261143-723.png]]
++[[image:image-20221021111201-16.png||height="572" width="792"]]
--The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00  00ef  013d  6390453d
++The payload is ASCII string, representative same HEX:
--**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__(%%)**
++**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0c78__(% style="color:#00b0f0" %) __17__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__ (% style="color:#660066" %)__00__ (% style="color:#aaaa40" %)__000009__(% style="color:#663300" %) __000002__ (% style="color:#d60093" %)__6315537b__ (% style="color:#660066" %)__01 00000b 02 0000026 63510fed__ (%%)__0100000e0200000263510f39__ __010000000000000063510e85__ __010000000000000063510d2e__ __010000000000000063510c7a__ __010000000000000063510bc6__ __010000000000000063510954__ __010000000000000063510882 __**
  **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" %)**Version:**(%%) 0x0064=100=1.0.0
--* (% style="color:#037691" %)**BAT :**(%%)    0x0cc3 = 3267 mV = 3.267V
++* (% style="color:#037691" %)**BAT :**(%%) 0x0c78 = 3192 mV = 3.192V
--* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
++* (% style="color:#037691" %)**Singal: **(%%)0x17 = 23
--* (% style="color:#037691" %)**Mod:**(%%)   0x01 = 1
++* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1
--* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
++* (% style="color:#037691" %)**Calculate Flag:**(%%) 0x00=0
--* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
++* (% style="color:#037691" %)**Contact Status:**(%%) 0x00=0
--* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
++* (% style="color:#037691" %)**Alarm: **(%%)0x00 =0
--* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
++* (% style="color:#037691" %)**Total pulse: **(%%)0x000009 =9
++* (% style="color:#037691" %)**The last open duration: **(%%)0x000002 =2
++* (% style="color:#037691" %)**Timestamp:**(%%) 0x6315537b =1662342011 (Unix Time)
++* (% style="color:#037691" %)**Contact Status, Total pulse,The last open duration ,Time stamp :**(%%) 01  00000b  000026  63510fed
++
++* (% style="color:#037691" %)**8 sets of recorded data: Contact Status, Total pulse, The last open duration ,Time stamp :**(%%) 0100000e00002663510f39,.......
++
  == 2.4  Payload Explanation and Sensor Interface ==
++
  === 2.4.1  Device ID ===
@@ -361,18 +361,20 @@
  The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
++
  === 2.4.2  Version Info ===
  Specify the software version: 0x64=100, which means firmware version 1.00.
--For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
++For example 0x00 64 : This device is CPN01 with firmware version 1.0.0.
++
  === 2.4.3  Battery Info ===
--Check the battery voltage for NDS03A.
++Check the battery voltage for CPN01.
  Ex1: 0x0B45 = 2885mV
@@ -379,6 +379,7 @@
  Ex2: 0x0B49 = 2889mV
++
  === 2.4.4  Signal Strength ===
@@ -397,38 +397,70 @@
  **99**      Not known or not detectable
--=== 2.4.5  Disalarm: (default: 0) ===
++=== 2.4.5  Calculate Flag ===
--(% 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" %)**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.
++The calculate flag is a user defined field, IoT server can use this filed to handle different meters with different pulse factors. For example, if there are 100 water meters, meter 1~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.
-- (% style="color:red" %)**Note:**(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
++User can set calculate flag to 1 for meter 1~~50 and 2 for meter 51 ~~ 100, So IoT Server can use this field for calculation.
++Default value: 0.
--=== 2.4.6  Keep Status & Keep Time ===
++Range (6 bits): (b)000000 ~~ (b) 111111
--Shows the configure value of Alarm Base on Timeout Feature
++=== 2.4.6  Alarm ===
--=== 2.4.7  Timestamp ===
++See [[Alarm Base on Timeout>>||anchor="H2.7A0AlarmBaseonTimeout"]]
--Timestamp : 0x6315537b =1662342011
--=== 2.4.8  Switch Dual Channel Mode ===
++=== 2.4.7  Contact Status ===
--NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
++0: Open
++1: Close
++
++
++=== 2.4.8  Total pulse ===
++
++
++Total pulse/counting based on dry [[contact trigger event>>||anchor="H2.12Setcountnumber"]]
++
++Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215
++
++
++
++=== 2.4.9  The last open duration ===
++
++
++Dry Contact last open duration.
++
++Unit: min.
++
++[[image:image-20221021111346-17.png||height="146" width="770"]]
++
++
++
++=== 2.4.10  Timestamp ===
++
++
++Timestamp : 0x6315537b =1662342011
++
++Convert Unix timestamp to time 2022-9-5 9:40:11.
++
++**~ **
++
++
  == 2.5  Downlink Payload ==
--By default, NDS03A prints the downlink payload to console port.
++By default, CPN01 prints the downlink payload to console port.
  [[image:image-20221021111414-18.png]]
@@ -445,7 +445,7 @@
  * (% style="color:#037691" %)**Reset**
--If payload = 0x04FF, it will reset the NDS03A
++If payload = 0x04FF, it will reset the NSE01
  * (% style="color:#037691" %)**INTMOD**
@@ -452,19 +452,20 @@
  Downlink Payload: 06000003, Set AT+INTMOD=3
++
  == 2.6  LED Indicator ==
--The NDS03A has an internal LED which is to show the status of different states.
++The CPN01 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.
++* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
  * For each uplink probe, LED will be on for 500ms.
  == 2.7  Alarm Base on Timeout ==
--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:
++CPN01 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" %)**1. Keep Status: Status to be monitor**
@@ -480,25 +480,17 @@
  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.
++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. CPN01 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=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 ==
@@ -520,57 +520,54 @@
  [[image:image-20221021111527-19.png]]
--== 2.10  Count Mod ==
++== 2.10  Set trigger mode ==
--(% style="color:blue" %)**AT Command: AT+COUNTMOD**
--[[image:image-20221118092935-1.png]]
++(% style="color:blue" %)**AT Command: AT+TTRMOD**
++Feature: Set the trigger interrupt mode.
--== 2.11  Interrupt Pin Channel Mod ==
++[[image:image-20221021111552-20.png]]
--(% style="color:blue" %)**AT Command: AT+TTRCHANNEL**
--[[image:image-20221118093144-2.png]]
++== 2.11  Set the calculate flag ==
--== 2.12  TTRIG1/2 timeout status alarm ==
++Feature: Set the calculate flag
++(% style="color:blue" %)**AT Command: AT+CALCFLAG**
--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.
++[[image:image-20221021111711-22.png]]
--(% style="color:blue" %)**AT Command: AT+TTRALARM**
--[[image:image-20221118093512-3.png]]
++== 2.12  Set count number ==
--== 2.13  Select counting mode ==
++Feature: Manually set the count number
--(% style="color:blue" %)**AT Command: AT+TTRMODx=a,b**
++(% style="color:blue" %)**AT Command: AT+SETCNT**
--When (% style="color:red" %)**a=0**(%%), the door is opened to count, and when (% style="color:red" %)**a=1**(%%),the closed door is counted.
++[[image:image-20221021111748-24.png]]
--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.
--[[image:image-20221118093658-4.png]]
++== 2.13  Set the number of data to be uploaded and the recording time ==
--== 2.14  Set the number of data to be uploaded and the recording time ==
--
  (% style="color:blue" %)**AT Command:**
--(% 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)
++(% 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)
--(% 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.
++(% 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.
--== 2.15  Read or Clear cached data ==
++== 2.14  Read or Clear cached data ==
++
  (% style="color:blue" %)**AT Command:**
  (% style="color:#037691" %)**AT+CDP**  (%%)       ~/~/ Read cached data
@@ -577,24 +577,27 @@
  (% style="color:#037691" %)**AT+CDP=0**  (%%)  ~/~/ Clear cached data
--[[image:image-20221118094227-5.png]]
++[[image:image-20221021111810-25.png||height="364" width="797"]]
--== 2.16  Firmware Change Log ==
++== 2.15  Firmware Change Log ==
--Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
++Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
++
  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
--== 2.17  Battery Analysis ==
--=== 2.17.1  Battery Type ===
++== 2.16  Battery Analysis ==
--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.
++=== 2.16.1  Battery Type ===
++
++The CPN01 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.
++
  The battery is designed to last for several years depends on the actual use environment and update interval.
  The battery-related documents as below:
@@ -608,9 +608,10 @@
  [[image:image-20221021111911-26.png]]
--=== 2.17.2  Power consumption Analyze ===
++=== 2.16.2  Power consumption Analyze ===
++
  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.
  Instruction to use as below:
@@ -630,18 +630,21 @@
  [[image:1666596205057-567.png]]
--=== 2.17.3  Battery Note ===
++=== 2.16.3  Battery Note ===
++
  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.
--=== 2.17.4  Replace the battery ===
++=== 2.16.4  Replace the battery ===
--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).
++The default battery pack of CPN01 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).
++
++
  = 3.  Access NB-IoT Module =
@@ -649,12 +649,13 @@
  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/]]
++[[image:image-20221021112006-28.png]]
--[[image:image-20221118094449-6.png]]
  = 4.  Using the AT Commands =
++
  == 4.1  Access AT Commands ==
@@ -701,21 +701,15 @@
  AT+ DEBUG   : Enable or Disable debug mode
--AT+ TTRIG1   : Get or Set PB14 PIN Alarm Base on Timeout
++AT+ TTRIG   : Get or Set Alarm Base on Timeout
--AT+ TTRIG2   : Get or Set PB15 PIN Alarm Base on Timeout
++AT+ TTRMOD   : Get or Set the trigger interrupt mode(0:falling,1:rising)
--AT+COUNTMOD  :   Get or Set the count mode
++AT+ CALCFLAG   : Get or Set the calculate flag
--AT+TTRCHANNEL  : Get or Set the number of interrupt channels
++AT+ CLRC   : Clear current door open count
--AT+TTRALARM  : Get or Set TTRIG1 of Alarm interval (unit: minute)
--AT+DISALARM  : Enable/Disable Alarm for door open/close or water leak event
--
--AT+ CLRC   :        Clear current door open count
--
--
  (% style="color:blue" %)**COAP Management**
  AT+URI            : Resource parameters
@@ -746,8 +746,10 @@
  AT+PWORD       : Serial Access Password
++
  = 5.  FAQ =
++
  == 5.1  How to Upgrade Firmware ==
@@ -755,11 +755,13 @@
  Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
--(% style="color:red" %)**Notice: **(% style="color:blue" %)**NDS03A** (%%)**and (% style="color:blue" %)LDS03A(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
++(% style="color:red" %)**Notice: **(% style="color:blue" %)**CPN01** (%%)**and (% style="color:blue" %)CPL01(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.**
++
  = 6.  Trouble Shooting =
++
  == 6.1  Connection problem when uploading firmware ==
@@ -766,6 +766,7 @@
  (% style="color:blue" %)**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
++
  == 6.2  AT Command input doesn't work ==
@@ -772,19 +772,27 @@
  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.
++
  = 7.  Order Info =
--Part Number**:** NDS03A
++Part Number**:** CPN01
++
  = 8.  Packing Info =
  (% style="color:blue" %)**Package Includes**:
--* NDS03A Open/Close Door Sensor x 1
++* CPN01 Open/Close Sensor x 1
++* External antenna x 1
++(% style="color:blue" %)**Dimension and weight**:
++
++* Size: 195 x 125 x 55 mm
++* Weight:   420g
++
  = 9.  Support =

1670404362039-351.png

Author

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

Size

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

Content

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

LMDS200_10.jpg

Author

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

Size

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

Content

image-20221117142300-1.png

Author

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

Size

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

Content

image-20221117145932-2.png

Author

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

Size

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

Content

image-20221117150312-3.png

Author

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

Size

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

Content

image-20221118092935-1.png

Author

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

Size

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

Content

image-20221118093144-2.png

Author

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

Size

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

Content

image-20221118093512-3.png

Author

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

Size

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

Content

image-20221118093658-4.png

Author

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

Size

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

Content

image-20221118094227-5.png

Author

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

Size

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

Content

image-20221118094449-6.png

Author

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

Size

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

Content

image-20221118103445-7.png

Author

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

Size

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

Content

image-20221118103453-8.png

Author

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

Size

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

Content

image-20221118103547-9.png

Author

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

Size

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

Content

image-20221207170748-1.png

Author

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

Size

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

Content

image-20221207170748-2.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-29.9 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