PB01 -- LoRaWAN Button User Manual

The (% style="color:blue" %)**PB01 LoRaWAN Push Button**(%%) is a wireless LoRaWAN device equipped with (% style="color:blue" %)**a single push button**(%%). When the user presses the button, the PB01 sends an uplink to the LoRaWAN Network Server using the long-range LoRaWAN wireless protocol. Additionally, the PB01 measures (% style="color:blue" %)**environment temperature & humidity**(%%) and periodically uplinks this data to the LoRaWAN Network Server.

26

27

The PB01 is powered by (% style="color:blue" %)**2 x AAA batteries**(%%), allowing it to operate for several years.* Users can easily replace the batteries once they are drained.

28

29

The PB01 also features a built-in speaker that can produce different sounds when the button is pressed or when a reply (downlink) is received from the Network Server. The speaker can be disabled if the user prefers.

30

31

The PB01 is fully compatible with the LoRaWAN v1.0.3 protocol, and works seamlessly with standard LoRaWAN gateways.

32

33

~* Battery life depends on the frequency of data transmission. Please refer to the [[battery analyzer>>||anchor="H4.2A0PowerConsumptionAnalyze"]] for details.

== 1.2 Features ==

* Wall-mountable

* LoRaWAN v1.0.3 protocol, Class A mode

41

* 1 x push button (available in different colors)

42

* Built-in temperature and humidity sensor

43

* Built-in speaker

44

* Frequency bands: CN470, EU433, KR920, US915, EU868, AS923, AU915

45

* AT commands for parameter changes

46

* Remote parameter configuration via LoRaWAN downlink

47

* Firmware upgradable via programming port

48

* Supports 2 x AAA LR03 batteries

49

* IP rating: IP52

50

51

== 1.3 Specification ==

52

53

54

(% style="color:blue" %)**Built-in Temperature Sensor:**

55

56

* **Resolution**: 0.01 °C

57

* **Accuracy Tolerance**: Typ ±0.2 °C

58

* **Long-Term Drift**: < 0.03 °C/year

59

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

60

61

(% style="color:blue" %)**Built-in Humidity Sensor:**

62

63

* **Resolution**: 0.01 %RH

64

* **Accuracy Tolerance**: Typ ±1.8 %RH

65

* **Long-Term Drift**: < 0.2 %RH/year

66

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

67

68

== 1.4 Power Consumption ==

69

70

71

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

72

73

74

== 1.5 Storage & Operation Temperature ==

75

76

77

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

78

79

80

== 1.6 Applications ==

81

82

83

* Smart buildings & home automation

84

* Logistics & supply chain management

* Smart metering

* Smart agriculture

* Smart cities

* Smart factories

= 2. Operation Mode =

91

92

== 2.1 How It Works? ==

93

94

95

Each PB01 is shipped with registration information that can be used to register and activate the device with a LoRaWAN Network Server using Over-The-Air Activation (OTAA), which is the most secure method for activating an end device on a LoRaWAN Network Server. It also supports Activation-By-Personalization (ABP), but this method is not recommended as it is less secure.

96

97

After registration, if the PB01 is within the LoRaWAN network's coverage area, it can join the network and start transmitting sensor data to the LoRaWAN Network Server. The default uplink interval is **20 minutes**.

98

99

100

== 2.2 How to turn on PB01? ==

101

102

103

(% style="color:red" %)** 1. Open the enclosure from the bottom.**

104

105

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

106

107

108

(% style="color:red" %)** 2. Insert 2 x AAA LR03 batteries to turn on the device.**

109

110

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

111

112

113

(% style="color:#ff0000" %)** 3. After **(% style="caret-color:#ff0000; color:#ff0000" %)**activating with a LoRaWAN network**(% style="color:#ff0000" %)**, you can re-join/restart the device by long pressing the ACT button as shown in the image below.**

114

115

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

116

117

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

118

119

120

== 2.3 Registering with a LoRaWAN network ==

121

122

123

This section explains how to register the PB01 with a LoRaWAN Network Server, such as The Things Stack Cloud. After registering, the PB01 can join the network once you long-press the ACT button.

124

125

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

126

The following network diagram shows how the PB01 communicates with The Things Stack Cloud (similarly to other LoRaWAN Network Servers) end to end.

127

128

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

129

130

131

Each PB01 is shipped with its unique registration information printed on a sticker affixed inside the cardboard package that the device is packed in. The registration information includes the following:

* DevEUI

* AppEUI

* AppKey

This information is required to perform the OTAA (Over-the-Air Activation) of the device, which is the most secure way of activating the device with a LoRaWAN network server.

138

139

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

140

141

142

=== 2.3.1 Add PB01 to The Things Stack ===

143

144

145

PB01 currently supports only **manual **registartion with The Things Stack.

146

147

148

==== 2.3.1.1 Creating an application ====

149

150

151

Sign up for a free account with [[The Things Stack Sandbox>>url:https://eu1.cloud.thethings.network/]] if you do not have one yet. Then, create an **application **as shown in the screenshots below.

152

153

154

==== 2.3.1.2 Adding manually ====

155

156

157

You can refer to the screenshots below to register your PB01 using The Things Stack's manual registration option.

158

159

On The Things Stack console:

160

161

* Click **Applications**.

162

* Click <**your application**>. E.g. dragino-docs

163

* Click **End devices**.

164

* Click **+ Register end devic**e button.

[[image:5.png]]

* Select **Enter end device specifies manually** option.

170

* **Frequency plan**: Select the frequency plan that matches your device. E.g.: Europe 863-870 MHz (SF9 for RX2 - recommended).

171

* **LoRaWAN version**: LoRaWAN Specification 1.0.3

172

* Regional Parameters version: You can't change it and it will select automatically.

[[image:2.png]]

* **JoinEUI**: Enter the **AppEUI** of the device (see the registration information sticker) and Click the **Confirm** button.

178

* **DevEUI**: Enter the DevEUI of the device (see the registration information sticker).

179

* **AppKey**: Enter the AppKey of the device (see the registration information sticker).

180

* **End device ID**: Enter a name for your end device to uniquely identify it within this application.

181

* Click **View registered end device** option.

182

* Click **Register end device** button.

[[image:3.png]]

You will be navigated to the **Device overview **page.

188

(% style="display:none" %)

189

190

191

==== 2.3.1.3 Activate the PB01 ====

192

193

194

Long press the **ACT** button to activate the PB01. It will then join The Things Stack. Once successfully connected, the device will begin uplinking sensor data to The Things Stack, which can be viewed on the **Live data** panel.

195

196

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

197

198

199

== 2.4 Uplink Payload ==

200

201

202

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

203

204

* Valid Sensor Value: Use FPORT=2

205

* Other control command: Use FPORT other than 2.

206

207

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

208

209

210

The 'Device Status' uplink is sent by the PB01 as its first uplink after successfully joining a LoRaWAN network. However, you can manually retrieve the device status as an uplink by sending a command as a downlink to the device. The format of the downlink command should be in hexadecimal.

211

212

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

213

214

The device uplinks its status via FPort=5, and the payload format is as follows:

215

216

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

217

|=(% 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**

218

219

220

The following figure shows the decoded device status payload as displayed on The Things Stack.

221

222

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

223

224

225

For example, if the device status uplink includes the payload, [[image:image-20240507152254-13.png||height="26" width="130"]]

226

227

228

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

229

230

(% style="color:#4472c4" %)**Firmware version**(%%): 0x0100 - value 0x0100 means v1.0.0.

231

232

(% style="color:#4472c4" %)**Frequency band**(%%): 01 - means EU868. The following are the possible values for other frequency bands.

*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**(%%): 0xFF - value 0x00 ~~ 0x08 (only for CN470, AU915, US915. Others are 0x00)

255

256

(% style="color:#4472c4" %)**BAT**(%%): 0x 0CDE - represents the battery voltage for PB01. The values 0x0CDE means 3294 mV = 3.294 V

257

258

259

=== 2.4.2 Uplink FPort~=2, Real time sensor values ===

260

261

262

The PB01 sends real time sensor values after the Device Status uplink. The device will continue to send this uplink periodically. The default interval is 20 minutes, but it can be changed.

263

264

This type of uplink uses FPort=2 and, by default, is sent every 20 minutes. The default uplink interval [[can be changed>>||anchor="H3.1A0DownlinkCommandSet"]] using AT commands.

265

266

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

267

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

268

**Size(bytes)**

269

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

270

**1**

271

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

272

**1**

273

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

274

**2**

275

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

276

**2**

277

)))

278

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

279

Value

280

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

281

Sound_ACK & Sound_key

282

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

(((

Alarm

)))

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

(((

Temperature

)))

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

Humidity

)))

The following figure shows the decoded real time sensor values payload as displayed on The Things Stack.

295

296

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

297

298

299

For example, if the real time sensor values uplink includes the payload (FPort=2): (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**

300

301

302

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

303

304

Byte 1 and 2: Check the battery voltage.

305

306

* Example 1: 0x0CEA = 3306mV

307

* Example 2: 0x0D08 = 3336mV

308

309

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

310

311

Byte 3: Key sound and ACK sound are enabled by default.

* Example1: 0x03

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

316

317

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

* Example 2: 0x01

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

322

323

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

324

325

326

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

Byte 4: Key alarm.

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

331

* Example 2: 0x00 & 0x01=0, FALSE.

332

333

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

334

335

Byte 5 and 6: Temperature.

336

337

* Example 1: 0x0111/10=27.3°C

338

* Example 2: (0xFF0D-65536)/10=-24.3°C

339

340

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

341

342

(FF0D & 8000 : Check whether the highest bit is 1. If the highest bit is 1, the value is negative)

343

344

345

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

346

347

Byte 7 and 8: Humidity

348

349

* Humidity: 0x02A8/10=68.0%

350

351

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

352

353

354

PB01 stores sensor values, and you can retrieve these historical values via a downlink command. The Datalog sensor values are sent via FPort=3.

355

356

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

357

358

359

Each data entry is 11 bytes. To save airtime and battery, the maximum payload size is depending on the current Date Rate and the frequency band.(% style="display:none" %) (%%) For example, in US915 band, the maximum payload for different DR is as follows:

360

361

1. **DR0**: maximum payload is 11 bytes. The device will uplink one entry of data.

362

1. **DR1**: maximum payload is 53 bytes. The device will upload 4 entries of data (total of 44 bytes)

363

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

364

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

365

366

(% style="color:red" %)**Note: The PB01 will save 178 sets of historical data. If the device doesn't have any data during the polling time, it will uplink 11 bytes of 0s.**

367

368

See [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]] for more information.

369

370

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

371

372

=== 2.4.4 Decoding the payload in The Things Stack Cloud ===

373

374

375

In the LoRaWAN protocol, the uplink payload uses HEX format to store data. You need to add a payload formatter or decoder in the LoRaWAN server to extract each field and convert them into readable values.

376

377

The following figure shows how to add the uplink payload formatter in The Things Stack. The uplink decoder for PB01 can be found here: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]

378

379

Select your **end device**, then click the **Payload Formatters **tab, followed by the **Uplink** tab. Next, select '**Custom Javascript Formatte**r' from the '**Formatter Type**' dropdown list. Finally, paste the payload formatter in the '**Formatter Code**' box and click the '**Save Changes**' button.

380

381

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

382

383

384

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

)))

(((

Please refer to the figure below.

417

)))

418

419

[[image:image-20240510150924-2.png||height="612" width="1186"]]

420

421

422

Log in to DATACAKE, copy the API under the account.

423

424

[[image:image-20240510151944-3.png||height="581" width="1191"]]

425

426

427

[[image:image-20240510152150-4.png||height="697" width="1188"]]

428

429

430

[[image:image-20240510152300-5.png||height="298" width="1191"]]

431

432

433

[[image:image-20240510152355-6.png||height="782" width="1193"]]

434

435

[[image:image-20240510152542-8.png||height="545" width="739"]]

436

437

[[image:image-20240510152634-9.png||height="748" width="740"]]

438

439

440

[[image:image-20240510152809-10.png||height="607" width="732"]]

441

442

[[image:image-20240510153934-14.png||height="460" width="1199"]]

443

444

445

[[image:image-20240510153435-12.png||height="428" width="1197"]]

446

447

448

Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.

449

450

[[image:image-20240510153624-13.png||height="468" width="1195"]]

451

452

Visual widgets please read the DATACAKE documentation.

453

454

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

455

456

== 2.6 Datalog Feature ==

457

458

459

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

460

To retrieve a sensor value, you can send a poll command from the network server to request the sensor to send the value within the required time period.

461

462

463

=== 2.6.1 Unix Timestamp ===

464

465

466

The Unix timestamp indicates the sampling time of the uplink payload, based on the following format:

467

468

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

469

470

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

471

472

For example, if the Unix timestamp is in HEX format as 0x60137afd, you can convert it to decimal: 1611889405, and then convert it to the time: 2021-Jan-29, Friday, 03:03:25 (GMT).

473

474

[[image:1655782409139-256.png]]

475

476

477

=== 2.6.2 Poll sensor value ===

(((

You can poll sensor values based on timestamps from the server. The start and end timestamps use the Unix timestamp format as mentioned above. The device will reply with all data logs from this time period, using the uplink interval.

)))

(((

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

)))

(((

**0x31 **: Prefix

**0x5FC5F350** and **0x5FC60160 **: This is equivalent to checking the stored data between **2020/12/1 07:40:00** and **2020/12/1 08:40:00**.

492

493

**0x05 **: The uplink interval is 5 seconds, which means the PB01 will send one packet every 5 seconds. The uplink interval can be mentioned in the downlink payload with a range of 5 to 255 seconds.

)))

=== 2.6.3 Datalog Uplink payload ===

498

499

500

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

501

502

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

== 2.7 Buttons ==

* **ACT button**

Long press this button, and the PB01 will reset and rejoin the network.

510

511

[[image:image-20240510161626-17.png||height="192" width="224"]]

* **Alarm button**

Press this button to immediately send an uplink, and the alarm will be set to 'TRUE'.

517

518

[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)

519

520

521

== 2.8 LED Indicators ==

(((

The PB01 has a single LED that displays different colors to indicate various stages:

526

527

1. **Hold the ACT button:** The LED will light up GREEN. GREEN flashing indicates the node is restarting. A BLUE flash signals a request for network access, and a solid GREEN light for 5 seconds signifies successful network access.

528

1. (((

529

**Normal Working State:**

530

531

* When the node restarts, hold the ACT button, and the LED will turn GREEN. GREEN flashing indicates a restart. A BLUE flash signals a request for network access, and a solid GREEN light for 5 seconds indicates successful network access.

532

)))

533

1. (((

534

**During OTAA Join:**

535

536

* For each Join Request uplink, the LED will blink GREEN once.

537

* Once the join is successful, the LED will remain solid GREEN for 5 seconds.

538

* After joining, for each uplink, the LED will blink either BLUE or GREEN.

)))

1. (((

**Alarm Button:**

* When the alarm button is pressed, the LED will flash RED until the node receives an acknowledgment (ACK) from the platform, followed by the LED staying BLUE for 5 seconds.

)))

)))

(((

)))

== 2.9 Buzzer ==

The PB01 produces different sounds or tones for the following events, which can be turned on or off using the [[AT+SOUND>>||anchor="H3.3A0SetbuttonsoundandACKsound"]] command.

555

556

* **Button Sound:** This is the tone produced by the node after the alarm button is pressed. Users can use the [[AT+OPTION>>||anchor="H3.4A0Setbuzzermusictype2807E429"]] command to set different button sounds.

557

* **ACK Sound:** This is the notification tone emitted when the node receives an acknowledgment (ACK).

558

559

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

560

561

562

You can configure PB01 via AT Commands or LoRaWAN Downlinks.

563

564

* See [[FAQ>>||anchor="H6.FAQ"]] to find out how to connect PB01 with a computer to configure it using AT commands.

565

566

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

567

568

(% style="display:none" %)

569

570

There are two types of commands to configure the PB01:

571

572

1. (((

573

**General Commands:**

574

These commands are used to configure:

575

576

* General system settings, such as the uplink interval.

577

* LoRaWAN protocol and radio-related parameters.

578

579

These commands are the same for all Dragino devices that support the DLWS-005 LoRaWAN stack (Note~*~*). You can find these commands on the wiki: [[End Device Downlink Command>>path:#]].

580

)))

581

1. **Commands Specifically Designed for PB01:**

582

These commands are valid only for the PB01, as listed below (see Downlink Commands):

583

584

== 3.1 Downlink Commands ==

585

586

587

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

588

|=(% style="width: 130px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 150px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 90px; background-color: rgb(79, 129, 189); color: white;" %)**Response**|=(% style="width: 140px; background-color: rgb(79, 129, 189); color: white;" %)**Downlink**

589

|(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((

590

Get the current TDC (uplink) time

591

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

592

1200000

593

OK

594

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

595

|(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set the TDC (uplink) time|(% style="width:92px" %)OK|(% style="width:206px" %)(((

(((

0x0100012C:

01: Prefix

00012C: 0X00012C=300(seconds)

)))

(((

)))

)))

|(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset the node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF

607

|(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore to factory settings|(% style="width:92px" %) |(% style="width:206px" %)0x04FE

608

|(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((

609

0,7,0

610

OK

611

)))|(% style="width:206px" %)Default 0,7,0

612

|(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((

613

Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry

614

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

615

OK

616

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

05010701

05: fixed command

01:confirmed uplink

07: retry 7 times

01: fcnt count plus 1

622

)))

623

|(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((

624

Check the current network connection method

625

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

626

1

627

OK

628

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

629

|(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((

630

Attention:Take effect after ATZ

631

OK

632

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

0x2000: ABP

0x2001: OTAA

20: fixed command

)))

|(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((

638

0

639

OK

640

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

641

|(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)Set RPL=1 |(% style="width:92px" %)OK|(% style="width:206px" %)(((

642

0x2101:

643

21: fixed command

644

01: for details, check wiki

645

)))

646

|(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((

647

1

648

OK

649

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

650

|(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((

0x2200: close

0x2201: open

22: fixed command

)))

|(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)

656

|(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((

657

Set DR to 1.

658

It takes effect only when ADR=0

659

)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((

0x22000101:

00: ADR=0

01: DR=1

01: TXP=1

22: fixed command

)))

|(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)

667

|(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((

668

Set TXP to 1.

669

It takes effect only when ADR=0

670

)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((

0x22000101:

00: ADR=0

01: DR=1

01: TXP=1

22: fixed command

)))

|(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((

0x26000A:

26: fixed command

000A: 0X000A=10(min)

for details, check wiki

682

)))

683

|(% style="width:130px" %) |(% style="width:151px" %)(((

684

(((

685

~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_

686

687

Retrieve stored data for a specified period of time

)))

(((

)))

)))|(% style="width:92px" %) |(% style="width:206px" %)(((

694

0x3161DE7C7061DE8A800A:

695

31: fixed command

696

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

697

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

0A: 0X0A=10(second)

View details 2.6.2

)))

|(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((

702

1,1440,2880

703

OK

704

)))|(% style="width:206px" %)Default 1,1440,2880(min)

705

|(% style="width:130px" %)AT+DDETECT=(((

706

1,1440,2880

707

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

708

Set DDETECT setting status and time

709

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

710

)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((

0x320005A0: close

0x320105A0: open

32: fixed command

05A0: 0X05A0=1440(min)

715

)))

716

717

== 3.2 Set Password ==

718

719

720

**Feature**: Set the device password with a maximum of 9 digits.

721

722

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

723

724

(% border="2" style="width:500px" %)

725

|(% style="width:141px" %)**Command**|(% style="width:357px" %)**AT+PWORD**

726

|(% style="width:141px" %)**Parameters**|(% style="width:357px" %)**password** : maximum up to 9 digits

727

|(% style="width:141px" %)**Get**|(% style="width:357px" %)AT+PWORD=?

728

|(% style="width:141px" %)**Response**|(% style="width:357px" %)(((

729

Returns the current password

730

OK

731

)))

732

|(% style="width:141px" %)**Set**|(% style="width:357px" %)AT+PWORD=<password>

733

|(% style="width:141px" %)**Response**|(% style="width:357px" %)OK

734

|(% style="width:141px" %)**Example**|(% style="width:357px" %)(((

735

AT+PWORD=999999999

736

Set the password 999999999

737

)))

738

739

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

740

741

There is no downlink command for this feature.

742

743

744

== 3.3 Set button sound and ACK sound ==

745

746

747

**Feature**: Turn on/off button sound and ACK alarm.

748

749

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

750

751

(% border="2" style="width:500px" %)

752

|(% style="width:143px" %)**Command**|(% style="width:355px" %)**AT+SOUND**

753

|(% style="width:143px" %)**Parameters**|(% style="width:355px" %)(((

**button_sound** :

**0** - off

**1** - on

**ack_sound** :

**0** - off

**1** - on

)))

|(% style="width:143px" %)**Get**|(% style="width:355px" %)AT+SOUND=?

762

|(% style="width:143px" %)**Response**|(% style="width:355px" %)(((

763

Returns the current sound settings. <button_sound>,<ack_sound>

764

OK

765

)))

766

|(% style="width:143px" %)**Set**|(% style="width:355px" %)(((

767

AT+SOUND=<button_sound>,<ack_sound>

768

)))

769

|(% style="width:143px" %)**Response**|(% style="width:355px" %)OK

770

|(% style="width:143px" %)**Example**|(% style="width:355px" %)(((

771

AT+SOUND=0,1

772

This will turn off the button sound and turn on the ACK sound.

773

)))

774

775

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

776

777

(% border="2" style="width:500px" %)

778

|(% style="width:143px" %)**Prefix**|(% style="width:355px" %)**0xA1**

779

|(% style="width:143px" %)**Parameters**|(% style="width:355px" %)(((

780

**button_sound** : 1 byte in hexadecimal.

781

**00** - off

782

**01** - on

783

**ack_sound** : 1 byte in hexadecimal.

**00** - off

**01** - on

)))

|(% style="width:143px" %)**Payload format**|(% style="width:355px" %)<prefix><button_sound><ack_sound>

788

|(% style="width:143px" %)**Example**|(% style="width:355px" %)(((

789

A10001

790

Turn off the button sound and turn on ACK sound.

791

)))

792

793

== 3.4 Set buzzer music type (0~~4) ==

794

795

796

Feature: Set different alarm key response sounds.There are five different types of button music.

797

798

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

799

800

(% border="2" style="width:500px" %)

801

|(% style="width:146px" %)**Command**|(% style="width:352px" %)**AT+OPTION**

802

|(% style="width:146px" %)**Parameters**|(% style="width:352px" %)(((

803

**<buzzer_music_type> :**

**0**

**1**

**2**

**3**

)))

|(% style="width:146px" %)**Get**|(% style="width:352px" %)AT+OPTION=?

810

|(% style="width:146px" %)**Response**|(% style="width:352px" %)(((

811

Return the current music type.

812

OK

813

)))

814

|(% style="width:146px" %)**Set**|(% style="width:352px" %)AT+OPTION=<buzzer_music_type>

815

|(% style="width:146px" %)**Response**|(% style="width:352px" %)OK

816

|(% style="width:146px" %)**Example**|(% style="width:352px" %)(((

817

AT+OPTION=1

818

Set the buzzer music to type 1

819

)))

820

821

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

822

823

(% border="2" style="width:500px" %)

824

|(% style="width:145px" %)**Prefix**|(% style="width:353px" %)**0xA3**

825

|(% style="width:145px" %)**Parameters**|(% style="width:353px" %)(((

826

**<buzzer_music_type> : **1 byte in hexadecimal

**0**

**1**

**2**

**3**

)))

|(% style="width:145px" %)**Payload format**|(% style="width:353px" %)<prefix><buzzer_music-type>

833

|(% style="width:145px" %)**Example**|(% style="width:353px" %)(((

834

A300

835

Set the buzzer music to type 0.

836

)))

837

838

== 3.5 Set Button Press Time ==

839

840

841

**Feature**: Set the holding time for pressing the alarm button to prevent accidental activation. The values range from 0 to 1000 ms.

842

843

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

844

845

(% border="2" style="width:500px" %)

846

|(% style="width:145px" %)**Command**|(% style="width:353px" %)**AT+STIME**

847

|(% style="width:145px" %)**Parameters**|(% style="width:353px" %)**button_press_duration** : in milliseconds

848

|(% style="width:145px" %)**Get**|(% style="width:353px" %)AT+STIME=?

849

|(% style="width:145px" %)**Response**|(% style="width:353px" %)Returns the current button press duration.

850

|(% style="width:145px" %)**Set**|(% style="width:353px" %)(((

851

AT+STIME=<button_press_duration>

852

)))

853

|(% style="width:145px" %)**Response**|(% style="width:353px" %)OK

854

|(% style="width:145px" %)**Example**|(% style="width:353px" %)(((

855

AT+STIME=1000

856

Set the button sound duration to 1000 ms.

857

)))

858

859

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

860

861

(% border="2" style="width:500px" %)

862

|(% style="width:146px" %)**Prefix**|(% style="width:352px" %)**0xA2**

863

|(% style="width:146px" %)**Parameters**|(% style="width:352px" %)**button_press_duration** : in milliseconds, 2 bytes in hex

864

|(% style="width:146px" %)**Payload format**|(% style="width:352px" %)<prefix><button_press_duration>

865

|(% style="width:146px" %)**Example**|(% style="width:352px" %)(((

866

A203E8

867

Hold the alarm button for 10 seconds before the node sends the alarm uplink packet.

)))

= 4. Battery =

PB01 uses 2xAAA LR03 (1.5V) batteries.

874

875

876

== 4.1 Replacing batteries ==

877

878

879

If the batteries are running low (if the battery voltage drops to 2.1V), you can use any two generic AAA batteries to replace them.

880

881

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

882

883

1. The PB01 doesn't have any screws; you can use a nail to open the battery cover.

884

885

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

886

887

888

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

889

890

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

891

892

893

== 4.2 Power Consumption Analysis ==

894

895

896

Dragino's battery-powered products all operate in Low Power mode. We provide an updated battery calculator based on real device measurements. You can use this calculator to estimate battery life and calculate it for different transmission intervals.

897

898

**Instructions for use:**

899

900

**Step 1:** Download the latest version of the **DRAGINO_Battery_Life_Prediction_Table.xlsx** from the [[battery calculator>>https://www.dropbox.com/sh/sxrgszkac4ips0q/AAA4XjBI3HAHNpdbU3ALN1j0a/Battery%20Document/Battery_Analyze?dl=0&subfolder_nav_tracking=1]].

901

902

**Step 2:** Open the file and select:

* Product Model

* Uplink Interval

* Working Mode

The expected battery life for different scenarios will be displayed on the right.

909

910

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

= 5. Accessories =

* (((

**AS-02 USB Type-C Converter**

918

919

The AS-02 is an optional accessory. It is a USB Type-C converter that provides access to the AT console of the PB01 when used with a USB-TTL adapter. For more details, see this [[link>>||anchor="H6.1HowtouseATCommandtoconfigurePB01"]].

920

)))

921

922

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

= 6. FAQ =

== 6.1 How to use AT Commands to configure PB01 ==

928

929

930

PB01 supports the AT Command set. Users can use a USB-to-TTL adapter along with the AS-02 USB Type-C converter to connect to the PB01 and issue AT commands, as shown below.

931

932

[[image:image-20240511085914-1.png||height="570" width="602"]]

**Connection:**

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

938

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

939

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

(((

)))

(((

On the PC, you need to set the serial tool (such as [[PuTTY>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access the serial console for the PB01. The AT commands are disabled by default, and you need to enter the password (default: **123456**) to activate them. The timeout for entering AT commands is 5 minutes; after 5 minutes, the user will need to enter the password again.

947

948

Enter the password 123456 and type "ATZ" to reboot the PB01, as shown below:

949

)))

950

951

[[image:image-20240510174509-18.png||height="572" width="791"]]

952

953

954

== 6.2 AT Commands ==

(((

* Sending "ATZ" will reboot the device.

959

* Sending "AT+FDR" will restore the device to factory settings.

960

* Get the device's AT command settings by sending "AT+CFG." The following is the output after issuing the AT+CFG command.

)))

(((

)))

(((

**Sample output:**

)))

(((

AT+DEUI=FA 23 45 55 55 55 55 51

973

974

AT+APPEUI=FF AA 23 45 42 42 41 11

975

976

AT+APPKEY=AC D7 35 81 63 3C B6 05 F5 69 44 99 C1 12 BA 95

AT+DADDR=FFFFFFFF

AT+APPSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

981

982

AT+NWKSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

AT+ADR=1

AT+TXP=7

AT+DR=5

AT+DCS=0

AT+PNM=1

AT+RX2FQ=869525000

AT+RX2DR=0

AT+RX1DL=5000

AT+RX2DL=6000

AT+JN1DL=5000

AT+JN2DL=6000

AT+NJM=1

AT+NWKID=00 00 00 13

AT+FCU=61

AT+FCD=11

AT+CLASS=A

AT+NJS=1

AT+RECVB=0:

AT+RECV=

AT+VER=EU868 v1.0.0

AT+CFM=0,7,0

AT+SNR=0

AT+RSSI=0

AT+TDC=1200000

AT+PORT=2

AT+PWORD=123456

AT+CHS=0

AT+RX1WTO=24

AT+RX2WTO=6

AT+DECRYPT=0

AT+RJTDC=20

AT+RPL=0

AT+TIMESTAMP=systime= 2024/5/11 01:10:58 (1715389858)

AT+LEAPSEC=18

AT+SYNCMOD=1

AT+SYNCTDC=10

AT+SLEEP=0

AT+ATDC=1

AT+UUID=003C0C53013259E0

1061

1062

AT+DDETECT=1,1440,2880

AT+SETMAXNBTRANS=1,0

AT+DISFCNTCHECK=0

AT+DISMACANS=0

AT+PNACKMD=0

AT+SOUND=0,0

AT+STIME=0

AT+OPTION=3

)))

(((

**Example:**

)))

[[image:image-20240511091518-2.png||height="601" width="836"]]

1086

1087

1088

== 6.3 How to upgrade the firmware? ==

1089

1090

1091

PB01 requires a USB-to-TTL adapter along with the AS-02 USB Type-C converter to upload a new firmware image to PB01: Upgrading the device firmware,

1092

1093

* supports new features

1094

* fixes bugs

1095

* allows change the LoRaWAN frequency bands.

1096

1097

The PB01 is shipped with firmware preloaded. The firmware is divided into a bootloader and a work program.

1098

1099

If the bootloader is erased for any reason, you will need to download the firmware (which includes both the bootloader and the work program).

1100

1101

The latest firmware version for the PB01 can be downloaded from this link: [[firmware>>url:https://www.dropbox.com/scl/fo/y7pvm58wcr8319d5o4ujr/APZtqlbzRCNbHoPWTmmMMWs?rlkey=wfh93x2dhcev3ydn0846rinf0&st=kdp6lg7t&dl=0]]

1102

1103

1104

=== 6.3.1 Update firmware (Assume device have bootloader) ===

1105

1106

1107

Follow the steps below only if the firmware needs to be updated and the bootloader of your device is not corrupted and is working properly.

1108

1109

(% style="color:blue" %)**Step 1**(%%):** Connect UART as per FAQ 6.1**

1110

1111

(% style="color:blue" %)**Step 2**(%%):** Update follow [[Instruction for update via DraginoSensorManagerUtility.exe>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H3.2.1UpdateafirmwareviaDraginoSensorManagerUtility.exe]]. **

1112

1113

1114

=== 6.3.2 Update firmware (Assume device doesn't have bootloader) ===

1115

1116

1117

Follow the steps below if the firmware needs to be updated along with the bootloader. This method is required if the bootloader of your device is corrupted.

1118

1119

Download both the bootloader and the worker program. After updating the firmware, the device will have the bootloader installed, allowing you to use the above 6.3.1 method to update the worker program.

1120

1121

1122

(% style="color:blue" %)**Step 1**(%%):** **Install [[TremoProgrammer>>url:https://www.dropbox.com/scl/fo/gk1rb5pnnjw4kv5m5cs0z/h?rlkey=906ouvgbvif721f9bj795vfrh&dl=0]] first.

1123

1124

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220615170542-5.png?rev=1.1||alt="image-20220615170542-5.png"]]

1125

1126

(% style="color:blue" %)**Step 2**(%%): Hardware Connection

1127

1128

Connect PC and PB01 via USB-TTL adapter .

1129

1130

(% style="color:red" %)**Note: To download firmware in this way, you need to pull the boot pin(Program Converter D- pin) high to enter the burn mode. After burning, disconnect the boot pin of the node and the 3V3 pin of the USB-TTL adapter, and reset the node to exit the burning mode.**

**Connection:**

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

1135

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

1136

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

1137

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

1138

1139

(% style="color:blue" %)**Step 3**(%%):** **Select the device port to be connected, baud rate and bin file to be downloaded.

1140

1141

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

1142

1143

Users need to reset the node to start downloading the program.

1144

~1. Reinstall the battery to reset the node

1145

2. Hold down the ACT button to reset the node (see [[2.7>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PB01--LoRaWAN_Button_User_Manual/#H2.7Button]] ).

1146

1147

When this interface appears, it indicates that the download has been completed.

1148

1149

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

1150

1151

Finally, Disconnect Program Converter D- pin, reset the node again , and the node exits burning mode.

1152

1153

1154

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

1155

1156

1157

If you want to change the frequency band/region of your device, the only way is to** upgrade its firmware** to support the desired frequency band/region. When downloading the firmware, ensure you choose the correct image that supports the required frequency band/region.

1158

1159

We have named each firmware file to make it easy for you to identify its frequency band/region. For example, for the **EU868** band, the file name is **eu868.bin.** You can follow the instructions in the section [[how to upgrade image>>||anchor="H6.3A0Howtoupgradethefirmware3F"]] to complete the process.

1160

1161

1162

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

1163

1164

1165

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

1166

1167

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

1168

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

1169

1170

= 7. Ordering Information =

== 7.1 PB01 ==

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

1176

1177

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

1178

1179

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

1180

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

1181

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

1182

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

1183

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

1184

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

1185

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

1186

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

1187

1188

= 8. Packaging Information =

1189

1190

1191

**Package Includes**:

1192

1193

* PB01 LoRaWAN Push Button x 1

= 9. Support =

* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible within the aforementioned schedule.

1199

* Please provide as much information as possible regarding your inquiry (e.g., product models, an accurate description of your problem, and steps to replicate it) and send an email to [[support@dragino.com>>mailto:support@dragino.com]].

1200

1201

= 10. Reference material =

1202

1203

1204

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

= 11. FCC Warning =

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

1210

1211

(1) This device may not cause harmful interference;

1212

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

1213

1214

Wiki source code of PB01 -- LoRaWAN Button User Manual

Applications

Navigation