CPN01- NB-IoT Outdoor Open/Close Dry Contact Sensor User Manual

(% style="text-align:center" %)

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652856952171-363.png?rev=1.1||alt="1652856952171-363.png" height="578" width="588"]]

3

4

5

6

= **1. Introduction** =

7

8

== **1.1 **What is CPN01 **NB-IoT** Pulse/Contact Sensor ==

9

10

The Dragino CPN01 is an (% style="color:blue" %)**NB-IoT Dry Contact Sensor**(%%). It detects open/close status and uplinks the info to IoT server via NB-IoT network. User can see the (% style="color:blue" %)**dry contact status, open time, and open counts**(%%) in the IoT Server.

11

12

The CPN01 will send periodically data every day as well as for each dry contact action. It also counts the contact open times and calculates the last open duration. Users can also disable the uplink for each Open/Close event, instead, device can count each open event and uplink periodically.

13

14

CPN01 has** (% style="color:blue" %)Open-Alarm feature(%%)**, user can set this feature so CPN01 will send an alarm if the contact has been open exceeds a certain time.

15

16

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

17

18

NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity, and spectrum efficiency, especially in deep coverage.

19

\\CPN01 supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.

20

\\CPN01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)

21

\\To use CPN01, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that CPN01 supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into CPN01 to get NB-IoT network connection.

== **1.2 Features** ==

26

27

* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD

28

* Open/Close detect

29

* Open/Close statistics

30

* Monitor Battery Level

31

* Uplink on periodically and open/close event

32

* Datalog feature

33

* Uplink periodically

34

* Downlink to change configure

35

* Wall Mountable

36

* Outdoor Use

37

* Ultra-Low Power consumption

38

* AT Commands to change parameters

39

* Micro SIM card slot for NB-IoT SIM

40

* 8500mAh Battery for long-term use

41

42

== **1.3 Specification** ==

43

44

**Common DC Characteristics:**

45

46

* Supply Voltage: 2.1v ~~ 3.6v

47

* Operating Temperature: -40 ~~ 85°C

**NB-IoT Spec:**

* - B1 @H-FDD: 2100MHz

52

* - B3 @H-FDD: 1800MHz

53

* - B8 @H-FDD: 900MHz

54

* - B5 @H-FDD: 850MHz

55

* - B20 @H-FDD: 800MHz

56

* - B28 @H-FDD: 700MHz

57

58

== **1.4 Installation** ==

59

60

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

61

62

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

63

64

[[image:image-20221022234602-2.png||height="288" width="922"]]

65

66

67

== **1.5 Applications** ==

68

69

* Open/Close Detection

70

* Pulse meter application

71

* Dry Contact Detection

72

73

74

== **1.6 Mechanical** ==

75

76

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

77

78

== ** 1.7 Pin Definitions and Switch** ==

79

80

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

81

82

=== **1.7.1 Pin Definition** ===

83

84

CPN01 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 **[[LSN50v2 User Manual>>doc:Main.User Manual for LoRaWAN End Nodes.LSN50 & LSN50-V2 - LoRaWAN Sensor Node User Manual.WebHome]]**.

85

86

87

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

88

89

Power on Device when putting this jumper.

90

91

92

=== **1.7.3 BOOT MODE / SW1** ===

93

94

95

1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.

96

97

2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.

98

99

100

=== **1.7.4 Reset Button** ===

101

102

103

Press to reboot the device.

== ==

=== **1.7.5 LED** ===

108

109

110

The LED will blink when :

111

112

1. Boot the device in flash mode

113

1. Send an uplink packet

114

115

116

= **2. Use CPN01 to communicate with IoT Server** =

117

118

== **2.1 How it works** ==

119

120

The CPN01 is equipped with a NB-IoT module, the pre-loaded firmware in CPN01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by CPN01.

121

122

The diagram below shows the working flow in default firmware of CPN01:

123

124

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

125

126

== **2.2 Configure the CPN01** ==

127

128

=== **2.2.1 Test Requirement** ===

129

130

To use CPN01 in your city, make sure meet below requirements:

131

132

* Your local operator has already distributed a NB-IoT Network there.

133

* The local NB-IoT network used the band that CPN01 supports.

134

* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.

135

136

Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The CPN01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server

=== **2.2.2 Insert SIM card** ===

141

142

Insert the NB-IoT Card get from your provider.

143

144

User need to take out the NB-IoT module and insert the SIM card like below:

145

146

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

147

148

=== **2.2.3 Connect USB – TTL to CPN01 to configure it** ===

149

150

User need to configure CPN01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. CPN01 support AT Commands, user can use a USB to TTL adapter to connect to CPN01 and use AT Commands to configure it, as below.

**Connection:**

USB TTL GND <~-~-~-~-> GND

155

156

USB TTL TXD <~-~-~-~-> UART_RXD

157

158

USB TTL RXD <~-~-~-~-> UART_TXD

159

160

In the PC, use below serial tool settings:

* Baud: **9600**

* Data bits:** 8**

* Stop bits: **1**

* Parity: **None**

* Flow Control: **None**

167

168

Make sure the switch is in FLASH position, then power on device by connecting the jumper on CPN01. CPN01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input.

169

170

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

171

172

**Note: the valid AT Commands can be found at: **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]

173

174

=== **2.2.4 Use CoAP protocol to uplink data** ===

175

176

**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]

177

178

**Use below commands:**

179

180

* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink

181

* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port

182

* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path

183

184

For parameter description, please refer to AT command set

185

186

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

187

188

After configure the server address and **reset the device** (via AT+ATZ ), CPN01 will start to uplink sensor values to CoAP server.

189

190

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

191

192

=== **2.2.5 Use UDP protocol to uplink data(Default protocol)** ===

193

194

This feature is supported since firmware version v1.0.1

195

196

* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink

197

* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port

198

* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary

199

200

[[image:image-20221021111025-10.png]]

201

202

[[image:image-20221021111033-11.png||height="241" width="576"]]

=== **2.2.6 Use MQTT protocol to uplink data** ===

207

208

This feature is supported since firmware version v110

209

210

* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink

211

* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port

212

* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT

213

* **AT+UNAME=UNAME **~/~/Set the username of MQTT

214

* **AT+PWD=PWD **~/~/Set the password of MQTT

215

* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT

216

* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT

217

218

[[image:image-20221021111058-12.png]]

219

220

[[image:image-20221021111108-13.png]]

MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.

225

226

=== **2.2.7 Use TCP protocol to uplink data** ===

227

228

This feature is supported since firmware version v110

229

230

* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink

231

* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port

232

233

[[image:image-20221021111125-14.png]]

234

235

[[image:image-20221021111131-15.png]]

=== **2.2.8 Change Update Interval** ===

240

241

User can use below command to change the **uplink interval**.

242

243

* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s

**NOTE:**

**~1. By default, the device will send an uplink message every 1 hour.**

248

249

== **2.3 Uplink Payload** ==

250

251

In this mode, uplink payload includes 87 bytes in total by default.

252

253

Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.

254

255

|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|**1**|**2**|**2**|4

|2|2|4|8 group

|[[Soil Temperature>>path:#H2.4.6A0SoilTemperature]]|[[Soil P>>path:#H2.4.7A0SoilConductivity28EC29]]H|Time stamp|...

260

261

If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the CPN01 uplink data.

262

263

[[image:image-20221021111201-16.png||height="572" width="792"]]

264

265

The payload is ASCII string, representative same HEX:

266

267

**0x (% style="color:red" %)__0xf867787050213317__ (% style="color:blue" %)__0064__ (% style="color:green" %)_0c78__ __(% style="color:#00b0f0" %)17__ __(% style="color:#7030a0" %)01__ __(% style="color:#d60093" %)00__ __(% style="color:#a14d07" %)01 __ __(% style="color:#0020b0" %)__ __00__ __(% style="color:#420042" %)000009__ __(% style="color:#663300" %) 000002__ __(% style="color:#d60093" %)6315537bb__ __(% style="color:#663300" %)// 0100000b02000002663510fed__ __0100000e0200000263510f39 010000000000000063510e85 010000000000000063510d2e 010000000000000063510c7a 010000000000000063510bc6 010000000000000063510954 010000000000000063510882 //(%%)**

268

269

where:

270

*(% style="color:#037691" %) **Device ID:**(%%) 0x f867787050213317 = f867787050213317

271

272

*(% style="color:#037691" %) **Version:**(%%) 0x0064=100=1.0.0

273

274

*(% style="color:#037691" %) **BAT:**(%%) 0x0c78 = 3192 mV = 3.192V

275

276

*(% style="color:#037691" %) **Singal: **(%%)0x17 = 23

277

278

*(% style="color:#037691" %) **Mod:**(%%) 0x01 = 1

279

280

*(% style="color:#037691" %) **Calculate Flag:**(%%) 0x00= 0

281

282

*(% style="color:#037691" %) **Contact Status:**(%%) 0x00= 0

283

284

*(% style="color:#037691" %) **Alarm:**(%%)0x00 =0

285

286

*(% style="color:#037691" %) **Total pulse:0x09 =0**

287

288

*(% style="color:#037691" %) **The last open duration:**(%%)0x02 =2

289

290

*(% style="color:#037691" %)**Time stamp :**(%%) 0x6315537b =1662342011

291

292

*(% style="color:#037691" %) **Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000b0200002663510fed

293

294

*(% style="color:#037691" %) **8 sets of recorded data: Contact Status, Total pulse, Calculate Flag, The last open duration ,Time stamp :**(%%) 0100000e0200002663510f39,.......

295

296

== **2.4 Payload Explanation and Sensor Interface** ==

297

298

=== **2.4.1 Device ID** ===

299

300

By default, the Device ID equal to the last 15 bits of IMEI.

301

302

User can use **AT+DEUI** to set Device ID

**Example:**

AT+DEUI=868411056754138

307

308

The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.

309

310

=== **2.4.2 Version Info** ===

311

312

Specify the software version: 0x64=100, means firmware version 1.00.

313

314

For example: 0x00 64 : this device is CPN01 with firmware version 1.0.0.

315

316

=== **2.4.3 Battery Info** ===

317

318

Check the battery voltage for CPN01.

Ex1: 0x0B45 = 2885mV

Ex2: 0x0B49 = 2889mV

=== **2.4.4 Signal Strength** ===

325

326

NB-IoT Network signal Strength.

**Ex1: 0x1d = 29**

**0** -113dBm or less

**1** -111dBm

**2...30** -109dBm... -53dBm

335

336

**31** -51dBm or greater

337

338

**99** Not known or not detectable

339

340

=== **2.4.5 Calculate Flag** ===

341

342

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.

343

344

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

349

350

=== **2.4.6 Alarm** ===

351

352

See [[Alarm Base on Timeout>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H3.5AlarmBaseonTimeout]]

353

354

=== **2.4.7 Contact Status** ===

0: Open

1: Close

=== **2.4.8 Total pulse** ===

361

362

Total pulse/counting base on dry [[contact trigger event>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.2SensorConfiguration2CFPORT3D4]]

363

364

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

365

366

=== **2.4.9 The last open duration** ===

367

368

Dry Contact last open duration.

Unit: min.

[[image:image-20221021111346-17.png||height="146" width="770"]]

373

374

375

=== **2.4.10 Timestamp** ===

376

377

Time stamp : 0x6315537b =1662342011

378

379

Convert Unix timestamp to time 2022-9-5 9:40:11.

**~ **

== **2.5 Downlink Payload** ==

384

385

By default, CPN01 prints the downlink payload to console port.

386

387

[[image:image-20221021111414-18.png]]

**Examples:**

* **Set TDC**

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

394

395

Payload: 01 00 00 1E TDC=30S

396

397

Payload: 01 00 00 3C TDC=60S

* **Reset**

If payload = 0x04FF, it will reset the NSE01

* **INTMOD**

Downlink Payload: 06000003, Set AT+INTMOD=3

406

407

== **2.6 LED Indicator** ==

408

409

The CPN01 has an internal LED which is to show the status of different state.

410

411

* When power on, CPN01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)

412

* Then the LED will be on for 1 second means device is boot normally.

413

* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.

414

* For each uplink probe, LED will be on for 500ms.

415

416

== **2.7 Alarm Base on Timeout** ==

417

418

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:

419

420

421

**~1. Keep Status: Status to be monitor**

422

423

Keep Status = 1: Monitor Close to Open event

424

425

Keep Status = 0: Monitor Open to Close event

426

427

428

**2. Keep Time: Timeout to send an Alarm**

429

430

Range 0 ~~ 65535(0xFFFF) seconds.

431

432

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

433

434

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

435

436

437

**AT Command** to configure:

438

439

**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>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.

440

441

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

442

443

== **2.8 Set debug mode** ==

444

445

Feature: Enable or Disable debug mode

446

447

448

**AT Command: AT+DEBUG**

449

450

[[image:image-20221021111629-21.png]]

451

452

== **2.9 Clear Flash Record** ==

453

454

Feature: Clear flash storage for data log feature.

455

456

**AT Command: AT+CLRDTA**

457

458

[[image:image-20221021111527-19.png]]

459

460

== ** 2.10 Set trigger mode** ==

461

462

➢ AT Command: **AT+TTRMOD**

463

464

Feature: Set the trigger interrupt mode.

465

466

[[image:image-20221021111552-20.png]]

467

468

== **2.11 Set the calculate flag** ==

469

470

Feature: Set the calculate flag

471

472

**AT Command: AT+CALCFLAG**

473

474

[[image:image-20221021111711-22.png]]

475

476

== **2.12 Set count number** ==

477

478

Feature: Manually set the count number

479

480

**AT Command: AT+SETCNT**

481

482

[[image:image-20221021111748-24.png]]

483

484

== **2.13 Set the number of data to be uploaded and the recording time** ==

➢ AT Command:

AT+TR=900 ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)

489

490

491

AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.

492

493

== **2.14 Read or Clear cached data** ==

➢ AT Command:

AT+CDP ~/~/ Read cached data

498

499

[[image:image-20221021111810-25.png||height="364" width="797"]]

500

501

502

AT+CDP=0 ~/~/ Clear cached data

503

504

== **2.15 Firmware Change Log** ==

505

506

Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]

507

508

Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]

509

510

== **2.16 Battery Analysis** ==

511

512

=== **2.16.1 Battery Type** ===

513

514

The CPN01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.

515

516

The battery is designed to last for several years depends on the actually use environment and update interval.

517

518

The battery related documents as below:

519

520

* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]

521

* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]

522

* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]

523

524

[[image:image-20221021111911-26.png]]

525

526

=== **2.16.2 Power consumption Analyze** ===

527

528

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.

529

530

Instruction to use as below:

531

532

**Step 1: **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[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/]]

533

534

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

541

542

[[image:image-20221021111923-27.png||height="253" width="783"]]

543

544

=== **2.16.3 Battery Note** ===

545

546

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.

547

548

=== **2.16.4 Replace the battery** ===

549

550

The default battery pack of CPN01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).

551

552

= **3. Access NB-IoT Module** =

553

554

Users can directly access the AT command set of the NB-IoT module.

555

556

The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]

557

558

[[image:image-20221021112006-28.png]]

559

560

= **4. Using the AT Commands** =

561

562

== **4.1 Access AT Commands** ==

563

564

See this link for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]

565

566

AT+<CMD>? : Help on <CMD>

AT+<CMD> : Run <CMD>

AT+<CMD>=<value> : Set the value

571

572

AT+<CMD>=? : Get the value

**General Commands**

AT : Attention

AT? : Short Help

ATZ : MCU Reset

AT+TDC : Application Data Transmission Interval

583

584

AT+CFG : Print all configurations

585

586

AT+CFGMOD : Working mode selection

587

588

AT+INTMOD : Set the trigger interrupt mode

589

590

AT+5VT : Set extend the time of 5V power

591

592

AT+PRO : Choose agreement

593

594

AT+RXDL : Extend the sending and receiving time

595

596

AT+SERVADDR : Server Address

597

598

AT+TR : Get or Set record time"

599

600

601

AT+NOUD : Get or Set the number of data to be uploaded

602

603

604

AT+CDP : Read or Clear cached data

605

606

607

AT+ DEBUG : Enable or Disable debug mode

608

609

AT+ TTRIG : Get or Set Alarm Base on Timeout

610

611

AT+ TTRMOD : Get or Set the trigger interrupt mode(0:falling,1:rising)

612

613

AT+ CALCFLAG : Get or Set the calculate flag

614

615

AT+ CLRC : Clear current door open count

**COAP Management**

AT+URI : Resource parameters

**UDP Management**

AT+CFM : Upload confirmation mode (only valid for UDP)

**MQTT Management**

AT+CLIENT : Get or Set MQTT client

628

629

AT+UNAME : Get or Set MQTT Username

630

631

AT+PWD : Get or Set MQTT password

632

633

AT+PUBTOPIC : Get or Set MQTT publish topic

634

635

AT+SUBTOPIC : Get or Set MQTT subscription topic

**Information**

AT+FDR : Factory Data Reset

640

641

AT+PWORD : Serial Access Password

= **5. FAQ** =

== **5.1 How to Upgrade Firmware** ==

646

647

User can upgrade the firmware for 1) bug fix, 2) new feature release.

648

649

Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]

650

651

**Notice, **CPN01 **and **CPN01 **share the same mother board. They use the same connection and method to update.**

652

653

== **5.2 Can I calibrate CPN01 to different soil types?** ==

654

655

CPN01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].

656

657

= **6. Trouble Shooting** =

658

659

== **6.1 Connection problem when uploading firmware** ==

660

661

**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]

662

663

== **6.2 AT Command input doesn't work** ==

664

665

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.

666

667

= **7. Order Info** =

668

669

Part Number**:** CPN01

670

671

= **8. Packing Info** =

672

673

**Package Includes**:

674

675

* CPN01 NB-IoT Soil Moisture & EC Sensor x 1

676

* External antenna x 1

677

678

**Dimension and weight**:

679

680

* Size: 195 x 125 x 55 mm

* Weight: 420g

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

686

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