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