Changes for page NLMS01-NB-IoT Leaf Moisture Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:54
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- 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,120 +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 - 197 - 198 198 For parameter description, please refer to AT command set 199 199 200 200 [[image:image-20220907171221-9.png]] 201 201 178 +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 207 - 208 - 209 209 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 210 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 **(%%)~/~/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 217 217 218 - 219 - 220 220 [[image:image-20220907171221-11.png]] 221 221 222 - 223 223 [[image:image-20220907171221-12.png]] 224 224 225 225 226 226 227 - 228 228 === 2.2.6 Use MQTT protocol to uplink data === 229 229 230 - 231 231 This feature is supported since firmware version v110 232 232 233 -* (% style="color:#037691" %)**AT+PRO=3 **(%%)~/~/234 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 **(%%)~/~/235 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT **(%%)~/~/236 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/237 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/238 -* (% style="color:#037691" %)**AT+PUBTOPIC=PUB **(%%)~/~/239 -* (% 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 240 240 241 - 242 - 243 243 [[image:image-20220907171221-13.png]] 244 244 245 - 246 - 247 247 [[image:image-20220907171221-14.png]] 248 248 249 249 ... ... @@ -250,59 +250,41 @@ 250 250 251 251 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. 252 252 253 - 254 - 255 255 === 2.2.7 Use TCP protocol to uplink data === 256 256 257 - 258 258 This feature is supported since firmware version v110 259 259 260 -* (% style="color:#037691" %)**AT+PRO=4 **(%%)~/~/261 -* (% 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 262 262 263 - 264 - 265 265 [[image:image-20220907171221-15.png]] 266 266 267 - 268 - 269 269 [[image:image-20220907171221-16.png]] 270 270 271 271 272 272 273 - 274 274 === 2.2.8 Change Update Interval === 275 275 276 - 277 277 User can use below command to change the **uplink interval**. 278 278 279 -* (% style="color:#037691" %)**AT+TDC=7200 **(%%)~/~/ Set Update Interval to 7200s (2 hour)233 +* **AT+TDC=7200 ** ~/~/ Set Update Interval to 7200s (2 hour) 280 280 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).** 281 281 282 282 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).** 284 - 285 - 286 - 287 287 == 2.3 Uplink Payload == 288 288 289 - 290 290 In this mode, uplink payload includes 87 bytes in total by default. 291 291 292 292 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. 293 293 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 ..... 294 294 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 - 300 300 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 301 301 302 - 303 303 [[image:image-20220907171221-17.png]] 304 304 305 - 306 306 The payload is ASCII string, representative same HEX: 307 307 308 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: ... ... @@ -319,10 +319,6 @@ 319 319 * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 320 320 * (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 321 321 322 - 323 - 324 - 325 - 326 326 == 2.4 Payload Explanation and Sensor Interface == 327 327 328 328 === 2.4.1 Device ID ===