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, 4 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.ting - Content
-
... ... @@ -1,31 +1,51 @@ 1 - [[image:image-20220907171221-1.jpeg]]1 + 2 2 3 +(% style="text-align:center" %) 4 +[[image:image-20220907171221-1.jpeg]] 3 3 6 + 4 4 5 -**~1. Introduction** 6 6 7 -**1.1 What is NLMS01 **Leaf Moisture Sensor 8 8 9 -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. 10 10 11 -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. 12 12 12 + 13 +{{toc/}} 14 + 15 + 16 + 17 += 1. Introduction = 18 + 19 +== 1.1 What is NLMS01 Leaf Moisture Sensor == 20 + 21 + 22 +((( 23 +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. 24 + 25 +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. 26 + 13 13 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. 14 -\\NLMS01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 15 -\\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) 16 -\\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 17 17 29 +NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 30 + 31 +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). 32 + 33 +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. 34 +))) 35 + 36 + 18 18 [[image:image-20220907171221-2.png]] 19 19 39 + 20 20 [[image:image-20220907171221-3.png]] 21 21 22 -**1.2 Features** 23 23 24 -* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 25 -* Monitor Leaf moisture 43 +== 1.2 Features == 26 26 27 -* Monitor Leaf temperature 28 28 46 +* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 47 +* Monitor Leaf moisture 48 +* Monitor Leaf temperature 29 29 * Moisture and Temperature alarm function 30 30 * Monitor Battery Level 31 31 * Uplink on periodically ... ... @@ -37,26 +37,33 @@ 37 37 * Micro SIM card slot for NB-IoT SIM 38 38 * 8500mAh Battery for long term use 39 39 40 -**1.3 Specification** 60 +((( 61 + 41 41 42 -**Common DC Characteristics:** 63 + 64 +))) 43 43 66 +== 1.3 Specification == 67 + 68 + 69 +(% style="color:#037691" %)**Common DC Characteristics:** 70 + 44 44 * Supply Voltage: 2.1v ~~ 3.6v 45 45 * Operating Temperature: -40 ~~ 85°C 46 46 47 -**NB-IoT Spec:** 74 +(% style="color:#037691" %)**NB-IoT Spec:** 48 48 49 -* -B1 @H-FDD: 2100MHz50 -* -B3 @H-FDD: 1800MHz51 -* -B8 @H-FDD: 900MHz52 -* -B5 @H-FDD: 850MHz53 -* -B20 @H-FDD: 800MHz54 -* -B28 @H-FDD: 700MHz76 +* B1 @H-FDD: 2100MHz 77 +* B3 @H-FDD: 1800MHz 78 +* B8 @H-FDD: 900MHz 79 +* B5 @H-FDD: 850MHz 80 +* B20 @H-FDD: 800MHz 81 +* B28 @H-FDD: 700MHz 55 55 56 - **1.4 Probe Specification**83 +== 1.4 Probe Specification == 57 57 58 58 59 -**Leaf Moisture: percentage of water drop over total leaf surface** 86 +(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface** 60 60 61 61 * Range 0-100% 62 62 * Resolution: 0.1% ... ... @@ -64,7 +64,7 @@ 64 64 * IP67 Protection 65 65 * Length: 3.5 meters 66 66 67 -**Leaf Temperature:** 94 +(% style="color:#037691" %)**Leaf Temperature:** 68 68 69 69 * Range -50℃~80℃ 70 70 * Resolution: 0.1℃ ... ... @@ -72,30 +72,36 @@ 72 72 * IP67 Protection 73 73 * Length: 3.5 meters 74 74 75 - **~1.5 Applications**102 +== 1.5 Applications == 76 76 104 + 77 77 * Smart Agriculture 78 78 79 - **1.6 Pin mapping and power on**107 +== 1.6 Pin mapping and power on == 80 80 109 + 81 81 [[image:image-20220907171221-4.png]] 82 82 83 83 **~ ** 84 84 85 - **2. Use NLMS01 to communicate with IoT Server**114 += 2. Use NLMS01 to communicate with IoT Server = 86 86 87 - **2.1 How it works**116 +== 2.1 How it works == 88 88 118 + 89 89 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. 90 90 91 91 The diagram below shows the working flow in default firmware of NLMS01: 92 92 123 + 93 93 [[image:image-20220907171221-5.png]] 94 94 95 -**2.2 Configure the NLMS01** 96 96 97 - **2.2.1Test Requirement**127 +== 2.2 Configure the NLMS01 == 98 98 129 +=== 2.2.1 Test Requirement === 130 + 131 + 99 99 To use NLMS01 in your city, make sure meet below requirements: 100 100 101 101 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -102,90 +102,108 @@ 102 102 * The local NB-IoT network used the band that NLMS01 supports. 103 103 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 104 104 105 -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 138 +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 106 106 140 + 107 107 [[image:image-20220907171221-6.png]] 108 108 109 -**2.2.2 Insert SIM card** 110 110 144 +=== 2.2.2 Insert SIM card === 145 + 146 + 111 111 Insert the NB-IoT Card get from your provider. 112 112 113 113 User need to take out the NB-IoT module and insert the SIM card like below: 114 114 151 + 115 115 [[image:image-20220907171221-7.png]] 116 116 117 -**2.2.3 Connect USB – TTL to NLMS01 to configure it** 118 118 119 - Userneedtoconfigure 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 aUSBtoTTLadapter toconnect toNLMS01and use AT Commandsto configure it,as below.155 +=== 2.2.3 Connect USB – TTL to NLMS01 to configure it === 120 120 121 -**Connection:** 122 122 123 - USB TTL GND<~-~-~-~->GND158 +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. 124 124 125 - USB TTL TXD <~-~-~-~-> UART_RXD 126 126 127 - USBTTL RXD <~-~-~-~-> UART_TXD161 +(% style="color:blue" %)**Connection:** 128 128 163 +**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)** 164 + 165 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 166 + 167 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 168 + 169 + 129 129 In the PC, use below serial tool settings: 130 130 131 -* Baud: **9600** 132 -* Data bits:** 8** 133 -* Stop bits: **1** 134 -* Parity: **None** 135 -* Flow Control: **None** 172 +* Baud: (% style="color:green" %)**9600** 173 +* Data bits:** (% style="color:green" %)8(%%)** 174 +* Stop bits: (% style="color:green" %)**1** 175 +* Parity: (% style="color:green" %)**None** 176 +* Flow Control: (% style="color:green" %)**None** 136 136 137 -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 +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. 138 138 139 -[[image:image-20220907 171221-8.png]]180 +[[image:image-20220913090720-1.png]] 140 140 141 -**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]] 142 142 143 -** 2.2.4UseCoAPprotocoluplinkdata**183 +(% 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]] 144 144 145 -**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/]] 146 146 147 - **Usebelowcommands:**186 +=== 2.2.4 Use CoAP protocol to uplink data === 148 148 149 -* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 150 -* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 151 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 152 152 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 + 153 153 For parameter description, please refer to AT command set 154 154 155 155 [[image:image-20220907171221-9.png]] 156 156 157 -After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 158 158 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 + 159 159 [[image:image-20220907171221-10.png]] 160 160 161 -**2.2.5 Use UDP protocol to uplink data(Default protocol)** 162 162 208 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 209 + 210 + 163 163 This feature is supported since firmware version v1.0.1 164 164 165 -* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 166 -* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 167 -* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 213 +* (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 214 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 168 168 169 169 [[image:image-20220907171221-11.png]] 170 170 218 + 171 171 [[image:image-20220907171221-12.png]] 172 172 173 173 174 174 175 - **2.2.6 Use MQTT protocol to uplink data**223 +=== 2.2.6 Use MQTT protocol to uplink data === 176 176 225 + 177 177 This feature is supported since firmware version v110 178 178 179 -* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 180 -* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 181 -* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 182 -* **AT+UNAME=UNAME 183 -* **AT+PWD=PWD 184 -* **AT+PUBTOPIC= NSE01_PUB **~/~/Set the sending topic of MQTT185 -* **AT+SUBTOPIC= NSE01_SUB ** ~/~/Set the subscription topic of MQTT228 +* (% style="color:#037691" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 229 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 230 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT ** (%%) ~/~/ Set up the CLIENT of MQTT 231 +* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/ Set the username of MQTT 232 +* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/ Set the password of MQTT 233 +* (% style="color:#037691" %)**AT+PUBTOPIC=PUB ** (%%) ~/~/ Set the sending topic of MQTT 234 +* (% style="color:#037691" %)**AT+SUBTOPIC=SUB ** (%%) ~/~/ Set the subscription topic of MQTT 186 186 187 187 [[image:image-20220907171221-13.png]] 188 188 238 + 239 + 189 189 [[image:image-20220907171221-14.png]] 190 190 191 191 ... ... @@ -192,81 +192,107 @@ 192 192 193 193 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. 194 194 195 -**2.2.7 Use TCP protocol to uplink data** 196 196 247 +=== 2.2.7 Use TCP protocol to uplink data === 248 + 249 + 197 197 This feature is supported since firmware version v110 198 198 199 -* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 200 -* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 252 +* (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 253 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port 201 201 202 202 [[image:image-20220907171221-15.png]] 203 203 257 + 258 + 204 204 [[image:image-20220907171221-16.png]] 205 205 206 206 207 207 208 -**2.2.8 Change Update Interval** 209 209 264 +=== 2.2.8 Change Update Interval === 265 + 266 + 210 210 User can use below command to change the **uplink interval**. 211 211 212 -* **AT+TDC= 600 ** ~/~/ Set Update Interval to600s269 +* (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 213 213 214 -**NOTE:** 271 +(% 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).** 215 215 216 -**~1. By default, the device will send an uplink message every 2 hour.** 217 217 218 - **2.3 Uplink Payload**274 +== 2.3 Uplink Payload == 219 219 276 + 220 220 In this mode, uplink payload includes 87 bytes in total by default. 221 221 222 222 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. 223 223 224 -|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|1|2|2|2|4 225 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Soil PH|Time stamp ..... 281 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:517px" %) 282 +|(% style="background-color:#4f81bd; color:white; width:50px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:20px" %)**2**|(% style="background-color:#4f81bd; color:white; width:20px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**|(% style="background-color:#4f81bd; color:white; width:30px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**4**|(% style="background-color:#4f81bd; color:white; width:50px" %)**2**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:37px" %)**4** 283 +|(% 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 ..... 226 226 227 227 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 228 228 287 + 229 229 [[image:image-20220907171221-17.png]] 230 230 290 + 231 231 The payload is ASCII string, representative same HEX: 232 232 233 -0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where:293 +**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 01110225631549f1 011502246315466b 01190223631542e5 011d022163153f62 011e022163153bde 011e022163153859__//(%%)** 234 234 235 -* Device ID: 0xf868411056754138 = f868411056754138 236 -* Version: 0x0064=100=1.0.0 295 +where: 237 237 238 -* BAT: 0x0c78 = 3192 mV = 3.192V 239 -* Singal: 0x17 = 23 240 -* Mod: 0x01 = 1 241 -* Interrupt: 0x00= 0 242 -* Leaf moisture: 0x0225= 549 = 54.9% 243 -* Leaf Temperature:0x010B =267=26.7 °C 244 -* Time stamp : 0x6315537b =1662342011 245 -* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 246 -* 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 297 +* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 247 247 248 -* *2.4Payload Explanationand Sensor Interface**299 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 249 249 250 -* *2.4.1 DeviceID**301 +* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 251 251 303 +* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 304 + 305 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 306 + 307 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 308 + 309 +* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9% 310 + 311 +* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C 312 + 313 +* (% style="color:#037691" %)**Time stamp :** (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 314 + 315 +* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp : **(%%)010b0226631550fb 316 + 317 +* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 318 + 319 +== 2.4 Payload Explanation and Sensor Interface == 320 + 321 +=== 2.4.1 Device ID === 322 + 323 + 252 252 By default, the Device ID equal to the last 15 bits of IMEI. 253 253 254 -User can use **AT+DEUI** to set Device ID 326 +User can use (% style="color:#037691" %)**AT+DEUI**(%%) to set Device ID 255 255 256 -**Example:** 257 257 329 +(% style="color:blue" %)**Example**: 330 + 258 258 AT+DEUI=868411056754138 259 259 260 260 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 261 261 262 -**2.4.2 Version Info** 263 263 336 +=== 2.4.2 Version Info === 337 + 338 + 264 264 Specify the software version: 0x64=100, means firmware version 1.00. 265 265 266 266 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 267 267 268 -**2.4.3 Battery Info** 269 269 344 +=== 2.4.3 Battery Info === 345 + 346 + 270 270 Check the battery voltage for NLMS01. 271 271 272 272 Ex1: 0x0B45 = 2885mV ... ... @@ -273,12 +273,15 @@ 273 273 274 274 Ex2: 0x0B49 = 2889mV 275 275 276 -**2.4.4 Signal Strength** 277 277 354 +=== 2.4.4 Signal Strength === 355 + 356 + 278 278 NB-IoT Network signal Strength. 279 279 280 -**Ex1: 0x1d = 29** 281 281 360 +(% style="color:blue" %)**Ex1: 0x1d = 29** 361 + 282 282 **0** -113dBm or less 283 283 284 284 **1** -111dBm ... ... @@ -289,37 +289,45 @@ 289 289 290 290 **99** Not known or not detectable 291 291 292 -**2.4.5 Leaf** moisture 293 293 294 - Getthemoisture of the **Leaf**.The value range of the register is 300-1000(Decimal), divide this value by 100 toget the percentage of moisturein the **Leaf**.373 +=== 2.4.5 Leaf moisture === 295 295 296 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is 297 297 298 - **0229(H)=549(D)/100=54.9.**376 +Get the moisture of the (% style="color:#037691" %)**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. 299 299 300 - **2.4.6LeafTemperature**378 +For example, if the data you get from the register is (% style="color:#037691" %)**__0x05 0xDC__**(%%), the moisture content in the (% style="color:#037691" %)**Leaf**(%%) is 301 301 302 - Getthetemperaturein the**Leaf**. The value range of the register is -4000-+800(Decimal),divide this value by100toget the temperature in the **Leaf**.For example, if the data you get from the register is **__0x090xEC__**, the temperature content in the **Leaf **is380 +(% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 303 303 304 -**Example**: 305 305 306 - If payload is 0105H: ((0x0105 & 0x8000)>>15===0),temp =0105(H)/10=26.1 °C383 +=== 2.4.6 Leaf Temperature === 307 307 308 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 309 309 310 - **2.4.7Timestamp**386 +Get the temperature in the Leaf. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the Leaf. For example, if the data you get from the register is (% style="color:#037691" %)**__0x09 0xEC__**(%%), the temperature content in the (% style="color:#037691" %)**Leaf **(%%)is 311 311 388 +(% style="color:blue" %)**Example**: 389 + 390 +If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 391 + 392 +If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 393 + 394 + 395 +=== 2.4.7 Timestamp === 396 + 397 + 312 312 Time stamp : 0x6315537b =1662342011 313 313 314 314 Convert Unix timestamp to time 2022-9-5 9:40:11. 315 315 316 -**2.4.8 Digital Interrupt** 317 317 318 -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.403 +=== 2.4.8 Digital Interrupt === 319 319 405 + 406 +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. 407 + 320 320 The command is: 321 321 322 -**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]])**.** 410 +(% style="color:blue" %)**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]])**.** 323 323 324 324 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. 325 325 ... ... @@ -329,27 +329,37 @@ 329 329 330 330 0x(01): Interrupt Uplink Packet. 331 331 332 -**2.4.9 +5V Output** 333 333 421 +=== 2.4.9 +5V Output === 422 + 423 + 334 334 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 335 335 336 336 The 5V output time can be controlled by AT Command. 337 337 338 -**AT+5VT=1000** 428 +(% style="color:blue" %)**AT+5VT=1000** 339 339 340 340 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 341 341 342 342 343 - **2.5 Downlink Payload**433 +== 2.5 Downlink Payload == 344 344 435 + 345 345 By default, NLMS01 prints the downlink payload to console port. 346 346 347 -[[image:image-20220907171221-18.png]] 438 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 439 +|=(% style="width: 183px; background-color:#4F81BD;color:white" %)**Downlink Control Type**|=(% style="width: 55px; background-color:#4F81BD;color:white" %)FPort|=(% style="width: 93px; background-color:#4F81BD;color:white" %)**Type Code**|=(% style="width: 179px; background-color:#4F81BD;color:white" %)**Downlink payload size(bytes)** 440 +|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4 441 +|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2 442 +|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4 348 348 349 - **Examples:**444 + 350 350 351 - ***Set TDC**446 +(% style="color:blue" %)**Examples:** 352 352 448 + 449 +* (% style="color:#037691" %)**Set TDC** 450 + 353 353 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 354 354 355 355 Payload: 01 00 00 1E TDC=30S ... ... @@ -356,16 +356,22 @@ 356 356 357 357 Payload: 01 00 00 3C TDC=60S 358 358 359 -* **Reset** 360 360 458 + 459 +* (% style="color:#037691" %)**Reset** 460 + 361 361 If payload = 0x04FF, it will reset the NLMS01 362 362 363 -* **INTMOD** 364 364 464 + 465 +* (% style="color:#037691" %)**INTMOD** 466 + 365 365 Downlink Payload: 06000003, Set AT+INTMOD=3 366 366 367 -**2.6 LED Indicator** 368 368 470 +== 2.6 LED Indicator == 471 + 472 + 369 369 The NLMS01 has an internal LED which is to show the status of different state. 370 370 371 371 * 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) ... ... @@ -373,18 +373,22 @@ 373 373 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 374 374 * For each uplink probe, LED will be on for 500ms. 375 375 376 - **2.7 Installation**480 +== 2.7 Installation == 377 377 482 + 378 378 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. 379 379 485 + 380 380 [[image:image-20220907171221-19.png]] 381 381 382 -**2.8 Moisture and Temperature alarm function** 383 383 384 - ➢ATCommand:489 +== 2.8 Moisture and Temperature alarm function == 385 385 386 -AT+ HUMALARM =min,max 387 387 492 +(% style="color:blue" %)**➢ AT Command:** 493 + 494 +(% style="color:#037691" %)**AT+ HUMALARM =min,max** 495 + 388 388 ² When min=0, and max≠0, Alarm higher than max 389 389 390 390 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -391,8 +391,9 @@ 391 391 392 392 ² When min≠0 and max≠0, Alarm higher than max or lower than min 393 393 394 -Example: 395 395 503 +(% style="color:blue" %)**Example:** 504 + 396 396 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 397 397 398 398 AT+ TEMPALARM=min,max ... ... @@ -403,197 +403,206 @@ 403 403 404 404 ² When min≠0 and max≠0, Alarm higher than max or lower than min 405 405 406 -Example: 407 407 516 +(% style="color:blue" %)**Example:** 517 + 408 408 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 409 409 410 410 411 - **2.9 Set the number of data to be uploaded and the recording time**521 +== 2.9 Set the number of data to be uploaded and the recording time == 412 412 413 -➢ AT Command: 414 414 415 - AT+TR=900~/~/The unit isseconds, andthe default is to record dataonce every 900 seconds.(Theminimum canbe set to 180 seconds)524 +(% style="color:blue" %)**➢ AT Command:** 416 416 526 +* (% 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) 527 +* (% 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. 417 417 418 - AT+NOUD=8~/~/The deviceuploads8 setsofrecorded databy default.Upto32setsofrecorddatacan be uploaded.529 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 419 419 420 - **2.10 Read or Clear cacheddata**531 +[[image:image-20221009001002-1.png||height="706" width="982"]] 421 421 422 -➢ AT Command: 423 423 424 - AT+CDP~/~/Read cached data534 +== 2.10 Read or Clear cached data == 425 425 426 -[[image:image-20220907171221-20.png]] 427 427 537 +(% style="color:blue" %)**➢ AT Command:** 428 428 429 -AT+CDP=0 ~/~/ Clear cached data 539 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 540 +* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 430 430 542 +[[image:image-20220907171221-20.png]] 431 431 432 -**2.8 Firmware Change Log** 433 433 434 - DownloadURL&Firmware Changelog: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]545 +== 2.11 Firmware Change Log == 435 435 436 -Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 437 437 438 - **2.9BatteryAnalysis**548 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]] 439 439 440 - **2.9.1 BatteryType**550 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 441 441 442 -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. 443 443 444 - Thebatteryisdesigned tolast for severalyears dependsonthe actually use environment andupdateinterval.553 +== 2.12 Battery & Power Consumption == 445 445 446 -The battery related documents as below: 447 447 448 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 449 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 450 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 556 +NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 451 451 452 -[[ image:image-20220907171221-21.png]]558 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 453 453 454 -**2.9.2 Power consumption Analyze** 455 455 456 - Draginobattery powered product are all runs in Low Power mode.Wehave an update batterycalculator which baseon the measurement of the real device. Usercan use this calculatortocheck the battery life andcalculatethe battery life if want to use different transmit interval.561 += 3. Access NB-IoT Module = 457 457 458 -Instruction to use as below: 459 459 460 - **Step1: **Downlinkthe up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsxfrom: [[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/]]564 +Users can directly access the AT command set of the NB-IoT module. 461 461 462 - **Step2:**Openit and566 +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/]] 463 463 464 -* Product Model 465 -* Uplink Interval 466 -* Working Mode 467 467 468 - And the Life expectation in difference casewill be shownon the right.569 +[[image:image-20220907171221-23.png]] 469 469 470 -[[image:image-20220907171221-22.jpeg]] 471 471 472 - **2.9.3BatteryNote**572 += 4. Using the AT Commands = 473 473 474 - TheLi-SICObattery is designed for smallcurrent / long period application. It is not good to usea high current,short period transmitmethod.Therecommended minimum period for use of this battery is 5 minutes. If you use a shorter periodtime to transmitLoRa, then the battery life may be decreased.574 +== 4.1 Access AT Commands == 475 475 476 -**2.9.4 Replace the battery** 477 477 478 - ThedefaultbatterypackofNLMS01 includesaER26500 plus supercapacitor.If usercan't find this packlocally, they can findER26500 or equivalence withouthe SPC1520 capacitor,whichwill alsowork in mostcase. The SPC can enlarge the battery life forigh frequencyuse (update periodbelow 5 minutes).577 +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]] 479 479 480 - **3.AccessNB-IoTModule**579 +AT+<CMD>? : Help on <CMD> 481 481 482 - Users can directly access theATcommandsetoftheNB-IoT module.581 +AT+<CMD> : Run <CMD> 483 483 484 - TheATommand set can refer the BC35-G NB-IoTModuleAT 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/]]583 +AT+<CMD>=<value>: Set the value 485 485 486 - [[image:image-20220907171221-23.png]]585 +AT+<CMD>=? : Get the value 487 487 488 -**4. Using the AT Commands** 489 489 490 - **4.1AccessATCommands**588 +(% style="color:#037691" %)**General Commands** 491 491 492 - Seethislinkfor detail:[[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]590 +AT : Attention 493 493 494 -AT +<CMD>?:Helpon <CMD>592 +AT? : Short Help 495 495 496 -AT +<CMD>:Run<CMD>594 +ATZ : MCU Reset 497 497 498 -AT+ <CMD>=<value>Set thevalue596 +AT+TDC : Application Data Transmission Interval 499 499 500 -AT+ <CMD>=?Getthe value598 +AT+CFG : Print all configurations 501 501 502 - **GeneralCommands**600 +AT+CFGMOD : Working mode selection 503 503 504 -AT : Attention602 +AT+INTMOD : Set the trigger interrupt mode 505 505 506 -AT ?: Short Help604 +AT+5VT : Set extend the time of 5V power 507 507 508 -AT ZMCUReset606 +AT+PRO : Choose agreement 509 509 510 -AT+ TDC: ApplicationDataTransmissionInterval608 +AT+RXDL: Extend the sending and receiving time 511 511 512 -AT+ CFGPrintall configurations610 +AT+SERVADDR : Server Address 513 513 514 -AT+ CFGMOD:Workingmode selection612 +AT+APN : Get or set the APN 515 515 516 -AT+ INTMODSet theriggerinterrupt mode614 +AT+FBAND : Get or Set whether to automatically modify the frequency band 517 517 518 -AT+ 5VTSetextendthetimeof5V power616 +AT+DNSCFG : Get or Set DNS Server 519 519 520 -AT+ PRO: Choose agreement618 +AT+GETSENSORVALUE : Returns the current sensor measurement 521 521 522 -AT+R XDL: Extendthesending andreceivingtime620 +AT+TR : Get or Set record time" 523 523 524 -AT+ SERVADDR: ServerAddress622 +AT+NOUD : Get or Set the number of data to be uploaded 525 525 526 -AT+ TR:GetorSetrecord time"624 +AT+CDP : Read or Clear cached data 527 527 626 +AT+TEMPALARM : Get or Set alarm of temp 528 528 529 -AT+ NOUD: Get or Setthe number of datatobeuploaded628 +AT+HUMALARM : Get or Set alarm of humidity 530 530 531 531 532 - AT+CDP: Reador Clearcached data631 +(% style="color:#037691" %)**COAP Management** 533 533 633 +AT+URI : Resource parameters 534 534 535 -AT+TEMPALARM : Get or Set alarm of temp 536 536 537 - AT+HUMALARM: GetSetalarmof PH636 +(% style="color:#037691" %)**MQTT Management** 538 538 638 +AT+CLIENT : Get or Set MQTT client 539 539 540 - **COAPManagement**640 +AT+UNAME : Get or Set MQTT Username 541 541 542 -AT+ URIResource parameters642 +AT+PWD : Get or Set MQTT password 543 543 544 - **UDPManagement**644 +AT+PUBTOPIC : Get or Set MQTT publish topic 545 545 546 -AT+C FM:Uploadconfirmationmode (only valid for UDP)646 +AT+SUBTOPIC : Get or Set MQTT subscription topic 547 547 548 -**MQTT Management** 549 549 550 - AT+CLIENT: Get or Set MQTT client649 +(% style="color:#037691" %)**Information** 551 551 552 -AT+ UNAME: GetSetMQTT Username651 +AT+FDR : Factory Data Reset 553 553 554 -AT+PWD GetorSetMQTT password653 +AT+PWORD : Serial Access Password 555 555 556 -AT+PUBTOPIC : Get or Set MQTT publish topic 557 557 558 - AT+SUBTOPIC: Get or Set MQTTsubscription topic656 += 5. FAQ = 559 559 560 - **Information**658 +== 5.1 How to Upgrade Firmware == 561 561 562 -AT+FDR : Factory Data Reset 563 563 564 - AT+PWORD:SerialAccessPassword661 +User can upgrade the firmware for 1) bug fix, 2) new feature release. 565 565 566 - **5.FAQ**663 +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]] 567 567 568 -**5.1 How to Upgrade Firmware** 569 569 570 - User canupgrade thefirmwarefor1)bugfix,2)newfeaturerelease.666 +(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 571 571 572 -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]] 573 573 574 - **Notice,**NLMS01**and **NLMS01 **share the same motherboard. Theyuse the same connectionand method to update.**669 += 6. Trouble Shooting = 575 575 576 - **6.TroubleShooting**671 +== 6.1 Connection problem when uploading firmware == 577 577 578 -**6.1 Connection problem when uploading firmware** 579 579 580 580 **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]] 581 581 582 -**6.2 AT Command input doesn't work** 583 583 584 - Inthe 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 sendingout the command.Some serialtooldoesn'tsend **ENTER**while press the sendkey,user need to add ENTER in their string.677 +== 6.2 AT Command input doesn't work == 585 585 586 -**7. Order Info** 587 587 680 +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. 681 + 682 + 683 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 684 + 685 + 686 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 687 + 688 + 689 +== 6.4 Possible reasons why the device is unresponsive: == 690 + 691 + 692 +1. Check whether the battery voltage is lower than 2.8V 693 +2. Check whether the jumper of the device is correctly connected 694 + 695 +[[image:image-20240330175629-2.png]] 696 +3. Check whether the switch here of the device is at the ISP(The switch can operate normally only when it is in RUN) 697 + 698 + 699 +[[image:image-20240330175554-1.png]] 700 + 701 += 7. Order Info = 702 + 703 + 588 588 Part Number**:** NLMS01 589 589 590 -**8. Packing Info** 591 591 592 - **PackageIncludes**:707 += 8. Packing Info = 593 593 709 + 710 +(% style="color:#037691" %)**Package Includes:** 711 + 594 594 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 595 595 596 -**Dimension and weight**: 714 +(% style="color:#037691" %)**Dimension and weight**: 597 597 598 598 * Device Size: cm 599 599 * Device Weight: g ... ... @@ -600,12 +600,10 @@ 600 600 * Package Size / pcs : cm 601 601 * Weight / pcs : g 602 602 721 += 9. Support = 603 603 604 -**9. Support** 605 605 606 606 * 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. 607 607 * 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]] 608 608 609 609 610 - 611 -
- image-20220913090720-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +224.9 KB - Content
- image-20221009001002-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content
- image-20240330175554-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +445.4 KB - Content
- image-20240330175629-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +445.4 KB - Content