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