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 === 2.3.3  Real-Time Open/Close Status, Uplink FPORT~=2 ===
328
329 LDS03A will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS03A will:
330
331
332 1. periodically send this uplink every 2 hours, this interval [[can be changed>>||anchor="H3.1SetTransmitIntervalTime"]].
333 1. There is an Open/Close event. 
334
335 Uplink Payload totals 11 bytes.
336
337 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:495px" %)
338 |(% colspan="5" style="width:492px" %)**Real-Time Open/Close Status, FPORT=2**
339 |(% style="width:101px" %)**Size (bytes)**|(% style="width:77px" %)**1**|(% style="width:99px" %)**3**|(% style="width:88px" %)**3**|(% style="width:126px" %)**4**
340 |(% style="width:101px" %)**Value**|(% style="width:77px" %)Status & [[Alarm>>||anchor="H3.8AlarmBaseonTimeout"]]|(% style="width:99px" %)Total open door events|(% style="width:88px" %)(((
341 The last door open
342
343 duration (unit: min)
344 )))|(% style="width:126px" %)[[Unix TimeStamp>>||anchor="H2.4.1UnixTimeStamp"]]
345
346 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:509px" %)
347 |(% colspan="4" style="width:506px" %)**Status & Alarm field**
348 |(% style="width:82px" %)**Size (bit)**|(% style="width:71px" %)**6**|(% style="width:221px" %)**1**|(% style="width:130px" %)**1**
349 |(% style="width:82px" %)**Value**|(% style="width:71px" %)Reserve|(% style="width:221px" %)[[Enable/disable Timeout Alarm>>||anchor="H3.8AlarmBaseonTimeout"]]
350 0: No Alarm; 1: Alarm|(% style="width:130px" %)Status
351 0: Close, 1: Open
352
353 [[image:image-20220609110547-6.png||height="337" width="1191"]]
354
355
356
357 === 2.3.4  Historical Door Open/Close Event, FPORT~=3 ===
358
359 LDS03A stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.4DatalogFeature"]].
360
361 The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time open/close status.
362
363
364 * Each data entry is 11 bytes and has the same structure as [[Real-Time open/close status>>||anchor="H2.3.3Real-TimeOpen/CloseStatus,Uplink FPORT=2"]], to save airtime and battery, LDS03A will send max bytes according to the current DR and Frequency bands.
365
366 For example, in the US915 band, the max payload for different DR is:
367
368 a)      DR0: max is 11 bytes so one entry of data
369
370 b)      DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
371
372 c)      DR2: total payload includes 11 entries of data
373
374 d)       DR3: total payload includes 22 entries of data.
375
376 If LDS03A doesn’t have any data in the polling time. It will uplink 11 bytes of 0
377
378
379 [[image:image-20220609112215-7.png||height="277" width="1250"]]
380
381 (% style="color:#037691" %)**Downlink:**
382
383 0x31 61 8E 57 40 61 8E 81 70 05
384
385
386 (% style="color:#037691" %)**Uplink:**
387
388 00 00 00 00 00 00 00 61 8E 5F 8F 01 00 00 01 00 00 00 61 8E 5F D2 00 00 00 01 00 00 02 61 8E 60 64 01 00 00 02 00 00 02 61 8E 60 75 00 00 00 02 00 00 01 61 8E 60 C6 00 00 00 02 00 00 01 61 8E 7B A7 01 00 00 03 00 00 01 61 8E 7F 38 00 00 00 03 00 00 02 61 8E 7F CE 01 00 00 04 00 00 02 61 8E 81 1B 00 00 00 04 00 00 00 61 8E 81 50
389
390
391 (% style="color:#037691" %)**Parsed Value:**
392
393 [ALARM, DOOR_OPEN_STATUS, DOOR_OPEN_TIMES,LAST_DOOR_OPEN_DURATION, TIME]
394
395
396 [FALSE, CLOSE, 0, 0, 2021-11-12 12:35:27],
397
398 [FALSE, OPEN,  1, 0, 2021-11-12 12:36:34],
399
400 [FALSE, CLOSE, 1, 2, 2021-11-12 12:39:00],
401
402 [FALSE, OPEN,  2, 2, 2021-11-12 12:39:17],
403
404 [FALSE, CLOSE, 2, 1, 2021-11-12 12:40:38],
405
406 [FALSE, CLOSE, 2, 1, 2021-11-12 14:35:19],
407
408 [FALSE, OPEN,  3, 1, 2021-11-12 14:50:32],
409
410 [FALSE, CLOSE, 3, 2, 2021-11-12 14:53:02],
411
412 [FALSE, OPEN,  4, 2, 2021-11-12 14:58:35],
413
414 [FALSE, CLOSE, 4, 0, 2021-11-12 14:59:28],
415
416
417
418 == 2.4  Datalog Feature ==
419
420 When a user wants to retrieve sensor value, he can send a poll command from the IoT platform to ask the sensor to send value in the required time slot.
421
422
423 === 2.4.1  Unix TimeStamp ===
424
425 LDS03A use Unix TimeStamp format based on
426
427 [[image:image-20220609113256-8.png]]
428
429
430 (((
431 Users can get this time from the link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
432 )))
433
434 (((
435 Below is the converter example
436 )))
437
438 [[image:image-20220609113256-9.png||height="467" width="1127"]]
439
440 (((
441 So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
442 )))
443
444
445 === 2.4.2  Set Device Time ===
446
447 (((
448 There are two ways to set the device’s time:
449 )))
450
451 (((
452 (% style="color:#037691" %)**1. Through LoRaWAN MAC Command (Default settings)**
453 )))
454
455 (((
456 Users need to set SYNCMOD=1 to enable sync time via the MAC command.
457 )))
458
459 (((
460 Once LDS03A Joined the LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LDS03A. If LDS03A fails to get the time from the server, LDS03A will use the internal time and wait for the next time request ~[[[via Device Status (FPORT=5)>>||anchor="H2.3.1DeviceStatus,FPORT=5"]]].
461 )))
462
463 (((
464
465 )))
466
467 (((
468 (% style="color:red" %)Note(%%): (% style="color:#037691" %)LoRaWAN Server needs to support LoRaWAN v1.0.3(MAC v1.0.3) (%%)or higher to support this MAC command feature.
469 )))
470
471 (((
472
473 )))
474
475 (((
476 (% style="color:#037691" %)**2. **(% style="color:#037691; font-weight:bold" %)**Manually Set Time**
477 )))
478
479 (((
480 Users need to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
481 )))
482
483
484 == 2.5 ​Show Data in DataCake IoT Server ==
485
486 (((
487 (((
488 Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
489 )))
490 )))
491
492 (((
493 (((
494
495 )))
496 )))
497
498 (((
499 (((
500 (% style="color:blue" %)**Step 1**(%%)**: Link TTNv3 to Datacake.**[[https:~~/~~/docs.datacake.de/lorawan/lns/thethingsindustries#create-integration-on-tti>>url:https://docs.datacake.de/lorawan/lns/thethingsindustries#create-integration-on-tti]]
501 )))
502 )))
503
504 (((
505 (((
506 (% style="color:blue" %)**Step 2**(%%)**: Configure LDS03A in Datacake.**
507 )))
508 )))
509
510
511 [[image:1654746350207-427.png]]
512
513
514 [[image:1654747162439-840.png]]
515
516
517 [[image:1654746405400-203.png]]
518
519
520
521 [[image:1654746763908-732.png]]
522
523
524
525 [[image:1654746716087-684.png]]
526
527
528 [[image:1654746693868-718.png]]
529
530
531 [[image:1654746674738-826.png]]
532
533
534 [[image:1654746646379-591.png]]
535
536
537 [[image:1654746549277-209.png]]
538
539
540 [[image:1654746593411-887.png]]
541
542
543
544 = 3.  Configure LDS03A via AT Command or LoRaWAN Downlink =
545
546 (((
547 Use can configure LDS03A via AT Command or LoRaWAN Downlink.
548 )))
549
550 * (((
551 AT Command Connection: See [[FAQ>>||anchor="H5.FAQ"]].
552 )))
553 * (((
554 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
555 )))
556
557 (((
558 There are two kinds of commands to configure LDS03A, they are:
559 )))
560
561 * (((
562 (% style="color:#4f81bd" %)** General Commands**.
563 )))
564
565 (((
566 These commands are to configure:
567 )))
568
569 * (((
570 General system settings like: uplink interval.
571 )))
572 * (((
573 LoRaWAN protocol & radio related command.
574 )))
575
576 (((
577 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]]
578 )))
579
580 (((
581
582 )))
583
584 * (((
585 (% style="color:#4f81bd" %)** Commands special design for LDS03A**
586 )))
587
588 (((
589 These commands only valid for LDS03A, as below:
590 )))
591
592
593 == 3.1  Set Transmit Interval Time ==
594
595 Feature: Change LoRaWAN End Node Transmit Interval.
596
597 (% style="color:#037691" %)**AT Command: AT+TDC**
598
599 [[image:image-20220607171554-8.png]]
600
601
602 (((
603 (% style="color:#037691" %)**Downlink Command: 0x01**
604 )))
605
606 (((
607 Format: Command Code (0x01) followed by 3 bytes time value.
608 )))
609
610 (((
611 If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
612 )))
613
614 * (((
615 Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
616 )))
617 * (((
618 Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
619
620
621 )))
622
623 == 3.2 Set Password ==
624
625 Feature: Set device password, max 9 digits
626
627 (% class="box infomessage" %)
628 (((
629 **AT Command: AT+PWORD**
630 )))
631
632 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:404.989px" %)
633 |=(% style="width: 170px;" %)**Command Example**|=(% style="width: 123px;" %)**Function**|=(% style="width: 109px;" %)**Response**
634 |(% style="width:170px" %)(((
635 AT+PWORD=?
636 )))|(% style="width:123px" %)(((
637 Show password
638 )))|(% style="width:109px" %)(((
639 (((
640 123456
641 )))
642
643 (((
644 OK
645 )))
646 )))
647 |(% style="width:170px" %)(((
648 AT+PWORD=999999
649 )))|(% style="width:123px" %)(((
650 Set password
651 )))|(% style="width:109px" %)(((
652 OK
653 )))
654
655 (% style="color:#4f81bd" %)**Downlink Command:**
656
657 No downlink command for this feature.
658
659
660
661 == 3.3 Quit AT Command ==
662
663 Feature: Quit AT Command mode, so user needs to input the password again before using AT Commands.
664
665 (% class="box infomessage" %)
666 (((
667 **AT Command: AT+DISAT**
668 )))
669
670 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:451.989px" %)
671 |=(% style="width: 155px;" %)**Command Example**|=(% style="width: 198px;" %)**Function**|=(% style="width: 96px;" %)**Response**
672 |(% style="width:155px" %)AT+DISAT|(% style="width:198px" %)Quit AT Commands mode|(% style="width:96px" %)OK
673
674 (% style="color:#4f81bd" %)**Downlink Command:**
675
676 No downlink command for this feature.
677
678
679
680 == 3.4 Enable / Disable Alarm ==
681
682 Feature: Enable/Disable Alarm for open/close event. Default value 0.
683
684 (% style="color:#4f81bd" %)**AT Command:**
685
686 [[image:image-20220609140712-1.png]]
687
688
689 (% style="color:#4f81bd" %)**Downlink Command:**
690
691 0xA7 01 ~/~/Same As AT+DISALARM=1
692
693 0xA7 00 ~/~/ Same As AT+DISALARM=0
694
695
696
697 == 3.5  Clear count ==
698
699 Feature: Clear current door open.
700
701 **AT Command:**
702
703 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510.222px" %)
704 |=(% style="width: 155px;" %)**Command Example**|=(% style="width: 266px;" %)**Function**|=(% style="width: 85px;" %)**Response**
705 |(% style="width:155px" %)AT+CLRC|(% style="width:266px" %)Clear the count of door open events.|(% style="width:85px" %)OK
706
707 **Downlink Command:**
708
709 0xA6 01 ~/~/ Same As AT+ CLRC
710
711
712
713 == 3.6  Set system time ==
714
715 Feature: Set system time, Unix format. [[See here for format detail.>>||anchor="H2.4.1UnixTimeStamp"]]
716
717 **AT Command:**
718
719 [[image:image-20220609141735-2.png]]
720
721
722 **Downlink Command:**
723
724 0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
725
726
727
728
729 == 3.8 Alarm Base on Timeout ==
730
731 (((
732 CPL01 can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
733 )))
734
735 (((
736 **~1. Keep Status: Status to be monitor**
737 )))
738
739 (((
740 Keep Status = 1: Monitor Close to Open event
741 )))
742
743 (((
744 Keep Status = 0: Monitor Open to Close event
745 )))
746
747 (((
748 **2. Keep Time: Timeout to send an Alarm**
749 )))
750
751 (((
752 Range 0 ~~ 65535(0xFFFF) seconds.
753 )))
754
755 (((
756 If keep time = 0, Disable Alarm Base on Timeout feature.
757 )))
758
759 (((
760 If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
761 )))
762
763 (((
764 (% style="color:#4f81bd" %)**AT Command**(%%) to configure:
765 )))
766
767 * (% class="box infomessage" %)
768 (((
769 **AT+TTRIG=1,30**  ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CPL01 will send an uplink packet, the [[Alarm bit>>path:#open_close_value]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
770 )))
771
772 * (% class="box infomessage" %)
773 (((
774 **AT+TTIG=0,0 ** ~-~-> Default Value, disable timeout Alarm.
775 )))
776
777 (((
778 (% style="color:#4f81bd" %)**Downlink Command**(%%) to configure:
779 )))
780
781 (% class="box infomessage" %)
782 (((
783 Command: 0xA9 aa bb cc
784 )))
785
786 (((
787 A9: Command Type Code
788 )))
789
790 (((
791 aa: status to be monitored
792 )))
793
794 (((
795 bb cc: timeout.
796 )))
797
798
799 (((
800 If user send 0xA9 01 00 1E: equal to AT+TTRIG=1,30
801 )))
802
803 (((
804 Or
805 )))
806
807 (((
808 0xA9 00 00 00: Equal to AT+TTRIG=0,0. Disable timeout Alarm.
809 )))
810
811
812
813 == 3.9 Clear Flash Record ==
814
815 Feature: Clear flash storage for data log feature.
816
817 (% class="box infomessage" %)
818 (((
819 **AT Command: AT+CLRDTA**
820 )))
821
822 (% border="1" style="background-color:#ffffcc; color:green; width:689.989px" %)
823 |(% style="width:159px" %)**Command Example**|(% style="width:290px" %)**Function**|(% style="width:237px" %)**Response**
824 |(% style="width:159px" %)AT+CLRDTA|(% style="width:290px" %)Clear flash storage for data log feature.|(% style="width:237px" %)Clear all stored sensor data… OK
825
826 (((
827 (% style="color:#4f81bd" %)**Downlink Command:**
828 )))
829
830 (% class="box infomessage" %)
831 (((
832 (((
833 ➢ **Example**: 0xA301 ~/~/Same as AT+CLRDTA
834 )))
835 )))
836
837
838
839
840
841 = 4. Battery & How to replace =
842
843 == 4.1 Battery Type ==
844
845 (((
846 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.
847 )))
848
849 (((
850 The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
851 )))
852
853 [[image:1654593587246-335.png]]
854
855
856 Minimum Working Voltage for the LSPH01:
857
858 LSPH01:  2.45v ~~ 3.6v
859
860
861
862 == 4.2 Replace Battery ==
863
864 (((
865 Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
866 )))
867
868 (((
869 And make sure the positive and negative pins match.
870 )))
871
872
873
874 == 4.3 Power Consumption Analyze ==
875
876 (((
877 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.
878 )))
879
880 (((
881 Instruction to use as below:
882 )))
883
884
885 **Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
886
887 [[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/]]
888
889
890 **Step 2**: Open it and choose
891
892 * Product Model
893 * Uplink Interval
894 * Working Mode
895
896 And the Life expectation in difference case will be shown on the right.
897
898 [[image:1654593605679-189.png]]
899
900
901 The battery related documents as below:
902
903 * (((
904 [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
905 )))
906 * (((
907 [[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
908 )))
909 * (((
910 [[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]]
911 )))
912
913 [[image:image-20220607172042-11.png]]
914
915
916
917 === 4.3.1 ​Battery Note ===
918
919 (((
920 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.
921 )))
922
923
924
925 === ​4.3.2 Replace the battery ===
926
927 (((
928 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.
929 )))
930
931 (((
932 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)
933 )))
934
935
936
937 = 5. Use AT Command =
938
939 == 5.1 Access AT Commands ==
940
941 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.
942
943 [[image:1654593668970-604.png]]
944
945 **Connection:**
946
947 (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
948
949 (% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
950
951 (% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
952
953
954 (((
955 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:
956 )))
957
958
959 [[image:1654593712276-618.png]]
960
961 Valid AT Command please check [[Configure Device>>||anchor="H3.ConfigureLSPH01viaATCommandorLoRaWANDownlink"]].
962
963
964 = 6. FAQ =
965
966 == 6.1 How to change the LoRa Frequency Bands/Region ==
967
968 You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
969 When downloading the images, choose the required image file for download. ​
970
971
972 = 7. Trouble Shooting =
973
974 == 7.1 AT Commands input doesn’t work ==
975
976 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.
977
978
979
980 = 8. Order Info =
981
982 Part Number: (% style="color:blue" %)**LSPH01-XX**
983
984
985 (% style="color:blue" %)**XX**(%%): The default frequency band
986
987 * (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
988 * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
989 * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
990 * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
991 * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
992 * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
993 * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
994 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
995
996 = 9. ​Packing Info =
997
998
999 **Package Includes**:
1000
1001 * LSPH01 LoRaWAN Soil Ph Sensor x 1
1002
1003 **Dimension and weight**:
1004
1005 * Device Size: cm
1006 * Device Weight: g
1007 * Package Size / pcs : cm
1008 * Weight / pcs : g
1009
1010 = 10. ​Support =
1011
1012 * 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.
1013 * 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]].
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0