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