Changes for page NLMS01-NB-IoT Leaf Moisture Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:54
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,41 +1,31 @@ 1 -(% style="text-align:center" %) 2 -[[image:image-20220907171221-1.jpeg]] 1 +[[image:image-20220907171221-1.jpeg]] 3 3 4 - 5 5 6 -{{toc/}} 7 7 5 +**~1. Introduction** 8 8 7 +**1.1 What is NLMS01 **Leaf Moisture Sensor 9 9 10 - =1.Introduction=9 +The Dragino NLMS01 is a **NB-IOT Leaf Moisture Sensor** for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof. 11 11 11 +NLMS01 detects leaf's** moisture and temperature **use FDR method, it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy. 12 12 13 -== 1.1 What is NLMS01 Leaf Moisture Sensor == 14 - 15 - 16 -The Dragino NLMS01 is a (% style="color:blue" %)**NB-IOT Leaf Moisture Sensor**(%%) for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof. 17 - 18 -NLMS01 detects leaf's(% style="color:blue" %)** moisture and temperature use FDR method**(%%), it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy. 19 - 20 20 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. 21 -\\NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement.22 -\\NLMS01 is powered by (% style="color:blue" %)**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).23 -\\To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%)from local operator and install NLMS01 to get NB-IoT network connection.14 +\\NLMS01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 15 +\\NLMS01 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) 16 +\\To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install NLMS01 to get NB-IoT network connection 24 24 25 - 26 26 [[image:image-20220907171221-2.png]] 27 27 28 - 29 29 [[image:image-20220907171221-3.png]] 30 30 22 +**1.2 Features** 31 31 32 - 33 -== 1.2 Features == 34 - 35 - 36 36 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 37 37 * Monitor Leaf moisture 38 -* Monitor Leaf temperature 26 + 27 +* Monitor Leaf temperature 28 + 39 39 * Moisture and Temperature alarm function 40 40 * Monitor Battery Level 41 41 * Uplink on periodically ... ... @@ -47,22 +47,14 @@ 47 47 * Micro SIM card slot for NB-IoT SIM 48 48 * 8500mAh Battery for long term use 49 49 50 -((( 51 - 40 +**1.3 Specification** 52 52 42 +**Common DC Characteristics:** 53 53 54 - 55 -))) 56 - 57 -== 1.3 Specification == 58 - 59 - 60 -(% style="color:#037691" %)**Common DC Characteristics:** 61 - 62 62 * Supply Voltage: 2.1v ~~ 3.6v 63 63 * Operating Temperature: -40 ~~ 85°C 64 64 65 - (% style="color:#037691" %)**NB-IoT Spec:**47 +**NB-IoT Spec:** 66 66 67 67 * - B1 @H-FDD: 2100MHz 68 68 * - B3 @H-FDD: 1800MHz ... ... @@ -71,12 +71,11 @@ 71 71 * - B20 @H-FDD: 800MHz 72 72 * - B28 @H-FDD: 700MHz 73 73 56 +**1.4 Probe Specification** 74 74 75 -== 1.4 Probe Specification == 76 76 59 +**Leaf Moisture: percentage of water drop over total leaf surface** 77 77 78 -(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface** 79 - 80 80 * Range 0-100% 81 81 * Resolution: 0.1% 82 82 * Accuracy: ±3%(0-50%);±6%(>50%) ... ... @@ -83,7 +83,7 @@ 83 83 * IP67 Protection 84 84 * Length: 3.5 meters 85 85 86 - (% style="color:#037691" %)**Leaf Temperature:**67 +**Leaf Temperature:** 87 87 88 88 * Range -50℃~80℃ 89 89 * Resolution: 0.1℃ ... ... @@ -91,42 +91,30 @@ 91 91 * IP67 Protection 92 92 * Length: 3.5 meters 93 93 75 +**~ 1.5 Applications** 94 94 95 -== 1.5 Applications == 96 - 97 - 98 98 * Smart Agriculture 99 99 79 +**1.6 Pin mapping and power on** 100 100 101 -== 1.6 Pin mapping and power on == 102 - 103 - 104 104 [[image:image-20220907171221-4.png]] 105 105 106 106 **~ ** 107 107 85 +**2. Use NLMS01 to communicate with IoT Server** 108 108 109 - =2.Use NLMS01 tocommunicatewith IoT Server =87 +**2.1 How it works** 110 110 111 - 112 -== 2.1 How it works == 113 - 114 - 115 115 The NLMS01 is equipped with a NB-IoT module, the pre-loaded firmware in NLMS01 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 NLMS01. 116 116 117 117 The diagram below shows the working flow in default firmware of NLMS01: 118 118 119 - 120 120 [[image:image-20220907171221-5.png]] 121 121 95 +**2.2 Configure the NLMS01** 122 122 97 +**2.2.1 Test Requirement** 123 123 124 -== 2.2 Configure the NLMS01 == 125 - 126 - 127 -=== 2.2.1 Test Requirement === 128 - 129 - 130 130 To use NLMS01 in your city, make sure meet below requirements: 131 131 132 132 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -133,114 +133,90 @@ 133 133 * The local NB-IoT network used the band that NLMS01 supports. 134 134 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 135 135 136 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NLMS01 will use (%style="color:#037691" %)**CoAP(120.24.4.116:5683)**(%%)or raw(%style="color:#037691" %)**UDP(120.24.4.116:5601)** or(%%)(% style="color:#037691"%)**MQTT(120.24.4.116:1883)**(%%)or(% style="color:#037691" %)**TCP(120.24.4.116:5600)**(%%)protocol to send data to the test server105 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NLMS01 will 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 server 137 137 138 - 139 139 [[image:image-20220907171221-6.png]] 140 140 109 +**2.2.2 Insert SIM card** 141 141 142 - 143 -=== 2.2.2 Insert SIM card === 144 - 145 - 146 146 Insert the NB-IoT Card get from your provider. 147 147 148 148 User need to take out the NB-IoT module and insert the SIM card like below: 149 149 150 - 151 151 [[image:image-20220907171221-7.png]] 152 152 117 +**2.2.3 Connect USB – TTL to NLMS01 to configure it** 153 153 119 +User need to configure NLMS01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USB to TTL adapter to connect to NLMS01 and use AT Commands to configure it, as below. 154 154 155 - === 2.2.3ConnectUSB – TTL toNLMS01 to configure it ===121 +**Connection:** 156 156 123 + USB TTL GND <~-~-~-~-> GND 157 157 158 - Userneed to configure NLMS01 via serial port to set the (% style="color:#037691" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USBtoTTLadaptertoconnect to NLMS01 and useATCommands to configure it, as below.125 + USB TTL TXD <~-~-~-~-> UART_RXD 159 159 127 + USB TTL RXD <~-~-~-~-> UART_TXD 160 160 161 -(% style="color:blue" %)**Connection:** 162 - 163 -**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)** 164 - 165 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 166 - 167 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 168 - 169 - 170 170 In the PC, use below serial tool settings: 171 171 172 -* Baud: (% style="color:green" %)**9600**173 -* Data bits:** (% style="color:green" %)8(%%)**174 -* Stop bits: (% style="color:green" %)**1**175 -* Parity: (% style="color:green" %)**None**176 -* Flow Control: (% style="color:green" %)**None**131 +* Baud: **9600** 132 +* Data bits:** 8** 133 +* Stop bits: **1** 134 +* Parity: **None** 135 +* Flow Control: **None** 177 177 178 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%)to access AT Command input.137 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input. 179 179 180 -[[image:image-202209 13090720-1.png]]139 +[[image:image-20220907171221-8.png]] 181 181 141 +**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]] 182 182 183 - (% style="color:red" %)**Note:thevalid AT Commandscan befoundat: **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]143 +**2.2.4 Use CoAP protocol to uplink data** 184 184 145 +**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**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/]] 185 185 147 +**Use below commands:** 186 186 187 -=== 2.2.4 Use CoAP protocol to uplink data === 149 +* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 150 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 151 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 188 188 189 - 190 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)[[**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/]] 191 - 192 - 193 -(% style="color:blue" %)**Use below commands:** 194 - 195 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 196 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 197 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 198 - 199 199 For parameter description, please refer to AT command set 200 200 201 201 [[image:image-20220907171221-9.png]] 202 202 157 +After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 203 203 204 -After configure the server address and (% style="color:#037691" %)**reset the device**(%%) (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 205 - 206 206 [[image:image-20220907171221-10.png]] 207 207 161 +**2.2.5 Use UDP protocol to uplink data(Default protocol)** 208 208 209 - 210 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 211 - 212 - 213 213 This feature is supported since firmware version v1.0.1 214 214 215 -* (% style="color:#037691" %)**AT+PRO=2 **(%%)~/~/216 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601(%%)~/~/217 -* (% style="color:#037691" %)**AT+CFM=1 **(%%)~/~/165 +* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 166 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 167 +* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 218 218 219 219 [[image:image-20220907171221-11.png]] 220 220 221 - 222 222 [[image:image-20220907171221-12.png]] 223 223 224 224 225 225 175 +**2.2.6 Use MQTT protocol to uplink data** 226 226 227 -=== 2.2.6 Use MQTT protocol to uplink data === 228 - 229 - 230 230 This feature is supported since firmware version v110 231 231 232 -* (% style="color:#037691" %)**AT+PRO=3 **(%%)~/~/233 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 **(%%)~/~/234 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT **(%%)~/~/235 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/236 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/237 -* (% style="color:#037691" %)**AT+PUBTOPIC=PUB **(%%)~/~/238 -* (% style="color:#037691" %)**AT+SUBTOPIC=SUB **(%%)179 +* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 180 +* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 181 +* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 182 +* **AT+UNAME=UNAME **~/~/Set the username of MQTT 183 +* **AT+PWD=PWD **~/~/Set the password of MQTT 184 +* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 185 +* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 239 239 240 240 [[image:image-20220907171221-13.png]] 241 241 242 - 243 - 244 244 [[image:image-20220907171221-14.png]] 245 245 246 246 ... ... @@ -247,62 +247,49 @@ 247 247 248 248 MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 249 249 195 +**2.2.7 Use TCP protocol to uplink data** 250 250 251 - 252 -=== 2.2.7 Use TCP protocol to uplink data === 253 - 254 - 255 255 This feature is supported since firmware version v110 256 256 257 -* (% style="color:#037691" %)**AT+PRO=4 **(%%)~/~/258 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 **(%%)~/~/199 +* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 200 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 259 259 260 260 [[image:image-20220907171221-15.png]] 261 261 262 - 263 - 264 264 [[image:image-20220907171221-16.png]] 265 265 266 266 267 267 208 +**2.2.8 Change Update Interval** 268 268 269 -=== 2.2.8 Change Update Interval === 270 - 271 - 272 272 User can use below command to change the **uplink interval**. 273 273 274 -* (% style="color:#037691" %)**AT+TDC=7200 **(%%)~/~/ Set Update Interval to7200s(2 hour)212 +* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s 275 275 276 - (% style="color:red" %)**NOTE:By default, the device will send an uplink message every 2 hour. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**214 +**NOTE:** 277 277 216 +**~1. By default, the device will send an uplink message every 2 hour.** 278 278 218 +**2.3 Uplink Payload** 279 279 280 -== 2.3 Uplink Payload == 281 - 282 - 283 283 In this mode, uplink payload includes 87 bytes in total by default. 284 284 285 285 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. 286 286 224 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|1|2|2|2|4 225 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Soil PH|Time stamp ..... 287 287 288 -(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 289 -|(% style="width:96px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:42px" %)**2**|(% style="width:48px" %)**2**|(% style="width:124px" %)1|(% style="width:58px" %)1|(% style="width:82px" %)1|(% style="width:113px" %)2|(% style="width:134px" %)2|(% style="width:100px" %)4|(% style="width:137px" %)2|(% style="width:110px" %)2|(% style="width:122px" %)4 290 -|(% style="width:96px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:42px" %)Ver|(% style="width:48px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:58px" %)MOD|(% style="width:82px" %)Interrupt|(% style="width:113px" %)Leaf moisture|(% style="width:134px" %)Leaf Temperature|(% style="width:100px" %)Time stamp|(% style="width:137px" %)Leaf Temperature|(% style="width:110px" %)Leaf moisture|(% style="width:122px" %)Time stamp ..... 291 - 292 292 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 293 293 294 - 295 295 [[image:image-20220907171221-17.png]] 296 296 297 - 298 298 The payload is ASCII string, representative same HEX: 299 299 300 - **0x(% style="color:red" %)__f868411056754138__ (% style="color:blue" %)__0064__ (% style="color:green" %)__0c78__ (% style="color:#00b0f0" %)__17__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__00__ (% style="color:#a14d07" %)__0225__ (% style="color:#0020b0" %) __010b__ (% style="color:#420042" %)__6315537b__ (% style="color:#663300" %)//__010b0226631550fb__ __010e022663154d77__//(%%)**233 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where: 301 301 302 -where: 303 - 304 304 * Device ID: 0xf868411056754138 = f868411056754138 305 305 * Version: 0x0064=100=1.0.0 237 + 306 306 * BAT: 0x0c78 = 3192 mV = 3.192V 307 307 * Singal: 0x17 = 23 308 308 * Mod: 0x01 = 1 ... ... @@ -309,42 +309,32 @@ 309 309 * Interrupt: 0x00= 0 310 310 * Leaf moisture: 0x0225= 549 = 54.9% 311 311 * Leaf Temperature:0x010B =267=26.7 °C 312 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])244 +* Time stamp : 0x6315537b =1662342011 313 313 * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 314 314 * 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 315 315 248 +**2.4 Payload Explanation and Sensor Interface** 316 316 317 - ==2.4Payload Explanation and Sensor Interface==250 +**2.4.1 Device ID** 318 318 319 - 320 -=== 2.4.1 Device ID === 321 - 322 - 323 323 By default, the Device ID equal to the last 15 bits of IMEI. 324 324 325 -User can use (% style="color:#037691" %)**AT+DEUI**(%%)to set Device ID254 +User can use **AT+DEUI** to set Device ID 326 326 256 +**Example:** 327 327 328 -(% style="color:blue" %)**Example**: 329 - 330 330 AT+DEUI=868411056754138 331 331 332 332 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 333 333 262 +**2.4.2 Version Info** 334 334 335 - 336 -=== 2.4.2 Version Info === 337 - 338 - 339 339 Specify the software version: 0x64=100, means firmware version 1.00. 340 340 341 341 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 342 342 268 +**2.4.3 Battery Info** 343 343 344 - 345 -=== 2.4.3 Battery Info === 346 - 347 - 348 348 Check the battery voltage for NLMS01. 349 349 350 350 Ex1: 0x0B45 = 2885mV ... ... @@ -351,16 +351,12 @@ 351 351 352 352 Ex2: 0x0B49 = 2889mV 353 353 276 +**2.4.4 Signal Strength** 354 354 355 - 356 -=== 2.4.4 Signal Strength === 357 - 358 - 359 359 NB-IoT Network signal Strength. 360 360 280 +**Ex1: 0x1d = 29** 361 361 362 -(% style="color:blue" %)**Ex1: 0x1d = 29** 363 - 364 364 **0** -113dBm or less 365 365 366 366 **1** -111dBm ... ... @@ -371,49 +371,37 @@ 371 371 372 372 **99** Not known or not detectable 373 373 292 +**2.4.5 Leaf** moisture 374 374 294 +Get the moisture of the **Leaf**. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the **Leaf**. 375 375 376 - ===2.4.5Leaf moisture===296 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is 377 377 298 +**0229(H) = 549(D) /100 = 54.9.** 378 378 379 - Get the moisture of the (% style="color:#037691" %)**Leaf**(%%).Thevalue range of the register is 300-1000(Decimal), divide this value by 100 to get thepercentage of moisturein the Leaf.300 +**2.4.6 Leaf Temperature** 380 380 381 -For example, if the data you get from the register is (% style="color:#037691" %)**__0x050xDC__**(%%), the moisture content in the(% style="color:#037691" %)**Leaf**(%%)is302 +Get the temperature in the **Leaf**. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the **Leaf**. For example, if the data you get from the register is **__0x09 0xEC__**, the temperature content in the **Leaf **is 382 382 383 - (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**304 +**Example**: 384 384 306 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 385 385 308 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 386 386 387 - ===2.4.6LeafTemperature ===310 +**2.4.7 Timestamp** 388 388 389 - 390 -Get the temperature in the Leaf. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the Leaf. For example, if the data you get from the register is (% style="color:#037691" %)**__0x09 0xEC__**(%%), the temperature content in the (% style="color:#037691" %)**Leaf **(%%)is 391 - 392 -(% style="color:blue" %)**Example**: 393 - 394 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 395 - 396 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 397 - 398 - 399 - 400 -=== 2.4.7 Timestamp === 401 - 402 - 403 403 Time stamp : 0x6315537b =1662342011 404 404 405 405 Convert Unix timestamp to time 2022-9-5 9:40:11. 406 406 316 +**2.4.8 Digital Interrupt** 407 407 318 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server. 408 408 409 -=== 2.4.8 Digital Interrupt === 410 - 411 - 412 -Digital Interrupt refers to pin (% style="color:#037691" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server. 413 - 414 414 The command is: 415 415 416 - (% style="color:blue" %)**AT+INTMOD=3 **(%%)~/~/322 +**AT+INTMOD=3 ** ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 417 417 418 418 The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 419 419 ... ... @@ -423,34 +423,27 @@ 423 423 424 424 0x(01): Interrupt Uplink Packet. 425 425 332 +**2.4.9 +5V Output** 426 426 427 - 428 -=== 2.4.9 +5V Output === 429 - 430 - 431 431 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 432 432 433 433 The 5V output time can be controlled by AT Command. 434 434 435 - (% style="color:blue" %)**AT+5VT=1000**338 +**AT+5VT=1000** 436 436 437 437 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 438 438 439 439 343 +**2.5 Downlink Payload** 440 440 441 -== 2.5 Downlink Payload == 442 - 443 - 444 444 By default, NLMS01 prints the downlink payload to console port. 445 445 446 446 [[image:image-20220907171221-18.png]] 447 447 349 +**Examples:** 448 448 449 - (%style="color:blue" %)**Examples:**351 +* **Set TDC** 450 450 451 - 452 -* (% style="color:#037691" %)**Set TDC** 453 - 454 454 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 455 455 456 456 Payload: 01 00 00 1E TDC=30S ... ... @@ -457,23 +457,16 @@ 457 457 458 458 Payload: 01 00 00 3C TDC=60S 459 459 359 +* **Reset** 460 460 461 - 462 -* (% style="color:#037691" %)**Reset** 463 - 464 464 If payload = 0x04FF, it will reset the NLMS01 465 465 363 +* **INTMOD** 466 466 467 - 468 -* (% style="color:#037691" %)**INTMOD** 469 - 470 470 Downlink Payload: 06000003, Set AT+INTMOD=3 471 471 367 +**2.6 LED Indicator** 472 472 473 - 474 -== 2.6 LED Indicator == 475 - 476 - 477 477 The NLMS01 has an internal LED which is to show the status of different state. 478 478 479 479 * When power on, NLMS01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) ... ... @@ -481,24 +481,18 @@ 481 481 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 482 482 * For each uplink probe, LED will be on for 500ms. 483 483 376 +**2.7 Installation** 484 484 485 -== 2.7 Installation == 486 - 487 - 488 488 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. 489 489 490 - 491 491 [[image:image-20220907171221-19.png]] 492 492 382 +**2.8 Moisture and Temperature alarm function** 493 493 384 +➢ AT Command: 494 494 495 - ==2.8Moistureand Temperature alarm function==386 +AT+ HUMALARM =min,max 496 496 497 - 498 -(% style="color:blue" %)**➢ AT Command:** 499 - 500 -(% style="color:#037691" %)**AT+ HUMALARM =min,max** 501 - 502 502 ² When min=0, and max≠0, Alarm higher than max 503 503 504 504 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -505,9 +505,8 @@ 505 505 506 506 ² When min≠0 and max≠0, Alarm higher than max or lower than min 507 507 394 +Example: 508 508 509 -(% style="color:blue" %)**Example:** 510 - 511 511 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 512 512 513 513 AT+ TEMPALARM=min,max ... ... @@ -518,54 +518,42 @@ 518 518 519 519 ² When min≠0 and max≠0, Alarm higher than max or lower than min 520 520 406 +Example: 521 521 522 -(% style="color:blue" %)**Example:** 523 - 524 524 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 525 525 526 526 411 +**2.9 Set the number of data to be uploaded and the recording time** 527 527 528 - ==2.9Set the numberof data to be uploaded andthe recording time ==413 +➢ AT Command: 529 529 415 +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) 530 530 531 -(% style="color:blue" %)**➢ AT Command:** 532 532 533 -* (% 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) 534 -* (% 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. 418 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 535 535 420 +**2.10 Read or Clear cached data** 536 536 537 - Thislink explains the relationship betweenTR,NOUD and TDCmore clearly.422 +➢ AT Command: 538 538 539 - [[https:~~/~~/www.processon.com/view/link/6340e606e401fd390891af87>>https://www.processon.com/view/link/6340e606e401fd390891af87]]424 +AT+CDP ~/~/ Read cached data 540 540 541 - 542 -== 2.10 Read or Clear cached data == 543 - 544 - 545 -(% style="color:blue" %)**➢ AT Command:** 546 - 547 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 548 -* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 549 - 550 550 [[image:image-20220907171221-20.png]] 551 551 552 552 429 +AT+CDP=0 ~/~/ Clear cached data 553 553 554 -== 2.11 Firmware Change Log == 555 555 432 +**2.8 Firmware Change Log** 556 556 557 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/ qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]434 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 558 558 559 -Upgrade Instruction: [[Upgrade Firmware>> ||anchor="H5.1200BHowtoUpgradeFirmware"]]436 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 560 560 438 +**2.9 Battery Analysis** 561 561 440 +**2.9.1 Battery Type** 562 562 563 -== 2.12 Battery Analysis == 564 - 565 - 566 -=== 2.12.1 Battery Type === 567 - 568 - 569 569 The NLMS01 battery 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. 570 570 571 571 The battery is designed to last for several years depends on the actually use environment and update interval. ... ... @@ -578,18 +578,15 @@ 578 578 579 579 [[image:image-20220907171221-21.png]] 580 580 454 +**2.9.2 Power consumption Analyze** 581 581 582 - 583 -=== 2.12.2 Power consumption Analyze === 584 - 585 - 586 586 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. 587 587 588 588 Instruction to use as below: 589 589 590 - (% 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/]]460 +**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/]] 591 591 592 - (% style="color:blue" %)**Step 2: **(%%)Open it and choose462 +**Step 2: ** Open it and choose 593 593 594 594 * Product Model 595 595 * Uplink Interval ... ... @@ -599,171 +599,131 @@ 599 599 600 600 [[image:image-20220907171221-22.jpeg]] 601 601 472 +**2.9.3 Battery Note** 602 602 603 -=== 2.12.3 Battery Note === 604 - 605 - 606 606 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. 607 607 476 +**2.9.4 Replace the battery** 608 608 609 - 610 -=== 2.12.4 Replace the battery === 611 - 612 - 613 613 The default battery pack of NLMS01 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). 614 614 480 +**3. Access NB-IoT Module** 615 615 616 - 617 -= 3. Access NB-IoT Module = 618 - 619 - 620 620 Users can directly access the AT command set of the NB-IoT module. 621 621 622 622 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/]] 623 623 624 - 625 625 [[image:image-20220907171221-23.png]] 626 626 488 +**4. Using the AT Commands** 627 627 490 +**4.1 Access AT Commands** 628 628 629 -= 4. Using the AT Commands = 630 - 631 - 632 -== 4.1 Access AT Commands == 633 - 634 - 635 635 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]] 636 636 637 -AT+<CMD>? : 494 +AT+<CMD>? : Help on <CMD> 638 638 639 -AT+<CMD> :Run <CMD>496 +AT+<CMD> : Run <CMD> 640 640 641 -AT+<CMD>=<value>: 498 +AT+<CMD>=<value> : Set the value 642 642 643 -AT+<CMD>=? :Get the value500 +AT+<CMD>=? : Get the value 644 644 502 +**General Commands** 645 645 646 - (%style="color:#037691"%)**General Commands**504 +AT : Attention 647 647 648 -AT :Attention506 +AT? : Short Help 649 649 650 -AT ?:ShortHelp508 +ATZ : MCU Reset 651 651 652 -AT Z:MCUReset510 +AT+TDC : Application Data Transmission Interval 653 653 654 -AT+ TDC :ApplicationDataTransmissionInterval512 +AT+CFG : Print all configurations 655 655 656 -AT+CFG Printallconfigurations514 +AT+CFGMOD : Working mode selection 657 657 658 -AT+ CFGMOD :Workingmodeselection516 +AT+INTMOD : Set the trigger interrupt mode 659 659 660 -AT+ INTMOD:Set the triggerinterruptmode518 +AT+5VT : Set extend the time of 5V power 661 661 662 -AT+ 5VT:Setextendthetimeof5Vpower520 +AT+PRO : Choose agreement 663 663 664 -AT+ PRO:Choose agreement522 +AT+RXDL : Extend the sending and receiving time 665 665 666 -AT+R XDL:Extendthesendingandreceivingtime524 +AT+SERVADDR : Server Address 667 667 668 -AT+ SERVADDR:verAddress526 +AT+TR : Get or Set record time" 669 669 670 -AT+APN : Get or set the APN 671 671 672 -AT+ FBAND :whetherto automaticallymodifythefrequency band529 +AT+NOUD : Get or Set the number of data to be uploaded 673 673 674 -AT+DNSCFG : Get or Set DNS Server 675 675 676 -AT+ GETSENSORVALUE: Returnsthe current sensormeasurement532 +AT+CDP : Read or Clear cached data 677 677 678 -AT+TR : Get or Set record time" 679 679 680 -AT+ NOUD:the number ofdata to beuploaded535 +AT+TEMPALARM : Get or Set alarm of temp 681 681 682 -AT+ CDP:ReadorClearcacheddata537 +AT+HUMALARM : Get or Set alarm of PH 683 683 684 -AT+TEMPALARM : Get or Set alarm of temp 685 685 686 -A T+HUMALARM: Get or Setalarmof humidity540 +**COAP Management** 687 687 542 +AT+URI : Resource parameters 688 688 689 - (% style="color:#037691" %)**COAP Management**544 +**UDP Management** 690 690 691 -AT+ URI:Resourceparameters546 +AT+CFM : Upload confirmation mode (only valid for UDP) 692 692 548 +**MQTT Management** 693 693 694 - (%style="color:#037691"%)**UDPManagement**550 +AT+CLIENT : Get or Set MQTT client 695 695 696 -AT+ CFM:Uploadconfirmationmode(onlyvalidfor UDP)552 +AT+UNAME : Get or Set MQTT Username 697 697 554 +AT+PWD : Get or Set MQTT password 698 698 699 - (%style="color:#037691"%)**MQTTManagement**556 +AT+PUBTOPIC : Get or Set MQTT publish topic 700 700 701 -AT+ CLIENT:Get or Set MQTT client558 +AT+SUBTOPIC : Get or Set MQTT subscription topic 702 702 703 - AT+UNAME : GetorSetMQTT Username560 +**Information** 704 704 705 -AT+ PWD:GetorSetMQTTpassword562 +AT+FDR : Factory Data Reset 706 706 707 -AT+P UBTOPIC:GetorSetMQTTpublishtopic564 +AT+PWORD : Serial Access Password 708 708 709 - AT+SUBTOPIC :Get or Set MQTT subscription topic566 +**5. FAQ** 710 710 568 +**5.1 How to Upgrade Firmware** 711 711 712 -(% style="color:#037691" %)**Information** 713 - 714 -AT+FDR : Factory Data Reset 715 - 716 -AT+PWORD : Serial Access Password 717 - 718 - 719 - 720 -= 5. FAQ = 721 - 722 - 723 -== 5.1 How to Upgrade Firmware == 724 - 725 - 726 726 User can upgrade the firmware for 1) bug fix, 2) new feature release. 727 727 728 728 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]] 729 729 574 +**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.** 730 730 731 - (% style="color:red" %)**Notice,NLMS01and LLMS01 share the same motherboard. Theyuse the same connectionand method to update.**576 +**6. Trouble Shooting** 732 732 578 +**6.1 Connection problem when uploading firmware** 733 733 734 - 735 -= 6. Trouble Shooting = 736 - 737 - 738 -== 6.1 Connection problem when uploading firmware == 739 - 740 - 741 741 **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]] 742 742 582 +**6.2 AT Command input doesn't work** 743 743 584 +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. 744 744 745 - == 6.2ATCommandinput doesn't work==586 +**7. Order Info** 746 746 747 - 748 -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. 749 - 750 - 751 - 752 -= 7. Order Info = 753 - 754 - 755 755 Part Number**:** NLMS01 756 756 590 +**8. Packing Info** 757 757 592 +**Package Includes**: 758 758 759 -= 8. Packing Info = 760 - 761 - 762 -(% style="color:#037691" %)**Package Includes:** 763 - 764 764 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 765 765 766 - (% style="color:#037691" %)**Dimension and weight**:596 +**Dimension and weight**: 767 767 768 768 * Device Size: cm 769 769 * Device Weight: g ... ... @@ -771,10 +771,11 @@ 771 771 * Weight / pcs : g 772 772 773 773 774 - =9. Support=604 +**9. Support** 775 775 776 - 777 777 * 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. 778 778 * 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]] 779 779 780 780 610 + 611 +
- image-20220913090720-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -224.9 KB - Content