Version 381.1 by Dilisi S on 2025/04/01 02:51
Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20250228144849-1.jpeg||height="490" width="490"]]
3
4
5
6
7 (% _mstvisible="1" %)
8 (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
9
10 {{toc/}}
11
12
13
14
15
16
17
18
19 = 1.  Introduction =
20
21 == 1.1  What is the PB05-L LoRaWAN Push Button? ==
22
23
24 The **PB05-L LoRaWAN Button** is a wireless device with (% style="color:blue" %)**5 push buttons**(%%). When a button is pressed, the device sends a signal to the IoT server using the LoRaWAN protocol.
25
26 It runs on (% style="color:blue" %)**2 x AA batteries**(%%), lasting for approximately (% style="color:blue" %)**30k presses**(%%) across all five buttons. When the batteries run out, they can be easily replaced.
27
28 The PB05-L also has a **built-in speaker** that plays different sounds when a button is pressed or when a response is received from the server. If needed, the speaker can be turned off.
29
30 This device is **fully compatible with LoRaWAN v1.0.3** and works with any standard LoRaWAN gateway.
31
32 {{info}}
33 **Note:** Battery life depends on how often the device sends data. Check the [[battery analyzer>>||anchor="H4.2A0PowerConsumptionAnalyze"]] for details.
34 {{/info}}
35
36 == 1.2  Features ==
37
38
39 * Wall-mountable
40 * LoRaWAN v1.0.3 Class A protocol
41 * 5 push buttons
42 * Built-in speaker
43 * Frequency bands: CN470, EU433, KR920, US915, EU868, AS923, AU915
44 * AT commands for parameter configuration
45 * Remote parameter configuration via LoRaWAN downlink
46 * Firmware upgradeable via programming port
47 * Supports 2 × AA LR6 batteries
48 * IP52-rated for dust and water resistance
49
50 == 1.3  Power Consumption ==
51
52
53 * **Idle:** 5 µA
54 * **Transmit:** Max 110 mA
55
56 == 1.4  Storage & Operation Temperature ==
57
58
59 -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on the battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
60
61
62 == 1.5  Applications ==
63
64
65 * Smart Buildings & Home Automation
66 * Logistics and Supply Chain Management
67 * Smart Metering
68 * Smart Agriculture
69 * Smart Cities
70 * Smart Factory
71
72 See **Use Cases** for more information.
73
74
75 == 1.6 Device Apperance ==
76
77
78 (% class="wikigeneratedid" %)
79 [[image:image-20250303102218-1.jpeg||height="340" width="572"]]
80
81 (% class="wikigeneratedid" %)
82 (% style="color:red" %)**Note: For customization purposes, the PVC sticker is not attached by default.**
83
84
85 == 1.7 Mechanical Drawings ==
86
87
88 [[image:image-20250312090840-1.png||height="509" width="671"]]
89
90
91 = 2.  Operation Mode =
92
93 == 2.1  How it works? ==
94
95
96 Each PB05-L is shipped with a unique set of **LoRaWAN OTAA keys**. To use the PB05-L in a LoRaWAN network, the user must enter these OTAA keys into the LoRaWAN network server.
97
98 Once the device is within the network’s coverage, it will automatically join and start transmitting sensor data. By default, the device sends an uplink every **20 minutes**.
99
100
101 == 2.2  How to Activate PB05-L? ==
102
103
104 (% style="color:red" %)** 1.  Open the enclosure from the bottom as shown in the image below.**
105
106 [[image:image-20250303105217-1.jpeg||height="298" width="493"]]
107
108
109 (% style="color:red" %)** 2.  Insert 2 x AA LR6 batteries. Make sure to insert them in the correct direction.**
110
111 [[image:image-20250303105439-2.jpeg||height="241" width="489"]]
112
113
114 (% style="color:red" %)** 3. Activate the device by pressing and holding (long press) the ACT button.**
115
116 [[image:image-20250303105945-3.jpeg||height="217" width="518"]]
117
118 You can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to determine the working state of the PB05-L.
119
120
121 == 2.3  Example to join LoRaWAN network ==
122
123
124 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.
125
126 (% _mstvisible="1" class="wikigeneratedid" %)
127 Assume the LPS8v2 is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. We need to add the PB05-L device in TTN V3 portal. 
128
129 [[image:image-20250305164059-1.jpeg]]
130
131 (% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB05-L.
132
133 Each PB05-L is shipped with a sticker with the default DEV EUI as below:
134
135 [[image:image-20230426083617-1.png||height="294" width="633"]]
136
137
138 Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
139
140
141 **Create the application.**
142
143 [[image:image-20250306095548-1.jpeg]]
144
145
146 [[image:image-20250306095614-2.jpeg]]
147
148
149 **Add devices to the created Application.**
150
151 [[image:image-20250306095639-3.jpeg]]
152
153
154
155 **Enter end device specifics manually.**
156
157 [[image:image-20250306095706-4.jpeg]]
158
159 [[image:image-20250306095754-5.jpeg]]
160
161
162 (% style="color:blue" %)**Step 2: **(%%)Add decoder
163
164 In TTN, user can add a custom payload so it shows friendly reading.
165
166 Click this link to get the decoder: [[PB05-L decoder>>https://github.com/dragino/dragino-end-node-decoder/tree/main/PB05]].
167
168 Below is TTN screen shot:
169
170 [[image:image-20241030172839-3.png||height="508" width="918"]]
171
172
173 (% style="color:blue" %)**Step 3:**(%%) Use ACT button to activate PB05-L 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.
174
175 [[image:image-20241030173150-5.png||height="304" width="1292"]]
176
177
178 == 2.4  Uplink Payload ==
179
180
181 Uplink payloads include two types: **Valid Sensor Valu**e and **Other Status / Control Commands**.
182
183 * **Valid Sensor Value**: Use FPort=2
184 * **Other Status / Control Commands**: Use an FPort other than 2.
185
186 === 2.4.1  Uplink FPORT~=5, Device Status ===
187
188
189 You can get the **Device Status** uplink through the downlink command:
190
191 (% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
192
193 The device uplinks the status using FPort=5.
194
195 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
196 |=(% 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**
197 |(% style="width:99px" %)Value|(% style="width:62px" %)Sensor Model|(% style="width:80px" %)Firmware Version|(% style="width:82px" %)Frequency Band|(% style="width:85px" %)Sub-band|(% style="width:46px" %)BAT
198
199 [[image:image-20241030165804-1.png]]
200
201 Example Payload (FPort=5):  [[image:image-20241030170029-2.png||height="24" width="136"]]
202
203 (% style="color:#4472c4" %)**Sensor Model**(%%): For PB05-L, this value is 0x3B.
204
205 (% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100 means v1.0.0 version.
206
207 (% style="color:#4472c4" %)**Frequency Band**:
208
209 * 0x01: EU868
210 * 0x02: US915
211 * 0x03: IN865
212 * 0x04: AU915
213 * 0x05: KZ865
214 * 0x06: RU864
215 * 0x07: AS923
216 * 0x08: AS923-1
217 * 0x09: AS923-2
218 * 0x0a: AS923-3
219
220 (% style="color:#4472c4" %)**Sub-Band**(%%): Value 0x00 ~~ 0x08 (only for CN470, AU915,US915. For others, it's 0x00)
221
222 (% style="color:#4472c4" %)**BAT**(%%): Shows the battery voltage for PB05-L.
223
224 (% style="color:#4472c4" %)**Example**(%%): 0x0C48 = 3144mV
225
226
227 === 2.4.2  Uplink FPORT~=2, Real time sensor value ===
228
229
230 PB05-L 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:470px" %)
235 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
236 **Size(bytes)**
237 )))|=(% style="width: 50px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 170px; background-color: rgb(79, 129, 189); color: white;" %)(((
238 **1**
239 )))|=(% style="width: 50px; background-color: rgb(79, 129, 189); color: white;" %)(((
240 **1**
241 )))|=(% style="width: 140px; background-color: rgb(79, 129, 189); color: white;" %)(((
242 **1**
243 )))
244 |(% style="width:97px" %)(((
245 Value
246 )))|(% style="width:63px" %)Battery|(% style="width:101px" %)(((
247 Sound_key & Sound_ACK
248 )))|(% style="width:62px" %)(((
249 (((
250 Alarm
251 )))
252 )))|(% style="width:140px" %)key1 & key2 & key3 & key4 & key5
253
254 (% style="color:blue" %)**key1 & key2 & key3 & key4 & key5:**
255
256 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:470px" %)
257 |=(% style="width: 81px; background-color: rgb(79, 129, 189); color: white;" %)**Size(bit)**|=(% style="width: 79px; background-color: rgb(79, 129, 189); color: white;" %)**bit[1:7]**|=(% style="width: 310px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
258 |(% style="width:81px" %)(((
259 Value
260 )))|(% style="width:79px" %)Reserve|(% style="width:294px" %)key1 & key2 & key3 & key4 & key5
261
262 Example in TTN.
263
264 [[image:image-20241031101215-3.png]]
265
266
267 * (((
268 (% class="wikigeneratedid" id="HBattery:" %)
269 (% style="color:blue" %)**Battery:**
270 )))
271
272 Check the battery voltage.
273
274 Ex1: 0x0CEA = 3306mV
275
276 Ex2: 0x0D08 = 3336mV
277
278
279 * (% style="color:blue" %)**Sound_key & Sound_ACK:**
280
281 Key sound and ACK sound are enabled by default.
282
283 Example 1: 0x03
284
285 Sound_ACK: (03>>1) & 0x01=1, OPEN.
286
287 **~ ** Sound_key:  03 & 0x01=1, OPEN.
288
289 Example 2: 0x01
290
291 Sound_ACK: (01>>1) & 0x01=0, CLOSE.
292
293 **~ ** Sound_key:  01 & 0x01=1, OPEN.
294
295
296 * (% style="color:blue" %)**Alarm:**
297
298 Key alarm.
299
300 Ex1: 0x01 & 0x01=1, "TRUE", key alarm packet.
301
302 Ex2: 0x00 & 0x01=0, "FALSE", normal uplink data.
303
304
305 * (% style="color:blue" %)**key1**
306
307 (% class="wikigeneratedid" %)
308 Displays whether the uplink data is triggered by key 1.
309
310 01 (H): (0x01&0x01)=01(H) =0000 000**1**(B)  bit0=1, "Yes"
311
312 02 (H): (0x02&0x01)=0  bit0=0, "No"
313
314
315 * (% style="color:blue" %)**key2**
316
317 (% class="wikigeneratedid" %)
318 Displays whether the uplink data is triggered by key 2.
319
320 02 (H): (0x02>>1)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
321
322 04 (H): (0x04>>1)&0x01 =0  bit0=0, "No"
323
324
325 * (% style="color:blue" %)**key3**
326
327 (% class="wikigeneratedid" %)
328 Displays whether the uplink data is triggered by key 3.
329
330 04 (H): (0x04>>2)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
331
332 08 (H): (0x08>>2)&0x01 =0  bit0=0, "No"
333
334
335 * (% style="color:blue" %)**key4**
336
337 (% class="wikigeneratedid" %)
338 Displays whether the uplink data is triggered by key 4.
339
340 08 (H): (0x08>>3)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
341
342 10 (H): (0x10>>3)&0x01 =0  bit0=0, "No"
343
344
345 * (% style="color:blue" %)**key5**
346
347 (% class="wikigeneratedid" %)
348 Displays whether the uplink data is triggered by key 5.
349
350 10 (H): (0x10>>4)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
351
352 01 (H): (0x01>>4)&0x01 =0  bit0=0, "No"
353
354
355 === 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
356
357
358 PB05-L stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
359
360 The historical payload includes one or multiplies entries.
361
362 (% border="1" cellspacing="2" style="background-color:#f2f2f2; width:510px" %)
363 |=(% style="width: 60px; background-color: rgb(79, 129, 189); color: white;" %)(((
364 **Size(bytes)**
365 )))|=(% style="width: 50px; background-color: rgb(79, 129, 189); color: white;" %)4|=(% style="width: 170px; background-color: rgb(79, 129, 189); color: white;" %)(((
366 **1**
367 )))|=(% style="width: 50px; background-color: rgb(79, 129, 189); color: white;" %)(((
368 **1**
369 )))|=(% style="width: 110px; background-color: rgb(79, 129, 189); color: white;" %)(((
370 **1**
371 )))|=(% style="width: 70px; background-color: rgb(79, 129, 189); color: white;" %)4
372 |(% style="width:87px" %)(((
373 Value
374 )))|(% style="width:78px" %)Reserve|(% style="width:102px" %)(((
375 key5 & key4 & key3 & key2 & key1
376 )))|(% style="width:75px" %)Reserve|(% style="width:55px" %)Poll message flag & alarm|(% style="width:68px" %)Unix Time Stamp
377
378 (% style="color:blue" %)**key5 & key4 & key3 & key2 & key1:**
379
380 (% border="1" cellspacing="2" style="background-color:#f2f2f2; width:470px" %)
381 |=(% style="width: 81px; background-color: rgb(79, 129, 189); color: white;" %)**Size(bit)**|=(% style="width: 79px; background-color: rgb(79, 129, 189); color: white;" %)**bit[1:7]**|=(% style="width: 310px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
382 |(% style="width:81px" %)(((
383 Value
384 )))|(% style="width:79px" %)Reserve|(% style="width:294px" %)key5 & key4 & key3 & key2 & key1
385
386 (% style="color:blue" %)**Poll message flag & Alarm:**
387
388 (% border="1" cellspacing="2" style="background-color:#f2f2f2; width:510px" %)
389 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bit)**|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)**bit**7|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)(((
390 **bit6**
391 )))|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)bit5|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)bit4|=(% style="width: 60px; background-color: rgb(79, 129, 189); color: white;" %)**bit[3:1]**|=(% style="width: 70px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
392 |(% style="width:97px" %)Status&Ext|(% style="width:63px" %)No ACK Message|(% style="width:101px" %)Poll Message Flag|(% style="width:140px" %)Sync time OK|(% style="width:140px" %)Unix Time Request|(% style="width:140px" %)Reserve|(% style="width:140px" %)(((
393 Alarm:1
394 )))
395
396 (% style="color:blue" %)**No ACK Message:**(%%) 1: This message means this payload is fromn Uplink Message which doesn't get ACK from the server before ( for [[PNACKMD=1>>url:https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/#H4.13AutoSendNone-ACKmessages]] feature)
397
398 (% style="color:blue" %)**Poll Message Flag: **(%%)1: This message is a poll message reply.
399
400
401 * Each data entry is 11 bytes, to save airtime and battery, PB05-L will send max bytes according to the current DR and Frequency bands.(% style="display:none" %)
402
403 For example, in US915 band, the max payload for different DR is:
404
405 1. **DR0**: max is 11 bytes so one entry of data
406 1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
407 1. **DR2**: total payload includes 11 entries of data
408 1. **DR3**: total payload includes 22 entries of data.
409
410 If user sends below downlink command:  [[image:image-20241031142131-3.png||height="31" width="216"]]
411
412 Where : Start time: 6722DD98 = time 24/10/31 Thursday 01:30:00
413
414 Stop time: 672300C0 = time 24/10/31 Thursday 04:00:00
415
416
417 PB05-L will uplink this payload:
418
419 [[image:image-20241031135901-2.png]]
420
421 **000000001000416722E531**
422
423 000000000800416722E538000000000400416722E540000000000200416722E54A000000000100416722E552000000000000406722E9BA000000000000406722EE6A000000000000406722F31A000000000000406722F7CA000000001000416722F9BA000000001000416722F9F6000000000800416722FB0E000000000000406722FC7A
424
425 Where the first 11 bytes is for the first entry:
426
427 [[image:image-20241031153803-1.png||height="35" width="240"]]
428
429 The first four bytes are reserved, meaningless.
430
431 key5 & key4 & key3 & key2 & key1: __10(H)__
432
433 * key5: ((0x10>>4)&0x01) = 1, "Yes".
434 * key4: ((0x10>>3)&0x01) = 0, "No".
435 * key3: ((0x10>>2)&0x01) = 0, "No".
436 * key2: ((0x10>>2)&0x01) = 0, "No".
437 * key1: (0x10 & 0x01) = 0, "No".
438
439 The sixth byte is reserved, meaningless.
440
441 poll message flag & Alarm: 41(H)  means reply data, For Alarm: 0x41&0x01 =1, "True".
442
443 Unix time is 0x6722E531= 1730340145s= 24/10/31 02:02:25
444
445
446 If PB05-L doesn't have any data in the polling time, it will uplink 11 bytes of 0:
447
448 [[image:image-20241031113339-4.png||height="307" width="1112"]](% style="display:none" %)
449
450 See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
451
452 (% style="display:none" %) (%%)
453
454 == 2.5 Show data on Datacake ==
455
456
457 (((
458 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:
459 )))
460
461 (((
462
463 )))
464
465 (((
466 (% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
467 )))
468
469 (((
470 (% 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.
471 )))
472
473 (((
474 ~1. Add Datacake:
475 )))
476
477 (((
478 2. Select default key as Access Key:
479 )))
480
481 (((
482 3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB05-L:
483 )))
484
485 (((
486 Please refer to the figure below.
487 )))
488
489 [[image:image-20240510150924-2.png||height="500" width="970"]]
490
491 Log in to DATACAKE, copy the API under the account.
492
493 [[image:image-20240510151944-3.png||height="482" width="989"]]
494
495
496 [[image:image-20241031114021-5.png||height="526" width="896"]]
497
498
499 [[image:image-20240510152300-5.png||height="249" width="995"]]
500
501
502 [[image:image-20240510152355-6.png||height="459" width="701"]]
503
504 [[image:image-20241031114330-6.png||height="462" width="626"]]
505
506 [[image:image-20240510152634-9.png||height="609" width="602"]]
507
508
509 [[image:image-20241031114443-7.png||height="498" width="601"]]
510
511 [[image:image-20241031114600-8.png||height="295" width="826"]]
512
513
514 Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder/tree/main/PB05]] here and save.
515
516 [[image:image-20240510153624-13.png||height="286" width="731"]]
517
518 Visual widgets please read the DATACAKE documentation.
519
520 (% style="display:none" %) (%%)
521
522 == 2.6  Datalog Feature ==
523
524
525 (% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
526 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.
527
528
529 === 2.6.1  Unix TimeStamp ===
530
531
532 Unix TimeStamp shows the sampling time of uplink payload. format base on
533
534 [[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
535
536 User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
537
538 For example: if the Unix Timestamp we got is hex 0x6722DD98, we can convert it to Decimal: 1730338200. and then convert to the time: 2024/10/31 Thursday 01:30:00 (GMT).
539
540 [[image:1655782409139-256.png]]
541
542
543 === 2.6.2 Set Device Time ===
544
545
546 (((
547 (% style="color:blue" %)**There are two ways to set device's time:**
548 )))
549
550 (((
551 **1.  Through LoRaWAN MAC Command (Default settings)**
552 )))
553
554 (((
555 User need to set **AT+SYNCMOD=1** to enable sync time via MAC command.
556 )))
557
558 (((
559 Once PB05-L Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to PB05-L. If PB05-L fails to get the
560
561 time from the server, PB05-L will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
562 )))
563
564 (((
565 (% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
566 )))
567
568 (((
569 **2. Manually Set Time**
570 )))
571
572 (((
573 User needs to set **AT+SYNCMOD=0** to manual time, otherwise, the user set time will be overwritten by the time set by the server.
574 )))
575
576
577 === 2.6.3 Poll sensor value ===
578
579
580 User can poll sensor value based on timestamps from the server.
581
582 Below is the downlink command.
583
584 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:428px" %)
585 |(% style="background-color:#4f81bd; color:white; width:59px" %)**1byte**|(% style="background-color:#4f81bd; color:white; width:128px" %)**4bytes**|(% style="background-color:#4f81bd; color:white; width:124px" %)**4bytes**|(% style="background-color:#4f81bd; color:white; width:117px" %)**1byte**
586 |(% style="width:58px" %)31|(% style="width:128px" %)Timestamp start|(% style="width:123px" %)Timestamp end|(% style="width:116px" %)Uplink Interval
587
588 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.
589
590 For example, downlink command [[image:image-20241031142131-3.png||height="31" width="216"]]
591
592 Is to check 2024/10/31 01:30:00 to 2020/12/1 04:00:00's data
593
594 Uplink Internal =5s, means PB05-L will send one packet every 5s. range 5~~255s.
595
596
597 === 2.6.4  Datalog Uplink payload ===
598
599
600 See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
601
602 (% style="display:none" %) (%%) (% style="display:none" %)
603
604 == 2.7 Buttons ==
605
606
607 * **ACT button**
608
609 Long press the ACT button to reset the device and allow it to join network again.
610
611 [[image:image-20250303110613-4.jpeg||height="198" width="472"]]
612
613 * **Alarm buttons**
614
615 When you press an alarm button, the PB05-L immediately uplinks data. The alarm flag is set to 'TRUE,' and the corresponding button status is 'Yes'.
616
617 [[image:image-20250303111505-5.jpeg||height="252" width="374"]](% style="display:none" %)
618
619
620 == 2.8 LED Indicators ==
621
622
623 (((
624 The** PB05-L** has a **tri-color LED** for easily indicating different stages.
625
626 Hold the **ACT** button until the green light turns on to reset the device. The green LED will flash as the node restarts, the blue LED will flash once when requesting network access, and the green LED will remain on for 5 seconds after successful network access.
627 )))
628
629 (((
630 **In a normal working state:**
631
632 * When the node restarts, hold the ACT button until the GREEN LED lights up. The GREEN LED will flash as the node restarts.
633 * The BLUE LED will flash once upon requesting network access.
634 * The GREEN LED will remain on for 5 seconds after successful network access.
635
636 **During OTAA Join:**
637
638 * For each Join Request uplink, the GREEN LED will blink once.
639 * Once the Join is successful, the GREEN LED will remain on for 5 seconds.
640 * After joining, for each uplink, either the BLUE or GREEN LED will blink once.
641
642 **Alarm Button Press:**
643
644 * When an alarm button is pressed, the RED LED will flash until the node receives an ACK from the platform.
645 * Once the ACK is received, the BLUE LED will stay on for 5 seconds.
646
647
648 )))
649
650 == 2.9 Buzzer ==
651
652
653 The PB05 has a **button sound** and an **ACK sound**, both of which users can turn on or off using [[AT+SOUND>>||anchor="H3.3A0SetbuttonsoundandACKsound"]].
654
655 * (% style="color:#4f81bd" %)**Button sound**(%%) is the tone played by the node after an alarm button is pressed.
656 You can use [[AT+OPTION>>||anchor="H3.4A0Setbuzzermusictype2807E429"]] to set different button sounds.
657 * (% style="color:#4f81bd" %)**ACK sound**(%%) is the notification tone played when the node receives an ACK.
658
659
660 == 2.10 E2 Extension Cable ==
661
662
663 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220619092222-1.png?width=188&height=182&rev=1.1||alt="image-20220619092222-1.png"]][[image:image-20250303135532-3.jpeg||height="184" width="234"]]
664
665
666 **1m Long Breakout Cable for PB05-L**
667
668 **Features:**
669
670 * Used for AT commands; compatible with LHT52, LHT65N, and PB05-L.
671 * Supports firmware updates for PB05-L; also works with LHT52 and LHT65N.
672 * Exposes all pins from the PB05-L Type-C connector.
673
674
675 The following diagram shows the pin mapping between PB05 and the E2 Cable.
676
677 [[image:image-20250303134914-1.png||height="320" width="456"]]
678
679
680 = 3.  Configure PB05-L via AT command or LoRaWAN downlink =
681
682
683 You can configure PB05-L via AT Command or LoRaWAN Downlink command.
684
685 * **AT Command Connection: **
686
687 [[image:image-20250303141745-4.jpeg||height="489" width="505"]]
688
689
690 (((
691 On a PC, you need to set the serial tool (such as [[PuTTY>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or SecureCRT) to a baud rate of **9600** to access the serial console for the PB05-L.
692
693 AT commands are disabled by default and require entering a password (default: **123456**) to activate them. The AT command input timeout is 5 minutes; after this period, the user must enter the password again.
694
695 Enter the password and ATZ to activate the PB05-L, as shown below:
696
697
698 [[image:image-20250303114409-8.png]]
699
700
701 )))
702
703 * LoRaWAN Downlink instruction for different platforms can be found here: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
704
705
706 (((
707 There are two types of commands to configure the PB05-L:
708
709 **General Commands**
710
711 These commands configure:
712
713 * General system settings, such as the uplink interval.
714 * LoRaWAN protocol and radio-related settings.
715
716 These commands are the same for all Dragino devices that support the DLWS-005 LoRaWAN stack (**Note~*~***). They can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]].
717
718 **Commands Specifically Designed for PB05-L**
719
720 These commands are only valid for the PB05-L, as listed below:
721
722
723 )))
724
725 == 3.1  Downlink Command Set ==
726
727
728 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
729 |=(% style="width: 100px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 161px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 92px; background-color: rgb(79, 129, 189); color: white;" %)**Response**|=(% style="width: 157px; background-color: rgb(79, 129, 189); color: white;" %)**Downlink**
730 |(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
731
732
733 View current TDC time
734 )))|(% style="width:92px" %)(((
735 1200000
736 OK
737 )))|(% style="width:206px" %)Default 1200000(ms)
738 |(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
739 (((
740 0X0100012C:
741 01: fixed command
742 00012C: 0X00012C=
743
744 300(seconds)
745 )))
746
747 (((
748
749 )))
750 )))
751 |(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
752 |(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
753 |(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
754 0,7,0
755 OK
756 )))|(% style="width:206px" %)Default 0,7,0
757 |(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
758 Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry
759 )))|(% style="width:92px" %)(((
760 OK
761 )))|(% style="width:206px" %)(((
762 05010701
763 05: fixed command
764 01:confirmed uplink
765 07: retry 7 times
766 01: fcnt count plus 1
767 )))
768 |(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
769 Check the current network connection method
770 )))|(% style="width:92px" %)(((
771 1
772 OK
773 )))|(% style="width:206px" %)Default 1
774 |(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((
775 Attention:Take effect after ATZ
776 OK
777 )))|(% style="width:206px" %)(((
778 0X2000: ABP
779 0x2001: OTAA
780 20: fixed command
781 )))
782 |(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
783 0
784 OK
785 )))|(% style="width:206px" %)Default 0
786 |(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
787 0x2101:
788 21: fixed command
789 01: for details, check wiki
790 )))
791 |(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
792 1
793 OK
794 )))|(% style="width:206px" %)Default 0
795 |(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
796 0x2200: close
797 0x2201: open
798 22: fixed command
799 )))
800 |(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
801 |(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
802 set DR to 1
803 It takes effect only when ADR=0
804 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
805 0X22000101:
806 00: ADR=0
807 01: DR=1
808 01: TXP=1
809 22: fixed command
810 )))
811 |(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
812 |(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
813 set TXP to 1
814 It takes effect only when ADR=0
815 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
816 0X22000101:
817 00: ADR=0
818 01: DR=1
819 01: TXP=1
820 22: fixed command
821 )))
822 |(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
823 0X26000A:
824 26: fixed command
825 000A: 0X000A=10(min)
826 for details, check wiki
827 )))
828 |(% style="width:130px" %) |(% style="width:151px" %)(((
829 (((
830 ~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
831
832 Retrieve stored data for a specified period of time
833 )))
834
835 (((
836
837 )))
838 )))|(% style="width:92px" %) |(% style="width:206px" %)(((
839 0X3161DE7C7061DE8A800A:
840 31: fixed command
841 61DE7C70:0X61DE7C70=2022/1/12 15:00:00
842 61DE8A80:0X61DE8A80=2022/1/12 16:00:00
843 0A: 0X0A=10(second)
844 View details 2.6.2
845 )))
846 |(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
847 1,1440,2880
848 OK
849 )))|(% style="width:206px" %)Default 1,1440,2880(min)
850 |(% style="width:130px" %)AT+DDETECT=(((
851 1,1440,2880
852 )))|(% style="width:151px" %)(((
853 Set DDETECT setting status and time
854 ((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
855 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
856 0X320005A0: close
857 0X320105A0: open
858 32: fixed command
859 05A0: 0X05A0=1440(min)
860 )))
861
862 == 3.2  Set Password ==
863
864
865 Feature: Set device password, max 9 digits.
866
867 (% style="color:#4f81bd" %)**AT Command: AT+PWORD**
868
869 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
870 |(% 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**
871 |(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
872 123456
873 OK
874 )))
875 |(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
876
877 (% style="color:#4f81bd" %)**Downlink Command:**
878
879 No downlink command for this feature.
880
881
882 == 3.3  Set button sound and ACK sound ==
883
884
885 Feature: Turn on/off button sound and ACK alarm.
886
887 (% style="color:#4f81bd" %)**AT Command: AT+SOUND**
888
889 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
890 |(% 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**
891 |(% style="width:155px" %)(((
892 AT+SOUND=?
893 )))|(% style="width:124px" %)Get the current status of button sound and ACK sound|(% style="width:86px" %)(((
894 1,1
895 OK
896 )))
897 |(% style="width:155px" %)(((
898 AT+SOUND=0,1
899 )))|(% style="width:124px" %)Turn off the button sound and turn on ACK sound|(% style="width:86px" %)OK
900
901 (% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
902
903 Format: Command Code (0xA1) followed by 2 bytes mode value.
904
905 The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
906
907 * **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
908
909 == 3.4  Set buzzer music type(0~~4) ==
910
911
912 Feature: Set different alarm key response sounds.There are five different types of button music.
913
914 (% style="color:#4f81bd" %)**AT Command: AT+OPTION**
915
916 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
917 |(% 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**
918 |(% style="width:155px" %)(((
919 AT+OPTION=?
920 )))|(% style="width:124px" %)(((
921 Get the buzzer music type
922 )))|(% style="width:86px" %)(((
923 3
924
925 OK
926 )))
927 |(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
928
929 (% style="color:#4f81bd" %)**Downlink Command: 0xA3**
930
931 Format: Command Code (0xA3) followed by 1 byte mode value.
932
933 * **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
934
935 == 3.5  Set Valid Push Time ==
936
937
938 Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
939
940 (% style="color:#4f81bd" %)**AT Command: AT+STIME**
941
942 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
943 |(% 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**
944 |(% style="width:155px" %)(((
945 AT+STIME=?
946 )))|(% style="width:124px" %)(((
947 Get the button sound time
948 )))|(% style="width:86px" %)(((
949 0
950 OK
951 )))
952 |(% style="width:155px" %)(((
953 AT+STIME=1000
954 )))|(% style="width:124px" %)Set the button sound time to 1000**ms**|(% style="width:86px" %)OK
955
956 (% style="color:#4f81bd" %)**Downlink Command: 0xA2**
957
958 Format: Command Code (0xA2) followed by 2 bytes mode value.
959
960 * **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
961
962 **~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
963
964
965 = 4.  Battery & How to replace =
966
967 == 4.1  Battery Type and replace ==
968
969
970 PB05-L uses 2 x AA LR6(1.5v) batteries. If the batteries running low (shows 2.1v in the platform). Users can buy generic AA battery and replace it.
971
972 (% style="color:red" %)**Note: **
973
974 1.  The PB05-L doesn't have any screw, users can use nail to open it by the middle.
975
976 [[image:image-20250303112351-7.png||height="234" width="494"]]
977
978
979 2.  Make sure the direction is correct when install the AA batteries.
980
981 [[image:image-20250303105439-2.jpeg||height="241" width="489"]]
982
983
984 == 4.2  Power Consumption Analyze ==
985
986
987 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.
988
989 Instruction to use as below:
990
991 (% style="color:blue" %)**Step 1**(%%):  Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
992
993 [[battery calculator>>https://www.dropbox.com/sh/sxrgszkac4ips0q/AAA4XjBI3HAHNpdbU3ALN1j0a/Battery%20Document/Battery_Analyze?dl=0&subfolder_nav_tracking=1]]
994
995
996 (% style="color:blue" %)**Step 2**(%%):  (% style="display:none" %) (%%)Open it and choose
997
998 * Product Model
999 * Uplink Interval
1000 * Working Mode
1001
1002 And the Life expectation in difference case will be shown on the right.
1003
1004 [[image:image-20220621143643-7.png||height="429" width="1326"]]
1005
1006
1007
1008 = 5. OTA Firmware update =
1009
1010 **User can change firmware PB05-L to:**
1011
1012 * Change Frequency band/ region.
1013 * Update with new features.
1014 * Fix bugs.
1015
1016 **Firmware and changelog can be downloaded from :** **[[Firmware download link>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/ACMiK0Y0E5C2ZEcSKxgvmeE/LoRaWAN%20End%20Node/PB05/Firmware?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]]**
1017
1018 **Methods to Update Firmware:**
1019
1020 * (Recommanded way) OTA firmware update via wireless: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]**
1021 * Update through UART TTL interface: **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**.
1022
1023 = 6. Use Cases =
1024
1025 == 6.1 Public Transport Satisfaction ==
1026
1027 Public transport satisfaction terminals, placed inside buses, trams, or train stations, allow passengers to quickly rate aspects like cleanliness, punctuality, or overall experience after a ride, providing cities and transport operators with valuable real-time feedback, even from locations with poor cellular or WiFi coverage. This helps to improve service quality and passenger satisfaction.
1028
1029
1030 == 6.2 Event or Conference Feedback ==
1031
1032 Event or conference feedback terminals, strategically placed at session exits, information booths, or entrance gates, enable attendees to rate specific talks, exhibitors, or their overall event experience on the spot. This setup provides organizers with detailed, location-specific feedback in real time, without relying on constant internet connectivity, allowing them to assess and improve various aspects of the event efficiently.
1033
1034
1035 == 6.3 Retail Stores or Service Desks ==
1036
1037 Placed at cashier counters or near store exits, these devices allow customers to quickly rate staff behavior, checkout experience, and store cleanliness. The feedback is captured in real time, giving store managers valuable, honest insights to help improve service quality and enhance the overall shopping experience.
1038
1039
1040 = 7. FAQ =
1041
1042
1043 == 7.1 How to design customized sticker? ==
1044
1045
1046 PB05-L is shipped with a default PVC stick with satisfied icons. This sticker is not attached to the design for easy customizerd purpose. User can design customized PVC sticker and change the panel design.
1047
1048 Below is the [[link>>https://www.dropbox.com/scl/fo/4i7ezfiwdxqvnmo5d30pe/AO8KACW7i6tRiNC22ZLR_RU?rlkey=9z9bdlix0hal7dmy9lztgmrel&st=9su98u3a&dl=0]] for the design template.
1049
1050
1051 = 8. Order Info =
1052
1053
1054 Part Number: (% style="color:#4472c4" %)**PB05-L-XX**
1055
1056 (% style="color:#4472c4" %)**XX **(%%): The default frequency band
1057
1058 * (% style="color:red" %)**AS923**(%%)**: **LoRaWAN AS923 band
1059 * (% style="color:red" %)**AU915**(%%)**: **LoRaWAN AU915 band
1060 * (% style="color:red" %)**EU433**(%%)**: **LoRaWAN EU433 band
1061 * (% style="color:red" %)**EU868**(%%)**:** LoRaWAN EU868 band
1062 * (% style="color:red" %)**KR920**(%%)**: **LoRaWAN KR920 band
1063 * (% style="color:red" %)**US915**(%%)**: **LoRaWAN US915 band
1064 * (% style="color:red" %)**IN865**(%%)**:  **LoRaWAN IN865 band
1065 * (% style="color:red" %)**CN470**(%%)**: **LoRaWAN CN470 band
1066
1067 = 9. Packing Info =
1068
1069
1070 (% style="color:#4472c4" %)**Package Includes:**
1071
1072 * PB05-L LoRaWAN Push Buttons x 1
1073
1074 (% style="color:#4472c4" %)**Dimension and weight:**
1075
1076 * Device Size: cm
1077 * Device Weight: g
1078 * Package Size / pcs : cm
1079 * Weight / pcs : g
1080
1081 = 10. Support =
1082
1083
1084 * 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.
1085 * 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]].

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0