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