Version 129.1 by Xiaoling on 2022/06/09 14:43
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
73
74 == 1.3  Storage & Operation Temperature ==
75
76
77 -40°C to +85°C
78
79
80 == 1.4  ​Applications ==
81
82
83 [[image:1654741400370-813.png]]
84
85
86
87 == 1.5  Mechanical ==
88
89 [[image:1654741444887-479.png]]
90
91
92 [[image:1654741488515-626.png]]
93
94 [[image:1654741510204-377.png]]
95
96
97 == 1.6  Pin Definitions and Switch ==
98
99 [[image:1654741572060-177.png]]
100
101 **LDS03A is based on LSN50v2**
102
103
104 === 1.6.1  Pin Definition ===
105
106 (((
107 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/]]
108 )))
109
110
111 === 1.6.2  Jumper JP2(Power ON/OFF) ===
112
113 Power on Device when putting this jumper.
114
115
116 === 1.6.3  BOOT MODE / SW1 ===
117
118 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.
119
120 2) Flash: work mode, the device starts to work and send out console output for further debug
121
122
123 === 1.6.4  Reset Button ===
124
125 Press to reboot the device.
126
127
128 === 1.6.5  LED ===
129
130 It will flash:
131
132 1. Boot the device in flash mode
133 1. Send an uplink packet
134
135
136
137 = 2.  Operation Mode =
138
139 == 2.1  How it works ==
140
141 (((
142 (((
143 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.
144 )))
145 )))
146
147
148 == 2.2  Example to use for LoRaWAN network ==
149
150 (((
151 This section shows an example of how to join the TTN V3 LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are similar.
152 )))
153
154 (((
155 [[image:1654742304325-850.png]]
156
157
158 )))
159
160 (((
161 * 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.
162
163 (((
164 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:
165 )))
166 )))
167
168 (((
169 (((
170 (% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from LDS03A.
171 )))
172
173 (((
174 Each LDS03A is shipped with a sticker with the default device EUI as below:
175 )))
176 )))
177
178 [[image:image-20220607170145-1.jpeg]]
179
180
181 Users can enter these keys in the LoRaWAN Server portal. Below is the TTN V3 screenshot:
182
183 Add APP EUI in the application.
184
185 [[image:1654742558691-332.png]]
186
187
188 [[image:1654742595660-519.png]]
189
190
191 [[image:1654742610413-498.png]]
192
193
194 [[image:1654742630064-347.png]]
195
196 **Add APP KEY and DEV EUI**
197
198
199 (% style="color:blue" %)**Step 2**(%%): Power on LDS03A
200
201 [[image:1654742860601-778.png]]
202
203
204 (((
205 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.
206 )))
207
208
209 [[image:image-20220609104802-1.png||height="369" width="1123"]]
210
211
212 == 2.3  ​Uplink Payload ==
213
214 (((
215 (((
216 Uplink payloads have two types:
217 )))
218
219 * (((
220 Open/Close Status: Use FPORT=2
221 )))
222 * (((
223 Other control commands: Use other FPORT fields.
224 )))
225
226 (((
227 The application server should parse the correct value based on FPORT settings.
228 )))
229
230 (((
231
232 )))
233
234 === 2.3.1  Device Status, FPORT~=5 ===
235 )))
236
237 (((
238 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.
239 )))
240
241 (((
242 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.
243 )))
244
245 [[image:image-20220609105437-3.png]]
246
247
248 Example parse in TTNv3
249
250 [[image:image-20220609105101-2.png||height="295" width="1208"]]
251
252 * (% style="color:#4f81bd" %)**Sensor Model**(%%): For LDS03A, this value is 0x0A
253
254 * (% style="color:#4f81bd" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version
255
256 * (% style="color:#4f81bd" %)**Frequency Band**:
257
258 *0x01: EU868
259
260 *0x02: US915
261
262 *0x03: IN865
263
264 *0x04: AU915
265
266 *0x05: KZ865
267
268 *0x06: RU864
269
270 *0x07: AS923
271
272 *0x08: AS923-1
273
274 *0x09: AS923-2
275
276 *0x0a: AS923-3
277
278 *0x0b: CN470
279
280 *0x0c: EU433
281
282 *0x0d: KR920
283
284 *0x0e: MA869
285
286
287 * (% style="color:#4f81bd" %)**Sub-Band**:
288 ** AU915 and US915:value 0x00 ~~ 0x08
289 ** CN470: value 0x0B ~~ 0x0C
290 ** Other Bands: Always 0x00
291
292 * (% style="color:#4f81bd" %)**Battery Info:**
293
294 Check the battery voltage.
295
296 Ex1: 0x0B45 = 2885mV
297
298 Ex2: 0x0B49 = 2889mV
299
300
301
302 === 2.3.2  Sensor Configuration, FPORT~=4 ===
303
304 LDS03A will only send this command after getting the downlink command (0x26 02) from the server.
305
306 [[image:image-20220609110123-5.png]]
307
308
309 * (% style="color:#4f81bd" %)**TDC: (default: 0x001C20)**
310
311 Uplink interval for the Open/Close Event, default value is 0x001C20 which is 7200 seconds = 2 hours.
312
313
314 * (% style="color:#4f81bd" %)**Disalarm: (default: 0)**
315
316 (% 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.
317
318 (% 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.
319
320 Note: When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
321
322
323 * (% style="color:#4f81bd" %)**Keep Status & Keep Time**
324
325 Shows the configure value of [[Alarm Base on Timeout Feature>>||anchor="H3.8AlarmBaseonTimeout"]]
326
327
328 [[image:image-20220609110018-4.png||height="291" width="1159"]]
329
330
331
332 === 2.3.3  Real-Time Open/Close Status, Uplink FPORT~=2 ===
333
334 LDS03A will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS03A will:
335
336
337 1. periodically send this uplink every 2 hours, this interval [[can be changed>>||anchor="H3.1SetTransmitIntervalTime"]].
338 1. There is an Open/Close event. 
339
340 Uplink Payload totals 11 bytes.
341
342 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:495px" %)
343 |(% colspan="5" style="width:492px" %)**Real-Time Open/Close Status, FPORT=2**
344 |(% style="width:101px" %)**Size (bytes)**|(% style="width:77px" %)**1**|(% style="width:99px" %)**3**|(% style="width:88px" %)**3**|(% style="width:126px" %)**4**
345 |(% style="width:101px" %)**Value**|(% style="width:77px" %)Status & [[Alarm>>||anchor="H3.8AlarmBaseonTimeout"]]|(% style="width:99px" %)Total open door events|(% style="width:88px" %)(((
346 The last door open
347
348 duration (unit: min)
349 )))|(% style="width:126px" %)[[Unix TimeStamp>>||anchor="H2.4.1UnixTimeStamp"]]
350
351 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:509px" %)
352 |(% colspan="4" style="width:506px" %)**Status & Alarm field**
353 |(% style="width:82px" %)**Size (bit)**|(% style="width:71px" %)**6**|(% style="width:221px" %)**1**|(% style="width:130px" %)**1**
354 |(% style="width:82px" %)**Value**|(% style="width:71px" %)Reserve|(% style="width:221px" %)[[Enable/disable Timeout Alarm>>||anchor="H3.8AlarmBaseonTimeout"]]
355 0: No Alarm; 1: Alarm|(% style="width:130px" %)Status
356 0: Close, 1: Open
357
358 [[image:image-20220609110547-6.png||height="337" width="1191"]]
359
360
361
362 === 2.3.4  Historical Door Open/Close Event, FPORT~=3 ===
363
364 LDS03A stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.4DatalogFeature"]].
365
366 The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time open/close status.
367
368
369 * 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.
370
371 For example, in the US915 band, the max payload for different DR is:
372
373 a)      DR0: max is 11 bytes so one entry of data
374
375 b)      DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
376
377 c)      DR2: total payload includes 11 entries of data
378
379 d)       DR3: total payload includes 22 entries of data.
380
381 If LDS03A doesn’t have any data in the polling time. It will uplink 11 bytes of 0
382
383
384 [[image:image-20220609112215-7.png||height="277" width="1250"]]
385
386 (% style="color:#037691" %)**Downlink:**
387
388 0x31 61 8E 57 40 61 8E 81 70 05
389
390
391 (% style="color:#037691" %)**Uplink:**
392
393 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
394
395
396 (% style="color:#037691" %)**Parsed Value:**
397
398 [ALARM, DOOR_OPEN_STATUS, DOOR_OPEN_TIMES,LAST_DOOR_OPEN_DURATION, TIME]
399
400
401 [FALSE, CLOSE, 0, 0, 2021-11-12 12:35:27],
402
403 [FALSE, OPEN,  1, 0, 2021-11-12 12:36:34],
404
405 [FALSE, CLOSE, 1, 2, 2021-11-12 12:39:00],
406
407 [FALSE, OPEN,  2, 2, 2021-11-12 12:39:17],
408
409 [FALSE, CLOSE, 2, 1, 2021-11-12 12:40:38],
410
411 [FALSE, CLOSE, 2, 1, 2021-11-12 14:35:19],
412
413 [FALSE, OPEN,  3, 1, 2021-11-12 14:50:32],
414
415 [FALSE, CLOSE, 3, 2, 2021-11-12 14:53:02],
416
417 [FALSE, OPEN,  4, 2, 2021-11-12 14:58:35],
418
419 [FALSE, CLOSE, 4, 0, 2021-11-12 14:59:28],
420
421
422
423 == 2.4  Datalog Feature ==
424
425 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.
426
427
428 === 2.4.1  Unix TimeStamp ===
429
430 LDS03A use Unix TimeStamp format based on
431
432 [[image:image-20220609113256-8.png]]
433
434
435 (((
436 Users can get this time from the link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
437 )))
438
439 (((
440 Below is the converter example
441 )))
442
443 [[image:image-20220609113256-9.png||height="467" width="1127"]]
444
445 (((
446 So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
447 )))
448
449
450 === 2.4.2  Set Device Time ===
451
452 (((
453 There are two ways to set the device’s time:
454 )))
455
456 (((
457 (% style="color:#037691" %)**1. Through LoRaWAN MAC Command (Default settings)**
458 )))
459
460 (((
461 Users need to set SYNCMOD=1 to enable sync time via the MAC command.
462 )))
463
464 (((
465 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"]]].
466 )))
467
468 (((
469
470 )))
471
472 (((
473 (% 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.
474 )))
475
476 (((
477
478 )))
479
480 (((
481 (% style="color:#037691" %)**2. **(% style="color:#037691; font-weight:bold" %)**Manually Set Time**
482 )))
483
484 (((
485 Users need to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
486 )))
487
488
489 == 2.5 ​Show Data in DataCake IoT Server ==
490
491 (((
492 (((
493 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:
494 )))
495 )))
496
497 (((
498 (((
499
500 )))
501 )))
502
503 (((
504 (((
505 (% 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]]
506 )))
507 )))
508
509 (((
510 (((
511 (% style="color:blue" %)**Step 2**(%%)**: Configure LDS03A in Datacake.**
512 )))
513 )))
514
515
516 [[image:1654746350207-427.png]]
517
518
519 [[image:1654747162439-840.png]]
520
521
522 [[image:1654746405400-203.png]]
523
524
525
526 [[image:1654746763908-732.png]]
527
528
529
530 [[image:1654746716087-684.png]]
531
532
533 [[image:1654746693868-718.png]]
534
535
536 [[image:1654746674738-826.png]]
537
538
539 [[image:1654746646379-591.png]]
540
541
542 [[image:1654746549277-209.png]]
543
544
545 [[image:1654746593411-887.png]]
546
547
548
549 = 3.  Configure LDS03A via AT Command or LoRaWAN Downlink =
550
551 (((
552 Use can configure LDS03A via AT Command or LoRaWAN Downlink.
553 )))
554
555 * (((
556 AT Command Connection: See [[FAQ>>||anchor="H5.FAQ"]].
557 )))
558 * (((
559 LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
560 )))
561
562 (((
563 There are two kinds of commands to configure LDS03A, they are:
564 )))
565
566 * (((
567 (% style="color:#4f81bd" %)** General Commands**.
568 )))
569
570 (((
571 These commands are to configure:
572 )))
573
574 * (((
575 General system settings like: uplink interval.
576 )))
577 * (((
578 LoRaWAN protocol & radio related command.
579 )))
580
581 (((
582 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]]
583 )))
584
585 (((
586
587 )))
588
589 * (((
590 (% style="color:#4f81bd" %)** Commands special design for LDS03A**
591 )))
592
593 (((
594 These commands only valid for LDS03A, as below:
595 )))
596
597
598 == 3.1  Set Transmit Interval Time ==
599
600 Feature: Change LoRaWAN End Node Transmit Interval.
601
602 (% style="color:#037691" %)**AT Command: AT+TDC**
603
604 [[image:image-20220607171554-8.png]]
605
606
607 (((
608 (% style="color:#037691" %)**Downlink Command: 0x01**
609 )))
610
611 (((
612 Format: Command Code (0x01) followed by 3 bytes time value.
613 )))
614
615 (((
616 If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
617 )))
618
619 * (((
620 Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
621 )))
622 * (((
623 Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
624
625
626 )))
627
628 == 3.2 Set Password ==
629
630 Feature: Set device password, max 9 digits
631
632 (% class="box infomessage" %)
633 (((
634 **AT Command: AT+PWORD**
635 )))
636
637 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:404.989px" %)
638 |=(% style="width: 170px;" %)**Command Example**|=(% style="width: 123px;" %)**Function**|=(% style="width: 109px;" %)**Response**
639 |(% style="width:170px" %)(((
640 AT+PWORD=?
641 )))|(% style="width:123px" %)(((
642 Show password
643 )))|(% style="width:109px" %)(((
644 (((
645 123456
646 )))
647
648 (((
649 OK
650 )))
651 )))
652 |(% style="width:170px" %)(((
653 AT+PWORD=999999
654 )))|(% style="width:123px" %)(((
655 Set password
656 )))|(% style="width:109px" %)(((
657 OK
658 )))
659
660 (% style="color:#4f81bd" %)**Downlink Command:**
661
662 No downlink command for this feature.
663
664
665
666 == 3.3 Quit AT Command ==
667
668 Feature: Quit AT Command mode, so user needs to input the password again before using AT Commands.
669
670 (% class="box infomessage" %)
671 (((
672 **AT Command: AT+DISAT**
673 )))
674
675 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:451.989px" %)
676 |=(% style="width: 155px;" %)**Command Example**|=(% style="width: 198px;" %)**Function**|=(% style="width: 96px;" %)**Response**
677 |(% style="width:155px" %)AT+DISAT|(% style="width:198px" %)Quit AT Commands mode|(% style="width:96px" %)OK
678
679 (% style="color:#4f81bd" %)**Downlink Command:**
680
681 No downlink command for this feature.
682
683
684
685 == 3.4 Enable / Disable Alarm ==
686
687 Feature: Enable/Disable Alarm for open/close event. Default value 0.
688
689 (% style="color:#4f81bd" %)**AT Command:**
690
691 [[image:image-20220609140712-1.png]]
692
693
694 (% style="color:#4f81bd" %)**Downlink Command:**
695
696 0xA7 01 ~/~/Same As AT+DISALARM=1
697
698 0xA7 00 ~/~/ Same As AT+DISALARM=0
699
700
701
702 == 3.5  Clear count ==
703
704 Feature: Clear current door open.
705
706 (% style="color:#4f81bd" %)**AT Command:**
707
708 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510.222px" %)
709 |=(% style="width: 155px;" %)**Command Example**|=(% style="width: 266px;" %)**Function**|=(% style="width: 85px;" %)**Response**
710 |(% style="width:155px" %)AT+CLRC|(% style="width:266px" %)Clear the count of door open events.|(% style="width:85px" %)OK
711
712 (% style="color:#4f81bd" %)**Downlink Command:**
713
714 0xA6 01 ~/~/ Same As AT+ CLRC
715
716
717
718 == 3.6  Set system time ==
719
720 Feature: Set system time, Unix format. [[See here for format detail.>>||anchor="H2.4.1UnixTimeStamp"]]
721
722 (% style="color:#4f81bd" %)**AT Command:**
723
724 [[image:image-20220609141735-2.png]]
725
726
727 (% style="color:#4f81bd" %)**Downlink Command:**
728
729 0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352
730
731
732
733 == 3.7  Set Time Sync Mode ==
734
735 Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply to this command.
736
737 SYNCMOD is set to 1 by default. If user wants to set a different time from the LoRaWAN server, the user needs to set this to 0.
738
739
740 (% style="color:#4f81bd" %)**AT Command:**
741
742 [[image:image-20220609142205-4.png]]
743
744
745 (% style="color:#4f81bd" %)**Downlink Command:**
746
747 0x28 01 ~/~/ Same As AT+SYNCMOD=1
748
749 0x28 01 08 ~/~/ Same As AT+SYNCMOD=1,8
750
751 0x28 01 F4 ~/~/ Same As AT+SYNCMOD=1,-12
752
753 0x28 00 ~/~/ Same As AT+SYNCMOD=0
754
755
756 == 3.8 Alarm Base on Timeout ==
757
758 (((
759 LDS03A 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:
760
761
762 * (% style="color:#4f81bd" %)**Keep Status: Status to be monitor**
763
764 Keep Status = 1: Monitor Close to Open event
765
766 Keep Status = 0: Monitor Open to Close event
767
768
769 * (% style="color:#4f81bd" %)**Keep Time: Timeout to send an Alarm**
770
771 Range 0 ~~ 65535(0xFFFF) seconds.
772
773 If keep time = 0, Disable Alarm Base on Timeout feature.
774
775 If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
776 )))
777
778 (((
779 (% style="color:#4f81bd" %)**AT Command**(%%) to configure:
780
781 * **AT+TTRIG=1,30**  **~-~->** When the **Keep Status** change from close to open, and device remains in open status for more than 30 seconds. LDS03A 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.
782
783 * **AT+TTIG=0,0**  **~-~-> ** Default Value, disable timeout Alarm.
784 )))
785
786 (((
787
788
789 (% style="color:#4f81bd" %)**Downlink Command**(%%) to configure:
790
791 **Command: 0xA9 aa bb cc**
792 )))
793
794 (((
795 A9: Command Type Code
796 )))
797
798 (((
799 aa: status to be monitored
800 )))
801
802 (((
803 bb cc: timeout.
804 )))
805
806
807 (((
808 If user send 0xA9 01 00 1E: equal to AT+TTRIG=1,30
809 )))
810
811 (((
812 Or
813 )))
814
815 (((
816 0xA9 00 00 00: Equal to AT+TTRIG=0,0. Disable timeout Alarm.
817 )))
818
819
820
821 == 3.9 Clear Flash Record ==
822
823 Feature: Clear flash storage for data log feature.
824
825 (% style="color:#4f81bd" %)**AT Command: AT+CLRDTA**
826
827 [[image:image-20220609142912-5.png]]
828
829
830 (((
831 (% style="color:#4f81bd" %)**Downlink Command:**
832
833 Example: 0xA301 ~/~/Same as AT+CLRDTA
834 )))
835
836
837
838 = 4. Battery & How to replace =
839
840 == 4.1 Battery Type ==
841
842 (((
843 (((
844 LDS03A is equipped with a [[8500mAH ER18505 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is an un-rechargeable battery with a low discharge rate targeting 8~~10 years of use. This type of battery is commonly used in IoT targets for long-term running, such as water meters.
845 )))
846
847 (((
848 The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
849 )))
850 )))
851
852 [[image:1654593587246-335.png]]
853
854
855 Minimum Working Voltage for the LDS03A:
856
857 LDS03A:  2.45v ~~ 3.6v
858
859
860
861 == 4.2 Replace Battery ==
862
863 (((
864 Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
865 )))
866
867 (((
868 And make sure the positive and negative pins match.
869 )))
870
871
872
873 == 4.3 Power Consumption Analyze ==
874
875 (((
876 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.
877 )))
878
879 (((
880 Instruction to use as below:
881 )))
882
883
884 **Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
885
886 [[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/]]
887
888
889 **Step 2**: Open it and choose
890
891 * Product Model
892 * Uplink Interval
893 * Working Mode
894
895 And the Life expectation in difference case will be shown on the right.
896
897 [[image:1654593605679-189.png]]
898
899
900 The battery related documents as below:
901
902 * (((
903 [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
904 )))
905 * (((
906 [[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
907 )))
908 * (((
909 [[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]]
910 )))
911
912 [[image:image-20220609143952-1.png]]
913
914
915
916 === 4.3.1 ​Battery Note ===
917
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
926 === ​4.3.2 Replace the battery ===
927
928 (((
929 (((
930 You can change the battery in the LDS03A.The type of battery is not limited as long as the output is between 3v to 3.6v.
931 )))
932
933 (((
934 The default battery pack of LDS03A includes an ER18505 plus super capacitor. If user can’t find this pack locally, they can find ER18505 or equivalence, which will also work in most cases. The SPC can enlarge the battery life for high-frequency use (update period below 5 minutes)
935 )))
936 )))
937
938
939
940 = 5. Use AT Command =
941
942 == 5.1 Access AT Commands ==
943
944 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.
945
946 [[image:1654593668970-604.png]]
947
948 **Connection:**
949
950 (% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
951
952 (% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
953
954 (% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
955
956
957 (((
958 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:
959 )))
960
961
962 [[image:1654593712276-618.png]]
963
964 Valid AT Command please check [[Configure Device>>||anchor="H3.ConfigureLSPH01viaATCommandorLoRaWANDownlink"]].
965
966
967 = 6. FAQ =
968
969 == 6.1 How to change the LoRa Frequency Bands/Region ==
970
971 You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
972 When downloading the images, choose the required image file for download. ​
973
974
975 = 7. Trouble Shooting =
976
977 == 7.1 AT Commands input doesn’t work ==
978
979 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.
980
981
982
983 = 8. Order Info =
984
985 Part Number: (% style="color:blue" %)**LSPH01-XX**
986
987
988 (% style="color:blue" %)**XX**(%%): The default frequency band
989
990 * (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
991 * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
992 * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
993 * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
994 * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
995 * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
996 * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
997 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
998
999 = 9. ​Packing Info =
1000
1001
1002 **Package Includes**:
1003
1004 * LSPH01 LoRaWAN Soil Ph Sensor x 1
1005
1006 **Dimension and weight**:
1007
1008 * Device Size: cm
1009 * Device Weight: g
1010 * Package Size / pcs : cm
1011 * Weight / pcs : g
1012
1013 = 10. ​Support =
1014
1015 * 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.
1016 * 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]].

Applications

Navigation

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