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