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, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -7,76 +7,62 @@ 7 7 8 8 9 9 10 -= 1. Introduction = 10 += 1. Introduction = 11 11 12 -== 1.1 What is NLMS01 Leaf Moisture Sensor == 13 13 13 +== 1.1 What is NLMS01 Leaf Moisture Sensor == 14 14 15 -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. 16 16 17 -NLMS01 detectsleaf's**moistureand temperature **useFDR method,itsensesthedielectricconstantcauseby liquid overtheleafsurface,and coverthevalueto leaf moisture.Theprobeis design inaleafshapetobestsimulatetherealleafcharacterizes.Theprobehasasdensityas15leaf veinlinesper centimeterwhich makeit cansensessmall drop andmore accuracy.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. 18 18 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 + 19 19 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. 20 -\\NLMS01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 21 -\\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) 22 -\\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 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. 23 23 25 + 24 24 [[image:image-20220907171221-2.png]] 25 25 28 + 26 26 [[image:image-20220907171221-3.png]] 27 27 28 -== 1.2 Features == 29 29 30 -* ((( 31 -NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 32 -))) 33 -* ((( 34 -Monitor Leaf moisture 35 -))) 36 36 37 -* ((( 38 - Monitor Leaf temperature 39 -))) 33 +== 1.2 Features == 40 40 41 -* ((( 42 -Moisture and Temperature alarm function 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 + 54 + 43 43 ))) 44 -* ((( 45 -Monitor Battery Level 46 -))) 47 -* ((( 48 -Uplink on periodically 49 -))) 50 -* ((( 51 -Downlink to change configure 52 -))) 53 -* ((( 54 -IP66 Waterproof Enclosure 55 -))) 56 -* ((( 57 -IP67 rate for the Sensor Probe 58 -))) 59 -* ((( 60 -Ultra-Low Power consumption 61 -))) 62 -* ((( 63 -AT Commands to change parameters 64 -))) 65 -* ((( 66 -Micro SIM card slot for NB-IoT SIM 67 -))) 68 -* ((( 69 -8500mAh Battery for long term use 70 -))) 71 71 72 72 == 1.3 Specification == 73 73 74 -**Common DC Characteristics:** 75 75 60 +(% style="color:#037691" %)**Common DC Characteristics:** 61 + 76 76 * Supply Voltage: 2.1v ~~ 3.6v 77 77 * Operating Temperature: -40 ~~ 85°C 78 78 79 -**NB-IoT Spec:** 65 +(% style="color:#037691" %)**NB-IoT Spec:** 80 80 81 81 * - B1 @H-FDD: 2100MHz 82 82 * - B3 @H-FDD: 1800MHz ... ... @@ -85,10 +85,10 @@ 85 85 * - B20 @H-FDD: 800MHz 86 86 * - B28 @H-FDD: 700MHz 87 87 88 -== 1.4 Probe Specification == 74 +== 1.4 Probe Specification == 89 89 90 90 91 -**Leaf Moisture: percentage of water drop over total leaf surface** 77 +(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface** 92 92 93 93 * Range 0-100% 94 94 * Resolution: 0.1% ... ... @@ -96,7 +96,7 @@ 96 96 * IP67 Protection 97 97 * Length: 3.5 meters 98 98 99 -**Leaf Temperature:** 85 +(% style="color:#037691" %)**Leaf Temperature:** 100 100 101 101 * Range -50℃~80℃ 102 102 * Resolution: 0.1℃ ... ... @@ -104,30 +104,40 @@ 104 104 * IP67 Protection 105 105 * Length: 3.5 meters 106 106 107 -== 1.5 Applications == 93 +== 1.5 Applications == 108 108 95 + 109 109 * Smart Agriculture 110 110 111 -== 1.6 Pin mapping and power on == 98 +== 1.6 Pin mapping and power on == 112 112 100 + 113 113 [[image:image-20220907171221-4.png]] 114 114 115 115 **~ ** 116 116 105 + 117 117 = 2. Use NLMS01 to communicate with IoT Server = 118 118 108 + 119 119 == 2.1 How it works == 120 120 111 + 121 121 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. 122 122 123 123 The diagram below shows the working flow in default firmware of NLMS01: 124 124 116 + 125 125 [[image:image-20220907171221-5.png]] 126 126 119 + 120 + 127 127 == 2.2 Configure the NLMS01 == 128 128 123 + 129 129 === 2.2.1 Test Requirement === 130 130 126 + 131 131 To use NLMS01 in your city, make sure meet below requirements: 132 132 133 133 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -134,90 +134,120 @@ 134 134 * The local NB-IoT network used the band that NLMS01 supports. 135 135 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 136 136 137 -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 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 server 138 138 135 + 139 139 [[image:image-20220907171221-6.png]] 140 140 138 + 139 + 141 141 === 2.2.2 Insert SIM card === 142 142 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 + 147 147 [[image:image-20220907171221-7.png]] 148 148 150 + 151 + 149 149 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 150 150 151 -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. 152 152 153 -**Connect ion:**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 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 - USB TTL GND <~-~-~-~-> GND 156 156 157 - USBTTL TXD <~-~-~-~-> UART_RXD158 +(% style="color:blue" %)**Connection:** 158 158 159 - USB TTL RXD <~-~-~-~->UART_TXD160 +**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)** 160 160 162 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 163 + 164 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 165 + 166 + 161 161 In the PC, use below serial tool settings: 162 162 163 -* Baud: **9600** 164 -* Data bits:** 8** 165 -* Stop bits: **1** 166 -* Parity: **None** 167 -* Flow Control: **None** 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** 168 168 169 -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. 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. 170 170 171 -[[image:image-20220907 171221-8.png]]177 +[[image:image-20220913090720-1.png]] 172 172 173 -**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]] 174 174 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 + 175 175 === 2.2.4 Use CoAP protocol to uplink data === 176 176 177 -**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/]] 178 178 179 -** Usebelowcommands:**187 +(% 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/]] 180 180 181 -* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 182 -* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 183 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 184 184 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 + 197 + 185 185 For parameter description, please refer to AT command set 186 186 187 187 [[image:image-20220907171221-9.png]] 188 188 189 -After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 190 190 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 + 191 191 [[image:image-20220907171221-10.png]] 192 192 207 + 208 + 193 193 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 194 194 211 + 195 195 This feature is supported since firmware version v1.0.1 196 196 197 -* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 198 -* **AT+SERVADDR=120.24.4.116,5601 199 -* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 214 +* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 215 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 216 +* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 200 200 218 + 219 + 201 201 [[image:image-20220907171221-11.png]] 202 202 222 + 203 203 [[image:image-20220907171221-12.png]] 204 204 205 205 206 206 227 + 207 207 === 2.2.6 Use MQTT protocol to uplink data === 208 208 230 + 209 209 This feature is supported since firmware version v110 210 210 211 -* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 212 -* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 213 -* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 214 -* **AT+UNAME=UNAME 215 -* **AT+PWD=PWD 216 -* **AT+PUBTOPIC=PUB **~/~/Set the sending topic of MQTT 217 -* **AT+SUBTOPIC=SUB ** ~/~/Set the subscription topic of MQTT 233 +* (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 234 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 235 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 236 +* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 237 +* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 238 +* (% style="color:#037691" %)**AT+PUBTOPIC=PUB ** (%%) ~/~/ Set the sending topic of MQTT 239 +* (% style="color:#037691" %)**AT+SUBTOPIC=SUB ** (%%) ~/~/ Set the subscription topic of MQTT 218 218 241 + 242 + 219 219 [[image:image-20220907171221-13.png]] 220 220 245 + 246 + 221 221 [[image:image-20220907171221-14.png]] 222 222 223 223 ... ... @@ -224,66 +224,90 @@ 224 224 225 225 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. 226 226 253 + 254 + 227 227 === 2.2.7 Use TCP protocol to uplink data === 228 228 257 + 229 229 This feature is supported since firmware version v110 230 230 231 -* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 232 -* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 260 +* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 261 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port 233 233 263 + 264 + 234 234 [[image:image-20220907171221-15.png]] 235 235 267 + 268 + 236 236 [[image:image-20220907171221-16.png]] 237 237 238 238 239 239 273 + 240 240 === 2.2.8 Change Update Interval === 241 241 276 + 242 242 User can use below command to change the **uplink interval**. 243 243 244 -* **AT+TDC=7200 ** ~/~/ Set Update Interval to 7200s (2 hour) 279 +* (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 245 245 246 246 247 -**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).** 248 248 283 +(% 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).** 249 249 285 + 286 + 250 250 == 2.3 Uplink Payload == 251 251 289 + 252 252 In this mode, uplink payload includes 87 bytes in total by default. 253 253 254 254 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. 255 255 256 -|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4 257 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Time stamp|Leaf Temperature|Leaf moisture|Time stamp ..... 258 258 295 +(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 296 +|(% 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 297 +|(% 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 ..... 298 + 299 + 259 259 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 260 260 302 + 261 261 [[image:image-20220907171221-17.png]] 262 262 305 + 263 263 The payload is ASCII string, representative same HEX: 264 264 265 -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" %)0225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859(%%) where:308 +0x(% style="color:red" %)f868411056754138(% style="color:blue" %)0064(% style="color:green" %)0c78(% style="color:red" %)17(% style="color:blue" %)01(% style="color:green" %)00(% style="color:blue" %)**0225010b6315537b**010b0226631550fb**010e022663154d77**01110225631549f1**011502246315466b**01190223631542e5**011d022163153f62**011e022163153bde**011e022163153859**(%%)** **where: 266 266 267 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 (%%)268 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0 (%%)269 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V (%%)270 -* (% style="color:red" %)Singal: 0x17 = 23 (%%)271 -* (% style="color:blue" %)Mod: 0x01 = 1 (%%)272 -* (% style="color:green" %)Interrupt: 0x00= 0 (%%)310 +* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 311 +* (% style="color:blue" %)Version: 0x0064=100=1.0.0 312 +* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V 313 +* (% style="color:red" %)Singal: 0x17 = 23 314 +* (% style="color:blue" %)Mod: 0x01 = 1 315 +* (% style="color:green" %)Interrupt: 0x00= 0 273 273 * Leaf moisture: 0x0225= 549 = 54.9% 274 274 * Leaf Temperature:0x010B =267=26.7 °C 275 -* Time stamp : 0x6315537b =1662342011 318 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 276 276 * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 277 -* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... (%%)320 +* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 278 278 322 + 323 + 324 + 325 + 279 279 == 2.4 Payload Explanation and Sensor Interface == 280 280 328 + 281 281 === 2.4.1 Device ID === 282 282 331 + 283 283 By default, the Device ID equal to the last 15 bits of IMEI. 284 284 285 285 User can use **AT+DEUI** to set Device ID 286 286 336 + 287 287 **Example:** 288 288 289 289 AT+DEUI=868411056754138 ... ... @@ -290,14 +290,20 @@ 290 290 291 291 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 292 292 343 + 344 + 293 293 === 2.4.2 Version Info === 294 294 347 + 295 295 Specify the software version: 0x64=100, means firmware version 1.00. 296 296 297 297 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 298 298 352 + 353 + 299 299 === 2.4.3 Battery Info === 300 300 356 + 301 301 Check the battery voltage for NLMS01. 302 302 303 303 Ex1: 0x0B45 = 2885mV ... ... @@ -304,8 +304,11 @@ 304 304 305 305 Ex2: 0x0B49 = 2889mV 306 306 363 + 364 + 307 307 === 2.4.4 Signal Strength === 308 308 367 + 309 309 NB-IoT Network signal Strength. 310 310 311 311 **Ex1: 0x1d = 29** ... ... @@ -320,8 +320,11 @@ 320 320 321 321 **99** Not known or not detectable 322 322 382 + 383 + 323 323 === 2.4.5 Leaf moisture === 324 324 386 + 325 325 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**. 326 326 327 327 For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is ... ... @@ -328,8 +328,11 @@ 328 328 329 329 **0229(H) = 549(D) /100 = 54.9.** 330 330 393 + 394 + 331 331 === 2.4.6 Leaf Temperature === 332 332 397 + 333 333 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 334 334 335 335 **Example**: ... ... @@ -338,14 +338,19 @@ 338 338 339 339 If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 340 340 406 + 407 + 341 341 === 2.4.7 Timestamp === 342 342 410 + 343 343 Time stamp : 0x6315537b =1662342011 344 344 345 345 Convert Unix timestamp to time 2022-9-5 9:40:11. 346 346 415 + 347 347 === 2.4.8 Digital Interrupt === 348 348 418 + 349 349 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. 350 350 351 351 The command is: ... ... @@ -360,8 +360,11 @@ 360 360 361 361 0x(01): Interrupt Uplink Packet. 362 362 433 + 434 + 363 363 === 2.4.9 +5V Output === 364 364 437 + 365 365 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 366 366 367 367 The 5V output time can be controlled by AT Command. ... ... @@ -371,12 +371,15 @@ 371 371 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 372 372 373 373 447 + 374 374 == 2.5 Downlink Payload == 375 375 450 + 376 376 By default, NLMS01 prints the downlink payload to console port. 377 377 378 378 [[image:image-20220907171221-18.png]] 379 379 455 + 380 380 **Examples:** 381 381 382 382 * **Set TDC** ... ... @@ -395,8 +395,11 @@ 395 395 396 396 Downlink Payload: 06000003, Set AT+INTMOD=3 397 397 474 + 475 + 398 398 == 2.6 LED Indicator == 399 399 478 + 400 400 The NLMS01 has an internal LED which is to show the status of different state. 401 401 402 402 * 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) ... ... @@ -404,18 +404,26 @@ 404 404 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 405 405 * For each uplink probe, LED will be on for 500ms. 406 406 407 -== 2.7 Installation == 408 408 487 + 488 + 489 +== 2.7 Installation == 490 + 491 + 409 409 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. 410 410 494 + 411 411 [[image:image-20220907171221-19.png]] 412 412 413 -== 2.8 Moisture and Temperature alarm function == 414 414 415 -➢ AT Command: 416 416 417 - AT+HUMALARM=min,max499 +== 2.8 Moisture and Temperature alarm function == 418 418 501 + 502 +**➢ AT Command:** 503 + 504 +**AT+ HUMALARM =min,max** 505 + 419 419 ² When min=0, and max≠0, Alarm higher than max 420 420 421 421 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -422,8 +422,9 @@ 422 422 423 423 ² When min≠0 and max≠0, Alarm higher than max or lower than min 424 424 425 -Example: 426 426 513 +**Example:** 514 + 427 427 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 428 428 429 429 AT+ TEMPALARM=min,max ... ... @@ -434,41 +434,53 @@ 434 434 435 435 ² When min≠0 and max≠0, Alarm higher than max or lower than min 436 436 437 -Example: 438 438 526 +**Example:** 527 + 439 439 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 440 440 441 441 442 -== 2.9 Set the number of data to be uploaded and the recording time == 443 443 444 - ➢ATCommand:532 +== 2.9 Set the number of data to be uploaded and the recording time == 445 445 446 -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) 447 447 448 -AT +NOUD=8~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data canbe uploaded.535 +**➢ AT Command:** 449 449 450 -= = 2.10ReadorClearcacheddata==537 +**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) 451 451 452 - ➢ATCommand:539 +**AT+NOUD=8** ~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 453 453 454 -AT+CDP ~/~/ Read cached data 455 455 456 -[[image:image-20220907171221-20.png]] 457 457 543 +== 2.10 Read or Clear cached data == 458 458 459 -AT+CDP=0 ~/~/ Clear cached data 460 460 546 +**➢ AT Command:** 461 461 548 +**AT+CDP** ~/~/ Read cached data 549 + 550 +**AT+CDP=0 ** ~/~/ Clear cached data 551 + 552 + 553 +[[image:image-20220907171221-20.png]] 554 + 555 + 556 + 462 462 == 2.11 Firmware Change Log == 463 463 559 + 464 464 Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 465 465 466 466 Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 467 467 564 + 565 + 468 468 == 2.12 Battery Analysis == 469 469 568 + 470 470 === 2.12.1 Battery Type === 471 471 571 + 472 472 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. 473 473 474 474 The battery is designed to last for several years depends on the actually use environment and update interval. ... ... @@ -481,8 +481,11 @@ 481 481 482 482 [[image:image-20220907171221-21.png]] 483 483 584 + 585 + 484 484 === 2.12.2 Power consumption Analyze === 485 485 588 + 486 486 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. 487 487 488 488 Instruction to use as below: ... ... @@ -499,26 +499,39 @@ 499 499 500 500 [[image:image-20220907171221-22.jpeg]] 501 501 605 + 502 502 === 2.12.3 Battery Note === 503 503 608 + 504 504 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. 505 505 611 + 612 + 506 506 === 2.12.4 Replace the battery === 507 507 615 + 508 508 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). 509 509 618 + 619 + 510 510 = 3. Access NB-IoT Module = 511 511 622 + 512 512 Users can directly access the AT command set of the NB-IoT module. 513 513 514 514 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/]] 515 515 627 + 516 516 [[image:image-20220907171221-23.png]] 517 517 630 + 631 + 518 518 = 4. Using the AT Commands = 519 519 634 + 520 520 == 4.1 Access AT Commands == 521 521 637 + 522 522 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]] 523 523 524 524 AT+<CMD>? : Help on <CMD> ... ... @@ -529,6 +529,7 @@ 529 529 530 530 AT+<CMD>=? : Get the value 531 531 648 + 532 532 **General Commands** 533 533 534 534 AT : Attention ... ... @@ -553,15 +553,20 @@ 553 553 554 554 AT+SERVADDR : Server Address 555 555 556 -AT+ TRSetrecordtime"673 +AT+APN : Get or set the APN 557 557 675 +AT+FBAND : Get or Set whether to automatically modify the frequency band 558 558 559 -AT+ NOUDthenumberof data to beuploaded677 +AT+DNSCFG : Get or Set DNS Server 560 560 679 +AT+GETSENSORVALUE : Returns the current sensor measurement 561 561 562 -AT+ CDP:ReadorClearcacheddata681 +AT+TR : Get or Set record time" 563 563 683 +AT+NOUD : Get or Set the number of data to be uploaded 564 564 685 +AT+CDP : Read or Clear cached data 686 + 565 565 AT+TEMPALARM : Get or Set alarm of temp 566 566 567 567 AT+HUMALARM : Get or Set alarm of PH ... ... @@ -571,10 +571,12 @@ 571 571 572 572 AT+URI : Resource parameters 573 573 696 + 574 574 **UDP Management** 575 575 576 576 AT+CFM : Upload confirmation mode (only valid for UDP) 577 577 701 + 578 578 **MQTT Management** 579 579 580 580 AT+CLIENT : Get or Set MQTT client ... ... @@ -587,6 +587,7 @@ 587 587 588 588 AT+SUBTOPIC : Get or Set MQTT subscription topic 589 589 714 + 590 590 **Information** 591 591 592 592 AT+FDR : Factory Data Reset ... ... @@ -593,32 +593,49 @@ 593 593 594 594 AT+PWORD : Serial Access Password 595 595 721 + 722 + 596 596 = 5. FAQ = 597 597 725 + 598 598 == 5.1 How to Upgrade Firmware == 599 599 728 + 600 600 User can upgrade the firmware for 1) bug fix, 2) new feature release. 601 601 602 602 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]] 603 603 604 -**Notice, **NLMS01 **and**NLMS01 **share the same mother board. They use the same connection and method to update.**733 +**Notice, NLMS01** **and LLMS01** **share the same mother board. They use the same connection and method to update.** 605 605 735 + 736 + 606 606 = 6. Trouble Shooting = 607 607 739 + 608 608 == 6.1 Connection problem when uploading firmware == 609 609 742 + 610 610 **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]] 611 611 745 + 746 + 612 612 == 6.2 AT Command input doesn't work == 613 613 749 + 614 614 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. 615 615 752 + 753 + 616 616 = 7. Order Info = 617 617 756 + 618 618 Part Number**:** NLMS01 619 619 759 + 760 + 620 620 = 8. Packing Info = 621 621 763 + 622 622 **Package Includes**: 623 623 624 624 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 ... ... @@ -630,8 +630,12 @@ 630 630 * Package Size / pcs : cm 631 631 * Weight / pcs : g 632 632 775 + 776 + 777 + 633 633 = 9. Support = 634 634 780 + 635 635 * 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. 636 636 * 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]] 637 637
- image-20220913090720-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +224.9 KB - Content