Wiki source code of LLMS01-LoRaWAN Leaf Moisture Sensor User Manual
Last modified by Bei Jinggeng on 2024/03/30 17:55
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% style="text-align:center" %) | ||
2 | [[image:image-20220614145607-2.jpeg||height="576" width="576"]] | ||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
9 | |||
10 | |||
11 | |||
12 | **Table of Contents:** | ||
13 | |||
14 | {{toc/}} | ||
15 | |||
16 | |||
17 | |||
18 | |||
19 | |||
20 | |||
21 | |||
22 | |||
23 | = 1. Introduction = | ||
24 | |||
25 | == 1.1 What is LoRaWAN Leaf Moisture Sensor == | ||
26 | |||
27 | |||
28 | ((( | ||
29 | The Dragino LLMS01 is a (% style="color:blue" %)**LoRaWAN Leaf Moisture Sensor**(%%) for IoT of Agriculture. It is designed to measure the (% style="color:blue" %)**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. | ||
30 | ))) | ||
31 | |||
32 | ((( | ||
33 | LLMS01 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. | ||
34 | ))) | ||
35 | |||
36 | ((( | ||
37 | The LoRa wireless technology used in LLMS01 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. | ||
38 | ))) | ||
39 | |||
40 | ((( | ||
41 | LLMS01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years. | ||
42 | ))) | ||
43 | |||
44 | ((( | ||
45 | Each LLMS01 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on. | ||
46 | ))) | ||
47 | |||
48 | |||
49 | [[image:1654597284339-263.png]] | ||
50 | |||
51 | |||
52 | |||
53 | == 1.2 Features == | ||
54 | |||
55 | |||
56 | * LoRaWAN 1.0.3 Class A | ||
57 | * Ultra-low power consumption | ||
58 | * Monitor Leaf moisture | ||
59 | * Monitor Leaf temperature | ||
60 | * Monitor Battery Level | ||
61 | * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865 | ||
62 | * AT Commands to change parameters | ||
63 | * Uplink on periodically | ||
64 | * Downlink to change configure | ||
65 | * IP66 Waterproof Enclosure | ||
66 | * IP67 rate for the Sensor Probe | ||
67 | * 8500mAh Battery for long term use | ||
68 | |||
69 | == 1.3 Probe Specification == | ||
70 | |||
71 | |||
72 | (% style="color:#4f81bd" %)**Leaf Moisture: percentage of water drop over total leaf surface** | ||
73 | |||
74 | * Range 0-100% | ||
75 | * Resolution: 0.1% | ||
76 | * Accuracy: ±3%(0-50%);±6%(>50%) | ||
77 | * IP67 Protection | ||
78 | * Length: 3.5 meters | ||
79 | |||
80 | (% style="color:#4f81bd" %)**Leaf Temperature:** | ||
81 | |||
82 | * Range -50℃~80℃ | ||
83 | * Resolution: 0.1℃ | ||
84 | * Accuracy: <±0.5℃(-10℃~70℃),<±1.0℃ (others) | ||
85 | * IP67 Protection | ||
86 | * Length: 3.5 meters | ||
87 | |||
88 | == 1.4 Applications == | ||
89 | |||
90 | |||
91 | * Smart Agriculture | ||
92 | |||
93 | == 1.5 Pin mapping and power on == | ||
94 | |||
95 | |||
96 | [[image:1654597566554-371.png]] | ||
97 | |||
98 | |||
99 | = 2. Configure LLMS01 to connect to LoRaWAN network = | ||
100 | |||
101 | == 2.1 How it works == | ||
102 | |||
103 | |||
104 | ((( | ||
105 | The LLMS01 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LLMS01. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes. | ||
106 | ))) | ||
107 | |||
108 | ((( | ||
109 | In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H5.UseATCommand"]]to set the keys in the LLMS01. | ||
110 | ))) | ||
111 | |||
112 | |||
113 | == 2.2 Quick guide to connect to LoRaWAN server (OTAA) == | ||
114 | |||
115 | |||
116 | ((( | ||
117 | Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example. | ||
118 | |||
119 | |||
120 | ))) | ||
121 | |||
122 | ((( | ||
123 | [[image:1654597672224-371.png]] | ||
124 | |||
125 | |||
126 | ))) | ||
127 | |||
128 | ((( | ||
129 | The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server. | ||
130 | |||
131 | |||
132 | ))) | ||
133 | |||
134 | ((( | ||
135 | (% style="color:blue" %)**Step 1**(%%)**: Create a device in TTN with the OTAA keys from LLMS01.** | ||
136 | ))) | ||
137 | |||
138 | ((( | ||
139 | Each LLMS01 is shipped with a sticker with the default device EUI as below: | ||
140 | ))) | ||
141 | |||
142 | [[image:image-20230426084806-1.png||height="235" width="506"]] | ||
143 | |||
144 | (% style="display:none" %) (%%) | ||
145 | |||
146 | You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot: | ||
147 | |||
148 | |||
149 | **Register the device** | ||
150 | |||
151 | |||
152 | [[image:1654592600093-601.png]] | ||
153 | |||
154 | |||
155 | |||
156 | **Add APP EUI and DEV EUI** | ||
157 | |||
158 | [[image:1654592619856-881.png]] | ||
159 | |||
160 | |||
161 | |||
162 | **Add APP EUI in the application** | ||
163 | |||
164 | [[image:1654592632656-512.png]] | ||
165 | |||
166 | |||
167 | |||
168 | **Add APP KEY** | ||
169 | |||
170 | [[image:1654592653453-934.png]] | ||
171 | |||
172 | |||
173 | (% style="color:blue" %)**Step 2**(%%): **Power on LLMS01** | ||
174 | |||
175 | Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position). | ||
176 | |||
177 | [[image:1654649435394-787.png]] | ||
178 | |||
179 | |||
180 | ((( | ||
181 | (% style="color:blue" %)**Step 3**(%%)**: The LLMS01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.** | ||
182 | |||
183 | |||
184 | ))) | ||
185 | |||
186 | [[image:1654649500522-138.png]] | ||
187 | |||
188 | |||
189 | == 2.3 Uplink Payload == | ||
190 | |||
191 | |||
192 | ((( | ||
193 | LLMS01 will uplink payload via LoRaWAN with below payload format: | ||
194 | ))) | ||
195 | |||
196 | ((( | ||
197 | Uplink payload includes in total 11 bytes. | ||
198 | ))) | ||
199 | |||
200 | ((( | ||
201 | Normal uplink payload: | ||
202 | ))) | ||
203 | |||
204 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
205 | |=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)((( | ||
206 | **Size(bytes)** | ||
207 | )))|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)2|=(% style="width: 62.5px;background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**2**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1**|=(% style="background-color:#4F81BD;color:white" %)**1** | ||
208 | |(% style="width:62.5px" %)Value|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)((( | ||
209 | [[Temperature (Optional)>>||anchor="H2.3.2DS18B20Temperaturesensor"]] | ||
210 | )))|[[ Leaf Moisture>>||anchor="H2.3.3LeafMoisture"]] |[[Leaf Temperature>>||anchor="H2.3.4LeafTemperature"]]|((( | ||
211 | [[Digital Interrupt (Optional)>>||anchor="H2.3.5InterruptPin"]] | ||
212 | )))|Reserve|((( | ||
213 | [[Message Type>>||anchor="H2.3.6MessageType"]] | ||
214 | ))) | ||
215 | |||
216 | [[image:1654649531303-864.png]] | ||
217 | |||
218 | |||
219 | === 2.3.1 Battery Info === | ||
220 | |||
221 | |||
222 | Check the battery voltage for LLMS01. | ||
223 | |||
224 | Ex1: 0x0B45 = 2885mV | ||
225 | |||
226 | Ex2: 0x0B49 = 2889mV | ||
227 | |||
228 | |||
229 | === 2.3.2 DS18B20 Temperature sensor === | ||
230 | |||
231 | |||
232 | This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. | ||
233 | |||
234 | |||
235 | **Example**: | ||
236 | |||
237 | If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree | ||
238 | |||
239 | If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
240 | |||
241 | |||
242 | === 2.3.3 Leaf Moisture === | ||
243 | |||
244 | |||
245 | Range: 0 ~~ 100% | ||
246 | |||
247 | **Example:** | ||
248 | |||
249 | (% style="color:#037691" %)**0x0015(H) = 21(D) /10= 2.1%** | ||
250 | |||
251 | |||
252 | === 2.3.4 Leaf Temperature === | ||
253 | |||
254 | |||
255 | Get Leaf Temperature | ||
256 | |||
257 | |||
258 | **Example**: | ||
259 | |||
260 | If payload is: **0105H**: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree | ||
261 | |||
262 | If payload is: **FF3FH** : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. | ||
263 | |||
264 | |||
265 | === 2.3.5 Interrupt Pin === | ||
266 | |||
267 | |||
268 | This data field shows if this packet is generated by interrupt or not. [[Click here>>path:#H3.2SetInterruptMode]] for the hardware and software set up. | ||
269 | |||
270 | |||
271 | **Example:** | ||
272 | |||
273 | 0x00: Normal uplink packet. | ||
274 | |||
275 | 0x01: Interrupt Uplink Packet. | ||
276 | |||
277 | |||
278 | === 2.3.6 Message Type === | ||
279 | |||
280 | |||
281 | ((( | ||
282 | For a normal uplink payload, the message type is always 0x01. | ||
283 | ))) | ||
284 | |||
285 | ((( | ||
286 | Valid Message Type: | ||
287 | ))) | ||
288 | |||
289 | |||
290 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:496px" %) | ||
291 | |=(% style="width: 162px;background-color:#4F81BD;color:white" %)**Message Type Code**|=(% style="width: 162px;background-color:#4F81BD;color:white" %)**Description**|=(% style="width: 172px;background-color:#4F81BD;color:white" %)**Payload** | ||
292 | |(% style="width:160px" %)0x01|(% style="width:161px" %)Normal Uplink|(% style="width:170px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]] | ||
293 | |(% style="width:160px" %)0x02|(% style="width:161px" %)Reply configures info|(% style="width:170px" %)[[Configure Info Payload>>||anchor="H3.3GetFirmwareVersionInfo"]] | ||
294 | |||
295 | === 2.3.7 Decode payload in The Things Network === | ||
296 | |||
297 | |||
298 | While using TTN network, you can add the payload format to decode the payload. | ||
299 | |||
300 | |||
301 | [[image:1654592762713-715.png]] | ||
302 | |||
303 | ((( | ||
304 | ((( | ||
305 | The payload decoder function for TTN is here: | ||
306 | ))) | ||
307 | |||
308 | ((( | ||
309 | LLMS01 TTN Payload Decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]] | ||
310 | ))) | ||
311 | ))) | ||
312 | |||
313 | |||
314 | == 2.4 Uplink Interval == | ||
315 | |||
316 | |||
317 | The LLMS01 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]] | ||
318 | |||
319 | |||
320 | == 2.5 Show Data in DataCake IoT Server == | ||
321 | |||
322 | |||
323 | ((( | ||
324 | [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps: | ||
325 | ))) | ||
326 | |||
327 | ((( | ||
328 | |||
329 | ))) | ||
330 | |||
331 | ((( | ||
332 | (% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.** | ||
333 | ))) | ||
334 | |||
335 | ((( | ||
336 | (% style="color:blue" %)**Step 2**(%%)**: To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:** | ||
337 | ))) | ||
338 | |||
339 | |||
340 | [[image:1654592790040-760.png]] | ||
341 | |||
342 | |||
343 | [[image:1654592800389-571.png]] | ||
344 | |||
345 | |||
346 | (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.** | ||
347 | |||
348 | (% style="color:blue" %)**Step 4**(%%)**: Create LLMS01 product.** | ||
349 | |||
350 | |||
351 | [[image:1654592819047-535.png]] | ||
352 | |||
353 | |||
354 | |||
355 | [[image:1654592833877-762.png]] | ||
356 | |||
357 | |||
358 | [[image:1654592856403-259.png]] | ||
359 | |||
360 | |||
361 | ((( | ||
362 | (% style="color:blue" %)**Step 5**(%%)**: add payload decode** | ||
363 | ))) | ||
364 | |||
365 | ((( | ||
366 | Download Datacake decoder from: [[https:~~/~~/www.dropbox.com/sh/53ga86dnhmr6cl8/AACP8ocyOf8k6_10NGAqnNk_a?dl=0>>https://www.dropbox.com/sh/53ga86dnhmr6cl8/AACP8ocyOf8k6_10NGAqnNk_a?dl=0]] | ||
367 | ))) | ||
368 | |||
369 | |||
370 | [[image:image-20220608091736-1.png]] | ||
371 | |||
372 | |||
373 | |||
374 | [[image:image-20220608091810-2.png||height="591" width="1266"]] | ||
375 | |||
376 | |||
377 | [[image:1654651109108-101.png]] | ||
378 | |||
379 | |||
380 | After added, the sensor data arrive TTN, it will also arrive and show in Mydevices. | ||
381 | |||
382 | [[image:1654651120712-832.png]] | ||
383 | |||
384 | |||
385 | == 2.6 Installation == | ||
386 | |||
387 | |||
388 | LLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. | ||
389 | |||
390 | ((( | ||
391 | [[image:image-20220608093428-3.png]] | ||
392 | |||
393 | |||
394 | ))) | ||
395 | |||
396 | == 2.7 Frequency Plans == | ||
397 | |||
398 | |||
399 | ((( | ||
400 | The LLMS01 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets. | ||
401 | ))) | ||
402 | |||
403 | |||
404 | === 2.7.1 EU863-870 (EU868) === | ||
405 | |||
406 | |||
407 | ((( | ||
408 | (% style="color:blue" %)**Uplink:** | ||
409 | ))) | ||
410 | |||
411 | ((( | ||
412 | 868.1 - SF7BW125 to SF12BW125 | ||
413 | ))) | ||
414 | |||
415 | ((( | ||
416 | 868.3 - SF7BW125 to SF12BW125 and SF7BW250 | ||
417 | ))) | ||
418 | |||
419 | ((( | ||
420 | 868.5 - SF7BW125 to SF12BW125 | ||
421 | ))) | ||
422 | |||
423 | ((( | ||
424 | 867.1 - SF7BW125 to SF12BW125 | ||
425 | ))) | ||
426 | |||
427 | ((( | ||
428 | 867.3 - SF7BW125 to SF12BW125 | ||
429 | ))) | ||
430 | |||
431 | ((( | ||
432 | 867.5 - SF7BW125 to SF12BW125 | ||
433 | ))) | ||
434 | |||
435 | ((( | ||
436 | 867.7 - SF7BW125 to SF12BW125 | ||
437 | ))) | ||
438 | |||
439 | ((( | ||
440 | 867.9 - SF7BW125 to SF12BW125 | ||
441 | ))) | ||
442 | |||
443 | ((( | ||
444 | 868.8 - FSK | ||
445 | ))) | ||
446 | |||
447 | ((( | ||
448 | |||
449 | ))) | ||
450 | |||
451 | ((( | ||
452 | (% style="color:blue" %)**Downlink:** | ||
453 | ))) | ||
454 | |||
455 | ((( | ||
456 | Uplink channels 1-9 (RX1) | ||
457 | ))) | ||
458 | |||
459 | ((( | ||
460 | 869.525 - SF9BW125 (RX2 downlink only) | ||
461 | ))) | ||
462 | |||
463 | |||
464 | === 2.7.2 US902-928(US915) === | ||
465 | |||
466 | |||
467 | ((( | ||
468 | Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document. | ||
469 | ))) | ||
470 | |||
471 | ((( | ||
472 | To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join. | ||
473 | ))) | ||
474 | |||
475 | ((( | ||
476 | After Join success, the end node will switch to the correct sub band by: | ||
477 | ))) | ||
478 | |||
479 | * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band | ||
480 | * Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) | ||
481 | |||
482 | === 2.7.3 CN470-510 (CN470) === | ||
483 | |||
484 | |||
485 | ((( | ||
486 | Used in China, Default use CHE=1 | ||
487 | ))) | ||
488 | |||
489 | ((( | ||
490 | (% style="color:blue" %)**Uplink:** | ||
491 | ))) | ||
492 | |||
493 | ((( | ||
494 | 486.3 - SF7BW125 to SF12BW125 | ||
495 | ))) | ||
496 | |||
497 | ((( | ||
498 | 486.5 - SF7BW125 to SF12BW125 | ||
499 | ))) | ||
500 | |||
501 | ((( | ||
502 | 486.7 - SF7BW125 to SF12BW125 | ||
503 | ))) | ||
504 | |||
505 | ((( | ||
506 | 486.9 - SF7BW125 to SF12BW125 | ||
507 | ))) | ||
508 | |||
509 | ((( | ||
510 | 487.1 - SF7BW125 to SF12BW125 | ||
511 | ))) | ||
512 | |||
513 | ((( | ||
514 | 487.3 - SF7BW125 to SF12BW125 | ||
515 | ))) | ||
516 | |||
517 | ((( | ||
518 | 487.5 - SF7BW125 to SF12BW125 | ||
519 | ))) | ||
520 | |||
521 | ((( | ||
522 | 487.7 - SF7BW125 to SF12BW125 | ||
523 | ))) | ||
524 | |||
525 | ((( | ||
526 | |||
527 | ))) | ||
528 | |||
529 | ((( | ||
530 | (% style="color:blue" %)**Downlink:** | ||
531 | ))) | ||
532 | |||
533 | ((( | ||
534 | 506.7 - SF7BW125 to SF12BW125 | ||
535 | ))) | ||
536 | |||
537 | ((( | ||
538 | 506.9 - SF7BW125 to SF12BW125 | ||
539 | ))) | ||
540 | |||
541 | ((( | ||
542 | 507.1 - SF7BW125 to SF12BW125 | ||
543 | ))) | ||
544 | |||
545 | ((( | ||
546 | 507.3 - SF7BW125 to SF12BW125 | ||
547 | ))) | ||
548 | |||
549 | ((( | ||
550 | 507.5 - SF7BW125 to SF12BW125 | ||
551 | ))) | ||
552 | |||
553 | ((( | ||
554 | 507.7 - SF7BW125 to SF12BW125 | ||
555 | ))) | ||
556 | |||
557 | ((( | ||
558 | 507.9 - SF7BW125 to SF12BW125 | ||
559 | ))) | ||
560 | |||
561 | ((( | ||
562 | 508.1 - SF7BW125 to SF12BW125 | ||
563 | ))) | ||
564 | |||
565 | ((( | ||
566 | 505.3 - SF12BW125 (RX2 downlink only) | ||
567 | ))) | ||
568 | |||
569 | |||
570 | === 2.7.4 AU915-928(AU915) === | ||
571 | |||
572 | |||
573 | ((( | ||
574 | Frequency band as per definition in LoRaWAN 1.0.3 Regional document. | ||
575 | ))) | ||
576 | |||
577 | ((( | ||
578 | To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join. | ||
579 | ))) | ||
580 | |||
581 | ((( | ||
582 | |||
583 | ))) | ||
584 | |||
585 | ((( | ||
586 | After Join success, the end node will switch to the correct sub band by: | ||
587 | ))) | ||
588 | |||
589 | * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band | ||
590 | * Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) | ||
591 | |||
592 | === 2.7.5 AS920-923 & AS923-925 (AS923) === | ||
593 | |||
594 | |||
595 | ((( | ||
596 | (% style="color:blue" %)**Default Uplink channel:** | ||
597 | ))) | ||
598 | |||
599 | ((( | ||
600 | 923.2 - SF7BW125 to SF10BW125 | ||
601 | ))) | ||
602 | |||
603 | ((( | ||
604 | 923.4 - SF7BW125 to SF10BW125 | ||
605 | ))) | ||
606 | |||
607 | ((( | ||
608 | |||
609 | ))) | ||
610 | |||
611 | ((( | ||
612 | (% style="color:blue" %)**Additional Uplink Channel**: | ||
613 | ))) | ||
614 | |||
615 | ((( | ||
616 | (OTAA mode, channel added by JoinAccept message) | ||
617 | ))) | ||
618 | |||
619 | ((( | ||
620 | |||
621 | ))) | ||
622 | |||
623 | ((( | ||
624 | (% style="color:blue" %)**AS920~~AS923 for Japan, Malaysia, Singapore**: | ||
625 | ))) | ||
626 | |||
627 | ((( | ||
628 | 922.2 - SF7BW125 to SF10BW125 | ||
629 | ))) | ||
630 | |||
631 | ((( | ||
632 | 922.4 - SF7BW125 to SF10BW125 | ||
633 | ))) | ||
634 | |||
635 | ((( | ||
636 | 922.6 - SF7BW125 to SF10BW125 | ||
637 | ))) | ||
638 | |||
639 | ((( | ||
640 | 922.8 - SF7BW125 to SF10BW125 | ||
641 | ))) | ||
642 | |||
643 | ((( | ||
644 | 923.0 - SF7BW125 to SF10BW125 | ||
645 | ))) | ||
646 | |||
647 | ((( | ||
648 | 922.0 - SF7BW125 to SF10BW125 | ||
649 | ))) | ||
650 | |||
651 | ((( | ||
652 | |||
653 | ))) | ||
654 | |||
655 | ((( | ||
656 | (% style="color:blue" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**: | ||
657 | ))) | ||
658 | |||
659 | ((( | ||
660 | 923.6 - SF7BW125 to SF10BW125 | ||
661 | ))) | ||
662 | |||
663 | ((( | ||
664 | 923.8 - SF7BW125 to SF10BW125 | ||
665 | ))) | ||
666 | |||
667 | ((( | ||
668 | 924.0 - SF7BW125 to SF10BW125 | ||
669 | ))) | ||
670 | |||
671 | ((( | ||
672 | 924.2 - SF7BW125 to SF10BW125 | ||
673 | ))) | ||
674 | |||
675 | ((( | ||
676 | 924.4 - SF7BW125 to SF10BW125 | ||
677 | ))) | ||
678 | |||
679 | ((( | ||
680 | 924.6 - SF7BW125 to SF10BW125 | ||
681 | ))) | ||
682 | |||
683 | ((( | ||
684 | |||
685 | ))) | ||
686 | |||
687 | ((( | ||
688 | (% style="color:blue" %)**Downlink:** | ||
689 | ))) | ||
690 | |||
691 | ((( | ||
692 | Uplink channels 1-8 (RX1) | ||
693 | ))) | ||
694 | |||
695 | ((( | ||
696 | 923.2 - SF10BW125 (RX2) | ||
697 | ))) | ||
698 | |||
699 | |||
700 | === 2.7.6 KR920-923 (KR920) === | ||
701 | |||
702 | |||
703 | ((( | ||
704 | (% style="color:blue" %)**Default channel:** | ||
705 | ))) | ||
706 | |||
707 | ((( | ||
708 | 922.1 - SF7BW125 to SF12BW125 | ||
709 | ))) | ||
710 | |||
711 | ((( | ||
712 | 922.3 - SF7BW125 to SF12BW125 | ||
713 | ))) | ||
714 | |||
715 | ((( | ||
716 | 922.5 - SF7BW125 to SF12BW125 | ||
717 | ))) | ||
718 | |||
719 | ((( | ||
720 | |||
721 | ))) | ||
722 | |||
723 | ((( | ||
724 | (% style="color:blue" %)**Uplink: (OTAA mode, channel added by JoinAccept message)** | ||
725 | ))) | ||
726 | |||
727 | ((( | ||
728 | 922.1 - SF7BW125 to SF12BW125 | ||
729 | ))) | ||
730 | |||
731 | ((( | ||
732 | 922.3 - SF7BW125 to SF12BW125 | ||
733 | ))) | ||
734 | |||
735 | ((( | ||
736 | 922.5 - SF7BW125 to SF12BW125 | ||
737 | ))) | ||
738 | |||
739 | ((( | ||
740 | 922.7 - SF7BW125 to SF12BW125 | ||
741 | ))) | ||
742 | |||
743 | ((( | ||
744 | 922.9 - SF7BW125 to SF12BW125 | ||
745 | ))) | ||
746 | |||
747 | ((( | ||
748 | 923.1 - SF7BW125 to SF12BW125 | ||
749 | ))) | ||
750 | |||
751 | ((( | ||
752 | 923.3 - SF7BW125 to SF12BW125 | ||
753 | ))) | ||
754 | |||
755 | ((( | ||
756 | |||
757 | ))) | ||
758 | |||
759 | ((( | ||
760 | (% style="color:blue" %)**Downlink:** | ||
761 | ))) | ||
762 | |||
763 | ((( | ||
764 | Uplink channels 1-7(RX1) | ||
765 | ))) | ||
766 | |||
767 | ((( | ||
768 | 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) | ||
769 | ))) | ||
770 | |||
771 | |||
772 | === 2.7.7 IN865-867 (IN865) === | ||
773 | |||
774 | |||
775 | ((( | ||
776 | (% style="color:blue" %)**Uplink:** | ||
777 | ))) | ||
778 | |||
779 | ((( | ||
780 | 865.0625 - SF7BW125 to SF12BW125 | ||
781 | ))) | ||
782 | |||
783 | ((( | ||
784 | 865.4025 - SF7BW125 to SF12BW125 | ||
785 | ))) | ||
786 | |||
787 | ((( | ||
788 | 865.9850 - SF7BW125 to SF12BW125 | ||
789 | ))) | ||
790 | |||
791 | ((( | ||
792 | |||
793 | ))) | ||
794 | |||
795 | ((( | ||
796 | (% style="color:blue" %)**Downlink:** | ||
797 | ))) | ||
798 | |||
799 | ((( | ||
800 | Uplink channels 1-3 (RX1) | ||
801 | ))) | ||
802 | |||
803 | ((( | ||
804 | 866.550 - SF10BW125 (RX2) | ||
805 | ))) | ||
806 | |||
807 | |||
808 | == 2.8 LED Indicator == | ||
809 | |||
810 | |||
811 | The LLMS01 has an internal LED which is to show the status of different state. | ||
812 | |||
813 | * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected. | ||
814 | * Blink once when device transmit a packet. | ||
815 | |||
816 | == 2.9 Firmware Change Log == | ||
817 | |||
818 | |||
819 | **Firmware download link: **[[https:~~/~~/www.dropbox.com/sh/0elufwppq5i6tfu/AAAMZklxDl-WdeT4xrAGXxCma?dl=0>>https://www.dropbox.com/sh/0elufwppq5i6tfu/AAAMZklxDl-WdeT4xrAGXxCma?dl=0]] | ||
820 | |||
821 | **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] | ||
822 | |||
823 | |||
824 | = 3. Configure LLMS01 via AT Command or LoRaWAN Downlink = | ||
825 | |||
826 | |||
827 | ((( | ||
828 | ((( | ||
829 | Use can configure LLMS01 via AT Command or LoRaWAN Downlink. | ||
830 | ))) | ||
831 | ))) | ||
832 | |||
833 | * ((( | ||
834 | ((( | ||
835 | AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]]. | ||
836 | ))) | ||
837 | ))) | ||
838 | * ((( | ||
839 | ((( | ||
840 | LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]] | ||
841 | ))) | ||
842 | ))) | ||
843 | |||
844 | ((( | ||
845 | ((( | ||
846 | There are two kinds of commands to configure LLMS01, they are: | ||
847 | ))) | ||
848 | ))) | ||
849 | |||
850 | * ((( | ||
851 | ((( | ||
852 | (% style="color:#4f81bd" %)** General Commands**. | ||
853 | ))) | ||
854 | ))) | ||
855 | |||
856 | ((( | ||
857 | ((( | ||
858 | These commands are to configure: | ||
859 | ))) | ||
860 | ))) | ||
861 | |||
862 | * ((( | ||
863 | ((( | ||
864 | General system settings like: uplink interval. | ||
865 | ))) | ||
866 | ))) | ||
867 | * ((( | ||
868 | ((( | ||
869 | LoRaWAN protocol & radio related command. | ||
870 | ))) | ||
871 | ))) | ||
872 | |||
873 | ((( | ||
874 | ((( | ||
875 | They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]] | ||
876 | ))) | ||
877 | ))) | ||
878 | |||
879 | ((( | ||
880 | ((( | ||
881 | |||
882 | ))) | ||
883 | ))) | ||
884 | |||
885 | * ((( | ||
886 | ((( | ||
887 | (% style="color:#4f81bd" %)** Commands special design for LLMS01** | ||
888 | ))) | ||
889 | ))) | ||
890 | |||
891 | ((( | ||
892 | ((( | ||
893 | These commands only valid for LLMS01, as below: | ||
894 | ))) | ||
895 | ))) | ||
896 | |||
897 | |||
898 | == 3.1 Set Transmit Interval Time == | ||
899 | |||
900 | |||
901 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
902 | |||
903 | (% style="color:#037691" %)**AT Command: AT+TDC** | ||
904 | |||
905 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
906 | |=(% style="width: 156px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 137px;background-color:#4F81BD;color:white" %)**Function**|=(% style="background-color:#4F81BD;color:white" %)**Response** | ||
907 | |(% style="width:156px" %)AT+TDC=?|(% style="width:137px" %)Show current transmit Interval|((( | ||
908 | 30000 | ||
909 | OK | ||
910 | the interval is 30000ms = 30s | ||
911 | ))) | ||
912 | |(% style="width:156px" %)AT+TDC=60000|(% style="width:137px" %)Set Transmit Interval|((( | ||
913 | OK | ||
914 | Set transmit interval to 60000ms = 60 seconds | ||
915 | ))) | ||
916 | |||
917 | ((( | ||
918 | ((( | ||
919 | (% style="color:#037691" %)**Downlink Command: 0x01** | ||
920 | ))) | ||
921 | ))) | ||
922 | |||
923 | ((( | ||
924 | ((( | ||
925 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
926 | ))) | ||
927 | ))) | ||
928 | |||
929 | ((( | ||
930 | ((( | ||
931 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
932 | ))) | ||
933 | ))) | ||
934 | |||
935 | * ((( | ||
936 | ((( | ||
937 | Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
938 | ))) | ||
939 | ))) | ||
940 | * ((( | ||
941 | ((( | ||
942 | Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
943 | ))) | ||
944 | |||
945 | |||
946 | |||
947 | ))) | ||
948 | |||
949 | == 3.2 Set Interrupt Mode == | ||
950 | |||
951 | |||
952 | Feature, Set Interrupt mode for GPIO_EXIT. | ||
953 | |||
954 | (% style="color:#037691" %)**AT Command: AT+INTMOD** | ||
955 | |||
956 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
957 | |=(% style="width: 154px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 199px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 157px;background-color:#4F81BD;color:white" %)**Response** | ||
958 | |(% style="width:154px" %)AT+INTMOD=?|(% style="width:196px" %)Show current interrupt mode|(% style="width:157px" %)((( | ||
959 | 0 | ||
960 | OK | ||
961 | the mode is 0 =No interruption | ||
962 | ))) | ||
963 | |(% style="width:154px" %)AT+INTMOD=2|(% style="width:196px" %)((( | ||
964 | Set Transmit Interval | ||
965 | ~1. (Disable Interrupt), | ||
966 | 2. (Trigger by rising and falling edge) | ||
967 | 3. (Trigger by falling edge) | ||
968 | 4. (Trigger by rising edge) | ||
969 | )))|(% style="width:157px" %)OK | ||
970 | |||
971 | ((( | ||
972 | (% style="color:#037691" %)**Downlink Command: 0x06** | ||
973 | ))) | ||
974 | |||
975 | ((( | ||
976 | Format: Command Code (0x06) followed by 3 bytes. | ||
977 | ))) | ||
978 | |||
979 | ((( | ||
980 | This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. | ||
981 | ))) | ||
982 | |||
983 | * ((( | ||
984 | Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode | ||
985 | ))) | ||
986 | * ((( | ||
987 | Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger | ||
988 | ))) | ||
989 | |||
990 | ((( | ||
991 | |||
992 | ))) | ||
993 | |||
994 | |||
995 | == 3.3 Get Firmware Version Info == | ||
996 | |||
997 | |||
998 | Feature: use downlink to get firmware version. | ||
999 | |||
1000 | (% style="color:#037691" %)**Downlink Command: 0x26** | ||
1001 | |||
1002 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %) | ||
1003 | |(% style="background-color:#4f81bd; color:white; width:193px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:57px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:91px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:159px" %)**Downlink payload size(bytes)** | ||
1004 | |(% style="width:193px" %)Get Firmware Version Info|(% style="width:57px" %)Any|(% style="width:91px" %)26|(% style="width:149px" %)2 | ||
1005 | |||
1006 | * Reply to the confirmation package: 26 01 | ||
1007 | * Reply to non-confirmed packet: 26 00 | ||
1008 | |||
1009 | Device will send an uplink after got this downlink command. With below payload: | ||
1010 | |||
1011 | Configures info payload: | ||
1012 | |||
1013 | (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) | ||
1014 | |(% style="background-color:#4f81bd; color:white; width:50px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:70px" %)**1**|(% style="background-color:#4f81bd; color:white; width:70px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**|(% style="background-color:#4f81bd; color:white; width:70px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:50px" %)**4**|(% style="background-color:#4f81bd; color:white; width:90px" %)**1** | ||
1015 | |Value|Software Type|((( | ||
1016 | Frequency | ||
1017 | Band | ||
1018 | )))|Sub-band|((( | ||
1019 | Firmware | ||
1020 | Version | ||
1021 | )))|Sensor Type|Reserve|((( | ||
1022 | [[Message Type>>||anchor="H2.3.6MessageType"]] | ||
1023 | Always 0x02 | ||
1024 | ))) | ||
1025 | |||
1026 | (% style="color:#037691" %)**Software Type**(%%): Always 0x03 for LLMS01 | ||
1027 | |||
1028 | (% style="color:#037691" %)**Frequency Band**: | ||
1029 | |||
1030 | 0x01: EU868 | ||
1031 | |||
1032 | 0x02: US915 | ||
1033 | |||
1034 | 0x03: IN865 | ||
1035 | |||
1036 | 0x04: AU915 | ||
1037 | |||
1038 | 0x05: KZ865 | ||
1039 | |||
1040 | 0x06: RU864 | ||
1041 | |||
1042 | 0x07: AS923 | ||
1043 | |||
1044 | 0x08: AS923-1 | ||
1045 | |||
1046 | 0x09: AS923-2 | ||
1047 | |||
1048 | 0xa0: AS923-3 | ||
1049 | |||
1050 | |||
1051 | (% style="color:#037691" %)**Sub-Band**(%%): value 0x00 ~~ 0x08 | ||
1052 | |||
1053 | (% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version | ||
1054 | |||
1055 | (% style="color:#037691" %)**Sensor Type**: | ||
1056 | |||
1057 | 0x01: LSE01 | ||
1058 | |||
1059 | 0x02: LDDS75 | ||
1060 | |||
1061 | 0x03: LDDS20 | ||
1062 | |||
1063 | 0x04: LLMS01 | ||
1064 | |||
1065 | 0x05: LSPH01 | ||
1066 | |||
1067 | 0x06: LSNPK01 | ||
1068 | |||
1069 | 0x07: LDDS45 | ||
1070 | |||
1071 | 0x08: LSLP01 | ||
1072 | |||
1073 | 0x018: LMDS120 | ||
1074 | |||
1075 | |||
1076 | = 4. Battery & Power Consumption = | ||
1077 | |||
1078 | |||
1079 | LLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
1080 | |||
1081 | [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
1082 | |||
1083 | |||
1084 | = 5. Use AT Command = | ||
1085 | |||
1086 | == 5.1 Access AT Commands == | ||
1087 | |||
1088 | |||
1089 | LLMS01 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LLMS01 for using AT command, as below. | ||
1090 | |||
1091 | [[image:1654593668970-604.png]] | ||
1092 | |||
1093 | **Connection:** | ||
1094 | |||
1095 | (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND** | ||
1096 | |||
1097 | (% style="background-color:yellow" %)** USB TTL TXD <~-~-~-~-> UART_RXD** | ||
1098 | |||
1099 | (% style="background-color:yellow" %)** USB TTL RXD <~-~-~-~-> UART_TXD** | ||
1100 | |||
1101 | |||
1102 | ((( | ||
1103 | ((( | ||
1104 | In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLMS01. LLMS01 will output system info once power on as below: | ||
1105 | ))) | ||
1106 | ))) | ||
1107 | |||
1108 | |||
1109 | [[image:1654653659449-932.png]] | ||
1110 | |||
1111 | Valid AT Command please check [[Configure Device>>||anchor="H3.ConfigureLLMS01viaATCommandorLoRaWANDownlink"]]. | ||
1112 | |||
1113 | |||
1114 | = 6. FAQ = | ||
1115 | |||
1116 | == 6.1 How to change the LoRa Frequency Bands/Region == | ||
1117 | |||
1118 | |||
1119 | You can follow the instructions for [[how to upgrade image>>||anchor="H2.9200BFirmwareChangeLog"]]. | ||
1120 | When downloading the images, choose the required image file for download. | ||
1121 | |||
1122 | |||
1123 | = 7. Trouble Shooting = | ||
1124 | |||
1125 | == 7.1 AT Commands input doesn't work == | ||
1126 | |||
1127 | |||
1128 | 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. | ||
1129 | |||
1130 | |||
1131 | == 7.2 Possible reasons why the device is unresponsive: == | ||
1132 | |||
1133 | |||
1134 | 1. Check whether the battery voltage is lower than 2.8V | ||
1135 | 2. Check whether the jumper of the device is correctly connected | ||
1136 | |||
1137 | [[image:image-20240330175459-1.png]] | ||
1138 | 3. Check whether the switch here of the device is at the ISP(The switch can operate normally only when it is in RUN) | ||
1139 | [[image:image-20240330175505-2.png]] | ||
1140 | |||
1141 | = 8. Order Info = | ||
1142 | |||
1143 | |||
1144 | Part Number: (% style="color:blue" %)**LLMS01-XXX** | ||
1145 | |||
1146 | (% style="color:blue" %)**XXX**(%%): The default frequency band | ||
1147 | |||
1148 | * (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band | ||
1149 | * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band | ||
1150 | * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band | ||
1151 | * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band | ||
1152 | * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band | ||
1153 | * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band | ||
1154 | * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band | ||
1155 | * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band | ||
1156 | |||
1157 | = 9. Packing Info = | ||
1158 | |||
1159 | |||
1160 | **Package Includes**: | ||
1161 | |||
1162 | * LLMS01 LoRaWAN Leaf Moisture Sensor x 1 | ||
1163 | |||
1164 | **Dimension and weight**: | ||
1165 | |||
1166 | * Device Size: cm | ||
1167 | * Device Weight: g | ||
1168 | * Package Size / pcs : cm | ||
1169 | * Weight / pcs : g | ||
1170 | |||
1171 | = 10. Support = | ||
1172 | |||
1173 | |||
1174 | * 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. | ||
1175 | * 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]]. |