CPL01 LoRaWAN Outdoor Pulse/Contact Sensor

The Dragino CPL01 is a LoRaWAN Contact Sensor. It detects open/close status and uplink to IoT server via LoRaWAN network. user can see the dry contact status, open time, open counts in the IoT Server.

22

)))

23

24

(((

25

CPL01 is powered by 8500mAh Li-SOCI2 battery, It is designed for long term use up to 10 years. (Actually Battery life depends on the use environment, update period.)

)))

(((

The CPL01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculate last open duration. User can also disable the uplink for each open/close event, instead, device can count each open event and uplink periodically.

)))

(((

CPL01 has the open alarm feature, user can set this feature so device will send Alarm if the contact has been open for a certain time.

)))

(((

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

)))

(((

Each CPL01 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.

52

* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864

53

* Open/Close detect

54

* Open/Close statistics

55

* 8500mAh industrial battery(none-rechargeable)

56

* AT Commands to change parameters

57

* Uplink on periodically and open/close event

58

* Datalog feature

59

* Remote configure parameters via LoRa Downlink

60

* Firmware upgradable via program port

* Wall Mountable

* Outdoor Use

== 1.3 Installation ==

65

66

Connect CPL01 to an Open Close sensor like below. So it can detect the open/close event.

67

68

[[image:1652857419839-473.png||height="435" width="482"]]

69

70

[[image:1652857455276-422.png||height="229" width="728"]]

== 1.4 Storage & Operation Temperature ==

-40°C to +85°C

== 1.5 Applications (% style="display:none" %) (%%) ==

80

81

* Open/Close Detection

82

* Pulse meter application

83

* Dry Contact Detection

== 1.6 Mechanical ==

[[image:1652857762997-798.png]]

88

89

[[image:1652857791347-991.png]]

== 1.7 Pin Definitions and Switch ==

94

95

[[image:1652857867227-591.png||height="374" width="727"]]

=== 1.7.1 Pin Definition ===

100

101

CPL01 is pre-configured to connect to two external wires. 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/]]

102

103

104

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

105

106

Power on Device when putting this jumper.

107

108

109

=== 1.7.3 BOOT MODE / SW1 ===

110

111

(((

112

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.7.4 Reset Button ===

121

122

Press to reboot the device.

=== 1.7.5 LED ===

It will flash:

1. Boot the device in flash mode

130

1. Send an uplink packet

131

132

= 2. Operation Mode =

133

134

== 2.1 How it works? ==

135

136

(((

137

Each CPL01 is shipped with a worldwide unique set of OTAA keys. To use CPL01 in a LoRaWAN network, user needs to input the OTAA keys in the LoRaWAN network server. So CPL01 can join the LoRaWAN network and start to transmit sensor data.

)))

== 2.2 Example to use for LoRaWAN network ==

142

143

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

144

145

[[image:1652858412212-334.png||height="327" width="723"]]

* (((

In this use case, the CPL01 is connect to a dry contact sensor to detect the open/close event and send the status to the LoRaWAN server. The CPL01 will uplink different types of messages to the LoRaWAN server. See [[Uplink payload>>||anchor="H2.3UplinkPayload"]] for detail.

)))

(((

Assume the DLOS8 is already set to connect to the [[TTN V3 network >>url:https://eu1.cloud.thethings.network]]. We need to add the CPL01 device in TTN V3:

)))

(((

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

)))

(((

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

162

)))

163

164

[[image:1652858451221-297.png]]

165

166

167

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

168

169

Add APP EUI in the application.

170

171

[[image:1652858478050-325.png]]

172

173

174

[[image:1652858498638-881.png||height="327" width="727"]]

175

176

177

[[image:1652858507748-628.png]]

178

179

[[image:1652858520534-791.png]]

180

181

182

Add APP KEY and DEV EUI

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

187

188

[[image:1652858584749-726.png]]

189

190

(((

191

Put the jumper to power on CPL01 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.

192

)))

193

194

[[image:1652858597931-989.png||height="322" width="721"]]

== 2.3 Uplink Payload ==

199

200

(((

201

Uplink payloads have two types:

)))

* (((

Open/Close Status: Use FPORT=2

206

)))

207

* (((

208

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

218

219

(((

220

Include device configure status. Once CPL01 Joined the network, it will uplink this message to the server. After that, CPL01 will uplink Device Status every 12 hours.

)))

(((

Users can also use the downlink command(0x26 01) to ask CPL01 to resend this uplink. This uplink payload also includes the DeviceTimeReq to get time.

225

226

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

)))

Example parse in TTNv3

231

232

[[image:1652859749264-179.png||height="275" width="723"]]

233

234

* (((

235

**Sensor Model**: For CPL01, this value is 0x0E

)))

* (((

**Firmware Version**: 0x0100, Means: v1.0.0 version

)))

* (((

**Frequency Band**:

)))

(% class="box" %)

(((

*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

)))

* (((

(((

**Sub-Band**:

)))

* (((

AU915 and US915:value 0x00 ~~ 0x08

271

)))

272

* (((

273

CN470: value 0x0B ~~ 0x0C

274

)))

275

* (((

276

Other Bands: Always 0x00

)))

)))

* (((

**Battery Info:**

)))

(((

Check the battery voltage.

)))

(((

**Ex1**: 0x0B45 = 2885mV

)))

(((

**Ex2**: 0x0B49 = 2889mV

)))

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

299

300

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

301

302

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

* (((

**TDC: (default: 0x001C20)**

)))

(((

Uplink interval for the total pulse count, default value is 0x001C20 which is 7200 seconds = 2 hours.

)))

* (((

**Disalarm: (default: 0)**

)))

(((

**If Disalarm = 1**, CPL01 will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many disconnect/connect event, and platform only care about the total number of pulse.

)))

(((

**If Disalarm = 0**, CPL01 will send uplink at every TDC periodically.

)))

* (((

**Keep Status & Keep Time**

)))

(((

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

)))

* (((

**Trigger mode (default: 0)**

)))

(((

**If Trigger mode = 0**, count close to open event.

)))

(((

**If Trigger mode = 1**, count open to close event.

349

)))

350

351

[[image:1652860064987-743.png||height="152" width="730"]]

352

353

354

[[image:1652860079526-831.png||height="209" width="729"]]

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

(((

(((

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

)))

)))

(((

(((

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

)))

)))

(((

(((

Uplink Payload totals 11 bytes.

)))

)))

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

379

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

380

381

|(% style="width:101px" %)**Value**|(% style="width:133px" %)Status & [[Alarm>>||anchor="H3.5AlarmBaseonTimeout"]]|(% style="width:92px" %)Total pulse|(% style="width:247px" %)The last open duration (unit: min)|(% style="width:149px" %)[[Unix TimeStamp>>||anchor="H2.4.1UnixTimeStamp"]]

382

383

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

* (((

**Calculate Flag**

)))

(((

The calculate flag is a user define field, IoT server can use this filed to handle different meter with different pulse factor. For example, if there are 100 water meters, meter 1 ~~50 are 1 liter/pulse and meter 51 ~~ 100 has 1.5 liter/pulse.

)))

(((

User can set calculate flag to 1 for meter 1~~50 and 2 for meter 51 ~~ 100, So IoT Server can use this field for calculation.

)))

(((

Default value: 0.

)))

(((

Range (6 bits): (b)000000 ~~ (b) 111111

)))

(((

Refer: [[Set Calculate Flag>>||anchor="H3.9Setthecalculateflag"]]

)))

* (((

**Alarm**

)))

(((

See [[Alarm Base on Timeout>>||anchor="H3.5AlarmBaseonTimeout"]]

)))

* (((

**Contact Status**

)))

(((

0: Open

)))

(((

1: Close

)))

* (((

**Total pulse**

)))

(((

Total pulse/counting base on dry [[contact trigger event>>||anchor="H2.3.2SensorConfiguration2CFPORT3D4"]]

)))

(((

Range (3 Bytes) : 0x000000 ~~ 0xFFFFFF . Max: 16777215

)))

* (((

**The last open duration**

)))

(((

Dry Contact last open duration.

)))

(((

Unit: min.

)))

[[image:1652860403792-491.png||height="153" width="735"]]

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

467

468

(((

469

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

)))

(((

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.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]], to save airtime and battery, CPL01 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:

)))

(((

a) DR0: max is 11 bytes so one entry of data

)))

(((

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

)))

(((

c) DR2: total payload includes 11 entries of data

)))

(((

d) DR3: total payload includes 22 entries of data.

)))

(((

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

)))

**Downlink:**

(% class="box" %)

(((

0x31 61 E9 3A D4 61 E9 3D E0 05

509

)))

510

511

[[image:1652861353248-624.png||height="189" width="720"]]

**Uplink:**

(% class="box" %)

(((

0E 00 23 E6 00 00 00 61 E9 3B 04 0E 00 23 E6 00 00 00 61 E9 3B 25 0D 00 00 00 00 00 00 61 E9 3B C8 0E 00 00 02 00 00 00 61 E9 3B D4 0E 00 00 06 00 00 00 61 E9 3B DB 01 00 00 00 00 00 00 61 E9 3C 91 01 00 00 00 00 00 00 61 E9 3C A1 0D 00 00 00 00 00 00 61 E9 3C BC 0E 00 00 07 00 00 00 61 E9 3C D6 00 00 00 00 00 00 00 61 E9 3D A6

)))

**Parsed Value:**

(((

[ALARM, PIN_STATUS, TOTAL_PULSE, CALCULATE_FLAG, LAST_OPEN_DURATION, TIME]

)))

(((

)))

(((

[TRUE,CLOSE,9190,3,0,2022-01-20 10:35:48],

)))

(((

[TRUE, CLOSE,9190,3,0,2022-01-20 10:36:21],

)))

(((

[FALSE, OPEN,0,3,0,2022-01-20 10:39:04],

)))

(((

[TRUE, CLOSE,2,3,0,2022-01-20 10:39:16],

)))

(((

[TRUE, CLOSE,6,3,0,2022-01-20 10:39:23],

)))

(((

[FALSE, OPEN,0,0,0,2022-01-20 10:42:25],

)))

(((

[FALSE, OPEN,0,0,0,2022-01-20 10:42:41],

)))

(((

[FALSE,OPEN,0,3,0,2022-01-20 10:43:08],

)))

(((

[TRUE, CLOSE,7,3,0,2022-01-20 10:43:34],

)))

(((

[FALSE, CLOSE,0,0,0,2022-01-20 10:47:02],

568

)))

569

570

[[image:1652861480446-216.png]]

== 2.4 Datalog Feature ==

575

576

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.

577

578

579

=== 2.4.1 Unix TimeStamp ===

580

581

CPL01 uses Unix TimeStamp format based on

582

583

[[image:1652861618065-927.png||height="109" width="705"]]

584

585

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

586

587

Below is the converter example

588

589

[[image:1652861637105-371.png||height="428" width="732"]]

=== 2.4.2 Set Device Time ===

594

595

(((

596

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

)))

(((

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

)))

(((

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

)))

(((

Once CPL01 Joined the LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to CPL01. If CPL01 fails to get the time from the server, CPL01 will use the internal time and wait for the next time request ~[[[via Device Status (FPORT=5)>>||anchor="H2.3.1DeviceStatus2CFPORT3D5"]]].

)))

(((

**Note**: LoRaWAN Server needs to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature.

)))

=== 2.4.3 Poll sensor value ===

617

618

Users can poll sensor values based on timestamps. Below is the downlink command.

619

620

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

621

|(% colspan="4" style="width:451px" %)**Downlink Command to poll Open/Close status (0x31)**

622

|(% style="width:59px" %)**1byte**|(% style="width:126px" %)**4bytes**|(% style="width:138px" %)**4bytes**|(% style="width:128px" %)**1byte**

623

|(% style="width:59px" %)31|(% style="width:126px" %)Timestamp start|(% style="width:138px" %)Timestamp end|(% style="width:128px" %)Uplink Interval

624

625

(((

626

Timestamp start and Timestamp end-use Unix TimeStamp format as mentioned above. Devices will reply with all data logs during this period, using the uplink interval.

)))

(((

For example, downlink command[[image:image-20220518162852-1.png]]

)))

(((

Is to check 2021/11/12 12:00:00 to 2021/11/12 15:00:00’s data

)))

(((

Uplink Internal =5s，means CPL01 will send one packet every 5s. range 5~~255s.

)))

=== 2.4.4 Decoder in TTN V3 ===

643

644

[[image:1652862574387-195.png||height="359" width="722"]]

645

646

(((

647

Please check the decoder from this link:

)))

(((

[[https:~~/~~/docs.google.com/document/d/1LFTp2IupfM3O4rQ1gJgZHJNP49BZFnm2xThiErnJYPQ/edit?usp=sharing>>url:https://docs.google.com/document/d/1LFTp2IupfM3O4rQ1gJgZHJNP49BZFnm2xThiErnJYPQ/edit?usp=sharing]]

)))

= 2.5 Show data on Datacake =

656

657

(((

658

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:

)))

(((

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

)))

(((

**Step 2**: Configure CPL01 in Datacake

667

)))

668

669

[[image:1652862663124-805.png]]

670

671

[[image:1652862686700-576.png]]

[[image:1652862716106-261.png]]

677

678

[[image:1652862734313-990.png||height="229" width="707"]]

679

680

[[image:1652862744310-982.png||height="380" width="715"]]

681

682

[[image:1652862755419-628.png||height="258" width="718"]]

683

684

[[image:1652862763975-153.png||height="214" width="720"]]

685

686

[[image:1652862773781-198.png||height="321" width="499"]]

687

688

[[image:1652862794151-835.png||height="327" width="487"]]

689

690

[[image:1652862807472-427.png||height="378" width="670"]]

691

692

693

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

694

695

Use can configure CPL01 via AT Command or LoRaWAN Downlink.

696

697

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

698

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

699

700

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

701

702

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

703

704

These commands are to configure:

705

706

* General system settings like uplink interval.

707

* LoRaWAN protocol & radio related command.

708

709

They are the same for all Dragino Devices which support DLWS-005 LoRaWAN Stack(Note~*~*). 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]]

710

711

712

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

713

714

These commands are only valid for CPL01, as below:

715

716

717

== 3.1 Set Transmit Interval Time ==

718

719

Feature: Change LoRaWAN End Node Transmit Interval.

720

721

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

722

723

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

724

725

726

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

727

728

729

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

730

731

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

732

733

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

734

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

== 3.2 Set Password ==

739

740

Feature: Set device password, max 9 digits

741

742

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

743

744

745

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

746

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

747

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

748

AT+PWORD=?

749

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

750

Show password

751

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

(((

123456

)))

(((

OK

)))

)))

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

761

AT+PWORD=999999

762

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

763

Set password

764

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

OK

)))

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

770

771

No downlink command for this feature.

772

773

774

== 3.3 Quit AT Command ==

775

776

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

777

778

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

779

780

781

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

782

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

783

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

784

785

786

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

787

788

No downlink command for this feature.

789

790

791

== 3.4 Enable / Disable Alarm ==

792

793

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

794

795

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

796

797

[[image:image-20220609151041-6.png]]

798

799

800

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

801

802

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

803

804

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

805

806

807

== 3.5 Alarm Base on Timeout ==

808

809

(((

810

CPL01 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" %)1. 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" %)2. 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:

845

846

**(% style="color:blue" %)AT+TTRIG=1,30**(%%) ~-~-> When the **Keep Status** change from connect to disconnect, and device remains in disconnect status for more than 30 seconds. CPL01 will send an uplink packet, the [[Alarm bit>>||anchor="H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2"]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.

847

848

**(% style="color:blue" %)AT+TTIG=0,0 **(%%) ~-~-> Default Value, disable timeout Alarm.

)))

(((

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

854

855

**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.6 Clear Flash Record ==

885

886

Feature: Clear flash storage for data log feature.

887

888

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

889

890

[[image:image-20220609151132-7.png]]

(((

(((

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

)))

(((

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

)))

)))

== 3.7 Set the sensor mode ==

905

906

Feature: LDS03A and CPL01 use the same firmware. User is possible to switch between this two models.

907

908

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

909

910

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

911

|=(% style="width: 156px;" %)**Command Example**|=(% style="width: 195px;" %)**Function**|=(% style="width: 88px;" %)**Response**

912

|(% style="width:156px" %)AT+MOD =1|(% style="width:195px" %)Set the sensor to LDS03A.|(% style="width:88px" %)OK

913

|(% style="width:156px" %)AT+MOD=2|(% style="width:195px" %)Set the sensor to CPL01.|(% style="width:88px" %)OK

914

915

916

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

917

918

➢ **Example**: 0x0A02 ~/~/Same as AT+MOD=2

919

920

921

== 3.8 Set trigger mode ==

922

923

Feature: Set the trigger interrupt mode.

924

925

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

926

927

[[image:image-20220609151344-9.png]]

928

929

930

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

931

932

➢ **Example**: 0xA401 ~/~/Same as AT+ TTRMOD =1

933

934

935

== 3.9 Set the calculate flag ==

936

937

Feature: Set the calculate flag

938

939

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

940

941

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

942

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

943

|(% style="width:158px" %)AT+CALCFLAG =1|(% style="width:192px" %)Set the calculate flag to 1.|(% style="width:109px" %)OK

944

|(% style="width:158px" %)AT+CALCFLAG =2|(% style="width:192px" %)Set the calculate flag to 2.|(% style="width:109px" %)OK

945

946

947

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

948

949

➢ **Example**: 0XA501 ~/~/Same as AT+CALCFLAG =1

950

951

952

== 3.10 Set count number ==

953

954

Feature: Manually set the count number

955

956

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

957

958

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

959

|=(% style="width: 160px;" %)**Command Example**|=(% style="width: 221px;" %)**Function**|=(% style="width: 95px;" %)**Response**

960

|(% style="width:160px" %)AT+ SETCNT =0|(% style="width:221px" %)Set the count number to 0.|(% style="width:95px" %)OK

961

|(% style="width:160px" %)AT+ SETCNT =100|(% style="width:221px" %)Set the count number to 100.|(% style="width:95px" %)OK

962

963

964

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

965

966

➢ **Example**: 0xA6000001 ~/~/Same as AT+ SETCNT =1; **Example**: 0xA6000064 ~/~/Same as AT+ SETCNT =100

967

968

969

= 4. Battery & how to replace =

970

971

== 4.1 Battery Info ==

972

973

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

974

975

(((

976

The battery-related documents are as below:

)))

* (((

[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],

981

)))

982

* (((

983

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

984

)))

985

* (((

986

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

)))

(((

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

991

992

[[image:1652864571107-510.png]]

)))

(((

Minimum Working Voltage for the CPL01:

)))

(((

CPL01: 2.45v ~~ 3.6v

)))

=== 4.1.1 Battery Note ===

1005

1006

(((

1007

The Li-SICO battery is designed for small current / long period applications. 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 to transmit LoRa, then the battery life may be decreased.

)))

== 4.2 Replace Battery ==

(((

(((

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

)))

)))

(((

(((

And make sure the positive and negative pins match.

)))

)))

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

1026

1027

1028

== 4.3 Battery Life Analyze ==

(((

(((

Dragino battery powered products are all run in Low Power mode. User can check the guideline from this link to calculate the estimate battery life:

)))

)))

(((

(((

[[https:~~/~~/www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf]]

)))

)))

= 5. FAQ =

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

1046

1047

CPL01 UART connection photo

1048

1049

[[image:1652864909750-855.png||height="356" width="728"]]

(((

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:

1054

)))

1055

1056

[[image:1652864915792-686.png||height="508" width="726"]]

1057

1058

1059

== 5.2 How to upgrade the firmware? ==

(((

(((

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: (same firmware as LDS03A)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/CPL01/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/CPL01/Firmware/]]

)))

)))

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

1097

1098

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

1099

1100

1101

= 6. Trouble Shooting =

1102

1103

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

1104

1105

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 **ENTER** while sending out the command. Some serial tool doesn’t send **ENTER** while press the send key, user need to add ENTER in their string.

= 7. Order Info =

(((

(((

Part Number: (% style="color:#4f81bd" %)**CPL01-XX**

)))

)))

(((

(((

(% style="color:#4f81bd" %)**XX**(%%): The default frequency band

)))

)))

* (((

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

1124

)))

1125

* (((

1126

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

1127

)))

1128

* (((

1129

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

1130

)))

1131

* (((

1132

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

1133

)))

1134

* (((

1135

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

1136

)))

1137

* (((

1138

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

1139

)))

1140

* (((

1141

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

1142

)))

1143

* (((

1144

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

)))

= 8. Packing Info =

(((

**Package Includes**:

)))

* (((

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

1165

)))

1166

* (((

1167

Provide as much information as possible regarding your inquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].

1168

)))

Wiki source code of CPL01 LoRaWAN Outdoor Pulse/Contact Sensor

Applications

Navigation