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