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