PB01 -- LoRaWAN Button User Manual

PB01 LoRaWAN Button is a LoRaWAN wireless device with one (% style="color:blue" %)**push button**(%%). Once user push the button, PB01 will transfer the signal to IoT server via Long Range LoRaWAN wireless protocol. PB01 also senses the (% style="color:blue" %)**environment temperature & humidity**(%%) and will also uplink these data to IoT Server.

30

31

PB01 supports (% style="color:blue" %)** 2 x AAA batteries**(%%) and works for a long time up to several years*. User can replace the batteries easily after they are finished.

32

33

PB01 has a built-in speaker, it can pronouns different sound when press button and get reply from server. The speaker can by disable if user want it.

34

35

PB01 is fully compatible with LoRaWAN v1.0.3 protocol, it can work with standard LoRaWAN gateway.

36

37

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

== 1.2 Features ==

* Wall Attachable.

* LoRaWAN v1.0.3 Class A protocol.

46

* 1 x push button. Different Color available.

47

* Built-in Temperature & Humidity sensor

48

* Built-in speaker

49

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

50

* AT Commands to change parameters

51

* Remote configure parameters via LoRaWAN Downlink

52

* Firmware upgradable via program port

53

* Support 2 x AAA LR03 batteries.

54

* IP Rating: IP52

55

56

== 1.3 Specification ==

57

58

59

**Built-in Temperature Sensor:**

60

61

* Resolution: 0.01 °C

62

* Accuracy Tolerance: Typ ±0.2 °C

63

* Long Term Drift: < 0.03 °C/yr

64

* Operating Range: -10 ~~ 50 °C or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])

65

66

**Built-in Humidity Sensor:**

67

68

* Resolution: 0.01 %RH

69

* Accuracy Tolerance: Typ ±1.8 %RH

70

* Long Term Drift: < 0.2% RH/yr

71

* Operating Range: 0 ~~ 99.0 %RH(no Dew)

72

73

== 1.4 Power Consumption ==

74

75

76

PB01 : Idle: 5uA, Transmit: max 110mA

77

78

79

== 1.5 Storage & Operation Temperature ==

80

81

82

-10 ~~ 50 °C or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])

83

84

85

== 1.6 Applications ==

86

87

88

* Smart Buildings & Home Automation

89

* Logistics and Supply Chain Management

* Smart Metering

* Smart Agriculture

* Smart Cities

* Smart Factory

= 2. Operation Mode =

96

97

== 2.1 How it work? ==

98

99

100

Each PB01 is shipped with a worldwide unique set of LoRaWAN OTAA keys. To use PB01 in a LoRaWAN network, user needs to input the OTAA keys in LoRaWAN network server. After this, if PB01 is under this LoRaWAN network coverage, PB01 can join the LoRaWAN network and start to transmit sensor data. The default period for each uplink is** 20 minutes**.

101

102

103

== 2.2 How to Activate PB01? ==

104

105

106

(% style="color:red" %)** 1. Open enclosure from below position.**

107

108

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

109

110

111

(% style="color:red" %)** 2. Insert 2 x AAA LR03 batteries and the node is activated.**

112

113

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

114

115

116

(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**

117

118

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

119

120

121

User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.

122

123

124

== 2.3 Example to join LoRaWAN network ==

125

126

127

This section shows an example for how to join the [[TheThingsNetwork>>url:https://www.thethingsnetwork.org/]] LoRaWAN IoT server. Usages with other LoRaWAN IoT servers are of similar procedure.

128

129

130

(% _mstvisible="1" class="wikigeneratedid" %)

131

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

132

133

134

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

135

136

Each PB01 is shipped with a sticker with the default DEV EUI as below:

137

138

[[image:image-20230426083617-1.png||height="294" width="633"]]

139

140

141

Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:

Create application.

choose to create the device manually.

146

147

Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)

148

149

[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)

150

151

152

[[image:image-20240507142157-2.png||height="559" width="1147"]]

153

154

[[image:image-20240507142401-3.png||height="693" width="1202"]]

155

156

[[image:image-20240507142651-4.png||height="760" width="1190"]]

157

158

**Default mode OTAA**

(% style="color:blue" %)**Step 2**(%%): Use ACT button to activate PB01 and it will auto join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.

163

164

[[image:image-20240507143104-5.png||height="434" width="1398"]]

165

166

167

== 2.4 Uplink Payload ==

168

169

170

Uplink payloads include two types: Valid Sensor Value and other status / control command.

171

172

* Valid Sensor Value: Use FPORT=2

173

* Other control command: Use FPORT other than 2.

174

175

=== 2.4.1 Uplink FPORT~=5, Device Status ===

176

177

178

Users can get the Device Status uplink through the downlink command:

179

180

(% style="color:#4472c4" %)**Downlink: **(%%)**0x2601**

181

182

Uplink the device configures with FPORT=5.

183

184

(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)

185

|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bytes)(% style="display:none" %) (%%)**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 30px;background-color:#4F81BD;color:white" %)**2**

186

187

188

[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)

189

190

Example Payload (FPort=5): [[image:image-20240507152254-13.png||height="26" width="130"]]

191

192

193

(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.

194

195

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

196

197

(% style="color:#4472c4" %)**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

(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)

221

222

(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.

223

224

(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV

225

226

227

=== 2.4.2 Uplink FPORT~=2, Real time sensor value ===

228

229

230

PB01 will send this uplink after Device Status uplink once join LoRaWAN network successfully. And it will periodically send this uplink. Default interval is 20 minutes and [[can be changed>>||anchor="H3.1A0DownlinkCommandSet"]].

231

232

Uplink uses FPORT=2 and every 20 minutes send one uplink by default.

233

234

(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:460px" %)

235

|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((

236

**Size(bytes)**

237

)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)2|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((

238

**1**

239

)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((

240

**1**

241

)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)(((

242

**2**

243

)))|=(% style="width: 40px;background-color:#4F81BD;color:white" %)(((

244

**2**

245

)))

246

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

247

Value

248

)))|(% style="width:39px" %)Battery|(% style="width:39px" %)(((

Sound_ACK

&Sound_key

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

(((

Alarm

)))

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

(((

Temperature

)))

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

Humidity

)))

Example in TTN.

[[image:image-20240507150155-11.png||height="549" width="1261"]]

267

268

Example Payload (FPort=2): (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**

269

270

==== (% style="color:blue" %)**Battery:**(%%) ====

271

272

Check the battery voltage.

273

274

* Ex1: 0x0CEA = 3306mV

275

* Ex2: 0x0D08 = 3336mV

276

277

==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====

278

279

Key sound and ACK sound are enabled by default.

* Example1: 0x03

Sound_ACK: (03>>1) & 0x01=1, OPEN.

284

285

**~ ** Sound_key: 03 & 0x01=1, OPEN.

* Example2: 0x01

Sound_ACK: (01>>1) & 0x01=0, CLOSE.

290

291

**~ ** Sound_key: 01 & 0x01=1, OPEN.

292

293

294

==== (% style="color:blue" %)**Alarm:**(%%) ====

Key alarm.

* Ex1: 0x01 & 0x01=1, TRUE.

299

* Ex2: 0x00 & 0x01=0, FALSE.

300

301

==== (% style="color:blue" %)**Temperature:**(%%) ====

302

303

* Example1: 0x0111/10=27.3℃

304

* Example2: (0xFF0D-65536)/10=-24.3℃

305

306

If payload is: FF0D : (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃

307

308

（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）

309

310

311

==== (% style="color:blue" %)**Humidity:**(%%) ====

312

313

* Humidity: 0x02A8/10=68.0%

314

315

316

=== 2.4.3 Uplink FPORT~=3, Datalog sensor value ===

317

318

319

PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.

320

321

[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)

322

323

324

* Each data entry is 11 bytes, to save airtime and battery, PB01 will send max bytes according to the current DR and Frequency bands.(% style="display:none" %)

325

326

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

327

328

1. **DR0**: max is 11 bytes so one entry of data

329

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

330

1. **DR2**: total payload includes 11 entries of data

331

1. **DR3**: total payload includes 22 entries of data.

332

333

(% style="color:red" %)**Notice: PB01 will save 178 set of history data, If device doesn't have any data in the polling time. Device will uplink 11 bytes of 0.**

334

335

See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].

=== 2.4.4 Decoder in TTN V3 ===

341

342

343

In LoRaWAN protocol, the uplink payload is HEX format, user need to add a payload formatter/decoder in LoRaWAN Server to get human friendly string.

344

345

In TTN , add formatter as below:

346

347

[[image:image-20240507162814-16.png||height="778" width="1135"]]

348

349

(((

350

Please check the decoder from this link: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]

)))

(((

)))

== 2.5 Show data on Datacake ==

(((

Datacake IoT platform provides a human friendly interface to show the sensor data in charts, 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**(%%): Be sure that your device is programmed and properly connected to the LoRaWAN network.

)))

(((

(% style="color:blue" %)**Step 2**(%%): Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations.

)))

(((

~1. Add Datacake:

)))

(((

2. Select default key as Access Key:

)))

(((

3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT52:

)))

(((

Please refer to the figure below

)))

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

394

395

396

Log in to DATACAKE, copy the API under the account

397

398

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

399

400

401

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

[[image:image-20220621112422-4.png||height="741" width="1237"]]

406

407

408

[[image:image-20220621112422-5.png||height="314" width="1226"]]

409

410

411

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

412

413

414

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

415

416

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

417

418

419

[[image:image-20220621112422-9.png||height="338" width="1211"]]

420

421

422

[[image:image-20220621112422-10.png||height="372" width="1215"]]

423

424

425

Copy and paste the [[TTN decoder>>https://www.dropbox.com/sh/6ighqpavkd33gqi/AACPu62g--x0gBADvHZs_xr6a?dl=0]] here and save

426

427

[[image:image-20220621112422-11.png||height="575" width="1215"]]

428

429

430

Visual widgets please read the DATACAKE documentation

431

432

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

433

434

435

== 2.6 Datalog Feature ==

436

437

438

(% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)

439

When user want to retrieve sensor value, he can send a poll command from the IoT platform to ask sensor to send value in the required time slot.

440

441

442

=== 2.6.1 Unix TimeStamp ===

443

444

445

Unix TimeStamp shows the sampling time of uplink payload. format base on

446

447

[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]

448

449

User can get this time from link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :

450

451

For example: if the Unix Timestamp we got is hex 0x60137afd, we can convert it to Decimal: 1611889405. and then convert to the time: 2021 – Jan ~-~- 29 Friday 03:03:25 (GMT)

452

453

454

[[image:1655782409139-256.png]]

455

456

457

=== 2.6.2 Poll sensor value ===

(((

User can poll sensor value based on timestamps from the server. Below is the downlink command.

)))

(((

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

)))

(((

For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)

)))

(((

Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data

)))

(((

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

)))

=== 2.6.3 Datalog Uplink payload ===

482

483

484

See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]

485

486

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

== ==

== 2.7 LED Indicator ==

(((

The LHT52 has a triple color LED which for easy showing different stage.

)))

(((

(% style="color:#037691" %)**In a normal working state**:

500

)))

501

502

* When the node is restarted, (% style="color:green" %)**GREEN, **(% style="color:red" %)**RED**(%%) and (% style="color:blue" %)**BLUE**(%%)** **are sequentially lit.

503

504

* During OTAA Join:

505

** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.

506

** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.

507

508

* After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.

509

** (% style="color:blue" %)**BLUE LED**(%%) when external sensor is connected

510

** (% style="color:green" %)**GREEN LED**(%%) when external sensor is not connected

511

512

* For each success downlink, the (% style="color:purple" %)**PURPLE LED**(%%) will blink once

513

514

(((

515

(% style="color:#037691" %)**In AT Command Mode:**

)))

(((

If user use console cable to send AT Command to LHT52, the (% style="color:red" %)**RED LED**(%%) will always on until:

)))

* Power off/on LHT52

* Press reset button of LHT52.

524

* Send an AT Command: AT+CLPM=1

525

526

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

== 2.8 Button ==

Press the button LHT52 will reset and join network again.

533

534

535

= 3. Configure LHT52 via AT command or LoRaWAN downlink =

536

537

538

Use can configure LHT52 via AT Command or LoRaWAN Downlink.

539

540

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

541

542

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

543

544

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

545

546

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

547

548

These commands are to configure:

549

550

* General system settings like: uplink interval.

551

552

* LoRaWAN protocol & radio-related commands.

553

554

They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]

555

556

557

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

558

559

These commands are only valid for LHT52, as below:

560

561

562

== 3.1 Downlink Command Set ==

563

564

565

(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)

566

|=(% style="width: 100px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 150px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 100px;background-color:#4F81BD;color:white" %)**Response**|=(% style="width: 150px;background-color:#4F81BD;color:white" %)**Downlink**

567

|(% style="width:161px" %)AT+TDC=?|(% style="width:138px" %)View current TDC time|(% style="width:243px" %)(((

568

1200000

569

OK

570

)))|(% style="width:1001px" %)Default 1200000(ms)

571

|(% style="width:161px" %)AT+TDC=300000|(% style="width:138px" %)Set TDC time|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

572

0X0100012C:

573

01: fixed command

574

00012C: 0X00012C=300(seconds)

575

)))

576

|(% style="width:161px" %)ATZ|(% style="width:138px" %)Reset node|(% style="width:243px" %) |(% style="width:1001px" %)0x04FF

577

|(% style="width:161px" %)AT+FDR|(% style="width:138px" %)Restore factory settings|(% style="width:243px" %) |(% style="width:1001px" %)0X04FE

578

|(% style="width:161px" %)AT+CFM=?|(% style="width:138px" %)View the current confirmation mode status|(% style="width:243px" %)(((

579

0

580

OK

581

)))|(% style="width:1001px" %)Default 0

582

|(% style="width:161px" %)AT+CFM=1|(% style="width:138px" %)Turn on confirmation mode|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

0x0500: close

0x0501: open

05: fixed command

)))

|(% style="width:161px" %)AT+CHE=?|(% style="width:138px" %)View the current sub-band select 0-7, the default is 0|(% style="width:243px" %)(((

588

0

589

OK

590

)))|(% style="width:1001px" %)Default 0

591

|(% style="width:161px" %)AT+CHE=2|(% style="width:138px" %)(((

592

Set subband to 2

593

(CN470,US915,AU915)

594

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

595

Attention:Take effect after ATZ

596

OK

597

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

0X0702:

07: fixed command

02: Select subband 2

)))

|(% style="width:161px" %)AT+WMOD=?|(% style="width:138px" %)View the current alarm mode status|(% style="width:243px" %)(((

603

0

604

OK

605

)))|(% style="width:1001px" %)Default 0

606

|(% style="width:161px" %)AT+WMOD=1|(% style="width:138px" %)Turn on alarm mode|(% style="width:243px" %)(((

607

Attention:Take effect after ATZ

608

OK

609

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

0xA501: open

0XA500: close

A5: fixed command

)))

|(% style="width:161px" %)AT+CITEMP=?|(% style="width:138px" %)View the current temperature detection time interval|(% style="width:243px" %)(((

615

1

616

OK

617

)))|(% style="width:1001px" %)Default 1(min)

618

|(% style="width:161px" %)AT+CITEMP=2|(% style="width:138px" %)Set the temperature detection time interval to 2min|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

0XA70002

A7: fixed command

0002: 0X0002=2(min)

)))

|(% style="width:161px" %)AT+NJM=?|(% style="width:138px" %)Check the current network connection method|(% style="width:243px" %)(((

624

1

625

OK

626

)))|(% style="width:1001px" %)Default 1

627

|(% style="width:161px" %)AT+NJM=0|(% style="width:138px" %)Change the network connection method to ABP|(% style="width:243px" %)(((

628

Attention:Take effect after ATZ

629

OK

630

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

0X2000: ABP

0x2001: OTAA

20: fixed command

)))

|(% style="width:161px" %)AT+RPL=?|(% style="width:138px" %)View current RPL settings|(% style="width:243px" %)(((

636

0

637

OK

638

)))|(% style="width:1001px" %)Default 0

639

|(% style="width:161px" %)AT+RPL=1|(% style="width:138px" %)set RPL=1|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

640

0x2101:

641

21: fixed command

642

01: for details, check wiki

643

)))

644

|(% style="width:161px" %)AT+ADR=?|(% style="width:138px" %)View current ADR status|(% style="width:243px" %)(((

645

1

646

OK

647

)))|(% style="width:1001px" %)Default 0

648

|(% style="width:161px" %)AT+ADR=0|(% style="width:138px" %)Set the ADR state to off|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

0x2200: close

0x2201: open

22: fixed command

)))

|(% style="width:161px" %)AT+DR=?|(% style="width:138px" %)View the current DR settings|(% style="width:243px" %)OK|(% style="width:1001px" %)

654

|(% style="width:161px" %)AT+DR=1|(% style="width:138px" %)(((

655

set DR to 1

656

It takes effect only when ADR=0

657

)))|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

0X22000101:

00: ADR=0

01: DR=1

01: TXP=1

22: fixed command

)))

|(% style="width:161px" %)AT+TXP=?|(% style="width:138px" %)View the current TXP|(% style="width:243px" %)OK|(% style="width:1001px" %)

665

|(% style="width:161px" %)AT+TXP=1|(% style="width:138px" %)(((

666

set TXP to 1

667

It takes effect only when ADR=0

668

)))|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

0X22000101:

00: ADR=0

01: DR=1

01: TXP=1

22: fixed command

)))

|(% style="width:161px" %) |(% style="width:138px" %)Upload node configuration or DS18B20 ID|(% style="width:243px" %) |(% style="width:1001px" %)(((

676

0X2301:Upload node configuration

677

0x2302: Upload DS18B20 ID

678

23: fixed command

679

)))

680

|(% style="width:161px" %)AT+DWELL=?|(% style="width:138px" %)Check the high-rate upload settings|(% style="width:243px" %)(((

681

1

682

OK

683

)))|(% style="width:1001px" %)Default 1

684

|(% style="width:161px" %)AT+DWELL=1|(% style="width:138px" %)(((

685

Set high rate upload

686

(AS923,AU915)

687

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

688

Attention:Take effect after ATZ

689

OK

690

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

0x2501: close

0x2500: open

25: fixed command

for details, check wiki

695

)))

696

|(% style="width:161px" %)AT+RJTDC=?|(% style="width:138px" %)View current RJTDC set time|(% style="width:243px" %)(((

697

20

698

OK

699

)))|(% style="width:1001px" %)Default 20(min)

700

|(% style="width:161px" %)AT+RJTDC=10|(% style="width:138px" %)Set RJTDC time interval|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

0X26000A:

26: fixed command

000A: 0X000A=10(min)

for details, check wiki

705

)))

706

|(% style="width:161px" %) |(% style="width:138px" %)Retrieve stored data for a specified period of time|(% style="width:243px" %) |(% style="width:1001px" %)(((

707

0X3161DE7C7061DE8A800A:

708

31: fixed command

709

61DE7C70:0X61DE7C70=2022/1/12 15:00:00

710

61DE8A80:0X61DE8A80=2022/1/12 16:00:00

0A: 0X0A=10(second)

View details 2.6.2

)))

|(% style="width:161px" %)AT+DDETECT=?|(% style="width:138px" %)View the current DDETECT setting status and time|(% style="width:243px" %)(((

715

0,1440

716

OK

717

)))|(% style="width:1001px" %)Default 0,1440(min)

718

|(% style="width:161px" %)AT+DDETECT=1,1440|(% style="width:138px" %)(((

719

Set DDETECT setting status and time

720

((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))

721

)))|(% style="width:243px" %)OK|(% style="width:1001px" %)(((

0X320005A0: close

0X320105A0: open

32: fixed command

05A0: 0X05A0=1440(min)

726

)))

727

|(% style="width:161px" %) |(% style="width:138px" %)(((

728

Downlink Modification Alarm Mode

729

(AT+WMOD,AT+CITEMP,AT+ARTEMP)

730

)))|(% style="width:243px" %) |(% style="width:1001px" %)(((

0XAA010002000F00032:

AA: fixed command

01: 0X01=1(AT+MOD)

0002: 0X0002=2(AT+CITEMP)

735

000F: 0X000F=15(AT+ARTEMP)

736

0032: 0X0032=50(AT+ARTEMP)

737

)))

738

739

== 3.2 Set Password ==

740

741

742

Feature: Set device password, max 9 digits.

743

744

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

745

746

(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)

747

|(% style="background-color:#4f81bd; color:white; width:155px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:128px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response**

748

|(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((

123456

OK

)))

|(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK

753

754

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

755

756

No downlink command for this feature.

757

758

759

= 4. Battery & How to replace =

760

761

== 4.1 Battery Type and replace ==

762

763

764

LHT52 uses 2 x AAA LR03(1.5v) batteries. If the batteries running low (shows 2.1v in the platform). User can buy generic AAA battery and replace it.

765

766

(% style="color:red" %)**Note: **

767

768

1. The LHT52 doesn't have any screw, use can use nail to open it by the middle.

769

770

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

771

772

773

2. Make sure the direction is correct when install the AAA batteries.

774

775

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

776

777

778

== 4.2 Power Consumption Analyze ==

779

780

781

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.

782

783

Instruction to use as below:

784

785

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

786

787

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

788

789

790

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

* Product Model

* Uplink Interval

* Working Mode

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

797

798

[[image:image-20220621143643-7.png||height="429" width="1326"]]

799

800

801

= 5. Sensors and Accessories =

802

803

== 5.1 Temperature Probe (AS-01) ==

804

805

806

External Temperature Probe base on DS18B20. (note: Default Package doesn't include AS-01)

807

808

[[image:image-20220621141939-4.png||height="315" width="279"]] [[image:image-20220621141546-2.png||height="308" width="205"]](% style="display:none" %)

809

810

811

**External Temperature Probe (AS-01):(% style="display:none" %) (%%)**

812

813

* Resolution: 0.0625 °C

814

* ±0.5°C accuracy from -10°C to +85°C

815

* ±2°C accuracy from -55°C to +125°C

816

* Operating Range: -55 °C ~~ 125 °C

817

* Cable Length: 2 meters

818

819

== 5.2 Program Converter (AS-02) ==

820

821

822

AS-02 is an optional accessory, it is USB Type-C converter. AS-02 provide below feature:

823

824

1. Access AT console of LHT52 when used with USB-TTL adapter. [[See this link>>||anchor="H6.1HowtouseATCommandtoconfigureLHT52"]].

825

1. Update firmware to LHT52 when used with DAP-Link adapter. [[See this link>>doc:Main.Firmware Upgrade Instruction.WebHome||anchor="H2.3LHT52"]].

826

827

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

= 6. FAQ =

== 6.1 How to use AT Command to configure LHT52 ==

833

834

835

LHT52 supports AT Command set. User can use a USB to TTL adapter plus the Program Cable to connect to LHT52 for using AT command, as below.

836

837

838

[[image:image-20220621144150-8.png||height="537" width="724"]]

**Connection:**

* (% style="background-color:yellow" %)USB to TTL GND <~-~-> Program Converter GND pin

844

* (% style="background-color:yellow" %)USB to TTL RXD <~-~-> Program Converter D+ pin

845

* (% style="background-color:yellow" %)USB to TTL TXD <~-~-> Program Converter A11 pin

846

847

It is also possible to connect using DAPLink

848

849

[[image:image-20220621144235-9.png||height="485" width="729"]]

(((

**Connection:**

)))

* (((

(% style="background-color:yellow" %)USB to DAP-LINK GND <~-~-> Program Converter GND pin

857

)))

858

* (((

859

(% style="background-color:yellow" %)USB to DAP-LINK RXD <~-~-> Program Converter D+ pin

860

)))

861

* (((

862

(% style="background-color:yellow" %)USB to DAP-LINK TXD <~-~-> Program Converter A11 pin

)))

(((

In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**115200**(%%) to access to access serial console for LHT52. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(%%)) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again.

)))

(((

Input password and ATZ to activate LHT52,As shown below:

)))

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

877

878

879

== 6.2 AT Command and Downlink ==

(((

Sending ATZ will reboot the node

)))

(((

Sending AT+FDR will restore the node to factory settings

)))

(((

Get the node's AT command setting by sending AT+CFG

)))

(((

)))

(((

**Example：**

)))

(((

AT+VER=EU868 v1.0

)))

(((

AT+NJM=1

)))

(((

AT+DEUI=25 32 12 45 65 26 12 35

)))

(((

AT+APPEUI=25 32 12 45 65 26 32 16

)))

(((

AT+APPKEY=25 32 12 45 65 26 32 16 89 48 85 65 45 87 89 55

)))

(((

AT+DADDR=00 00 00 00

)))

(((

AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

)))

(((

AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

)))

(((

AT+NWKID=00 00 00 13

)))

(((

AT+ADR=1

)))

(((

AT+DR=5

)))

(((

AT+TXP=1

)))

(((

AT+CHS=0

)))

(((

AT+CLASS=A

)))

(((

AT+CFM=0

)))

(((

AT+JN1DL=5000

)))

(((

AT+JN2DL=6000

)))

(((

AT+RX1DL=5000

)))

(((

AT+RX2DL=6000

)))

(((

AT+RX1WTO=24

)))

(((

AT+RX2WTO=6

)))

(((

AT+RX2FQ=869525000

)))

(((

AT+RX2DR=0

)))

(((

AT+RPL=0

)))

(((

AT+FCU=6

)))

(((

AT+FCD=0

)))

(((

AT+CFS=0

)))

(((

AT+NJS=1

)))

(((

AT+DCS=0

)))

(((

AT+PNM=1

)))

(((

AT+PWORD=123456

)))

(((

AT+EXT=1

)))

(((

AT+TDC=120000

)))

(((

AT+TIMESTAMP=1640851037 2021 12 30 7 57 17

)))

(((

AT+RJTDC=20

)))

(((

AT+DDETECT=0,1440

)))

(((

AT+WMOD=0

)))

(((

AT+CITEMP=1

)))

(((

AT+ARTEMP=-40,125

)))

(((

Send AT+PDTA=? to get the stored 174 data

)))

(((

**Example：**

)))

[[image:image-20220621144804-11.png]]

1068

1069

1070

== 6.3 How to upgrade the firmware? ==

1071

1072

1073

LHT52 requires a program converter to upload images to LHT52, which is used to upload image to LHT52 for:

1074

1075

* Support new features

1076

* For bug fix

1077

* Change LoRaWAN bands.

1078

1079

(((

1080

User can check this link for the detail of operation of firmware upgrade: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction.WebHome||anchor="H2.3LHT52"]]

)))

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

1085

1086

1087

User can follow the introduction for [[how to upgrade image>>||anchor="H6.3A0Howtoupgradethefirmware3F"]]. When download the images, choose the required image file for download.

1088

1089

1090

== 6.5 Why i see different working temperature for the device? ==

1091

1092

1093

The working temperature range of device depends on the battery user choose.

1094

1095

* Normal AAA Battery can support -10 ~~ 50°C working range.

1096

* Special AAA battery can support -40 ~~ 60 °C working range. For example: [[Energizer L92>>https://data.energizer.com/pdfs/l92.pdf]]

= 7. Order Info =

== 7.1 Main Device ==

1101

1102

1103

Part Number: (% style="color:#4472c4" %)PB01-LW-XX(%%) (white button) / (% style="color:#4472c4" %)PB01-LR-XX(%%)(Red Button)

1104

1105

(% style="color:#4472c4" %)**XX **(%%): The default frequency band

1106

1107

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

1108

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

1109

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

1110

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

1111

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

1112

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

1113

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

1114

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

= 7. Packing Info =

**Package Includes**:

1120

1121

* PB01 LoRaWAN Push Button x 1

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

1127

* 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:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].

1128

1129

= 9. Reference material =

1130

1131

1132

* [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/scl/fo/y7pvm58wcr8319d5o4ujr/APZtqlbzRCNbHoPWTmmMMWs?rlkey=wfh93x2dhcev3ydn0846rinf0&st=kdp6lg7t&dl=0]]

= 10. FCC Warning =

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

1138

1139

(1) This device may not cause harmful interference;

1140

1141

(2) this device must accept any interference received,including interference that may cause undesired operation.

1142

Wiki source code of PB01 -- LoRaWAN Button User Manual

Applications

Navigation