Last modified by Mengting Qiu on 2024/04/02 16:54
<
From version < 36.1 >
edited by Edwin Chen
on 2022/10/09 00:08
To version < 32.1 >
edited by David Huang
on 2022/09/08 09:49
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.David
Content
... ... @@ -7,62 +7,76 @@
7 7  
8 8  
9 9  
10 -= 1.  Introduction =
10 += 1. Introduction =
11 11  
12 +== 1.1 ​What is NLMS01 Leaf Moisture Sensor ==
12 12  
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.
15 15  
16 -The Dragino NLMS01 is a (% style="color:blue" %)**NB-IOT Leaf Moisture Sensor**(%%) for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof.
17 +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.
17 17  
18 -NLMS01 detects leaf's(% style="color:blue" %)** moisture and temperature use FDR method**(%%), it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy.
19 -
20 20  NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
21 -\\NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
22 -\\NLMS01 is powered by  (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method).
23 -\\To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from local operator and install NLMS01 to get NB-IoT network connection.
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
24 24  
25 -
26 26  ​[[image:image-20220907171221-2.png]]
27 27  
28 -
29 29  ​ [[image:image-20220907171221-3.png]]
30 30  
28 +== ​1.2 Features ==
31 31  
30 +* (((
31 +NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
32 +)))
33 +* (((
34 +Monitor Leaf moisture
35 +)))
32 32  
33 -== ​1.2  Features ==
37 +* (((
38 + Monitor Leaf temperature
39 +)))
34 34  
35 -
36 -* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
37 -* Monitor Leaf moisture
38 -* Monitor Leaf temperature
39 -* Moisture and Temperature alarm function
40 -* Monitor Battery Level
41 -* Uplink on periodically
42 -* Downlink to change configure
43 -* IP66 Waterproof Enclosure
44 -* IP67 rate for the Sensor Probe
45 -* Ultra-Low Power consumption
46 -* AT Commands to change parameters
47 -* Micro SIM card slot for NB-IoT SIM
48 -* 8500mAh Battery for long term use
49 -
50 -(((
51 -
52 -
53 -
54 -
41 +* (((
42 +Moisture and Temperature alarm function
55 55  )))
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 +)))
56 56  
57 57  == 1.3  Specification ==
58 58  
74 +**Common DC Characteristics:**
59 59  
60 -(% style="color:#037691" %)**Common DC Characteristics:**
61 -
62 62  * Supply Voltage: 2.1v ~~ 3.6v
63 63  * Operating Temperature: -40 ~~ 85°C
64 64  
65 -(% style="color:#037691" %)**NB-IoT Spec:**
79 +**NB-IoT Spec:**
66 66  
67 67  * - B1 @H-FDD: 2100MHz
68 68  * - B3 @H-FDD: 1800MHz
... ... @@ -71,10 +71,10 @@
71 71  * - B20 @H-FDD: 800MHz
72 72  * - B28 @H-FDD: 700MHz
73 73  
74 -== 1.4  Probe Specification ==
88 +== 1.4 Probe Specification ==
75 75  
76 76  
77 -(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface**
91 +**Leaf Moisture: percentage of water drop over total leaf surface**
78 78  
79 79  * Range 0-100%
80 80  * Resolution: 0.1%
... ... @@ -82,7 +82,7 @@
82 82  * IP67 Protection
83 83  * Length: 3.5 meters
84 84  
85 -(% style="color:#037691" %)**Leaf Temperature:**
99 +**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 ​ Applications ==
107 +== 1.5 ​Applications ==
94 94  
95 -
96 96  * Smart Agriculture
97 97  
98 -== 1.6  Pin mapping and power on ==
111 +== 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,114 +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 server
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
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  
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.
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 AT Commands, user can use a USB to TTL adapter to connect to NLMS01 and use AT Commands to configure it, as below.
153 +**Connection:**
156 156  
155 + USB TTL GND <~-~-~-~-> GND
157 157  
158 -(% style="color:blue" %)**Connection:**
157 + USB TTL TXD <~-~-~-~-> UART_RXD
159 159  
160 -**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)**
159 + 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**
163 +* Baud:  **9600**
164 +* Data bits:** 8**
165 +* Stop bits: **1**
166 +* Parity:  **None**
167 +* 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.
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.
176 176  
177 -​[[image:image-20220913090720-1.png]]
171 +​[[image:image-20220907171221-8.png]]
178 178  
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]]
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  
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/]]
186 186  
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/]]
179 +**Use below commands:**
188 188  
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
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 196  For parameter description, please refer to AT command set
197 197  
198 198  [[image:image-20220907171221-9.png]]
199 199  
189 +After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server.
200 200  
201 -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.
202 -
203 203  [[image:image-20220907171221-10.png]] ​
204 204  
205 -
206 -
207 207  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
208 208  
209 -
210 210  This feature is supported since firmware version v1.0.1
211 211  
212 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
213 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601     ** (%%) ~/~/  to set UDP server address and port
214 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
197 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
198 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
199 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
215 215  
216 216  ​ [[image:image-20220907171221-11.png]]
217 217  
218 -
219 219  [[image:image-20220907171221-12.png]]
220 220  
221 221  ​
222 222  
223 -
224 224  === 2.2.6 Use MQTT protocol to uplink data ===
225 225  
226 -
227 227  This feature is supported since firmware version v110
228 228  
229 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
230 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
231 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
232 -* (% style="color:#037691" %)**AT+UNAME=UNAME                        **(%%)** **~/~/  Set the username of MQTT
233 -* (% style="color:#037691" %)**AT+PWD=PWD                            **(%%)** **~/~/  Set the password of MQTT
234 -* (% style="color:#037691" %)**AT+PUBTOPIC=PUB                    ** (%%) ~/~/  Set the sending topic of MQTT
235 -* (% style="color:#037691" %)**AT+SUBTOPIC=SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
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                               **~/~/Set the username of MQTT
215 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
216 +* **AT+PUBTOPIC=PUB                    **~/~/Set the sending topic of MQTT
217 +* **AT+SUBTOPIC=SUB          ** ~/~/Set the subscription topic of MQTT
236 236  
237 237  ​ [[image:image-20220907171221-13.png]]
238 238  
239 -
240 -
241 241  [[image:image-20220907171221-14.png]]
242 242  
243 243  ​
... ... @@ -244,103 +244,79 @@
244 244  
245 245  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.
246 246  
247 -
248 -
249 249  === 2.2.7 Use TCP protocol to uplink data ===
250 250  
251 -
252 252  This feature is supported since firmware version v110
253 253  
254 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
255 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  to set TCP server address and port
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
256 256  
257 257  ​ [[image:image-20220907171221-15.png]]
258 258  
259 -
260 -
261 261  [[image:image-20220907171221-16.png]]
262 262  
263 263  ​
264 264  
265 -
266 266  === 2.2.8 Change Update Interval ===
267 267  
268 -
269 269  User can use below command to change the **uplink interval**.
270 270  
271 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
244 +* **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hour)
272 272  
273 -(% 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).**
246 +**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).**
274 274  
275 275  
276 -
277 277  == 2.3  Uplink Payload ==
278 278  
279 -
280 280  In this mode, uplink payload includes 87 bytes in total by default.
281 281  
282 282  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.
283 283  
255 +|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4
256 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Time stamp|Leaf Temperature|Leaf moisture|Time stamp  .....
284 284  
285 -(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %)
286 -|(% 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
287 -|(% 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  .....
288 -
289 289  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data.
290 290  
291 -
292 292  [[image:image-20220907171221-17.png]]
293 293  
294 -
295 295  The payload is ASCII string, representative same HEX:
296 296  
297 -**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__//(%%)**
264 +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:
298 298  
299 -where:
300 -
301 -* Device ID: 0xf868411056754138 = f868411056754138
302 -* Version: 0x0064=100=1.0.0
303 -* BAT: 0x0c78 = 3192 mV = 3.192V
304 -* Singal: 0x17 = 23
305 -* Mod: 0x01 = 1
306 -* Interrupt: 0x00= 0
266 +* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
267 +* (% style="color:blue" %)Version: 0x0064=100=1.0.0
268 +* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
269 +* (% style="color:red" %)Singal: 0x17 = 23
270 +* (% style="color:blue" %)Mod: 0x01 = 1
271 +* (% style="color:green" %)Interrupt: 0x00= 0
307 307  * Leaf moisture: 0x0225= 549 = 54.9%
308 308  * Leaf Temperature:0x010B =267=26.7 °C
309 309  * Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])
310 310  * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb
311 -* 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
276 +* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
312 312  
313 313  == 2.4  Payload Explanation and Sensor Interface ==
314 314  
315 -
316 316  === 2.4.1  Device ID ===
317 317  
318 -
319 319  By default, the Device ID equal to the last 15 bits of IMEI.
320 320  
321 -User can use (% style="color:#037691" %)**AT+DEUI**(%%) to set Device ID
284 +User can use **AT+DEUI** to set Device ID
322 322  
286 +**Example:**
323 323  
324 -(% style="color:blue" %)**Example**:
325 -
326 326  AT+DEUI=868411056754138
327 327  
328 328  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
329 329  
330 -
331 -
332 332  === 2.4.2  Version Info ===
333 333  
334 -
335 335  Specify the software version: 0x64=100, means firmware version 1.00.
336 336  
337 337  For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
338 338  
339 -
340 -
341 341  === 2.4.3  Battery Info ===
342 342  
343 -
344 344  Check the battery voltage for NLMS01.
345 345  
346 346  Ex1: 0x0B45 = 2885mV
... ... @@ -347,16 +347,12 @@
347 347  
348 348  Ex2: 0x0B49 = 2889mV
349 349  
350 -
351 -
352 352  === 2.4.4  Signal Strength ===
353 353  
354 -
355 355  NB-IoT Network signal Strength.
356 356  
310 +**Ex1: 0x1d = 29**
357 357  
358 -(% style="color:blue" %)**Ex1: 0x1d = 29**
359 -
360 360  **0**  -113dBm or less
361 361  
362 362  **1**  -111dBm
... ... @@ -367,49 +367,37 @@
367 367  
368 368  **99**    Not known or not detectable
369 369  
370 -
371 -
372 372  === 2.4.5  Leaf moisture ===
373 373  
324 +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**.
374 374  
375 -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.
326 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is
376 376  
377 -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
328 +**0229(H) = 549(D) /100 = 54.9.**
378 378  
379 -(% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**
380 -
381 -
382 -
383 383  === 2.4.6  Leaf Temperature ===
384 384  
332 +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
385 385  
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
334 +**Example**:
387 387  
388 -(% style="color:blue" %)**Example**:
336 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
389 389  
390 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
338 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
391 391  
392 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
393 -
394 -
395 -
396 396  === 2.4.7  Timestamp ===
397 397  
398 -
399 399  Time stamp : 0x6315537b =1662342011
400 400  
401 401  Convert Unix timestamp to time 2022-9-5 9:40:11.
402 402  
403 -
404 -
405 405  === 2.4.8  Digital Interrupt ===
406 406  
348 +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.
407 407  
408 -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.
409 -
410 410  The command is:
411 411  
412 -(% 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]])**.**
352 +**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]])**.**
413 413  
414 414  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.
415 415  
... ... @@ -419,34 +419,27 @@
419 419  
420 420  0x(01): Interrupt Uplink Packet.
421 421  
422 -
423 -
424 424  === 2.4.9  ​+5V Output ===
425 425  
426 -
427 427  NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
428 428  
429 429  The 5V output time can be controlled by AT Command.
430 430  
431 -(% style="color:blue" %)**AT+5VT=1000**
368 +**AT+5VT=1000**
432 432  
433 433  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
434 434  
435 435  
436 -
437 437  == 2.5  Downlink Payload ==
438 438  
439 -
440 440  By default, NLMS01 prints the downlink payload to console port.
441 441  
442 442  [[image:image-20220907171221-18.png]] ​
443 443  
379 +**Examples:**
444 444  
445 -(% style="color:blue" %)**Examples:**
381 +* **Set TDC**
446 446  
447 -
448 -* (% style="color:#037691" %)**Set TDC**
449 -
450 450  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
451 451  
452 452  Payload:    01 00 00 1E    TDC=30S
... ... @@ -453,23 +453,16 @@
453 453  
454 454  Payload:    01 00 00 3C    TDC=60S
455 455  
389 +* **Reset**
456 456  
457 -
458 -* (% style="color:#037691" %)**Reset**
459 -
460 460  If payload = 0x04FF, it will reset the NLMS01
461 461  
393 +* **INTMOD**
462 462  
463 -
464 -* (% style="color:#037691" %)**INTMOD**
465 -
466 466  Downlink Payload: 06000003, Set AT+INTMOD=3
467 467  
468 -
469 -
470 470  == 2.6  ​LED Indicator ==
471 471  
472 -
473 473  The NLMS01 has an internal LED which is to show the status of different state.
474 474  
475 475  * 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)
... ... @@ -477,23 +477,18 @@
477 477  * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds.
478 478  * For each uplink probe, LED will be on for 500ms.
479 479  
480 -== 2.7  Installation ==
406 +== 2.7 Installation ==
481 481  
482 -
483 483  NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor.
484 484  
485 -
486 486  [[image:image-20220907171221-19.png]]
487 487  
412 +== 2.8 Moisture and Temperature alarm function ==
488 488  
414 +➢ AT Command:
489 489  
490 -== 2.8  Moisture and Temperature alarm function ==
416 +AT+ HUMALARM =min,max
491 491  
492 -
493 -(% style="color:blue" %)**➢ AT Command:**
494 -
495 -(% style="color:#037691" %)**AT+ HUMALARM =min,max**
496 -
497 497  ² When min=0, and max≠0, Alarm higher than max
498 498  
499 499  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -500,9 +500,8 @@
500 500  
501 501  ² When min≠0 and max≠0, Alarm higher than max or lower than min
502 502  
424 +Example:
503 503  
504 -(% style="color:blue" %)**Example:**
505 -
506 506  AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50.
507 507  
508 508  AT+ TEMPALARM=min,max
... ... @@ -513,53 +513,41 @@
513 513  
514 514  ² When min≠0 and max≠0, Alarm higher than max or lower than min
515 515  
436 +Example:
516 516  
517 -(% style="color:blue" %)**Example:**
518 -
519 519  AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
520 520  
521 521  
441 +== 2.9 Set the number of data to be uploaded and the recording time ==
522 522  
523 -== 2.9  Set the number of data to be uploaded and the recording time ==
443 +➢ AT Command:
524 524  
445 +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)
525 525  
526 -(% style="color:blue" %)**➢ AT Command:**
447 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
527 527  
528 -* (% 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)
529 -* (% 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.
449 +== 2.10 Read or Clear cached data ==
530 530  
531 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
451 +➢ AT Command:
532 532  
533 -[[image:image-20221009000513-1.png||height="732" width="1018"]]
453 +AT+CDP    ~/~/ Read cached data
534 534  
535 -
536 -== 2.10  Read or Clear cached data ==
537 -
538 -
539 -(% style="color:blue" %)**➢ AT Command:**
540 -
541 -* (% style="color:#037691" %)**AT+CDP**      (%%) ~/~/  Read cached data
542 -* (% style="color:#037691" %)**AT+CDP=0  ** (%%) ~/~/  Clear cached data
543 -
544 544  [[image:image-20220907171221-20.png]]
545 545  
546 546  
458 +AT+CDP=0    ~/~/ Clear cached data
547 547  
460 +
548 548  == 2.11  ​Firmware Change Log ==
549 549  
463 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
550 550  
551 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]
465 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
552 552  
553 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
554 -
555 -
556 -
557 557  == 2.12  ​Battery Analysis ==
558 558  
559 -
560 560  === 2.12.1  ​Battery Type ===
561 561  
562 -
563 563  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.
564 564  
565 565  The battery is designed to last for several years depends on the actually use environment and update interval. 
... ... @@ -572,18 +572,15 @@
572 572  
573 573  [[image:image-20220907171221-21.png]] ​
574 574  
575 -
576 -
577 577  === 2.12.2  Power consumption Analyze ===
578 578  
579 -
580 580  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.
581 581  
582 582  Instruction to use as below:
583 583  
584 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
489 +**Step 1:  **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
585 585  
586 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
491 +**Step 2: ** Open it and choose
587 587  
588 588  * Product Model
589 589  * Uplink Interval
... ... @@ -593,171 +593,136 @@
593 593  
594 594  [[image:image-20220907171221-22.jpeg]] ​
595 595  
596 -
597 597  === 2.12.3  ​Battery Note ===
598 598  
599 -
600 600  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.
601 601  
602 -
603 -
604 604  === 2.12.4  Replace the battery ===
605 605  
606 -
607 607  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).
608 608  
609 -
610 -
611 611  = 3. ​ Access NB-IoT Module =
612 612  
613 -
614 614  Users can directly access the AT command set of the NB-IoT module.
615 615  
616 616  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/]] 
617 617  
618 -
619 619  [[image:image-20220907171221-23.png]] ​
620 620  
621 -
622 -
623 623  = 4.  Using the AT Commands =
624 624  
625 -
626 626  == 4.1  Access AT Commands ==
627 627  
628 -
629 629  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]]
630 630  
631 -AT+<CMD>?  :  Help on <CMD>
523 +AT+<CMD>?  : Help on <CMD>
632 632  
633 -AT+<CMD>  :  Run <CMD>
525 +AT+<CMD>         : Run <CMD>
634 634  
635 -AT+<CMD>=<value>:  Set the value
527 +AT+<CMD>=<value> : Set the value
636 636  
637 -AT+<CMD>=?  :  Get the value
529 +AT+<CMD>=?  : Get the value
638 638  
531 +**General Commands**      
639 639  
640 -(% style="color:#037691" %)**General Commands**      
533 +AT  : Attention       
641 641  
642 -AT  :  Attention       
535 +AT?  : Short Help     
643 643  
644 -AT?  :  Short Help     
537 +ATZ  : MCU Reset    
645 645  
646 -ATZ  :  MCU Reset    
539 +AT+TDC  : Application Data Transmission Interval
647 647  
648 -AT+TDC  :  Application Data Transmission Interval
541 +AT+CFG  : Print all configurations
649 649  
650 -AT+CFG  :  Print all configurations
543 +AT+CFGMOD           : Working mode selection
651 651  
652 -AT+CFGMOD  :  Working mode selection
545 +AT+INTMOD            : Set the trigger interrupt mode
653 653  
654 -AT+INTMOD  :  Set the trigger interrupt mode
547 +AT+5VT  : Set extend the time of 5V power  
655 655  
656 -AT+5VT  :  Set extend the time of 5V power  
549 +AT+PRO  : Choose agreement
657 657  
658 -AT+PRO :  Choose agreement
551 +AT+RXDL  : Extend the sending and receiving time
659 659  
660 -AT+RXDL:  Extend the sending and receiving time
553 +AT+SERVADDR  : Server Address
661 661  
662 -AT+SERVADDR :  Server Address
555 +AT+APN     : Get or set the APN
663 663  
664 -AT+APN :  Get or set the APN
557 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
665 665  
666 -AT+FBAND :  Get or Set whether to automatically modify the frequency band
559 +AT+DNSCFG  : Get or Set DNS Server
667 667  
668 -AT+DNSCFG : Get or Set DNS Server
669 -
670 670  AT+GETSENSORVALUE   : Returns the current sensor measurement
671 671  
672 -AT+TR :  Get or Set record time"
563 +AT+TR      : Get or Set record time"
673 673  
674 -AT+NOUD :  Get or Set the number of data to be uploaded
565 +AT+NOUD      : Get or Set the number of data to be uploaded
675 675  
676 -AT+CDP :  Read or Clear cached data
567 +AT+CDP     : Read or Clear cached data
677 677  
678 -AT+TEMPALARM :  Get or Set alarm of temp
569 +AT+TEMPALARM      : Get or Set alarm of temp
679 679  
680 -AT+HUMALARM :  Get or Set alarm of humidity
571 +AT+HUMALARM     : Get or Set alarm of PH
681 681  
682 682  
683 -(% style="color:#037691" %)**COAP Management**      
574 +**COAP Management**      
684 684  
685 -AT+URI :  Resource parameters
576 +AT+URI            : Resource parameters
686 686  
578 +**UDP Management**
687 687  
688 -(% style="color:#037691" %)**UDP Management**
580 +AT+CFM          : Upload confirmation mode (only valid for UDP)
689 689  
690 -AT+CFM :  Upload confirmation mode (only valid for UDP)
582 +**MQTT Management**
691 691  
584 +AT+CLIENT               : Get or Set MQTT client
692 692  
693 -(% style="color:#037691" %)**MQTT Management**
586 +AT+UNAME  : Get or Set MQTT Username
694 694  
695 -AT+CLIENT  :  Get or Set MQTT client
588 +AT+PWD                  : Get or Set MQTT password
696 696  
697 -AT+UNAME  : Get or Set MQTT Username
590 +AT+PUBTOPIC  : Get or Set MQTT publish topic
698 698  
699 -AT+PWD  :  Get or Set MQTT password
592 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
700 700  
701 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
594 +**Information**          
702 702  
703 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
596 +AT+FDR  : Factory Data Reset
704 704  
598 +AT+PWORD  : Serial Access Password
705 705  
706 -(% style="color:#037691" %)**Information**          
707 -
708 -AT+FDR :  Factory Data Reset
709 -
710 -AT+PWORD :  Serial Access Password
711 -
712 -
713 -
714 714  = ​5.  FAQ =
715 715  
716 -
717 717  == 5.1 ​ How to Upgrade Firmware ==
718 718  
719 -
720 720  User can upgrade the firmware for 1) bug fix, 2) new feature release.
721 721  
722 722  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]]
723 723  
608 +**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.**
724 724  
725 -(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.**
726 -
727 -
728 -
729 729  = 6.  Trouble Shooting =
730 730  
731 -
732 732  == 6.1  ​Connection problem when uploading firmware ==
733 733  
734 -
735 735  **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]]
736 736  
737 -
738 -
739 739  == 6.2  AT Command input doesn't work ==
740 740  
618 +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.
741 741  
742 -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.
743 -
744 -
745 -
746 746  = 7. ​ Order Info =
747 747  
748 -
749 749  Part Number**:** NLMS01
750 750  
751 -
752 -
753 753  = 8.  Packing Info =
754 754  
626 +**Package Includes**:
755 755  
756 -(% style="color:#037691" %)**Package Includes:**
757 -
758 758  * NLMS01 NB-IoT Leaf Moisture Sensor x 1
759 759  
760 -(% style="color:#037691" %)**Dimension and weight**:
630 +**Dimension and weight**:
761 761  
762 762  * Device Size: cm
763 763  * Device Weight: g
... ... @@ -766,7 +766,6 @@
766 766  
767 767  = 9.  Support =
768 768  
769 -
770 770  * 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.
771 771  * 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]]
772 772  
image-20220913090720-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -224.9 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0