Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 17:03
Change comment:
Uploaded new attachment "1670471559211-638.png", version {1}
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 37 added, 0 removed)
- 1666596205057-567.png
- 1670404362039-351.png
- 1670405841875-916.png
- 1670405928926-116.png
- 1670406036256-101.png
- 1670406261143-723.png
- 1670407401682-959.png
- 1670408172929-569.png
- 1670471530120-960.png
- 1670471559211-638.png
- LMDS200_10.jpg
- image-20221022234529-1.png
- image-20221022234602-2.png
- image-20221023000439-3.png
- image-20221117105556-1.png
- image-20221117114459-2.png
- image-20221117114842-3.png
- image-20221117114937-4.png
- image-20221117114949-5.png
- image-20221117115010-6.png
- image-20221117142300-1.png
- image-20221117145932-2.png
- image-20221117150312-3.png
- image-20221118092935-1.png
- image-20221118093144-2.png
- image-20221118093512-3.png
- image-20221118093658-4.png
- image-20221118094227-5.png
- image-20221118094449-6.png
- image-20221118103445-7.png
- image-20221118103453-8.png
- image-20221118103547-9.png
- image-20221207170748-1.png
- image-20221207170748-2.png
- image-20221207173200-3.png
- image-20221207173300-4.png
- image-20221208090742-1.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - CPN01- NB-IoTOutdoorOpen/CloseDryContactSensor User Manual1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - Content
-
... ... @@ -1,36 +1,61 @@ 1 1 (% style="text-align:center" %) 2 -[[image: http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png"]]2 +[[image:LMDS200_10.jpg]] 3 3 4 4 5 -** ~1.Introduction**5 +**Table of Contents:** 6 6 7 - **1.1 **Whatis CPN01 **NB-IOT** Pulse/Contact Sensor7 +{{toc/}} 8 8 9 -The Dragino CPL01 is a **NB-IOT Contact Sensor**. It detects open/close status and uplink to IoT server via LoRaWAN network. user can see the dry contact status, open time, open counts in the IoT Server. 10 10 11 -The CPL01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculate last open duration. User can also disable the uplink for each open/close event, instead, device can count each open event and uplink periodically. 12 12 13 -CPL01 has the open alarm feature, user can set this feature so device will send Alarm if the contact has been open for a certain time. 14 14 15 - CPL01is designed for outdoor use. Ithas a weatherproof enclosure andindustrial level battery towork inlow to high temperatures.12 += 1. Introduction = 16 16 17 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 18 -\\CPN01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 19 -\\CPN01 is powered by **8500mAh Li-SOCI2 battery**, It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 20 -\\To use CPN01, user needs to check if there is NB-IoT coverage in local area and with the bands CPN01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install CPN01 to get NB-IoT network connection 14 +== 1.1 What is NMDS200 NB-IoT Microwave Radar Distance Sensor == 21 21 22 - 23 23 17 +((( 18 +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. 19 +))) 24 24 25 -**1.2 Features** 21 +((( 22 +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. 23 +))) 26 26 25 +((( 26 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one. 27 +))) 28 + 29 +((( 30 +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. 31 +))) 32 + 33 +((( 34 +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. 35 +))) 36 + 37 +((( 38 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements. 39 +))) 40 + 41 +((( 42 +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) 43 +))) 44 + 45 +((( 46 +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. 47 +))) 48 + 49 + 50 +== 1.2 Features == 51 + 52 + 27 27 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 28 -* Open/Close detect 29 -* Open/Close statistics 54 +* Short uplink interval for Distance Alarm 30 30 * Monitor Battery Level 31 -* Uplink on periodicallyand open/close event56 +* Microwave Radar for distance detection 32 32 * Datalog feature 33 -* Uplink onperiodically58 +* Uplink periodically 34 34 * Downlink to change configure 35 35 * Wall Mountable 36 36 * Outdoor Use ... ... @@ -37,524 +37,536 @@ 37 37 * Ultra-Low Power consumption 38 38 * AT Commands to change parameters 39 39 * Micro SIM card slot for NB-IoT SIM 40 -* 8500mAh Battery for long 65 +* 8500mAh Battery for long-term use 41 41 42 -**1.3 Specification** 43 43 44 -**Common DC Characteristics:** 45 45 46 -* Supply Voltage: 2.1v ~~ 3.6v 47 -* Operating Temperature: -40 ~~ 85°C 69 +== 1.3 Radar probe specification == 48 48 49 -**NB-IoT Spec:** 50 50 51 -* - B1 @H-FDD: 2100MHz 52 -* - B3 @H-FDD: 1800MHz 53 -* - B8 @H-FDD: 900MHz 54 -* - B5 @H-FDD: 850MHz 55 -* - B20 @H-FDD: 800MHz 56 -* - B28 @H-FDD: 700MHz 72 +* Measuring Method: FMCW 73 +* Frequency: 24.000 ~~ 24.500 GHz 74 +* Measurement output power: 6dBm 75 +* Measure range: 0.5 ~~ 20m 76 +* Accuracy: ±0.1m 77 +* Resolution: 0.01m 78 +* Horizontal Angel: 78° 79 +* Vertical Angel: 23° 57 57 58 -**1.4 Installation** 59 59 60 -Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event. 61 61 62 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image001.png]] [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image002.png]]83 +== 1.4 Storage Temperature == 63 63 64 -**1.5 Applications** 65 65 66 -* Open/Close Detection 67 -* Pulse meter application 68 -* Dry Contact Detection 86 + -40°C to +85°C 69 69 70 -**1.6 Mechanical** 71 71 72 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image003.png]]89 +== 1.5 Applications == 73 73 74 -**~ 1.7 Pin Definitions and Switch** 75 75 76 -[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image004.png]] 92 +* Horizontal distance measurement 93 +* Liquid level measurement 94 +* Parking management system 95 +* Object proximity and presence detection 96 +* Intelligent trash can management system 97 +* Robot obstacle avoidance 98 +* Automatic control 99 +* Sewer 100 +* Bottom water level monitoring 77 77 78 -**1.7.1 Pin Definition** 79 79 80 -CPL01 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 user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>url:https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]] 81 81 82 - **1.7.2Jumper JP2(PowerON/OFF)**104 +== 1.6 Specification == 83 83 84 84 85 - Power on Devicewhen puttingthisjumper.107 +(% style="color:blue" %)**Common DC Characteristics:** 86 86 109 +* Supply Voltage: 2.1v ~~ 3.6v 110 +* Operating Temperature: 0 ~~ 70°C 87 87 112 +(% style="color:blue" %)**NB-IoT Spec:** 88 88 89 -**1.7.3 BOOT MODE / SW1** 114 +* B1 @H-FDD: 2100MHz 115 +* B3 @H-FDD: 1800MHz 116 +* B8 @H-FDD: 900MHz 117 +* B5 @H-FDD: 850MHz 118 +* B20 @H-FDD: 800MHz 119 +* B28 @H-FDD: 700MHz 90 90 91 91 92 -1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 93 93 94 - 2)Flash:work mode, the devicestarts to workand send outconsoleoutput for further debug123 +== 1.7 Installation == 95 95 96 96 126 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object. 97 97 98 -**1.7.4 Reset Button** 99 99 129 +[[image:image-20221207170748-1.png]] 100 100 101 -Press to reboot the device. 102 102 132 + [[image:image-20221207170748-2.png||height="345" width="634"]] 103 103 104 104 105 -**1.7.5 LED** 106 106 136 +== 1.8 Pin Definitions and Switch == 107 107 108 -It will flash: 109 109 110 -1. Boot the device in flash mode 111 -1. Send an uplink packet 139 +[[image:1670404362039-351.png]] 112 112 113 113 114 - **2. UseCPN01to communicate with IoT Server**142 += 2. Use NMDS200 to communicate with IoT Server = 115 115 116 - **2.1 How it works**144 +== 2.1 How it works == 117 117 118 -The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01. 119 119 120 -The diagram belowshows thengflow indefaultfirmware ofCPN01:147 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200. 121 121 122 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image005.png||alt="说明:image-20220708101605-2.png"]]149 +The diagram below shows the working flow in the default firmware of NMDS200: 123 123 124 - **2.2 Configure the CPN01**151 +[[image:image-20221021110615-5.png||height="996" width="492"]] 125 125 126 -**2.2.1 Test Requirement** 127 127 128 - TouseCPN01in your city, make suremeetbelow requirements:154 +== 2.2 Configure NMDS200 == 129 129 130 -* Your local operator has already distributed a NB-IoT Network there. 131 -* The local NB-IoT network used the band that CPN01 supports. 156 + 157 +To use NMDS200 in your city, make sure to meet below requirements: 158 + 159 +* Your local operator has already distributed an NB-IoT Network. 160 +* The local NB-IoT network used the band that NMDS200 supports. 132 132 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 133 133 134 -Below figure shows our testing structure. CPN01will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server163 +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. 135 135 136 - 165 +[[image:image-20221208090742-1.png]] 137 137 138 -**2.2.2 Insert SIM card** 139 139 168 +=== 2.2.1 Insert NB-IoT SIM card === 169 + 170 + 140 140 Insert the NB-IoT Card get from your provider. 141 141 142 -User need to take out the NB-IoT module and insert the SIM card like below: 173 +User needs to take out the NB-IoT module and insert the SIM card like below: 143 143 144 -[[image: file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image006.png||alt="说明:1657249468462-536.png"]] 175 +[[image:image-20221021110745-6.png]] 145 145 146 -**2.2.3 Connect USB – TTL to CPN01 to configure it** 147 147 148 - UserneedtoconfigureCPN01 via serial port to set the **Server Address** / **Uplink Topic** to definewhere and how-to uplink packets.CPN01 support AT Commands, user can use aUSBtoTTLadapter toconnect to CPN01anduse AT Commands toconfigure it,as below.178 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it === 149 149 150 -**Connection:** 151 151 152 - USB TTL GND<~-~-~-~->GND181 +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. 153 153 154 - USBTTL TXD <~-~-~-~-> UART_RXD183 +(% style="color:blue" %)**Connection:** 155 155 156 - USB TTL RXD <~-~-~-~->UART_TXD185 +(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND** 157 157 187 +(% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** 188 + 189 +(% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** 190 + 191 + 158 158 In the PC, use below serial tool settings: 159 159 160 -* Baud: **9600** 161 -* Data bits:** 8** 162 -* Stop bits: **1** 163 -* Parity: **None** 164 -* Flow Control: **None** 194 +* Baud: (% style="color:red" %)**9600** 165 165 166 - Makesuretheswitch isin FLASH position, then power on device byconnecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enterthe **password:12345678**to access AT Command input.196 +* Data bits:** (% style="color:red" %)8(%%)** 167 167 168 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image007.png]]198 +* Stop bits: (% style="color:red" %)**1** 169 169 170 -* *Note:the validATCommandscanbefoundat: **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]200 +* Parity: (% style="color:red" %)**None** 171 171 172 -* *2.2.4UseCoAP protocoltouplink data**202 +* Flow Control: (% style="color:red" %)**None** 173 173 174 - **Note: if you don't haveCoAPserver,you can referthislinktosetupone:**[[**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/]]204 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%). 175 175 176 - **Usebelow commands:**206 +[[image:image-20221021110817-7.png]] 177 177 178 -* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 179 -* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 180 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 208 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input. 181 181 210 + 211 +(% 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]] 212 + 213 + 214 +=== 2.2.3 Use CoAP protocol to uplink data === 215 + 216 + 217 +(% 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/]] 218 + 219 + 220 +(% style="color:blue" %)**Use below commands in NMDS200:** 221 + 222 +* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 223 + 224 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ Set CoAP server address and port 225 + 226 +* (% style="color:#037691" %)**AT+URI=0,0,11,2,"mqtt" ** (%%) ~/~/ Set CoAP resource path 227 + 182 182 For parameter description, please refer to AT command set 183 183 184 -[[image: file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image008.png]]230 +[[image:image-20221021110948-8.png]] 185 185 186 -After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server. 187 187 188 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image009.png]]233 +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. 189 189 190 - **2.2.5 Use UDP protocol to uplink data(Defaultprotocol)**235 +[[image:1670405841875-916.png]] 191 191 192 -This feature is supported since firmware version v1.0.1 193 193 194 -* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 195 -* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 196 -* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 238 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) === 197 197 198 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image010.png]] 199 199 200 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image011.png||alt="说明:1657249930215-289.png"]]241 +(% style="color:blue" %)**AT Commands:** 201 201 243 +* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 244 + 245 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ Set UDP server address and port 246 + 247 +* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 248 + 249 + [[image:image-20221021111025-10.png]] 250 + 251 + 252 +[[image:image-20221021111033-11.png||height="241" width="576"]] 253 + 202 202 203 203 204 - **2.2.6Use MQTT protocol to uplink data**256 +=== 2.2.5 Use MQTT protocol to uplink data === 205 205 206 -This feature is supported since firmware version v110 207 207 208 -* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 209 -* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 210 -* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 211 -* **AT+UNAME=UNAME **~/~/Set the username of MQTT 212 -* **AT+PWD=PWD **~/~/Set the password of MQTT 213 -* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 214 -* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 259 +(% style="color:blue" %)**AT Commands:** 215 215 216 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image012.png]]261 +* (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 217 217 218 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image013.png]]263 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 219 219 265 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 266 + 267 +* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 268 + 269 +* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 270 + 271 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB **(%%)** **~/~/ Set the sending topic of MQTT 272 + 273 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB ** (%%) ~/~/ Set the subscription topic of MQTT 274 + 275 + [[image:image-20221118103445-7.png]] 276 + 277 + 278 +[[image:1670405928926-116.png]] 279 + 220 220 221 221 222 -MQTT protocol has a much higher power consumption compare vsUDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.282 +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. 223 223 224 -**2.2.7 Use TCP protocol to uplink data** 225 225 226 - Thisfeatureissupported sincefirmwareversionv110285 +=== 2.2.6 Use TCP protocol to uplink data === 227 227 228 -* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 229 -* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 230 230 231 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image014.png]]288 +(% style="color:blue" %)**AT Commands:** 232 232 233 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image015.png||alt="说明: 1657250255956-604.png"]]290 +* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 234 234 292 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 293 + 294 + [[image:1670406036256-101.png||height="676" width="713"]] 295 + 296 + 297 +[[image:image-20221021111131-15.png]] 298 + 235 235 236 236 237 - **2.2.8Change Update Interval**301 +=== 2.2.7 Change Update Interval === 238 238 239 -User can use below command to change the **uplink interval**. 240 240 241 - ***AT+TDC=600**~/~/SetUpdateIntervalto 600s304 +User can use below command to change the (% style="color:blue" %)**uplink interval**. 242 242 243 -** NOTE:**306 +* (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (4 hours) 244 244 245 - **~1.Bydefault, thedevice will sendan uplink message every 1 hour.**308 +(% style="color:red" %)**NOTE:** 246 246 247 - **2.3UplinkPayload**310 +1. By default, the device will send an uplink message every 4 hour. 248 248 249 -In this mode, uplink payload includes 87 bytes in total by default. 250 250 251 - Eachtimethe device uploads a data package,8 sets of recorded data will be attached. Up to32 sets of recorded data can be uploaded.313 +== 2.3 Uplink Payload == 252 252 253 -|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4 254 -|**Value**|[[Device ID>>path:#H2.4.1A0A0DeviceID]]|[[Ver>>path:#H2.4.2A0VersionInfo]]|[[BAT>>path:#H2.4.3A0BatteryInfo]]|[[Signal Strength>>path:#H2.4.4A0SignalStrength]]|MOD|[[Interrupt>>path:#H2.4.8A0DigitalInterrupt]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|Time stamp 255 255 316 +The uplink payload includes 23 bytes in total by default. 256 256 257 -|2|2|4|8 group 258 -|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|... 318 +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. 259 259 260 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data. 261 261 262 -[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image016.png]] 321 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:450px" %) 322 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:50px" %)**8**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:75px" %)**1**|(% style="width:30px" %)**1**|(% style="width:50px" %)**1**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2** 323 +|=(% 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>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]] 263 263 264 -The payload is ASCII string, representative same HEX: 325 +(% border="1" style="background-color:#ffffcc; color:green; width:429px" %) 326 +|(% style="width:60px" %)**4**|(% style="width:60px" %)**2**|(% style="width:60px" %)**2**|(% style="width:60px" %)**4**|(% style="width:100px" %)((( 327 +**1-32 group** 328 +))) 329 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance 2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)... 265 265 266 - 0xf86778705021331700640c7817010001000000090000026315537b0100000b02000002663510fed0100000e0200000263510f39010000000000000063510e85010000000000000063510d2e010000000000000063510c7a010000000000000063510bc6010000000000000063510954010000000000000063510882where:331 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data. 267 267 268 -* **Device ID: 0x f867787050213317 = f867787050213317** 269 -* **Version: 0x0064=100=1.0.0** 333 +[[image:1670406261143-723.png]] 270 270 271 -* **BAT: 0x0c78 = 3192 mV = 3.192V** 272 -* **Singal: 0x17 = 23** 273 -* **Mod: 0x01 = 1** 274 -* **Calculate Flag: 0x00= 0** 275 -* **Contact Status: 0x00= 0** 276 -* **Alarm:0x00 =0** 277 -* **Total pulse:0x09 =0** 278 -* **The last open duration:0x02 =2** 279 -* **Time stamp : 0x6315537b =1662342011** 280 -* **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000b0200002663510fed** 281 -* **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp : 0100000e0200002663510f39,.......** 282 282 283 - **2.4PayloadExplanationandSensorInterface**336 +The payload is ASCII string, representative same HEX: f867787050471071 0064 0cc3 09 01 00 00ef 013d 6390453d 284 284 285 -** 2.4.1DeviceID**338 +**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__(%%)** 286 286 287 - By default, theDevice ID equal to the last 15 bits of IMEI.340 +**where:** 288 288 289 - Usercanuse **AT+DEUI** to set Device ID342 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071 290 290 291 -* *Example:**344 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 292 292 293 - AT+DEUI=868411056754138346 +* (% style="color:#037691" %)**BAT :**(%%) 0x0cc3 = 3267 mV = 3.267V 294 294 295 - TheDeviceID isstoredina none-erase area, Upgradethefirmwareor run AT+FDR won't erase Device ID.348 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9 296 296 297 -* *2.4.2VersionInfo**350 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 298 298 299 - Specifythesoftwareversion:x64=100,meansfirmwareversion 1.00.352 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0 300 300 301 - Forexample:0x00 64 : thisdevice is CPN01with firmwareversion1.0.0.354 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239 302 302 303 -* *2.4.3BatteryInfo**356 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317 304 304 305 - CheckthebatteryvoltageforCPN01.358 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time) 306 306 307 -Ex1: 0x0B45 = 2885mV 308 308 309 -Ex2: 0x0B49 = 2889mV 310 310 311 - **2.4.4SignalStrength**362 +== 2.4 Payload Explanation and Sensor Interface == 312 312 313 - NB-IoTNetwork signal Strength.364 +=== 2.4.1 Device ID === 314 314 315 -**Ex1: 0x1d = 29** 316 316 317 - **0**-113dBmorless367 +By default, the Device ID is equal to the last 15 bits of IMEI. 318 318 319 -** 1**-111dBm369 +User can use (% style="color:blue" %)**AT+DEUI** (%%)to set Device ID 320 320 321 -** 2...30**-109dBm... -53dBm371 +**Example:** 322 322 323 - **31** -51dBm or greater373 +AT+DEUI=868411056754138 324 324 325 - **99**Notknown or notdetectable375 +The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID. 326 326 327 -**2.4.5 Calculate Flag** 328 328 329 - Thecalculateflag is a userdefine field, IoTserver can use this filed tohandledifferent meter with different pulse factor.For example, if there are 100 water meters, meter 1 ~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.378 +=== 2.4.2 Version Info === 330 330 331 -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. 332 332 333 - Defaultvalue: 0.381 +Specify the software version: 0x64=100, which means firmware version 1.00. 334 334 335 - Range(6bits):(b)000000~~(b)111111383 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0. 336 336 337 -**2.4.6 Alarm** 338 338 339 - See[[AlarmBase on Timeout>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H3.5AlarmBaseonTimeout]]386 +=== 2.4.3 Battery Info === 340 340 341 -**2.4.7 Contact Status** 342 342 343 - 0:Open389 +Check the battery voltage for NMDS200. 344 344 345 -1: Close391 +Ex1: 0x0B45 = 2885mV 346 346 347 - **2.4.8Totalpulse**393 +Ex2: 0x0B49 = 2889mV 348 348 349 -Total pulse/counting base on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]] 350 350 351 - Range(3 Bytes) : 0x000000 ~~ 0xFFFFFF.Max:16777215396 +=== 2.4.4 Signal Strength === 352 352 353 -**2.4.9 The last open duration** 354 354 355 - DryContactlastopenduration.399 +NB-IoT Network signal Strength. 356 356 357 - Unit:min.401 +(% style="color:blue" %)**Ex1: 0x1d = 29** 358 358 359 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image017.png]]403 +(% style="color:#037691" %)**0** (%%) -113dBm or less 360 360 405 +(% style="color:#037691" %)**1** (%%) -111dBm 361 361 362 -**2. 4.10Timestamp**407 +(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm 363 363 364 - Timestamp:x6315537b =1662342011409 +(% style="color:#037691" %)**31** (%%) -51dBm or greater 365 365 366 - ConvertUnixtimestampto time2022-9-5 9:40:11.411 +(% style="color:#037691" %)**99** (%%) Not known or not detectable 367 367 368 -**~ ** 369 369 370 - **2.5 DownlinkPayload**414 +=== 2.4.5 Distance === 371 371 372 -By default, CPN01 prints the downlink payload to console port. 373 373 374 -[[image: file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image018.png||alt="说明: image-20220708133731-5.png"]]417 +[[image:1670407401682-959.png]] 375 375 376 -**Examples:** 377 377 378 - ***SetTDC**420 +(% style="color:blue" %)**Object1 Distance:** 379 379 380 - Ifthepayload=0100003C, itmeanssetthe END Node'sTDCto0x00003C=60(S), while typecode is01.422 +Distance between sensor probe to the first object. (unit: cm) 381 381 382 - Payload:0100 001ETDC=30S424 +For example, if the data you get from the register is 0x02 0x05, the distance between the sensor and the measured object is 383 383 384 - Payload:100003CTDC=60S426 +(% style="color:blue" %)**0205(H) = 517 (D) = 517 cm.** 385 385 386 -* **Reset** 387 387 388 - Ifpayload=0x04FF, it willreset theNSE01429 +(% style="color:blue" %)**Object2 Distance:** 389 389 390 - * **INTMOD**431 +Distance between sensor probe to the second object. (unit: cm) 391 391 392 -Downlink Payload: 06000003, Set AT+INTMOD=3 393 393 394 - **2.6LED Indicator**434 +=== 2.4.6 Timestamp === 395 395 396 -The CPN01 has an internal LED which is to show the status of different state. 397 397 398 -* When power on, CPN01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 399 -* Then the LED will be on for 1 second means device is boot normally. 400 -* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds. 401 -* For each uplink probe, LED will be on for 500ms. 437 +Timestamp : 0x6315537b =1662342011 402 402 403 -**2.7 ** Alarm Base on Timeout 404 404 405 - CPL01canmonitor the timeout for a status change,this feature can be used to monitor some events such as door opening toolong etc. RelatedParameters are:440 +== 2.5 Downlink Payload == 406 406 407 407 408 - **~1.Keep Status:Status to bemonitor**443 +By default, NMDS200 prints the downlink payload to console port. 409 409 410 - Keep Status = 1:Monitor Closeto Openevent445 +[[image:image-20221021111414-18.png]] 411 411 412 -Keep Status = 0: Monitor Open to Close event 413 413 448 +**Examples:** 414 414 415 -* *2.KeepTime:Timeoutto send an Alarm**450 +* (% style="color:#037691" %)**Set TDC** 416 416 417 - Range0~~65535(0xFFFF)seconds.452 +If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 418 418 419 - If keep time = 0, Disable AlarmBaseonTimeoutfeature.454 +Payload: 01 00 00 1E TDC=30S 420 420 421 - If keep time > 0, device will monitor the keep status event andsendanalarmwhenstatus doesn’t change after timeout.456 +Payload: 01 00 00 3C TDC=60S 422 422 458 +* (% style="color:#037691" %)**Reset** 423 423 424 - **ATCommand**toconfigure:460 +If payload = 0x04FF, it will reset the NMDS200 425 425 426 -* *AT+TTRIG=1,30**~-~-> When the **Keep Status** change from connectto disconnect, and device remains in disconnect status for more than 30 seconds. CPL01 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.462 +* (% style="color:#037691" %)**INTMOD** 427 427 428 - **AT+TTIG=0,0 ** ~-~->DefaultValue,disableimeoutAlarm.464 +Downlink Payload: 06000003, Set AT+INTMOD=3 429 429 430 -**2.8** Set debug mode 431 431 432 - Feature:EnableorDisable debug mode467 +== 2.6 LED Indicator == 433 433 434 434 435 - **ATCommand:AT+DEBUG**470 +The NMDS200 has an internal LED which is to show the status of different states. 436 436 437 - |**CommandExample**|**Function**|**Response**438 - |AT+DEBUG=0|Disabledebug modeto0|OK439 - |AT+DEBUG=1|Enabledebugmodeto1|OK472 +* When the device starts normally, the LED will light up for 1 second. 473 +* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds. 474 +* For each uplink probe, LED will be on for 500ms. 440 440 441 -== 2.9 Clear Flash Record == 442 442 443 -Feature: Clear flash storage for data log feature. 444 444 445 - **ATCommand:AT+CLRDTA**478 +== 2.7 Distance alarm function == 446 446 447 -[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image019.png||alt="说明: image-20220609151132-7.png"]] 448 448 449 - **~2.10 **Settriggermode481 +(% style="color:blue" %)**AT Command: AT+ALARM1=min,max** 450 450 451 - ➢AT Command: **AT+TTRMOD**483 +(% style="color:#037691" %)**Example 1:** 452 452 453 - Feature:Set the triggerinterruptmode.485 +AT+ ALARM1 =60,200 ~/~/ Alarm when moisture lower than 60. 454 454 455 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image020.png||alt="说明:image-20220609151344-9.png"]]487 +AT+ ALARM2 =min,max 456 456 457 -**2.11** Set the calculate flag 458 458 459 - Feature:Setthealculateflag490 +(% style="color:#037691" %)**Example 2:** 460 460 461 - **ATCommand:AT+CALCFLAG**492 +AT+ ALARM2 =200,1500 ~/~/ Alarm when temperature lower than 1500 462 462 463 -|**Command Example**|**Function**|**Response** 464 -|AT+CALCFLAG =1|Set the calculate flag to 1.|OK 465 -|AT+CALCFLAG =2|Set the calculate flag to 2.|OK 466 466 467 - **2.12**count number495 +== 2.8 Set the number of data to be uploaded and the recording time == 468 468 469 -Feature: Manually set the count number 470 470 471 -**AT Command: AT+SETCNT**498 +(% style="color:blue" %)**AT Command:** 472 472 473 -|**Command Example**|**Function**|**Response** 474 -|AT+ SETCNT =0|Set the count number to 0.|OK 475 -|AT+ SETCNT =100|Set the count number to 100.|OK 500 +(% 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) 476 476 502 +(% 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. 477 477 478 -**2.13 Set the number of data to be uploaded and the recording time** 479 479 480 - ➢ATCommand:505 +== 2.9 Read or Clear cached data == 481 481 482 -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) 483 483 508 +(% style="color:blue" %)**AT Command:** 484 484 485 - AT+NOUD=8~/~/The device uploads8 sets of recordeddatabydefault.Upto32setsofrecorddatacan beuploaded.510 +(% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 486 486 487 - **2.14Reador Clear cached data**512 +(% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 488 488 489 - ➢ AT Command:514 +[[image:1670408172929-569.png]] 490 490 491 -AT+CDP ~/~/ Read cached data 492 492 493 - [[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image021.png]]517 +== 2.10 Firmware Change Log == 494 494 495 495 496 - AT+CDP=0~/~/learheddata 520 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]] 497 497 498 - **2.15FirmwareChange Log**522 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 499 499 500 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 501 501 502 - UpgradeInstruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]525 +== 2.11 Battery Analysis == 503 503 504 - **2.16BatteryAnalysis**527 +=== 2.11.1 Battery Type === 505 505 506 -**2.16.1 Battery Type** 507 507 508 -The CPN01battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.530 +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. 509 509 510 -The battery is designed to last for several years depends on the actual lyuse environment and update interval.532 +The battery is designed to last for several years depends on the actual use environment and update interval. 511 511 512 -The battery 534 +The battery-related documents as below: 513 513 514 514 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 537 + 515 515 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 539 + 516 516 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 517 517 518 -[[image: file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image022.png||alt="说明: image-20220708140453-6.png"]] 542 +[[image:image-20221021111911-26.png]] 519 519 520 -**2.16.2 Power consumption Analyze** 521 521 545 +=== 2.11.2 Power consumption Analyze === 546 + 547 + 522 522 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. 523 523 524 524 Instruction to use as below: 525 525 526 -**Step 1: **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 552 +(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 527 527 528 -**Step 2: ** Open it and choose 554 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 529 529 530 530 * Product Model 557 + 531 531 * Uplink Interval 559 + 532 532 * Working Mode 533 533 534 534 And the Life expectation in difference case will be shown on the right. 535 535 536 -[[image: file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image023.jpg||alt="说明: image-20220708141352-7.jpeg"]] 564 +[[image:1666596205057-567.png]] 537 537 538 -**2.16.3 Battery Note** 539 539 567 +=== 2.11.3 Battery Note === 568 + 569 + 540 540 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. 541 541 542 -**2.16.4 Replace the battery** 543 543 544 - Thedefault battery pack of CPN01 includes a ER26500 plus super capacitor.If user can't find this pack locally, they can find ER26500 orequivalence without the SPC1520 capacitor, which willalso work in mostcase.The SPC can enlargethe batterylife for high frequency use (update period below 5 minutes).573 +=== 2.11.4 Replace the battery === 545 545 546 -**3. Access NB-IoT Module** 547 547 576 +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). 577 + 578 + 579 += 3. Access NB-IoT Module = 580 + 581 + 548 548 Users can directly access the AT command set of the NB-IoT module. 549 549 550 550 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/]] 551 551 552 -[[image:file:///C:\Users\ADMINI~~1\AppData\Local\Temp\msohtmlclip1\01\clip_image024.png||alt="说明: 1657261278785-153.png"]] 553 553 554 - **4. UsingtheAT Commands**587 +[[image:image-20221118094449-6.png]] 555 555 556 -**4.1 Access AT Commands** 557 557 590 += 4. Using the AT Commands = 591 + 592 +== 4.1 Access AT Commands == 593 + 594 + 558 558 See this link for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 559 559 560 560 AT+<CMD>? : Help on <CMD> ... ... @@ -565,8 +565,9 @@ 565 565 566 566 AT+<CMD>=? : Get the value 567 567 568 -**General Commands** 569 569 606 +(% style="color:blue" %)**General Commands** 607 + 570 570 AT : Attention 571 571 572 572 AT? : Short Help ... ... @@ -581,133 +581,107 @@ 581 581 582 582 AT+INTMOD : Set the trigger interrupt mode 583 583 584 -AT+5VT 622 +AT+5VT : Set extend the time of 5V power 585 585 586 -AT+PRO 624 +AT+PRO : Choose agreement 587 587 588 -AT+RXDL 626 +AT+RXDL : Extend the sending and receiving time 589 589 590 -AT+SERVADDR 628 +AT+SERVADDR : Server Address 591 591 592 -AT+TR : Get or Set record time "630 +AT+TR : Get or Set record time 593 593 632 +AT+NOUD : Get or Set the number of data to be uploaded 594 594 595 -AT+ NOUDGetorSetthenumber ofdatato be uploaded634 +AT+CDP : Read or Clear cached data 596 596 636 +AT+DEBUG: Enable or Disable debug mode 597 597 598 -AT+ CDP: ReadorClearcacheddata638 +AT+ALARM1: Get or Set alarm of distance1 599 599 640 +AT+ALARM2: Get or Set alarm of distance2 600 600 601 -AT+ DEBUG:EnableorDisabledebugmode642 +AT+GETSENSORVALUE : Returns the current sensor measurement 602 602 603 -AT+ TTRIG: Get orSetAlarm Base on Timeout644 +AT+POWERIC : Get or set the Power IC flag 604 604 605 -AT+ TTRMOD : Get or Set the trigger interrupt mode(0:falling,1:rising) 606 606 607 - AT+CALCFLAG : GetSetthecalculateflag647 +(% style="color:blue" %)**COAP Management** 608 608 609 -AT+ CLRC:Clearcurrentdoor open count649 +AT+URI : Resource parameters 610 610 611 -**COAP Management** 612 612 613 - AT+URI: Resourceparameters652 +(% style="color:blue" %)**UDP Management** 614 614 615 - **UDPManagement**654 +AT+CFM : Upload confirmation mode (only valid for UDP) 616 616 617 -AT+CFM : Upload confirmation mode (only valid for UDP) 618 618 619 -**MQTT Management** 657 +(% style="color:blue" %)**MQTT Management** 620 620 621 -AT+CLIENT 659 +AT+CLIENT : Get or Set MQTT client 622 622 623 -AT+UNAME 661 +AT+UNAME : Get or Set MQTT Username 624 624 625 -AT+PWD 663 +AT+PWD : Get or Set MQTT password 626 626 627 -AT+PUBTOPIC :Get or Set MQTT publish topic665 +AT+PUBTOPIC : Get or Set MQTT publish topic 628 628 629 -AT+SUBTOPIC :Get or Set MQTT subscription topic667 +AT+SUBTOPIC : Get or Set MQTT subscription topic 630 630 631 -**Information** 632 632 633 - AT+FDR: FactoryDataReset670 +(% style="color:blue" %)**Information** 634 634 635 -AT+ PWORD:SerialAccessPassword672 +AT+FDR : Factory Data Reset 636 636 637 - **5.FAQ**674 +AT+PWORD : Serial Access Password 638 638 639 -**5.1 How to Upgrade Firmware** 640 640 641 - Usercanupgradethe firmware for 1) bug fix, 2) new feature release.677 += 5. FAQ = 642 642 643 - Pleaseseethislink for how toupgrade: [[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]]679 +== 5.1 How to Upgrade Firmware == 644 644 645 -**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.** 646 646 647 - **5.2CanI calibrateCPN01todifferentsoiltypes?**682 +User can upgrade the firmware for 1) bug fix, 2) new feature release. 648 648 649 - CPN01 is calibratedforsaline-alkalisoilandloamy soil.Ifuserswantto useitfor othersoil, they cancalibratethe valueinhe IoT platformbasen the value measuredby saline-alkali soil andloamy soil. Theformula can befoundat[[thislink>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].684 +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]] 650 650 651 -** 6.Trouble Shooting**686 +(% style="color:red" %)**Notice: **(% style="color:blue" %)**NMDS200** (%%)**and (% style="color:blue" %)LMDS200(%%)**(% style="color:blue" %) (%%)**share the same mother board. They use the same connection and method to update.** 652 652 653 -**6.1 Connection problem when uploading firmware** 654 654 655 - **Pleasesee: **[[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]]689 += 6. Trouble Shooting = 656 656 657 - **6.2ATCommand inputdoesn'twork**691 +== 6.1 Connection problem when uploading firmware == 658 658 659 -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 **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string. 660 660 661 -** 7.Order**694 +(% 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]] 662 662 663 -Part Number**:** CPN01 664 664 665 - **8.PackingInfo**697 +== 6.2 AT Command input doesn't work == 666 666 667 -**Package Includes**: 668 668 669 -* CPN01 NB-IoT Soil Moisture & EC Sensor x 1 670 -* External antenna x 1 700 +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. 671 671 672 -**Dimension and weight**: 673 673 674 -* Size: 195 x 125 x 55 mm 675 -* Weight: 420g 703 += 7. Order Info = 676 676 677 -**9. Support** 678 678 679 -* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 680 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] 706 +Part Number:(% style="color:blue" %)** NMDS200** 681 681 682 - 683 683 709 += 8. Packing Info = 684 684 685 685 712 +(% style="color:blue" %)**Package Includes**: 686 686 714 +* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1 687 687 688 688 689 689 718 += 9. Support = 690 690 691 691 721 +* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 692 692 723 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] 693 693 694 - 695 - 696 - 697 - 698 - 699 - 700 - 701 - 702 - 703 - 704 - 705 - 706 - 707 - 708 - 709 - 710 - 711 - 712 - 713 - 725 +
- 1666596205057-567.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +179.8 KB - Content
- 1670404362039-351.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +492.6 KB - Content
- 1670405841875-916.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.1 KB - Content
- 1670405928926-116.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.7 KB - Content
- 1670406036256-101.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +181.0 KB - Content
- 1670406261143-723.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.9 KB - Content
- 1670407401682-959.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.7 KB - Content
- 1670408172929-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +211.8 KB - Content
- 1670471530120-960.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +67.6 KB - Content
- 1670471559211-638.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +170.6 KB - Content
- LMDS200_10.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +39.9 KB - Content
- image-20221022234529-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.3 KB - Content
- image-20221022234602-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +135.7 KB - Content
- image-20221023000439-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +82.1 KB - Content
- image-20221117105556-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +133.3 KB - Content
- image-20221117114459-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +14.9 KB - Content
- image-20221117114842-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +964.1 KB - Content
- image-20221117114937-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +79.1 KB - Content
- image-20221117114949-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +33.4 KB - Content
- image-20221117115010-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +40.4 KB - Content
- image-20221117142300-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +147.8 KB - Content
- image-20221117145932-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +51.9 KB - Content
- image-20221117150312-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +8.7 KB - Content
- image-20221118092935-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +13.1 KB - Content
- image-20221118093144-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +11.7 KB - Content
- image-20221118093512-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +9.5 KB - Content
- image-20221118093658-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +12.7 KB - Content
- image-20221118094227-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.2 KB - Content
- image-20221118094449-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.5 KB - Content
- image-20221118103445-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +20.4 KB - Content
- image-20221118103453-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +46.2 KB - Content
- image-20221118103547-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +43.5 KB - Content
- image-20221207170748-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +26.1 KB - Content
- image-20221207170748-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.9 KB - Content
- image-20221207173200-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +76.7 KB - Content
- image-20221207173300-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.0 KB - Content
- image-20221208090742-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +79.7 KB - Content