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

Applications

Navigation

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