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