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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - 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,13 +71,11 @@ 71 71 * - B20 @H-FDD: 800MHz 72 72 * - B28 @H-FDD: 700MHz 73 73 56 +**1.4 Probe Specification** 74 74 75 75 76 - ==1.4 ProbeSpecification==59 +**Leaf Moisture: percentage of water drop over total leaf surface** 77 77 78 - 79 -(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface** 80 - 81 81 * Range 0-100% 82 82 * Resolution: 0.1% 83 83 * Accuracy: ±3%(0-50%);±6%(>50%) ... ... @@ -84,9 +84,8 @@ 84 84 * IP67 Protection 85 85 * Length: 3.5 meters 86 86 67 +**Leaf Temperature:** 87 87 88 -(% style="color:#037691" %)**Leaf Temperature:** 89 - 90 90 * Range -50℃~80℃ 91 91 * Resolution: 0.1℃ 92 92 * Accuracy: <±0.5℃(-10℃~70℃),<±1.0℃ (others) ... ... @@ -93,44 +93,30 @@ 93 93 * IP67 Protection 94 94 * Length: 3.5 meters 95 95 75 +**~ 1.5 Applications** 96 96 97 - 98 -== 1.5 Applications == 99 - 100 - 101 101 * Smart Agriculture 102 102 79 +**1.6 Pin mapping and power on** 103 103 104 - 105 -== 1.6 Pin mapping and power on == 106 - 107 - 108 108 [[image:image-20220907171221-4.png]] 109 109 110 110 **~ ** 111 111 85 +**2. Use NLMS01 to communicate with IoT Server** 112 112 113 - =2.Use NLMS01 tocommunicatewith IoT Server =87 +**2.1 How it works** 114 114 115 - 116 -== 2.1 How it works == 117 - 118 - 119 119 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. 120 120 121 121 The diagram below shows the working flow in default firmware of NLMS01: 122 122 123 - 124 124 [[image:image-20220907171221-5.png]] 125 125 95 +**2.2 Configure the NLMS01** 126 126 97 +**2.2.1 Test Requirement** 127 127 128 -== 2.2 Configure the NLMS01 == 129 - 130 - 131 -=== 2.2.1 Test Requirement === 132 - 133 - 134 134 To use NLMS01 in your city, make sure meet below requirements: 135 135 136 136 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -137,116 +137,90 @@ 137 137 * The local NB-IoT network used the band that NLMS01 supports. 138 138 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 139 139 140 -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 141 141 142 - 143 143 [[image:image-20220907171221-6.png]] 144 144 109 +**2.2.2 Insert SIM card** 145 145 146 - 147 -=== 2.2.2 Insert SIM card === 148 - 149 - 150 150 Insert the NB-IoT Card get from your provider. 151 151 152 152 User need to take out the NB-IoT module and insert the SIM card like below: 153 153 154 - 155 155 [[image:image-20220907171221-7.png]] 156 156 117 +**2.2.3 Connect USB – TTL to NLMS01 to configure it** 157 157 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. 158 158 159 - === 2.2.3ConnectUSB – TTL toNLMS01 to configure it ===121 +**Connection:** 160 160 123 + USB TTL GND <~-~-~-~-> GND 161 161 162 - 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 163 163 127 + USB TTL RXD <~-~-~-~-> UART_TXD 164 164 165 -(% style="color:blue" %)**Connection:** 166 - 167 -**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)** 168 - 169 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 170 - 171 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 172 - 173 - 174 174 In the PC, use below serial tool settings: 175 175 176 -* Baud: (% style="color:green" %)**9600**177 -* Data bits:** (% style="color:green" %)8(%%)**178 -* Stop bits: (% style="color:green" %)**1**179 -* Parity: (% style="color:green" %)**None**180 -* Flow Control: (% style="color:green" %)**None**131 +* Baud: **9600** 132 +* Data bits:** 8** 133 +* Stop bits: **1** 134 +* Parity: **None** 135 +* Flow Control: **None** 181 181 182 -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. 183 183 184 -[[image:image-202209 13090720-1.png]]139 +[[image:image-20220907171221-8.png]] 185 185 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]] 186 186 187 - (% 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** 188 188 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/]] 189 189 147 +**Use below commands:** 190 190 191 -=== 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 192 192 193 - 194 -(% 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/]] 195 - 196 - 197 -(% style="color:blue" %)**Use below commands:** 198 - 199 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 200 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 201 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 202 - 203 203 For parameter description, please refer to AT command set 204 204 205 205 [[image:image-20220907171221-9.png]] 206 206 157 +After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 207 207 208 -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. 209 - 210 210 [[image:image-20220907171221-10.png]] 211 211 161 +**2.2.5 Use UDP protocol to uplink data(Default protocol)** 212 212 213 - 214 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 215 - 216 - 217 217 This feature is supported since firmware version v1.0.1 218 218 219 -* (% style="color:#037691" %)**AT+PRO=2 **(%%)~/~/220 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601(%%)~/~/221 -* (% 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 222 222 223 - 224 224 [[image:image-20220907171221-11.png]] 225 225 226 - 227 227 [[image:image-20220907171221-12.png]] 228 228 229 229 230 230 175 +**2.2.6 Use MQTT protocol to uplink data** 231 231 232 -=== 2.2.6 Use MQTT protocol to uplink data === 233 - 234 - 235 235 This feature is supported since firmware version v110 236 236 237 -* (% style="color:#037691" %)**AT+PRO=3 **(%%)~/~/238 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 **(%%)~/~/239 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT **(%%)~/~/240 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/241 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/242 -* (% style="color:#037691" %)**AT+PUBTOPIC=PUB **(%%)~/~/243 -* (% 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 244 244 245 - 246 246 [[image:image-20220907171221-13.png]] 247 247 248 - 249 - 250 250 [[image:image-20220907171221-14.png]] 251 251 252 252 ... ... @@ -253,105 +253,81 @@ 253 253 254 254 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. 255 255 195 +**2.2.7 Use TCP protocol to uplink data** 256 256 257 - 258 -=== 2.2.7 Use TCP protocol to uplink data === 259 - 260 - 261 261 This feature is supported since firmware version v110 262 262 263 -* (% style="color:#037691" %)**AT+PRO=4 **(%%)~/~/264 -* (% 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 265 265 266 - 267 267 [[image:image-20220907171221-15.png]] 268 268 269 - 270 - 271 271 [[image:image-20220907171221-16.png]] 272 272 273 273 274 274 208 +**2.2.8 Change Update Interval** 275 275 276 -=== 2.2.8 Change Update Interval === 277 - 278 - 279 279 User can use below command to change the **uplink interval**. 280 280 281 -* (% style="color:#037691" %)**AT+TDC=7200 **(%%)~/~/ Set Update Interval to7200s(2 hour)212 +* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s 282 282 214 +**NOTE:** 283 283 284 - (% 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).**216 +**~1. By default, the device will send an uplink message every 2 hour.** 285 285 218 +**2.3 Uplink Payload** 286 286 287 - 288 -== 2.3 Uplink Payload == 289 - 290 - 291 291 In this mode, uplink payload includes 87 bytes in total by default. 292 292 293 293 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. 294 294 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 ..... 295 295 296 -(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 297 -|(% 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 298 -|(% 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 ..... 299 - 300 300 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 301 301 302 - 303 303 [[image:image-20220907171221-17.png]] 304 304 305 - 306 306 The payload is ASCII string, representative same HEX: 307 307 308 -0x (% style="color:red" %)f868411056754138(% style="color:blue" %)0064(% style="color:green" %)0c78(% style="color:red" %)17(% style="color:blue" %)01(% style="color:green" %)00(% style="color:blue" %)**0225010b6315537b**010b0226631550fb**010e022663154d77**01110225631549f1**011502246315466b**01190223631542e5**011d022163153f62**011e022163153bde**011e022163153859**(%%)****where:233 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where: 309 309 310 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 311 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0 312 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V 313 -* (% style="color:red" %)Singal: 0x17 = 23 314 -* (% style="color:blue" %)Mod: 0x01 = 1 315 -* (% style="color:green" %)Interrupt: 0x00= 0 235 +* Device ID: 0xf868411056754138 = f868411056754138 236 +* Version: 0x0064=100=1.0.0 237 + 238 +* BAT: 0x0c78 = 3192 mV = 3.192V 239 +* Singal: 0x17 = 23 240 +* Mod: 0x01 = 1 241 +* Interrupt: 0x00= 0 316 316 * Leaf moisture: 0x0225= 549 = 54.9% 317 317 * Leaf Temperature:0x010B =267=26.7 °C 318 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])244 +* Time stamp : 0x6315537b =1662342011 319 319 * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 320 -* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......246 +* 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 321 321 248 +**2.4 Payload Explanation and Sensor Interface** 322 322 250 +**2.4.1 Device ID** 323 323 324 -== 2.4 Payload Explanation and Sensor Interface == 325 - 326 - 327 -=== 2.4.1 Device ID === 328 - 329 - 330 330 By default, the Device ID equal to the last 15 bits of IMEI. 331 331 332 -User can use (% style="color:#037691" %)**AT+DEUI**(%%)to set Device ID254 +User can use **AT+DEUI** to set Device ID 333 333 256 +**Example:** 334 334 335 -(% style="color:blue" %)**Example**: 336 - 337 337 AT+DEUI=868411056754138 338 338 339 339 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 340 340 262 +**2.4.2 Version Info** 341 341 342 - 343 -=== 2.4.2 Version Info === 344 - 345 - 346 346 Specify the software version: 0x64=100, means firmware version 1.00. 347 347 348 348 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 349 349 268 +**2.4.3 Battery Info** 350 350 351 - 352 -=== 2.4.3 Battery Info === 353 - 354 - 355 355 Check the battery voltage for NLMS01. 356 356 357 357 Ex1: 0x0B45 = 2885mV ... ... @@ -358,16 +358,12 @@ 358 358 359 359 Ex2: 0x0B49 = 2889mV 360 360 276 +**2.4.4 Signal Strength** 361 361 362 - 363 -=== 2.4.4 Signal Strength === 364 - 365 - 366 366 NB-IoT Network signal Strength. 367 367 280 +**Ex1: 0x1d = 29** 368 368 369 -(% style="color:blue" %)**Ex1: 0x1d = 29** 370 - 371 371 **0** -113dBm or less 372 372 373 373 **1** -111dBm ... ... @@ -378,49 +378,37 @@ 378 378 379 379 **99** Not known or not detectable 380 380 292 +**2.4.5 Leaf** moisture 381 381 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**. 382 382 383 - ===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 384 384 298 +**0229(H) = 549(D) /100 = 54.9.** 385 385 386 - 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** 387 387 388 -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 389 389 390 - (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**304 +**Example**: 391 391 306 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 392 392 308 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 393 393 394 - ===2.4.6LeafTemperature ===310 +**2.4.7 Timestamp** 395 395 396 - 397 -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 398 - 399 -(% style="color:blue" %)**Example**: 400 - 401 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 402 - 403 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 404 - 405 - 406 - 407 -=== 2.4.7 Timestamp === 408 - 409 - 410 410 Time stamp : 0x6315537b =1662342011 411 411 412 412 Convert Unix timestamp to time 2022-9-5 9:40:11. 413 413 316 +**2.4.8 Digital Interrupt** 414 414 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. 415 415 416 -=== 2.4.8 Digital Interrupt === 417 - 418 - 419 -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. 420 - 421 421 The command is: 422 422 423 - (% 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]])**.** 424 424 425 425 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. 426 426 ... ... @@ -430,34 +430,27 @@ 430 430 431 431 0x(01): Interrupt Uplink Packet. 432 432 332 +**2.4.9 +5V Output** 433 433 434 - 435 -=== 2.4.9 +5V Output === 436 - 437 - 438 438 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 439 439 440 440 The 5V output time can be controlled by AT Command. 441 441 442 - (% style="color:blue" %)**AT+5VT=1000**338 +**AT+5VT=1000** 443 443 444 444 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 445 445 446 446 343 +**2.5 Downlink Payload** 447 447 448 -== 2.5 Downlink Payload == 449 - 450 - 451 451 By default, NLMS01 prints the downlink payload to console port. 452 452 453 453 [[image:image-20220907171221-18.png]] 454 454 349 +**Examples:** 455 455 456 - (%style="color:blue" %)**Examples:**351 +* **Set TDC** 457 457 458 - 459 -* (% style="color:#037691" %)**Set TDC** 460 - 461 461 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 462 462 463 463 Payload: 01 00 00 1E TDC=30S ... ... @@ -464,23 +464,16 @@ 464 464 465 465 Payload: 01 00 00 3C TDC=60S 466 466 359 +* **Reset** 467 467 468 - 469 -* (% style="color:#037691" %)**Reset** 470 - 471 471 If payload = 0x04FF, it will reset the NLMS01 472 472 363 +* **INTMOD** 473 473 474 - 475 -* (% style="color:#037691" %)**INTMOD** 476 - 477 477 Downlink Payload: 06000003, Set AT+INTMOD=3 478 478 367 +**2.6 LED Indicator** 479 479 480 - 481 -== 2.6 LED Indicator == 482 - 483 - 484 484 The NLMS01 has an internal LED which is to show the status of different state. 485 485 486 486 * 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) ... ... @@ -488,25 +488,18 @@ 488 488 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 489 489 * For each uplink probe, LED will be on for 500ms. 490 490 376 +**2.7 Installation** 491 491 492 - 493 -== 2.7 Installation == 494 - 495 - 496 496 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. 497 497 498 - 499 499 [[image:image-20220907171221-19.png]] 500 500 382 +**2.8 Moisture and Temperature alarm function** 501 501 384 +➢ AT Command: 502 502 503 - ==2.8Moistureand Temperature alarm function==386 +AT+ HUMALARM =min,max 504 504 505 - 506 -(% style="color:blue" %)**➢ AT Command:** 507 - 508 -(% style="color:#037691" %)**AT+ HUMALARM =min,max** 509 - 510 510 ² When min=0, and max≠0, Alarm higher than max 511 511 512 512 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -513,9 +513,8 @@ 513 513 514 514 ² When min≠0 and max≠0, Alarm higher than max or lower than min 515 515 394 +Example: 516 516 517 -(% style="color:blue" %)**Example:** 518 - 519 519 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 520 520 521 521 AT+ TEMPALARM=min,max ... ... @@ -526,51 +526,42 @@ 526 526 527 527 ² When min≠0 and max≠0, Alarm higher than max or lower than min 528 528 406 +Example: 529 529 530 -(% style="color:blue" %)**Example:** 531 - 532 532 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 533 533 534 534 411 +**2.9 Set the number of data to be uploaded and the recording time** 535 535 536 - ==2.9Set the numberof data to be uploaded andthe recording time ==413 +➢ AT Command: 537 537 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) 538 538 539 -(% style="color:blue" %)**➢ AT Command:** 540 540 541 -* (% 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) 542 -* (% 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. 543 543 420 +**2.10 Read or Clear cached data** 544 544 422 +➢ AT Command: 545 545 546 - == 2.10Reador Clearcached data==424 +AT+CDP ~/~/ Read cached data 547 547 548 - 549 -(% style="color:blue" %)**➢ AT Command:** 550 - 551 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 552 -* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 553 - 554 - 555 555 [[image:image-20220907171221-20.png]] 556 556 557 557 429 +AT+CDP=0 ~/~/ Clear cached data 558 558 559 -== 2.11 Firmware Change Log == 560 560 432 +**2.8 Firmware Change Log** 561 561 562 -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]] 563 563 564 -Upgrade Instruction: [[Upgrade Firmware>> ||anchor="H5.1200BHowtoUpgradeFirmware"]]436 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 565 565 438 +**2.9 Battery Analysis** 566 566 440 +**2.9.1 Battery Type** 567 567 568 -== 2.12 Battery Analysis == 569 - 570 - 571 -=== 2.12.1 Battery Type === 572 - 573 - 574 574 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. 575 575 576 576 The battery is designed to last for several years depends on the actually use environment and update interval. ... ... @@ -583,18 +583,15 @@ 583 583 584 584 [[image:image-20220907171221-21.png]] 585 585 454 +**2.9.2 Power consumption Analyze** 586 586 587 - 588 -=== 2.12.2 Power consumption Analyze === 589 - 590 - 591 591 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. 592 592 593 593 Instruction to use as below: 594 594 595 - (% 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/]] 596 596 597 - (% style="color:blue" %)**Step 2: **(%%)Open it and choose462 +**Step 2: ** Open it and choose 598 598 599 599 * Product Model 600 600 * Uplink Interval ... ... @@ -604,39 +604,26 @@ 604 604 605 605 [[image:image-20220907171221-22.jpeg]] 606 606 472 +**2.9.3 Battery Note** 607 607 608 -=== 2.12.3 Battery Note === 609 - 610 - 611 611 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. 612 612 476 +**2.9.4 Replace the battery** 613 613 614 - 615 -=== 2.12.4 Replace the battery === 616 - 617 - 618 618 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). 619 619 480 +**3. Access NB-IoT Module** 620 620 621 - 622 -= 3. Access NB-IoT Module = 623 - 624 - 625 625 Users can directly access the AT command set of the NB-IoT module. 626 626 627 627 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/]] 628 628 629 - 630 630 [[image:image-20220907171221-23.png]] 631 631 488 +**4. Using the AT Commands** 632 632 490 +**4.1 Access AT Commands** 633 633 634 -= 4. Using the AT Commands = 635 - 636 - 637 -== 4.1 Access AT Commands == 638 - 639 - 640 640 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]] 641 641 642 642 AT+<CMD>? : Help on <CMD> ... ... @@ -647,9 +647,8 @@ 647 647 648 648 AT+<CMD>=? : Get the value 649 649 502 +**General Commands** 650 650 651 -(% style="color:#037691" %)**General Commands** 652 - 653 653 AT : Attention 654 654 655 655 AT? : Short Help ... ... @@ -672,37 +672,30 @@ 672 672 673 673 AT+SERVADDR : Server Address 674 674 675 -AT+APN : Get or set the APN 676 - 677 -AT+FBAND : Get or Set whether to automatically modify the frequency band 678 - 679 -AT+DNSCFG : Get or Set DNS Server 680 - 681 -AT+GETSENSORVALUE : Returns the current sensor measurement 682 - 683 683 AT+TR : Get or Set record time" 684 684 528 + 685 685 AT+NOUD : Get or Set the number of data to be uploaded 686 686 531 + 687 687 AT+CDP : Read or Clear cached data 688 688 534 + 689 689 AT+TEMPALARM : Get or Set alarm of temp 690 690 691 691 AT+HUMALARM : Get or Set alarm of PH 692 692 693 693 694 - (% style="color:#037691" %)**COAP Management**540 +**COAP Management** 695 695 696 696 AT+URI : Resource parameters 697 697 544 +**UDP Management** 698 698 699 -(% style="color:#037691" %)**UDP Management** 700 - 701 701 AT+CFM : Upload confirmation mode (only valid for UDP) 702 702 548 +**MQTT Management** 703 703 704 -(% style="color:#037691" %)**MQTT Management** 705 - 706 706 AT+CLIENT : Get or Set MQTT client 707 707 708 708 AT+UNAME : Get or Set MQTT Username ... ... @@ -713,62 +713,43 @@ 713 713 714 714 AT+SUBTOPIC : Get or Set MQTT subscription topic 715 715 560 +**Information** 716 716 717 -(% style="color:#037691" %)**Information** 718 - 719 719 AT+FDR : Factory Data Reset 720 720 721 721 AT+PWORD : Serial Access Password 722 722 566 +**5. FAQ** 723 723 568 +**5.1 How to Upgrade Firmware** 724 724 725 -= 5. FAQ = 726 - 727 - 728 -== 5.1 How to Upgrade Firmware == 729 - 730 - 731 731 User can upgrade the firmware for 1) bug fix, 2) new feature release. 732 732 733 733 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]] 734 734 574 +**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.** 735 735 736 - (% style="color:red" %)**Notice,NLMS01and LLMS01 share the same motherboard. Theyuse the same connectionand method to update.**576 +**6. Trouble Shooting** 737 737 578 +**6.1 Connection problem when uploading firmware** 738 738 739 - 740 -= 6. Trouble Shooting = 741 - 742 - 743 -== 6.1 Connection problem when uploading firmware == 744 - 745 - 746 746 **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]] 747 747 582 +**6.2 AT Command input doesn't work** 748 748 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. 749 749 750 - == 6.2ATCommandinput doesn't work==586 +**7. Order Info** 751 751 752 - 753 -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. 754 - 755 - 756 - 757 -= 7. Order Info = 758 - 759 - 760 760 Part Number**:** NLMS01 761 761 590 +**8. Packing Info** 762 762 592 +**Package Includes**: 763 763 764 -= 8. Packing Info = 765 - 766 - 767 -(% style="color:#037691" %)**Package Includes:** 768 - 769 769 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 770 770 771 - (% style="color:#037691" %)**Dimension and weight**:596 +**Dimension and weight**: 772 772 773 773 * Device Size: cm 774 774 * Device Weight: g ... ... @@ -776,10 +776,11 @@ 776 776 * Weight / pcs : g 777 777 778 778 779 - =9. Support=604 +**9. Support** 780 780 781 - 782 782 * 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. 783 783 * 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]] 784 784 785 785 610 + 611 +
- image-20220913090720-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -224.9 KB - Content