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