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

Applications

Navigation

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