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