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