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