LDS03A - Outdoor LoRaWAN Open/Close Door Sensor Manual

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.

)))

(((

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.

)))

(((

LDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from LoRaWAN.

)))

(((

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.

)))

(((

LDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.

)))

(((

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.

)))

(((

*Battery life depends on how often to send data, please see [[battery analyzer>>||anchor="H4.Battery26Howtoreplace"]].

)))

)))

== 1.2 Features ==

* 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

* Wall Mountable

* Outdoor Use

== 1.3 Storage & Operation Temperature ==

-40°C to +85°C

== 1.4 Applications ==

89

90

91

[[image:1654741400370-813.png]]

== 1.5 Mechanical ==

[[image:1654741444887-479.png]]

98

99

100

[[image:1654741488515-626.png]]

101

102

103

[[image:1654741510204-377.png]]

104

105

106

== 1.6 Pin Definitions and Switch ==

107

108

[[image:1654741572060-177.png]]

109

110

**LDS03A is based on LSN50v2**

111

112

113

=== 1.6.1 Pin Definition ===

114

115

(((

116

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/]]

)))

=== 1.6.2 Jumper JP2(Power ON/OFF) ===

121

122

Power on Device when putting this jumper.

123

124

125

=== 1.6.3 BOOT MODE / SW1 ===

126

127

(((

128

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.

)))

(((

2) Flash: work mode, the device starts to work and send out console output for further debug

)))

=== 1.6.4 Reset Button ===

137

138

Press to reboot the device.

=== 1.6.5 LED ===

It will flash:

1. Boot the device in flash mode

146

1. Send an uplink packet

147

148

= 2. Operation Mode =

149

150

== 2.1 How it works ==

(((

(((

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.

)))

)))

== 2.2 Example to use for LoRaWAN network ==

160

161

(((

162

This section shows an example of how to join the TTN V3 LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are similar.

)))

(((

[[image:1654742304325-850.png]]

)))

(((

* 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.

(((

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:

)))

)))

(((

(((

(% style="color:blue" %)**Step 1**(%%): Create a device in TTN V3 with the OTAA keys from LDS03A.

)))

(((

Each LDS03A is shipped with a sticker with the default device EUI as below:

)))

)))

[[image:image-20220607170145-1.jpeg]]

192

193

194

Users can enter these keys in the LoRaWAN Server portal. Below is the TTN V3 screenshot:

195

196

**Add APP EUI in the application:**

197

198

[[image:1654742558691-332.png]]

199

200

201

[[image:1654742595660-519.png]]

202

203

204

[[image:1654742610413-498.png]]

[[image:1654742630064-347.png]]

209

210

**Add APP KEY and DEV EUI**

211

212

213

(% style="color:blue" %)**Step 2**(%%): Power on LDS03A

214

215

[[image:1654742860601-778.png]]

(((

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.

)))

[[image:image-20220609104802-1.png||height="369" width="1123"]]

224

225

226

== 2.3 Uplink Payload ==

(((

(((

Uplink payloads have two types:

)))

* (((

Open/Close Status: Use FPORT=2

235

)))

236

* (((

237

Other control commands: Use other FPORT fields.

)))

(((

The application server should parse the correct value based on FPORT settings.

)))

(((

)))

=== 2.3.1 Device Status, FPORT~=5 ===

)))

(((

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.

)))

(((

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.

257

)))

258

259

[[image:image-20220609105437-3.png]]

260

261

262

Example parse in TTNv3

263

264

[[image:image-20220609105101-2.png||height="295" width="1208"]]

265

266

* (% style="color:#4f81bd" %)**Sensor Model**(%%): For LDS03A, this value is 0x0A

267

268

* (% style="color:#4f81bd" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version

269

270

* (% style="color:#4f81bd" %)**Frequency Band**:

*0x01: EU868

*0x02: US915

*0x03: IN865

*0x04: AU915

*0x05: KZ865

*0x06: RU864

*0x07: AS923

*0x08: AS923-1

*0x09: AS923-2

*0x0a: AS923-3

*0x0b: CN470

*0x0c: EU433

*0x0d: KR920

*0x0e: MA869

* (% style="color:#4f81bd" %)**Sub-Band**:

303

** AU915 and US915:value 0x00 ~~ 0x08

304

** CN470: value 0x0B ~~ 0x0C

305

** Other Bands: Always 0x00

306

307

* (% style="color:#4f81bd" %)**Battery Info:**

308

309

Check the battery voltage.

Ex1: 0x0B45 = 2885mV

Ex2: 0x0B49 = 2889mV

=== 2.3.2 Sensor Configuration, FPORT~=4 ===

317

318

(((

319

LDS03A will only send this command after getting the downlink command (0x26 02) from the server.

)))

(((

[[image:image-20220609110123-5.png]]

)))

(((

)))

* (((

(% style="color:#4f81bd" %)**TDC: (default: 0x001C20)**

)))

(((

Uplink interval for the Open/Close Event, default value is 0x001C20 which is 7200 seconds = 2 hours.

)))

(((

)))

* (((

(% style="color:#4f81bd" %)**Disalarm: (default: 0)**

)))

(((

(% 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.

)))

(((

(% 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.

)))

(((

Note: When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.

)))

(((

)))

* (((

(% style="color:#4f81bd" %)**Keep Status & Keep Time**

)))

(((

Shows the configure value of [[Alarm Base on Timeout Feature>>||anchor="H3.8AlarmBaseonTimeout"]]

)))

[[image:image-20220609110018-4.png||height="291" width="1159"]]

372

373

374

=== 2.3.3 Real-Time Open/Close Status, Uplink FPORT~=2 ===

375

376

LDS03A will send this uplink **after** Device Status once join the LoRaWAN network successfully. And LDS03A will:

377

378

379

1. periodically send this uplink every 2 hours, this interval [[can be changed>>||anchor="H3.1A0SetTransmitIntervalTime"]].

380

1. There is an Open/Close event.

381

382

Uplink Payload totals 11 bytes.

383

384

(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:495px" %)

385

|(% colspan="5" style="width:492px" %)**Real-Time Open/Close Status, FPORT=2**

386

387

|(% style="width:101px" %)**Value**|(% style="width:77px" %)Status & [[Alarm>>||anchor="H3.8AlarmBaseonTimeout"]]|(% style="width:99px" %)Total open door events|(% style="width:88px" %)(((

The last door open

duration (unit: min)

)))|(% style="width:126px" %)[[Unix TimeStamp>>||anchor="H2.4.1A0UnixTimeStamp"]]

392

393

(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:506.222px" %)

394

|(% colspan="4" style="width:503px" %)**Status & Alarm field**

395

|(% style="width:82px" %)**Size (bit)**|(% style="width:71px" %)**6**|(% style="width:220px" %)**1**|(% style="width:129px" %)**1**

396

|(% style="width:82px" %)**Value**|(% style="width:71px" %)Reserve|(% style="width:220px" %)[[Enable/disable Timeout Alarm>>||anchor="H3.8AlarmBaseonTimeout"]]

397

0: No Alarm; 1: Alarm|(% style="width:129px" %)Status

398

0: Close, 1: Open

399

400

[[image:image-20220609110547-6.png||height="337" width="1191"]]

=== 2.3.4 Historical Door Open/Close Event, FPORT~=3 ===

405

406

(((

407

LDS03A stores sensor values and users can retrieve these history values via the [[downlink command>>||anchor="H2.4A0DatalogFeature"]].

)))

(((

The historical payload includes one or multiplies entries and every entry has the same payload as Real-Time open/close status.

)))

(((

)))

* (((

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.

)))

(((

For example, in the US915 band, the max payload for different DR is:

)))

1. (((

DR0: max is 11 bytes so one entry of data

428

)))

429

1. (((

430

DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)

431

)))

432

1. (((

433

DR2: total payload includes 11 entries of data

434

)))

435

1. (((

436

DR3: total payload includes 22 entries of data.

)))

(((

If LDS03A doesn't have any data in the polling time. It will uplink 11 bytes of 0

)))

[[image:image-20220609112215-7.png||height="277" width="1250"]]

(((

(% style="color:#037691" %)**Downlink:**

)))

(((

0x31 61 8E 57 40 61 8E 81 70 05

)))

(((

)))

(((

(% style="color:#037691" %)**Uplink:**

)))

(((

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

)))

(((

)))

(((

(% style="color:#037691" %)**Parsed Value:**

)))

(((

[ALARM, DOOR_OPEN_STATUS, DOOR_OPEN_TIMES,LAST_DOOR_OPEN_DURATION, TIME]

)))

(((

)))

(((

[FALSE, CLOSE, 0, 0, 2021-11-12 12:35:27],

)))

(((

[FALSE, OPEN, 1, 0, 2021-11-12 12:36:34],

)))

(((

[FALSE, CLOSE, 1, 2, 2021-11-12 12:39:00],

)))

(((

[FALSE, OPEN, 2, 2, 2021-11-12 12:39:17],

)))

(((

[FALSE, CLOSE, 2, 1, 2021-11-12 12:40:38],

)))

(((

[FALSE, CLOSE, 2, 1, 2021-11-12 14:35:19],

)))

(((

[FALSE, OPEN, 3, 1, 2021-11-12 14:50:32],

)))

(((

[FALSE, CLOSE, 3, 2, 2021-11-12 14:53:02],

)))

(((

[FALSE, OPEN, 4, 2, 2021-11-12 14:58:35],

)))

(((

[FALSE, CLOSE, 4, 0, 2021-11-12 14:59:28],

)))

== 2.4 Datalog Feature ==

527

528

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.

529

530

531

=== 2.4.1 Unix TimeStamp ===

532

533

LDS03A use Unix TimeStamp format based on

534

535

[[image:image-20220609113256-8.png]]

(((

Users can get this time from the link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :

)))

(((

Below is the converter example

544

)))

545

546

[[image:image-20220609113256-9.png||height="467" width="1127"]]

(((

So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25

)))

=== 2.4.2 Set Device Time ===

555

556

(((

557

There are two ways to set the device’s time:

)))

(((

(% style="color:#037691" %)**1. Through LoRaWAN MAC Command (Default settings)**

)))

(((

Users need to set SYNCMOD=1 to enable sync time via the MAC command.

)))

(((

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"]]].

)))

(((

)))

(((

(% 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.

)))

(((

)))

(((

(% style="color:#037691" %)**2. **(% style="color:#037691; font-weight:bold" %)**Manually Set Time**

)))

(((

Users need to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.

)))

== 2.5 Show Data in DataCake IoT Server ==

(((

(((

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:

)))

)))

(((

(((

)))

)))

(((

(((

(% 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]]

)))

)))

(((

(((

(% style="color:blue" %)**Step 2**(%%)**: Configure LDS03A in Datacake.**

)))

)))

[[image:1654746350207-427.png]]

623

624

625

[[image:1654747162439-840.png]]

626

627

628

[[image:1654746405400-203.png]]

[[image:1654746763908-732.png]]

[[image:1654746716087-684.png]]

637

638

639

[[image:1654746693868-718.png]]

640

641

642

[[image:1654746674738-826.png]]

643

644

645

[[image:1654746646379-591.png]]

646

647

648

[[image:1654746549277-209.png]]

649

650

651

[[image:1654746593411-887.png]]

= 3. Configure LDS03A via AT Command or LoRaWAN Downlink =

656

657

(((

658

Use can configure LDS03A via AT Command or LoRaWAN Downlink.

)))

* (((

AT Command Connection: See [[FAQ>>||anchor="H5.A0FAQ"]].

663

)))

664

* (((

665

LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]

)))

(((

There are two kinds of commands to configure LDS03A, they are:

)))

* (((

(% style="color:#4f81bd" %)** General Commands**.

)))

(((

These commands are to configure:

)))

* (((

General system settings like: uplink interval.

684

)))

685

* (((

686

LoRaWAN protocol & radio related command.

)))

(((

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]]

)))

(((

)))

* (((

(% style="color:#4f81bd" %)** Commands special design for LDS03A**

)))

(((

These commands only valid for LDS03A, as below:

)))

== 3.1 Set Transmit Interval Time ==

707

708

Feature: Change LoRaWAN End Node Transmit Interval.

709

710

(% style="color:#037691" %)**AT Command: AT+TDC**

711

712

[[image:image-20220607171554-8.png]]

(((

(% style="color:#037691" %)**Downlink Command: 0x01**

)))

(((

Format: Command Code (0x01) followed by 3 bytes time value.

)))

(((

If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.

)))

* (((

Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds

729

)))

730

* (((

731

Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds

)))

== 3.2 Set Password ==

737

738

Feature: Set device password, max 9 digits.

739

740

(% style="color:#4f81bd" %)**AT Command: AT+PWORD**

741

742

(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:404.989px" %)

743

|=(% style="width: 170px;" %)**Command Example**|=(% style="width: 123px;" %)**Function**|=(% style="width: 109px;" %)**Response**

744

|(% style="width:170px" %)(((

745

AT+PWORD=?

746

)))|(% style="width:123px" %)(((

747

Show password

748

)))|(% style="width:109px" %)(((

(((

123456

)))

(((

OK

)))

)))

|(% style="width:170px" %)(((

758

AT+PWORD=999999

759

)))|(% style="width:123px" %)(((

760

Set password

761

)))|(% style="width:109px" %)(((

OK

)))

(% style="color:#4f81bd" %)**Downlink Command:**

766

767

No downlink command for this feature.

768

769

770

== 3.3 Quit AT Command ==

771

772

Feature: Quit AT Command mode, so user needs to input the password again before using AT Commands.

773

774

(% style="color:#4f81bd" %)**AT Command: AT+DISAT**

775

776

(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:451.989px" %)

777

|=(% style="width: 155px;" %)**Command Example**|=(% style="width: 198px;" %)**Function**|=(% style="width: 96px;" %)**Response**

778

|(% style="width:155px" %)AT+DISAT|(% style="width:198px" %)Quit AT Commands mode|(% style="width:96px" %)OK

779

780

(% style="color:#4f81bd" %)**Downlink Command:**

781

782

No downlink command for this feature.

783

784

785

== 3.4 Enable / Disable Alarm ==

786

787

Feature: Enable/Disable Alarm for open/close event. Default value 0.

788

789

(% style="color:#4f81bd" %)**AT Command:**

790

791

[[image:image-20220609140712-1.png]]

792

793

794

(% style="color:#4f81bd" %)**Downlink Command:**

795

796

0xA7 01 ~/~/Same As AT+DISALARM=1

797

798

0xA7 00 ~/~/ Same As AT+DISALARM=0

799

800

801

== 3.5 Clear count ==

802

803

Feature: Clear current door open.

804

805

(% style="color:#4f81bd" %)**AT Command:**

806

807

(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510.222px" %)

808

|=(% style="width: 155px;" %)**Command Example**|=(% style="width: 266px;" %)**Function**|=(% style="width: 85px;" %)**Response**

809

|(% style="width:155px" %)AT+CLRC|(% style="width:266px" %)Clear the count of door open events.|(% style="width:85px" %)OK

810

811

(% style="color:#4f81bd" %)**Downlink Command:**

812

813

0xA6 01 ~/~/ Same As AT+ CLRC

814

815

816

== 3.6 Set system time ==

817

818

Feature: Set system time, Unix format. [[See here for format detail.>>||anchor="H2.4.1A0UnixTimeStamp"]]

819

820

(% style="color:#4f81bd" %)**AT Command:**

821

822

[[image:image-20220609141735-2.png]]

823

824

825

(% style="color:#4f81bd" %)**Downlink Command:**

826

827

0x306007806000 ~/~/ Set timestamp to 0x(6007806000),Same as AT+TIMESTAMP=1611104352

828

829

830

== 3.7 Set Time Sync Mode ==

831

832

(((

833

Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply to this command.

)))

(((

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.

)))

(% style="color:#4f81bd" %)**AT Command:**

842

843

[[image:image-20220609142205-4.png]]

844

845

846

(% style="color:#4f81bd" %)**Downlink Command:**

847

848

0x28 01 ~/~/ Same As AT+SYNCMOD=1

849

850

0x28 01 08 ~/~/ Same As AT+SYNCMOD=1,8

851

852

0x28 01 F4 ~/~/ Same As AT+SYNCMOD=1,-12

853

854

0x28 00 ~/~/ Same As AT+SYNCMOD=0

855

856

857

== 3.8 Alarm Base on Timeout ==

(((

(((

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:

)))

(((

)))

* (((

(% style="color:#4f81bd" %)**Keep Status: Status to be monitor**

)))

(((

Keep Status = 1: Monitor Close to Open event

)))

(((

Keep Status = 0: Monitor Open to Close event

)))

(((

)))

* (((

(% style="color:#4f81bd" %)**Keep Time: Timeout to send an Alarm**

)))

(((

Range 0 ~~ 65535(0xFFFF) seconds.

)))

(((

If keep time = 0, Disable Alarm Base on Timeout feature.

)))

(((

If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.

)))

(((

)))

)))

(((

(((

(% style="color:#4f81bd" %)**AT Command**(%%) to configure:

)))

* (((

**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.

)))

* (((

**AT+TTIG=0,0** **~-~-> ** Default Value, disable timeout Alarm.

)))

)))

(((

(((

)))

(((

(% style="color:#4f81bd" %)**Downlink Command**(%%) to configure:

)))

(((

**Command: 0xA9 aa bb cc**

)))

)))

(((

(((

A9: Command Type Code

)))

)))

(((

(((

aa: status to be monitored

)))

)))

(((

(((

bb cc: timeout.

)))

)))

(((

)))

(((

(((

If user send 0xA9 01 00 1E: equal to AT+TTRIG=1,30

)))

)))

(((

(((

Or

)))

)))

(((

(((

0xA9 00 00 00: Equal to AT+TTRIG=0,0. Disable timeout Alarm.

)))

)))

== 3.9 Clear Flash Record ==

975

976

(((

977

Feature: Clear flash storage for data log feature.

)))

(((

(% style="color:#4f81bd" %)**AT Command: AT+CLRDTA**

)))

(((

[[image:image-20220609142912-5.png]]

)))

(((

)))

(((

(((

(% style="color:#4f81bd" %)**Downlink Command:**

)))

(((

Example: 0xA301 ~/~/Same as AT+CLRDTA

)))

)))

= 4. Battery & How to replace =

1004

1005

== 4.1 Battery Type ==

(((

(((

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.

)))

(((

The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.

)))

)))

[[image:1654593587246-335.png]]

1018

1019

1020

Minimum Working Voltage for the LDS03A:

1021

1022

LDS03A: 2.45v ~~ 3.6v

1023

1024

1025

== 4.2 Replace Battery ==

1026

1027

(((

1028

Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.

)))

(((

And make sure the positive and negative pins match.

)))

== 4.3 Power Consumption Analyze ==

1037

1038

(((

1039

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.

)))

(((

Instruction to use as below:

)))

(% style="color:blue" %)**Step 1**(%%): Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:

1048

1049

[[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/]]

1050

1051

1052

(% style="color:blue" %)**Step 2**(%%): Open it and choose

* Product Model

* Uplink Interval

* Working Mode

And the Life expectation in difference case will be shown on the right.

1059

1060

[[image:1654593605679-189.png]]

1061

1062

1063

The battery related documents as below:

1064

1065

* (((

1066

[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],

1067

)))

1068

* (((

1069

[[Lithium-Thionyl Chloride Battery datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],

1070

)))

1071

* (((

1072

[[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/]]

1073

)))

1074

1075

[[image:image-20220609143952-1.png]]

=== 4.3.1 Battery Note ===

(((

(((

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.

)))

)))

=== 4.3.2 Replace the battery ===

(((

(((

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.

)))

(((

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)

)))

)))

= 5. FAQ =

== 5.1 How to use AT Command to configure LDS03A ==

1104

1105

LDS03A UART connection photo

1106

1107

1108

[[image:1654757007713-791.png]]

(((

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:

)))

[[image:image-20220609144231-3.png||height="644" width="922"]]

1117

1118

1119

== 5.2 How to upgrade the firmware? ==

1120

1121

(((

1122

A new firmware might be available for:

)))

* (((

Support new features

)))

* (((

For bug fix

)))

* (((

Change LoRaWAN bands.

)))

(((

Instruction for how to upgrade: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome||anchor="H2.HardwareUpgradeMethodSupportList"]]

)))

(((

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/]]

)))

== 5.3 How to change the LoRa Frequency Bands/Region? ==

1145

1146

Users can follow the introduction for how to upgrade image. When downloading the images, choose the required image file for download.

1147

1148

1149

= 6. Trouble Shooting =

1150

1151

== 6.1 AT Commands input doesn't work ==

1152

1153

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.

= 7. Order Info =

Part Number: (% style="color:blue" %)**LDS03A-XX**

1159

1160

1161

(% style="color:blue" %)**XX**(%%): The default frequency band

1162

1163

* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band

1164

* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band

1165

* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band

1166

* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band

1167

* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band

1168

* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band

1169

* (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band

1170

* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band

= 8. Packing Info =

**Package Includes**:

1178

1179

* LDS03A Open/Close Sensor x 1

= 9. Support =

* 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.

1187

* 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]].

= 10. FCC Warning =

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions:

1195

1196

(1) This device may not cause harmful interference;