Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20220610095606-1.png]]
3
4
5 **Contents:**
6
7
8
9
10
11
12
13 = 1. Introduction =
14
15 == 1.1 ​What is LoRaWAN LiDAR ToF Distance Sensor ==
16
17 (((
18
19
20 The Dragino LLDS12 is a (% style="color:blue" %)**LoRaWAN LiDAR ToF (Time of Flight) Distance Sensor**(%%) for Internet of Things solution. It is capable to measure the distance to an object as close as 10 centimeters (+/- 5cm up to 6m) and as far as 12 meters (+/-1% starting at 6m)!. The LiDAR probe uses laser induction technology for distance measurement.
21
22 The LLDS12 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
23
24 It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server.
25
26 The LoRa wireless technology used in LLDS12 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.
27
28 LLDS12 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years.
29
30 Each LLDS12 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.
31 )))
32
33
34 [[image:1654826306458-414.png]]
35
36
37
38 == ​1.2 Features ==
39
40 * LoRaWAN 1.0.3 Class A
41 * Ultra-low power consumption
42 * Laser technology for distance detection
43 * Operating Range - 0.1m~~12m①
44 * Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
45 * Monitor Battery Level
46 * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
47 * AT Commands to change parameters
48 * Uplink on periodically
49 * Downlink to change configure
50 * 8500mAh Battery for long term use
51
52
53
54 == 1.3 Probe Specification ==
55
56
57 * Storage temperature :-20℃~~75℃
58 * Operating temperature - -20℃~~60℃
59 * Operating Range - 0.1m~~12m①
60 * Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
61 * Distance resolution - 5mm
62 * Ambient light immunity - 70klux
63 * Enclosure rating - IP65
64 * Light source - LED
65 * Central wavelength - 850nm
66 * FOV - 3.6°
67 * Material of enclosure - ABS+PC
68 * Wire length - 25cm
69
70
71
72 == 1.4 ​Applications ==
73
74 * Smart Agriculture
75
76
77
78 == 1.5 Pin mapping and power on ==
79
80 [[image:1654592472094-134.png]]
81
82
83
84 = 2. Configure LSPH01 to connect to LoRaWAN network =
85
86 == 2.1 How it works ==
87
88 (((
89 The LSPH01 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 LSPH01. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
90 )))
91
92 (((
93 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 LSPH01.
94 )))
95
96
97 == 2.2 ​Quick guide to connect to LoRaWAN server (OTAA) ==
98
99 (((
100 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.
101 )))
102
103 (((
104 [[image:1654592492399-921.png]]
105 )))
106
107 (((
108 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.
109 )))
110
111 (((
112 (% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
113 )))
114
115 (((
116 Each LSPH01 is shipped with a sticker with the default device EUI as below:
117 )))
118
119 [[image:image-20220607170145-1.jpeg]]
120
121
122
123 You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
124
125
126 **Register the device**
127
128
129 [[image:1654592600093-601.png]]
130
131
132 **Add APP EUI and DEV EUI**
133
134 [[image:1654592619856-881.png]]
135
136
137 **Add APP EUI in the application**
138
139 [[image:1654592632656-512.png]]
140
141
142
143 **Add APP KEY**
144
145 [[image:1654592653453-934.png]]
146
147
148 (% style="color:blue" %)**Step 2**(%%): Power on LSPH01
149
150
151 Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
152
153 [[image:image-20220607170442-2.png]]
154
155
156 (((
157 (% style="color:blue" %)**Step 3**(%%)**:** The LSPH01 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.
158 )))
159
160 [[image:1654592697690-910.png]]
161
162
163
164 == 2.3 ​Uplink Payload ==
165
166 (((
167 LSPH01 will uplink payload via LoRaWAN with below payload format: 
168 )))
169
170 (((
171 Uplink payload includes in total 11 bytes.
172 )))
173
174 (((
175 Normal uplink payload:
176 )))
177
178 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
179 |=(% style="width: 62.5px;" %)(((
180 **Size (bytes)**
181 )))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
182 |(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1BatteryInfo"]]|(% style="width:62.5px" %)(((
183 [[Temperature>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
184
185 [[(Optional)>>||anchor="H2.3.2DS18B20Temperaturesensor"]]
186 )))|[[Soil pH>>||anchor="H2.3.3SoilpH"]]|[[Soil Temperature>>||anchor="H2.3.4SoilTemperature"]]|(((
187 [[Digital Interrupt (Optional)>>||anchor="H2.3.5InterruptPin"]]
188 )))|Reserve|(((
189 [[Message Type>>||anchor="H2.3.6MessageType"]]
190 )))
191
192 [[image:1654592721645-318.png]]
193
194
195
196 === 2.3.1 Battery Info ===
197
198
199 Check the battery voltage for LSPH01.
200
201 Ex1: 0x0B45 = 2885mV
202
203 Ex2: 0x0B49 = 2889mV
204
205
206
207 === 2.3.2 DS18B20 Temperature sensor ===
208
209 This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
210
211
212 **Example**:
213
214 If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
215
216 If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
217
218
219
220 === 2.3.3 Soil pH ===
221
222 Range: 0 ~~ 14 pH
223
224 **Example:**
225
226 (% style="color:#037691" %)** 0x02B7(H) = 695(D) = 6.95pH**
227
228
229
230 === 2.3.4 Soil Temperature ===
231
232 Get Soil 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
243 === 2.3.5 Interrupt Pin ===
244
245 This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.2SetInterruptMode"]] for the hardware and software set up.
246
247
248 **Example:**
249
250 0x00: Normal uplink packet.
251
252 0x01: Interrupt Uplink Packet.
253
254
255
256 === 2.3.6 Message Type ===
257
258 (((
259 For a normal uplink payload, the message type is always 0x01.
260 )))
261
262 (((
263 Valid Message Type:
264 )))
265
266
267 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
268 |=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
269 |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]]
270 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]]
271 |(% style="width:160px" %)0x03|(% style="width:163px" %)Reply Calibration Info|(% style="width:173px" %)[[Calibration Payload>>||anchor="H2.7Calibration"]]
272
273 === 2.3.7 Decode payload in The Things Network ===
274
275 While using TTN network, you can add the payload format to decode the payload.
276
277
278 [[image:1654592762713-715.png]]
279
280 (((
281 The payload decoder function for TTN is here:
282 )))
283
284 (((
285 LSPH01 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]]
286 )))
287
288
289
290 == 2.4 Uplink Interval ==
291
292 The LSPH01 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"]]
293
294
295
296 == 2.5 ​Show Data in DataCake IoT Server ==
297
298 (((
299 [[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:
300 )))
301
302 (((
303
304 )))
305
306 (((
307 (% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.**
308 )))
309
310 (((
311 (% 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:**
312 )))
313
314
315 [[image:1654592790040-760.png]]
316
317
318 [[image:1654592800389-571.png]]
319
320
321 (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
322
323 (% style="color:blue" %)**Step 4**(%%)**: Create LSPH01 product.**
324
325 [[image:1654592819047-535.png]]
326
327
328
329 [[image:1654592833877-762.png]]
330
331
332 [[image:1654592856403-259.png]]
333
334
335 (((
336 (% style="color:blue" %)**Step 5**(%%)**: add payload decode**
337 )))
338
339 (((
340 Download Datacake decoder from: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]]
341 )))
342
343
344 [[image:1654592878525-845.png]]
345
346 [[image:1654592892967-474.png]]
347
348
349 [[image:1654592905354-123.png]]
350
351
352 After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
353
354
355 [[image:1654592917530-261.png]]
356
357
358
359 == 2.6 Installation and Maintain ==
360
361 === 2.6.1 Before measurement ===
362
363 (((
364 (((
365 If the LSPH01 has more than 7 days not use or just clean the pH probe. User should put the probe inside pure water for more than 24 hours for activation. If no put in water, user need to put inside soil for more than 24 hours to ensure the measurement accuracy. 
366 )))
367 )))
368
369
370
371 === 2.6.2 Measurement ===
372
373
374 (((
375 (% style="color:#4f81bd" %)**Measurement the soil surface:**
376 )))
377
378 (((
379 [[image:1654592946732-634.png]]
380 )))
381
382 (((
383 Choose the proper measuring position. Split the surface soil according to the measured deep.
384 )))
385
386 (((
387 Put pure water, or rainwater to make the soil of measurement point to moist mud. Remove rocks or hard things.
388 )))
389
390 (((
391 Slowly insert the probe to the measure point. Don’t use large force which will break the probe. Make sure not shake when inserting.
392 )))
393
394 (((
395 Put soil over the probe after insert. And start to measure.
396 )))
397
398 (((
399
400 )))
401
402 (((
403 (% style="color:#4f81bd" %)**Measurement inside soil:**
404 )))
405
406 (((
407 Dig a hole with diameter > 20CM.
408 )))
409
410 (((
411 Insert the probe inside, method like measure the surface.
412 )))
413
414
415
416 === 2.6.3 Maintain Probe ===
417
418 1. (((
419 pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.
420 )))
421 1. (((
422 After long time use (3~~ 6  months). The probe electrode needs to be clean; user can use high grade sandpaper to polish it or put in 5% hydrochloric acid for several minutes. After the metal probe looks like new, user can use pure water to wash it.
423 )))
424 1. (((
425 Probe reference electrode is also no strong, need to avoid strong force or hitting.
426 )))
427 1. (((
428 User should keep reference electrode wet while not use.
429 )))
430 1. (((
431 Avoid the probes to touch oily matter. Which will cause issue in accuracy.
432 )))
433 1. (((
434 The probe is IP68 can be put in water.
435
436
437
438 )))
439
440 == 2.7 Calibration ==
441
442 (((
443 User can do calibration for the probe. It is limited to use below pH buffer solution to calibrate: 4.00, 6.86, 9.18. When calibration, user need to clean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode might need max 24 hours to be stable).
444 )))
445
446 (((
447 After stable, user can use below command to calibrate.
448 )))
449
450 [[image:image-20220607171149-4.png]]
451
452
453 (% style="color:#037691" %)**Calibration Payload**
454
455 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
456 |=(% style="width: 62.5px;" %)(((
457 **Size (bytes)**
458 )))|=(% style="width: 89px;" %)**1**|=(% style="width: 89px;" %)**1**|=(% style="width: 89px;" %)**1**|=(% style="width: 89px;" %)**7**|=(% style="width: 89px;" %)**1**
459 |**Value**|(((
460 PH4
461
462 Calibrate value
463 )))|PH6.86 Calibrate value|(((
464 PH9.18
465
466 Calibrate value
467 )))|Reserve|(((
468 [[Message Type>>||anchor="H2.3.6MessageType"]]
469
470 Always 0x03
471 )))
472
473 User can also send 0x14 downlink command to poll the current calibration payload.
474
475 [[image:image-20220607171416-7.jpeg]]
476
477
478 * Reply to the confirmation package: 14 01
479 * Reply to non-confirmed packet: 14 00
480
481 == 2.8 Frequency Plans ==
482
483 (((
484 The LSPH01 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.
485 )))
486
487
488 === 2.8.1 EU863-870 (EU868) ===
489
490 (((
491 (% style="color:blue" %)**Uplink:**
492 )))
493
494 (((
495 868.1 - SF7BW125 to SF12BW125
496 )))
497
498 (((
499 868.3 - SF7BW125 to SF12BW125 and SF7BW250
500 )))
501
502 (((
503 868.5 - SF7BW125 to SF12BW125
504 )))
505
506 (((
507 867.1 - SF7BW125 to SF12BW125
508 )))
509
510 (((
511 867.3 - SF7BW125 to SF12BW125
512 )))
513
514 (((
515 867.5 - SF7BW125 to SF12BW125
516 )))
517
518 (((
519 867.7 - SF7BW125 to SF12BW125
520 )))
521
522 (((
523 867.9 - SF7BW125 to SF12BW125
524 )))
525
526 (((
527 868.8 - FSK
528 )))
529
530 (((
531
532 )))
533
534 (((
535 (% style="color:blue" %)**Downlink:**
536 )))
537
538 (((
539 Uplink channels 1-9 (RX1)
540 )))
541
542 (((
543 869.525 - SF9BW125 (RX2 downlink only)
544 )))
545
546
547
548 === 2.8.2 US902-928(US915) ===
549
550 (((
551 Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
552 )))
553
554 (((
555 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.
556 )))
557
558 (((
559 After Join success, the end node will switch to the correct sub band by:
560 )))
561
562 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
563 * 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)
564
565 === 2.8.3 CN470-510 (CN470) ===
566
567 (((
568 Used in China, Default use CHE=1
569 )))
570
571 (((
572 (% style="color:blue" %)**Uplink:**
573 )))
574
575 (((
576 486.3 - SF7BW125 to SF12BW125
577 )))
578
579 (((
580 486.5 - SF7BW125 to SF12BW125
581 )))
582
583 (((
584 486.7 - SF7BW125 to SF12BW125
585 )))
586
587 (((
588 486.9 - SF7BW125 to SF12BW125
589 )))
590
591 (((
592 487.1 - SF7BW125 to SF12BW125
593 )))
594
595 (((
596 487.3 - SF7BW125 to SF12BW125
597 )))
598
599 (((
600 487.5 - SF7BW125 to SF12BW125
601 )))
602
603 (((
604 487.7 - SF7BW125 to SF12BW125
605 )))
606
607 (((
608
609 )))
610
611 (((
612 (% style="color:blue" %)**Downlink:**
613 )))
614
615 (((
616 506.7 - SF7BW125 to SF12BW125
617 )))
618
619 (((
620 506.9 - SF7BW125 to SF12BW125
621 )))
622
623 (((
624 507.1 - SF7BW125 to SF12BW125
625 )))
626
627 (((
628 507.3 - SF7BW125 to SF12BW125
629 )))
630
631 (((
632 507.5 - SF7BW125 to SF12BW125
633 )))
634
635 (((
636 507.7 - SF7BW125 to SF12BW125
637 )))
638
639 (((
640 507.9 - SF7BW125 to SF12BW125
641 )))
642
643 (((
644 508.1 - SF7BW125 to SF12BW125
645 )))
646
647 (((
648 505.3 - SF12BW125 (RX2 downlink only)
649 )))
650
651
652
653 === 2.8.4 AU915-928(AU915) ===
654
655 (((
656 Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
657 )))
658
659 (((
660 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.
661 )))
662
663 (((
664
665 )))
666
667 (((
668 After Join success, the end node will switch to the correct sub band by:
669 )))
670
671 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
672 * 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)
673
674 === 2.8.5 AS920-923 & AS923-925 (AS923) ===
675
676 (((
677 (% style="color:blue" %)**Default Uplink channel:**
678 )))
679
680 (((
681 923.2 - SF7BW125 to SF10BW125
682 )))
683
684 (((
685 923.4 - SF7BW125 to SF10BW125
686 )))
687
688 (((
689
690 )))
691
692 (((
693 (% style="color:blue" %)**Additional Uplink Channel**:
694 )))
695
696 (((
697 (OTAA mode, channel added by JoinAccept message)
698 )))
699
700 (((
701
702 )))
703
704 (((
705 (% style="color:blue" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
706 )))
707
708 (((
709 922.2 - SF7BW125 to SF10BW125
710 )))
711
712 (((
713 922.4 - SF7BW125 to SF10BW125
714 )))
715
716 (((
717 922.6 - SF7BW125 to SF10BW125
718 )))
719
720 (((
721 922.8 - SF7BW125 to SF10BW125
722 )))
723
724 (((
725 923.0 - SF7BW125 to SF10BW125
726 )))
727
728 (((
729 922.0 - SF7BW125 to SF10BW125
730 )))
731
732 (((
733
734 )))
735
736 (((
737 (% style="color:blue" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
738 )))
739
740 (((
741 923.6 - SF7BW125 to SF10BW125
742 )))
743
744 (((
745 923.8 - SF7BW125 to SF10BW125
746 )))
747
748 (((
749 924.0 - SF7BW125 to SF10BW125
750 )))
751
752 (((
753 924.2 - SF7BW125 to SF10BW125
754 )))
755
756 (((
757 924.4 - SF7BW125 to SF10BW125
758 )))
759
760 (((
761 924.6 - SF7BW125 to SF10BW125
762 )))
763
764 (((
765
766 )))
767
768 (((
769 (% style="color:blue" %)**Downlink:**
770 )))
771
772 (((
773 Uplink channels 1-8 (RX1)
774 )))
775
776 (((
777 923.2 - SF10BW125 (RX2)
778 )))
779
780
781
782 === 2.8.6 KR920-923 (KR920) ===
783
784 (((
785 (% style="color:blue" %)**Default channel:**
786 )))
787
788 (((
789 922.1 - SF7BW125 to SF12BW125
790 )))
791
792 (((
793 922.3 - SF7BW125 to SF12BW125
794 )))
795
796 (((
797 922.5 - SF7BW125 to SF12BW125
798 )))
799
800 (((
801
802 )))
803
804 (((
805 (% style="color:blue" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
806 )))
807
808 (((
809 922.1 - SF7BW125 to SF12BW125
810 )))
811
812 (((
813 922.3 - SF7BW125 to SF12BW125
814 )))
815
816 (((
817 922.5 - SF7BW125 to SF12BW125
818 )))
819
820 (((
821 922.7 - SF7BW125 to SF12BW125
822 )))
823
824 (((
825 922.9 - SF7BW125 to SF12BW125
826 )))
827
828 (((
829 923.1 - SF7BW125 to SF12BW125
830 )))
831
832 (((
833 923.3 - SF7BW125 to SF12BW125
834 )))
835
836 (((
837
838 )))
839
840 (((
841 (% style="color:blue" %)**Downlink:**
842 )))
843
844 (((
845 Uplink channels 1-7(RX1)
846 )))
847
848 (((
849 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
850 )))
851
852
853
854 === 2.8.7 IN865-867 (IN865) ===
855
856 (((
857 (% style="color:blue" %)**Uplink:**
858 )))
859
860 (((
861 865.0625 - SF7BW125 to SF12BW125
862 )))
863
864 (((
865 865.4025 - SF7BW125 to SF12BW125
866 )))
867
868 (((
869 865.9850 - SF7BW125 to SF12BW125
870 )))
871
872 (((
873
874 )))
875
876 (((
877 (% style="color:blue" %)**Downlink:**
878 )))
879
880 (((
881 Uplink channels 1-3 (RX1)
882 )))
883
884 (((
885 866.550 - SF10BW125 (RX2)
886 )))
887
888
889
890 == 2.9 LED Indicator ==
891
892 The LSPH01 has an internal LED which is to show the status of different state.
893
894 * The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
895 * Blink once when device transmit a packet.
896
897 == 2.10 ​Firmware Change Log ==
898
899
900 **Firmware download link:**
901
902 [[http:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
903
904
905 **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>path:/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/]]
906
907
908
909 = 3. Configure LSPH01 via AT Command or LoRaWAN Downlink =
910
911 (((
912 Use can configure LSPH01 via AT Command or LoRaWAN Downlink.
913 )))
914
915 * (((
916 AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
917 )))
918 * (((
919 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>path:/xwiki/bin/view/Main/]]
920 )))
921
922 (((
923 There are two kinds of commands to configure LSPH01, they are:
924 )))
925
926 * (((
927 (% style="color:#4f81bd" %)** General Commands**.
928 )))
929
930 (((
931 These commands are to configure:
932 )))
933
934 * (((
935 General system settings like: uplink interval.
936 )))
937 * (((
938 LoRaWAN protocol & radio related command.
939 )))
940
941 (((
942 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>>path:/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
943 )))
944
945 (((
946
947 )))
948
949 * (((
950 (% style="color:#4f81bd" %)** Commands special design for LSPH01**
951 )))
952
953 (((
954 These commands only valid for LSPH01, as below:
955 )))
956
957
958
959 == 3.1 Set Transmit Interval Time ==
960
961 Feature: Change LoRaWAN End Node Transmit Interval.
962
963 (% style="color:#037691" %)**AT Command: AT+TDC**
964
965 [[image:image-20220607171554-8.png]]
966
967
968
969 (((
970 (% style="color:#037691" %)**Downlink Command: 0x01**
971 )))
972
973 (((
974 Format: Command Code (0x01) followed by 3 bytes time value.
975 )))
976
977 (((
978 If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
979 )))
980
981 * (((
982 Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
983 )))
984 * (((
985 Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
986
987
988
989 )))
990
991 == 3.2 Set Interrupt Mode ==
992
993 Feature, Set Interrupt mode for GPIO_EXIT.
994
995 (% style="color:#037691" %)**AT Command: AT+INTMOD**
996
997 [[image:image-20220607171716-9.png]]
998
999
1000 (((
1001 (% style="color:#037691" %)**Downlink Command: 0x06**
1002 )))
1003
1004 (((
1005 Format: Command Code (0x06) followed by 3 bytes.
1006 )))
1007
1008 (((
1009 This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
1010 )))
1011
1012 * (((
1013 Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
1014 )))
1015 * (((
1016 Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
1017 )))
1018
1019 (((
1020
1021 )))
1022
1023
1024
1025 == 3.3 Calibrate Sensor ==
1026
1027 Detail See [[Calibration Guide>>||anchor="H2.7Calibration"]] for the user of 0x13 and 0x14 downlink commands
1028
1029
1030
1031 == 3.4 Get Firmware Version Info ==
1032
1033 Feature: use downlink to get firmware version.
1034
1035 (% style="color:#037691" %)**Downlink Command: 0x26**
1036
1037 [[image:image-20220607171917-10.png]]
1038
1039 * Reply to the confirmation package: 26 01
1040 * Reply to non-confirmed packet: 26 00
1041
1042 Device will send an uplink after got this downlink command. With below payload:
1043
1044 Configures info payload:
1045
1046 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
1047 |=(((
1048 **Size(bytes)**
1049 )))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
1050 |**Value**|Software Type|(((
1051 Frequency
1052
1053 Band
1054 )))|Sub-band|(((
1055 Firmware
1056
1057 Version
1058 )))|Sensor Type|Reserve|(((
1059 [[Message Type>>||anchor="H2.3.6MessageType"]]
1060 Always 0x02
1061 )))
1062
1063 **Software Type**: Always 0x03 for LSPH01
1064
1065
1066 **Frequency Band**:
1067
1068 *0x01: EU868
1069
1070 *0x02: US915
1071
1072 *0x03: IN865
1073
1074 *0x04: AU915
1075
1076 *0x05: KZ865
1077
1078 *0x06: RU864
1079
1080 *0x07: AS923
1081
1082 *0x08: AS923-1
1083
1084 *0x09: AS923-2
1085
1086 *0xa0: AS923-3
1087
1088
1089 **Sub-Band**: value 0x00 ~~ 0x08
1090
1091
1092 **Firmware Version**: 0x0100, Means: v1.0.0 version
1093
1094
1095 **Sensor Type**:
1096
1097 0x01: LSE01
1098
1099 0x02: LDDS75
1100
1101 0x03: LDDS20
1102
1103 0x04: LLMS01
1104
1105 0x05: LSPH01
1106
1107 0x06: LSNPK01
1108
1109 0x07: LDDS12
1110
1111
1112
1113 = 4. Battery & How to replace =
1114
1115 == 4.1 Battery Type ==
1116
1117 (((
1118 LSPH01 is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.
1119 )))
1120
1121 (((
1122 The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
1123 )))
1124
1125 [[image:1654593587246-335.png]]
1126
1127
1128 Minimum Working Voltage for the LSPH01:
1129
1130 LSPH01:  2.45v ~~ 3.6v
1131
1132
1133
1134 == 4.2 Replace Battery ==
1135
1136 (((
1137 Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
1138 )))
1139
1140 (((
1141 And make sure the positive and negative pins match.
1142 )))
1143
1144
1145
1146 == 4.3 Power Consumption Analyze ==
1147
1148 (((
1149 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.
1150 )))
1151
1152 (((
1153 Instruction to use as below:
1154 )))
1155
1156
1157 **Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
1158
1159 [[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/]]
1160
1161
1162 **Step 2**: Open it and choose
1163
1164 * Product Model
1165 * Uplink Interval
1166 * Working Mode
1167
1168 And the Life expectation in difference case will be shown on the right.
1169
1170 [[image:1654593605679-189.png]]
1171
1172
1173 The battery related documents as below:
1174
1175 * (((
1176 [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
1177 )))
1178 * (((
1179 [[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
1180 )))
1181 * (((
1182 [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
1183 )))
1184
1185 [[image:image-20220607172042-11.png]]
1186
1187
1188
1189 === 4.3.1 ​Battery Note ===
1190
1191 (((
1192 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.
1193 )))
1194
1195
1196
1197 === ​4.3.2 Replace the battery ===
1198
1199 (((
1200 You can change the battery in the LSPH01.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
1201 )))
1202
1203 (((
1204 The default battery pack of LSPH01 includes a ER26500 plus super capacitor. If user can’t find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
1205 )))
1206
1207
1208
1209 = 5. Use AT Command =
1210
1211 == 5.1 Access AT Commands ==
1212
1213 LSPH01 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LSPH01 for using AT command, as below.
1214
1215 [[image:1654593668970-604.png]]
1216
1217 **Connection:**
1218
1219 (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
1220
1221 (% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
1222
1223 (% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
1224
1225
1226 (((
1227 In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LSPH01. LSPH01 will output system info once power on as below:
1228 )))
1229
1230
1231 [[image:1654593712276-618.png]]
1232
1233 Valid AT Command please check [[Configure Device>>||anchor="H3.ConfigureLSPH01viaATCommandorLoRaWANDownlink"]].
1234
1235
1236 = 6. FAQ =
1237
1238 == 6.1 How to change the LoRa Frequency Bands/Region ==
1239
1240 You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
1241 When downloading the images, choose the required image file for download. ​
1242
1243
1244 = 7. Trouble Shooting =
1245
1246 == 7.1 AT Commands input doesn’t work ==
1247
1248 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.
1249
1250
1251
1252 = 8. Order Info =
1253
1254 Part Number: (% style="color:blue" %)**LSPH01-XX**
1255
1256
1257 (% style="color:blue" %)**XX**(%%): The default frequency band
1258
1259 * (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
1260 * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1261 * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1262 * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1263 * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1264 * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1265 * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1266 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1267
1268 = 9. ​Packing Info =
1269
1270
1271 **Package Includes**:
1272
1273 * LSPH01 LoRaWAN Soil Ph Sensor x 1
1274
1275 **Dimension and weight**:
1276
1277 * Device Size: cm
1278 * Device Weight: g
1279 * Package Size / pcs : cm
1280 * Weight / pcs : g
1281
1282 = 10. ​Support =
1283
1284 * 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.
1285 * 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]].
1286
1287
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0