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