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)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -62,7 +62,6 @@ 62 62 * Supply Voltage: 2.1v ~~ 3.6v 63 63 * Operating Temperature: -40 ~~ 85°C 64 64 65 - 66 66 (% style="color:#037691" %)**NB-IoT Spec:** 67 67 68 68 * - B1 @H-FDD: 2100MHz ... ... @@ -72,13 +72,11 @@ 72 72 * - B20 @H-FDD: 800MHz 73 73 * - B28 @H-FDD: 700MHz 74 74 74 +== 1.4 Probe Specification == 75 75 76 76 77 - ==1.4ProbeSpecification==77 +(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface** 78 78 79 - 80 -**Leaf Moisture: percentage of water drop over total leaf surface** 81 - 82 82 * Range 0-100% 83 83 * Resolution: 0.1% 84 84 * Accuracy: ±3%(0-50%);±6%(>50%) ... ... @@ -85,7 +85,7 @@ 85 85 * IP67 Protection 86 86 * Length: 3.5 meters 87 87 88 -**Leaf Temperature:** 85 +(% style="color:#037691" %)**Leaf Temperature:** 89 89 90 90 * Range -50℃~80℃ 91 91 * Resolution: 0.1℃ ... ... @@ -93,30 +93,40 @@ 93 93 * IP67 Protection 94 94 * Length: 3.5 meters 95 95 96 -== 1.5 Applications == 93 +== 1.5 Applications == 97 97 95 + 98 98 * Smart Agriculture 99 99 100 -== 1.6 Pin mapping and power on == 98 +== 1.6 Pin mapping and power on == 101 101 100 + 102 102 [[image:image-20220907171221-4.png]] 103 103 104 104 **~ ** 105 105 105 + 106 106 = 2. Use NLMS01 to communicate with IoT Server = 107 107 108 + 108 108 == 2.1 How it works == 109 109 111 + 110 110 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. 111 111 112 112 The diagram below shows the working flow in default firmware of NLMS01: 113 113 116 + 114 114 [[image:image-20220907171221-5.png]] 115 115 119 + 120 + 116 116 == 2.2 Configure the NLMS01 == 117 117 123 + 118 118 === 2.2.1 Test Requirement === 119 119 126 + 120 120 To use NLMS01 in your city, make sure meet below requirements: 121 121 122 122 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -123,90 +123,120 @@ 123 123 * The local NB-IoT network used the band that NLMS01 supports. 124 124 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 125 125 126 -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 127 127 135 + 128 128 [[image:image-20220907171221-6.png]] 129 129 138 + 139 + 130 130 === 2.2.2 Insert SIM card === 131 131 142 + 132 132 Insert the NB-IoT Card get from your provider. 133 133 134 134 User need to take out the NB-IoT module and insert the SIM card like below: 135 135 147 + 136 136 [[image:image-20220907171221-7.png]] 137 137 150 + 151 + 138 138 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 139 139 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. 141 141 142 -**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. 143 143 144 - USB TTL GND <~-~-~-~-> GND 145 145 146 - USBTTL TXD <~-~-~-~-> UART_RXD158 +(% style="color:blue" %)**Connection:** 147 147 148 - USB TTL RXD <~-~-~-~->UART_TXD160 +**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)** 149 149 162 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 163 + 164 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 165 + 166 + 150 150 In the PC, use below serial tool settings: 151 151 152 -* Baud: **9600** 153 -* Data bits:** 8** 154 -* Stop bits: **1** 155 -* Parity: **None** 156 -* 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** 157 157 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. 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. 159 159 160 -[[image:image-20220907 171221-8.png]]177 +[[image:image-20220913090720-1.png]] 161 161 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]] 163 163 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 + 164 164 === 2.2.4 Use CoAP protocol to uplink data === 165 165 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/]] 167 167 168 -** 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/]] 169 169 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 173 173 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 + 174 174 For parameter description, please refer to AT command set 175 175 176 176 [[image:image-20220907171221-9.png]] 177 177 178 -After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 179 179 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 + 180 180 [[image:image-20220907171221-10.png]] 181 181 207 + 208 + 182 182 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 183 183 211 + 184 184 This feature is supported since firmware version v1.0.1 185 185 186 -* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 187 -* **AT+SERVADDR=120.24.4.116,5601 188 -* **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 189 189 218 + 219 + 190 190 [[image:image-20220907171221-11.png]] 191 191 222 + 192 192 [[image:image-20220907171221-12.png]] 193 193 194 194 195 195 227 + 196 196 === 2.2.6 Use MQTT protocol to uplink data === 197 197 230 + 198 198 This feature is supported since firmware version v110 199 199 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 204 -* **AT+PWD=PWD 205 -* **AT+PUBTOPIC=PUB **~/~/Set the sending topic of MQTT 206 -* **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 207 207 241 + 242 + 208 208 [[image:image-20220907171221-13.png]] 209 209 245 + 246 + 210 210 [[image:image-20220907171221-14.png]] 211 211 212 212 ... ... @@ -213,41 +213,59 @@ 213 213 214 214 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. 215 215 253 + 254 + 216 216 === 2.2.7 Use TCP protocol to uplink data === 217 217 257 + 218 218 This feature is supported since firmware version v110 219 219 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 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 222 222 263 + 264 + 223 223 [[image:image-20220907171221-15.png]] 224 224 267 + 268 + 225 225 [[image:image-20220907171221-16.png]] 226 226 227 227 228 228 273 + 229 229 === 2.2.8 Change Update Interval === 230 230 276 + 231 231 User can use below command to change the **uplink interval**. 232 232 233 -* **AT+TDC=7200 ** ~/~/ Set Update Interval to 7200s (2 hour) 279 +* (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 234 234 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).** 236 236 237 237 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 + 238 238 == 2.3 Uplink Payload == 239 239 289 + 240 240 In this mode, uplink payload includes 87 bytes in total by default. 241 241 242 242 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. 243 243 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 ..... 246 246 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 + 247 247 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 248 248 302 + 249 249 [[image:image-20220907171221-17.png]] 250 250 305 + 251 251 The payload is ASCII string, representative same HEX: 252 252 253 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: ... ... @@ -264,6 +264,10 @@ 264 264 * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 265 265 * (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 266 266 322 + 323 + 324 + 325 + 267 267 == 2.4 Payload Explanation and Sensor Interface == 268 268 269 269 === 2.4.1 Device ID ===
- image-20220913090720-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +224.9 KB - Content