Version 344.1 by Mengting Qiu on 2025/03/03 10:59

Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20250228144849-1.jpeg||height="490" width="490"]]
3
4
5
6
7 (% _mstvisible="1" %)
8 (% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
9
10 {{toc/}}
11
12
13
14
15
16
17
18
19 = 1.  Introduction =
20
21 == 1.1  What is PB05 LoRaWAN Push Button ==
22
23
24 PB05 LoRaWAN Button is a LoRaWAN wireless device with (% style="color:blue" %)**5 push buttons**(%%). Once the user presses the button, the PB05 will transmit the signal to the IoT server via remote LoRaWAN wireless protocol.
25
26 PB05 supports (% style="color:blue" %)** 2 x AA batteries**(%%) and works for a long time up to several years*. User can replace the batteries easily after they are finished.
27
28 PB05 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 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 : Idle: 5uA, Transmit: max 110mA
53
54
55 == 1.4  Storage & Operation Temperature ==
56
57
58 -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on battery type, see [[FAQ>>||anchor="H6.5Whyiseedifferentworkingtemperatureforthedevice3F"]])
59
60
61 == 1.5  Applications ==
62
63
64 * Smart Buildings & Home Automation
65 * Logistics and Supply Chain Management
66 * Smart Metering
67 * Smart Agriculture
68 * Smart Cities
69 * Smart Factory
70
71 == 1.6 Device Apperance ==
72
73
74 (% class="wikigeneratedid" %)
75 [[image:image-20250303102218-1.jpeg||height="340" width="572"]]
76
77 (% class="wikigeneratedid" %)
78 (% style="color:red" %)**Note: For customized purpose, the PVC sticker is not attached by default.**
79
80
81 = 2.  Operation Mode =
82
83 == 2.1  How it work? ==
84
85
86 Each PB05 is shipped with a worldwide unique set of LoRaWAN OTAA keys. To use PB05 in a LoRaWAN network, user needs to input the OTAA keys in LoRaWAN network server. After this, if PB05 is under this LoRaWAN network coverage, PB05 can join the LoRaWAN network and start to transmit sensor data. The default period for each uplink is** 20 minutes**.
87
88
89 == 2.2  How to Activate PB05? ==
90
91
92 (% style="color:red" %)** 1.  Open enclosure from below position.**
93
94
95 (% style="color:red" %)** 2.  Insert 2 x AA LR6 batteries and the node is activated.**
96
97
98
99 (% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
100
101
102 User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB05.
103
104
105 == 2.3  Example to join LoRaWAN network ==
106
107
108 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.
109
110 (% _mstvisible="1" class="wikigeneratedid" %)
111 Assume the LPS8v2 is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. We need to add the PB05 device in TTN V3 portal. 
112
113 [[image:image-20250228145402-3.png]]
114
115 (% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB05.
116
117 Each PB05 is shipped with a sticker with the default DEV EUI as below:
118
119 [[image:image-20230426083617-1.png||height="294" width="633"]]
120
121
122 Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
123
124
125 **Create the application.**
126
127 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111048-1.png?width=1001&height=183&rev=1.1||alt="image-20240907111048-1.png"]]
128
129 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111305-2.png?width=1000&height=572&rev=1.1||alt="image-20240907111305-2.png"]]
130
131
132 **Add devices to the created Application.**
133
134 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111820-5.png?width=975&height=377&rev=1.1||alt="image-20240907111820-5.png"]]
135
136
137 **Enter end device specifics manually.**
138
139 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112136-6.png?width=697&height=687&rev=1.1||alt="image-20240907112136-6.png" height="673" width="683"]]
140
141 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112427-7.png?rev=1.1||alt="image-20240907112427-7.png"]]
142
143
144 (% style="color:blue" %)**Step 2: **(%%)Add decoder
145
146 In TTN, user can add a custom payload so it shows friendly reading.
147
148 Click this link to get the decoder: [[PB05 decoder>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/LWL04-LB]].
149
150 Below is TTN screen shot:
151
152 [[image:image-20241030172839-3.png||height="508" width="918"]]
153
154
155 (% style="color:blue" %)**Step 3:**(%%) Use ACT button to activate PB05 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.
156
157 [[image:image-20241030173150-5.png||height="304" width="1292"]]
158
159
160
161 == 2.4  Uplink Payload ==
162
163
164 Uplink payloads include two types: Valid Sensor Value and other status / control command.
165
166 * Valid Sensor Value: Use FPORT=2
167 * Other control command: Use FPORT other than 2.
168
169 === 2.4.1  Uplink FPORT~=5, Device Status ===
170
171
172 Users can  get the Device Status uplink through the downlink command:
173
174 (% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
175
176 Uplink the device configures with FPORT=5. ,
177
178 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
179 |=(% 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**
180 |(% 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
181
182 [[image:image-20241030165804-1.png]]
183
184 Example Payload (FPort=5):  [[image:image-20241030170029-2.png||height="24" width="136"]]
185
186 (% style="color:#4472c4" %)**Sensor Model**(%%): For PB05, this value is 0x3B.
187
188 (% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
189
190 (% style="color:#4472c4" %)**Frequency Band**:
191
192 *0x01: EU868
193
194 *0x02: US915
195
196 *0x03: IN865
197
198 *0x04: AU915
199
200 *0x05: KZ865
201
202 *0x06: RU864
203
204 *0x07: AS923
205
206 *0x08: AS923-1
207
208 *0x09: AS923-2
209
210 *0x0a: AS923-3
211
212
213 (% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
214
215 (% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB05.
216
217 (% style="color:#4472c4" %)**Ex1**(%%): 0x0C48 = 3144mV
218
219
220 === 2.4.2  Uplink FPORT~=2, Real time sensor value ===
221
222
223 PB05 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"]].
224
225 Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
226
227 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:470px" %)
228 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
229 **Size(bytes)**
230 )))|=(% style="width: 63px; background-color: rgb(79, 129, 189); color: white;" %)2|=(% style="width: 101px; background-color: rgb(79, 129, 189); color: white;" %)(((
231 **1**
232 )))|=(% style="width: 62px; background-color: rgb(79, 129, 189); color: white;" %)(((
233 **1**
234 )))|=(% style="width: 140px; background-color: rgb(79, 129, 189); color: white;" %)(((
235 **1**
236 )))
237 |(% style="width:97px" %)(((
238 Value
239 )))|(% style="width:63px" %)Battery|(% style="width:101px" %)(((
240 Sound_key
241
242 & Sound_ACK
243 )))|(% style="width:62px" %)(((
244 (((
245 Alarm
246 )))
247 )))|(% style="width:140px" %)key1 & key2 & key3 & key4 & key5
248
249 (% style="color:blue" %)**key1 & key2 & key3 & key4 & key5:**
250
251 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:470px" %)
252 |=(% 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: 294px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
253 |(% style="width:81px" %)(((
254 Value
255 )))|(% style="width:79px" %)Reserve|(% style="width:294px" %)key1 & key2 & key3 & key4 & key5
256
257 Example in TTN.
258
259 [[image:image-20241031101215-3.png]]
260
261
262 * (((
263 (% class="wikigeneratedid" id="HBattery:" %)
264 (% style="color:blue" %)**Battery:**
265 )))
266
267 Check the battery voltage.
268
269 Ex1: 0x0CEA = 3306mV
270
271 Ex2: 0x0D08 = 3336mV
272
273
274 * (% style="color:blue" %)**Sound_key & Sound_ACK:**
275
276 Key sound and ACK sound are enabled by default.
277
278 Example 1: 0x03
279
280 Sound_ACK: (03>>1) & 0x01=1, OPEN.
281
282 **~ ** Sound_key:  03 & 0x01=1, OPEN.
283
284 Example 2: 0x01
285
286 Sound_ACK: (01>>1) & 0x01=0, CLOSE.
287
288 **~ ** Sound_key:  01 & 0x01=1, OPEN.
289
290
291 * (% style="color:blue" %)**Alarm:**
292
293 Key alarm.
294
295 Ex1: 0x01 & 0x01=1, "TRUE", key alarm packet.
296
297 Ex2: 0x00 & 0x01=0, "FALSE", normal uplink data.
298
299
300 * (% style="color:blue" %)**key1**
301
302 (% class="wikigeneratedid" %)
303 Displays whether the uplink data is triggered by key 1.
304
305 01 (H): (0x01&0x01)=01(H) =0000 000**1**(B)  bit0=1, "Yes"
306
307 02 (H): (0x02&0x01)=0  bit0=0, "No"
308
309
310 * (% style="color:blue" %)**key2**
311
312 (% class="wikigeneratedid" %)
313 Displays whether the uplink data is triggered by key 2.
314
315 02 (H): (0x02>>1)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
316
317 04 (H): (0x04>>1)&0x01 =0  bit0=0, "No"
318
319
320 * (% style="color:blue" %)**key3**
321
322 (% class="wikigeneratedid" %)
323 Displays whether the uplink data is triggered by key 3.
324
325 04 (H): (0x04>>2)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
326
327 08 (H): (0x08>>2)&0x01 =0  bit0=0, "No"
328
329
330 * (% style="color:blue" %)**key4**
331
332 (% class="wikigeneratedid" %)
333 Displays whether the uplink data is triggered by key 4.
334
335 08 (H): (0x08>>3)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
336
337 10 (H): (0x10>>3)&0x01 =0  bit0=0, "No"
338
339
340 * (% style="color:blue" %)**key5**
341
342 (% class="wikigeneratedid" %)
343 Displays whether the uplink data is triggered by key 5.
344
345 10 (H): (0x10>>4)&0x01 =01(H) =0000 000**1**(B)  bit0=1, "Yes"
346
347 01 (H): (0x01>>4)&0x01 =0  bit0=0, "No"
348
349
350 === 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
351
352
353 PB05 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
354
355 The historical payload includes one or multiplies entries.
356
357 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:470px" %)
358 |=(% style="width: 87px; background-color: rgb(79, 129, 189); color: white;" %)(((
359 **Size(bytes)**
360 )))|=(% style="width: 78px; background-color: rgb(79, 129, 189); color: white;" %)4|=(% style="width: 102px; background-color: rgb(79, 129, 189); color: white;" %)(((
361 **1**
362 )))|=(% style="width: 75px; background-color: rgb(79, 129, 189); color: white;" %)(((
363 **1**
364 )))|=(% style="width: 55px; background-color: rgb(79, 129, 189); color: white;" %)(((
365 **1**
366 )))|=(% style="width: 68px; background-color: rgb(79, 129, 189); color: white;" %)4
367 |(% style="width:87px" %)(((
368 Value
369 )))|(% style="width:78px" %)Reserve|(% style="width:102px" %)(((
370 key5 & key4 & key3 & key2 & key1
371 )))|(% style="width:75px" %)Reserve|(% style="width:55px" %)Poll message flag & alarm|(% style="width:68px" %)Unix Time Stamp
372
373 (% style="color:blue" %)**key5 & key4 & key3 & key2 & key1:**
374
375 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:470px" %)
376 |=(% 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: 294px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
377 |(% style="width:81px" %)(((
378 Value
379 )))|(% style="width:79px" %)Reserve|(% style="width:294px" %)key5 & key4 & key3 & key2 & key1
380
381 (% style="color:blue" %)**Poll message flag & Alarm:**
382
383 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:470px" %)
384 |=(% style="width: 60px;background-color:#4F81BD;color:white" %)**Size(bit)**|=(% style="width: 63px; background-color: rgb(79, 129, 189); color: white;" %)**bit**7|=(% style="width: 101px; background-color: rgb(79, 129, 189); color: white;" %)(((
385 **bit6**
386 )))|=(% style="width: 140px; background-color: rgb(79, 129, 189); color: white;" %)bit5|=(% style="width: 140px; background-color: rgb(79, 129, 189); color: white;" %)bit4|=(% style="width: 140px; background-color: rgb(79, 129, 189); color: white;" %)**bit[3:1]**|=(% style="width: 140px; background-color: rgb(79, 129, 189); color: white;" %)**bit0**
387 |(% 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" %)(((
388 Alarm:
389
390 1
391 )))
392
393 (% 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)
394
395 (% style="color:blue" %)**Poll Message Flag: **(%%)1: This message is a poll message reply.
396
397
398 * Each data entry is 11 bytes, to save airtime and battery, PB05 will send max bytes according to the current DR and Frequency bands.(% style="display:none" %)
399
400 For example, in US915 band, the max payload for different DR is:
401
402 1. **DR0**: max is 11 bytes so one entry of data
403 1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
404 1. **DR2**: total payload includes 11 entries of data
405 1. **DR3**: total payload includes 22 entries of data.
406
407 If user sends below downlink command:  [[image:image-20241031142131-3.png||height="31" width="216"]]
408
409 Where : Start time: 6722DD98 = time 24/10/31 Thursday 01:30:00
410
411 Stop time: 672300C0 = time 24/10/31 Thursday 04:00:00
412
413
414 PB05 will uplink this payload:
415
416 [[image:image-20241031135901-2.png]]
417
418 **000000001000416722E531**
419
420 000000000800416722E538000000000400416722E540000000000200416722E54A000000000100416722E552000000000000406722E9BA000000000000406722EE6A000000000000406722F31A000000000000406722F7CA000000001000416722F9BA000000001000416722F9F6000000000800416722FB0E000000000000406722FC7A
421
422 Where the first 11 bytes is for the first entry:
423
424 [[image:image-20241031153803-1.png||height="35" width="240"]]
425
426 The first four bytes are reserved, meaningless.
427
428 key5 & key4 & key3 & key2 & key1: __10(H)__
429
430 * key5: ((0x10>>4)&0x01) = 1, "Yes".
431 * key4: ((0x10>>3)&0x01) = 0, "No".
432 * key3: ((0x10>>2)&0x01) = 0, "No".
433 * key2: ((0x10>>2)&0x01) = 0, "No".
434 * key1: (0x10 & 0x01) = 0, "No".
435
436 The sixth byte is reserved, meaningless.
437
438 poll message flag & Alarm: 41(H)  means reply data, For Alarm: 0x41&0x01 =1, "True".
439
440 Unix time is 0x6722E531= 1730340145s= 24/10/31 02:02:25
441
442
443 If PB05 doesn't have any data in the polling time, it will uplink 11 bytes of 0:
444
445 [[image:image-20241031113339-4.png||height="307" width="1112"]](% style="display:none" %)
446
447 See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
448
449 (% style="display:none" %) (%%)
450
451 == 2.5 Show data on Datacake ==
452
453
454 (((
455 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:
456 )))
457
458 (((
459
460 )))
461
462 (((
463 (% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
464 )))
465
466 (((
467 (% 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.
468 )))
469
470 (((
471 ~1. Add Datacake:
472 )))
473
474 (((
475 2. Select default key as Access Key:
476 )))
477
478 (((
479 3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB05:
480 )))
481
482 (((
483 Please refer to the figure below.
484 )))
485
486 [[image:image-20240510150924-2.png||height="584" width="1132"]]
487
488 Log in to DATACAKE, copy the API under the account.
489
490 [[image:image-20240510151944-3.png||height="527" width="1081"]]
491
492
493 [[image:image-20241031114021-5.png||height="571" width="973"]]
494
495
496 [[image:image-20240510152300-5.png||height="276" width="1103"]]
497
498
499 [[image:image-20240510152355-6.png||height="563" width="859"]]
500
501 [[image:image-20241031114330-6.png]]
502
503 [[image:image-20240510152634-9.png||height="722" width="714"]]
504
505
506 [[image:image-20241031114443-7.png||height="557" width="672"]]
507
508 [[image:image-20241031114600-8.png]]
509
510
511 Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
512
513 [[image:image-20240510153624-13.png||height="468" width="1195"]]
514
515 Visual widgets please read the DATACAKE documentation.
516
517 (% style="display:none" %) (%%)
518
519 == 2.6  Datalog Feature ==
520
521
522 (% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
523 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.
524
525
526 === 2.6.1  Unix TimeStamp ===
527
528
529 Unix TimeStamp shows the sampling time of uplink payload. format base on
530
531 [[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
532
533 User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
534
535 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).
536
537 [[image:1655782409139-256.png]]
538
539
540 === 2.6.2 Set Device Time ===
541
542
543 (((
544 (% style="color:blue" %)**There are two ways to set device's time:**
545 )))
546
547 (((
548 **1.  Through LoRaWAN MAC Command (Default settings)**
549 )))
550
551 (((
552 User need to set **AT+SYNCMOD=1** to enable sync time via MAC command.
553 )))
554
555 (((
556 Once PB05 Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to PB05. If PB05 fails to get the time from the server, PB05 will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
557 )))
558
559 (((
560 (% 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.**
561 )))
562
563 (((
564 **2. Manually Set Time**
565 )))
566
567 (((
568 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.
569 )))
570
571
572 === 2.6.3 Poll sensor value ===
573
574
575 User can poll sensor value based on timestamps from the server.
576
577 Below is the downlink command.
578
579 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:428px" %)
580 |(% 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**
581 |(% style="width:58px" %)31|(% style="width:128px" %)Timestamp start|(% style="width:123px" %)Timestamp end|(% style="width:116px" %)Uplink Interval
582
583 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.
584
585 For example, downlink command [[image:image-20241031142131-3.png||height="31" width="216"]]
586
587 Is to check 2024/10/31 01:30:00 to 2020/12/1 04:00:00's data
588
589 Uplink Internal =5s, means LHT65N will send one packet every 5s. range 5~~255s.
590
591
592 === 2.6.4  Datalog Uplink payload ===
593
594
595 See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
596
597 (% style="display:none" %) (%%) (% style="display:none" %)
598
599 == 2.7 Button ==
600
601
602 * ACT button
603
604 Long press this button PB05 will reset and join network again.
605
606 [[image:image-20240510161626-17.png||height="192" width="224"]]
607
608 * Alarm button
609
610 Press the button PB05 will immediately uplink data, and alarm is "TRUE".
611
612 [[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
613
614
615 == 2.8 LED Indicator ==
616
617
618 (((
619 The PB05 has a triple color LED which for easy showing different stage.
620 )))
621
622 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
623
624 (((
625 (% style="color:#037691" %)**In a normal working state**:
626 )))
627
628 * 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(% style="color:#0000ff" %)**.**
629 * During OTAA Join:
630 ** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.
631 ** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.
632 * After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.
633 * 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.
634
635 (((
636
637 )))
638
639 == 2.9 Buzzer ==
640
641
642 The PB05 has** button sound** and** ACK sound** and users can turn on or off both sounds by using [[AT+SOUND>>||anchor="H3.3A0Setbuttonsoundandbuttonalarm"]].
643
644 * (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
645
646 Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
647
648 * (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
649
650 = 3.  Configure PB05 via AT command or LoRaWAN downlink =
651
652
653 Users can configure PB05 via AT Command or LoRaWAN Downlink.
654
655 * AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
656
657 * LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
658
659 There are two kinds of commands to configure PB05, they are:
660
661 * (% style="color:#4f81bd" %)**General Commands:**
662
663 These commands are to configure:
664
665 * General system settings like: uplink interval.
666
667 * LoRaWAN protocol & radio-related commands.
668
669 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]]
670
671
672 * (% style="color:#4f81bd" %)**Commands special design for PB05**
673
674 These commands are only valid for PB05, as below:
675
676 (% style="display:none" %) (%%)
677
678 == 3.1  Downlink Command Set ==
679
680
681 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
682 |=(% style="width: 130px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 151px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 92px; background-color: rgb(79, 129, 189); color: white;" %)**Response**|=(% style="width: 206px; background-color: rgb(79, 129, 189); color: white;" %)**Downlink**
683 |(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
684
685
686 View current TDC time
687 )))|(% style="width:92px" %)(((
688 1200000
689 OK
690 )))|(% style="width:206px" %)Default 1200000(ms)
691 |(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
692 (((
693 0X0100012C:
694 01: fixed command
695 00012C: 0X00012C=
696
697 300(seconds)
698 )))
699
700 (((
701
702 )))
703 )))
704 |(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
705 |(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
706 |(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
707 0,7,0
708
709 OK
710 )))|(% style="width:206px" %)Default 0,7,0
711 |(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
712 Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry
713 )))|(% style="width:92px" %)(((
714 OK
715 )))|(% style="width:206px" %)(((
716 05010701
717
718 05: fixed command
719
720 01:confirmed uplink
721
722 07: retry 7 times
723
724 01: fcnt count plus 1
725 )))
726 |(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
727 Check the current network connection method
728 )))|(% style="width:92px" %)(((
729 1
730 OK
731 )))|(% style="width:206px" %)Default 1
732 |(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((
733 Attention:Take effect after ATZ
734 OK
735 )))|(% style="width:206px" %)(((
736 0X2000: ABP
737 0x2001: OTAA
738 20: fixed command
739 )))
740 |(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
741 0
742 OK
743 )))|(% style="width:206px" %)Default 0
744 |(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
745 0x2101:
746 21: fixed command
747 01: for details, check wiki
748 )))
749 |(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
750 1
751 OK
752 )))|(% style="width:206px" %)Default 0
753 |(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
754 0x2200: close
755 0x2201: open
756 22: fixed command
757 )))
758 |(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
759 |(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
760 set DR to 1
761 It takes effect only when ADR=0
762 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
763 0X22000101:
764 00: ADR=0
765 01: DR=1
766 01: TXP=1
767 22: fixed command
768 )))
769 |(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
770 |(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
771 set TXP to 1
772 It takes effect only when ADR=0
773 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
774 0X22000101:
775 00: ADR=0
776 01: DR=1
777 01: TXP=1
778 22: fixed command
779 )))
780 |(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
781 0X26000A:
782 26: fixed command
783 000A: 0X000A=10(min)
784 for details, check wiki
785 )))
786 |(% style="width:130px" %) |(% style="width:151px" %)(((
787 (((
788 ~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
789
790 Retrieve stored data for a specified period of time
791 )))
792
793 (((
794
795 )))
796 )))|(% style="width:92px" %) |(% style="width:206px" %)(((
797 0X3161DE7C7061DE8A800A:
798 31: fixed command
799 61DE7C70:0X61DE7C70=2022/1/12 15:00:00
800 61DE8A80:0X61DE8A80=2022/1/12 16:00:00
801 0A: 0X0A=10(second)
802 View details 2.6.2
803 )))
804 |(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
805 1,1440,2880
806 OK
807 )))|(% style="width:206px" %)Default 1,1440,2880(min)
808 |(% style="width:130px" %)AT+DDETECT=(((
809 1,1440,2880
810 )))|(% style="width:151px" %)(((
811 Set DDETECT setting status and time
812 ((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
813 )))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
814 0X320005A0: close
815 0X320105A0: open
816 32: fixed command
817 05A0: 0X05A0=1440(min)
818 )))
819
820 == 3.2  Set Password ==
821
822
823 Feature: Set device password, max 9 digits.
824
825 (% style="color:#4f81bd" %)**AT Command: AT+PWORD**
826
827 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
828 |(% 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**
829 |(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
830 123456
831 OK
832 )))
833 |(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
834
835 (% style="color:#4f81bd" %)**Downlink Command:**
836
837 No downlink command for this feature.
838
839
840 == 3.3  Set button sound and ACK sound ==
841
842
843 Feature: Turn on/off button sound and ACK alarm.
844
845 (% style="color:#4f81bd" %)**AT Command: AT+SOUND**
846
847 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
848 |(% 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**
849 |(% style="width:155px" %)(((
850 AT+SOUND=?
851 )))|(% style="width:124px" %)Get the current status of button sound and ACK sound|(% style="width:86px" %)(((
852 1,1
853 OK
854 )))
855 |(% style="width:155px" %)(((
856 AT+SOUND=0,1
857 )))|(% style="width:124px" %)Turn off the button sound and turn on ACK sound|(% style="width:86px" %)OK
858
859 (% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
860
861 Format: Command Code (0xA1) followed by 2 bytes mode value.
862
863 The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
864
865 * **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
866
867 == 3.4  Set buzzer music type(0~~4) ==
868
869
870 Feature: Set different alarm key response sounds.There are five different types of button music.
871
872 (% style="color:#4f81bd" %)**AT Command: AT+OPTION**
873
874 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
875 |(% 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**
876 |(% style="width:155px" %)(((
877 AT+OPTION=?
878 )))|(% style="width:124px" %)(((
879 Get the buzzer music type
880 )))|(% style="width:86px" %)(((
881 3
882
883 OK
884 )))
885 |(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
886
887 (% style="color:#4f81bd" %)**Downlink Command: 0xA3**
888
889 Format: Command Code (0xA3) followed by 1 byte mode value.
890
891 * **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
892
893 == 3.5  Set Valid Push Time ==
894
895
896 Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
897
898 (% style="color:#4f81bd" %)**AT Command: AT+STIME**
899
900 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
901 |(% 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**
902 |(% style="width:155px" %)(((
903 AT+STIME=?
904 )))|(% style="width:124px" %)(((
905 Get the button sound time
906 )))|(% style="width:86px" %)(((
907 0
908 OK
909 )))
910 |(% style="width:155px" %)(((
911 AT+STIME=1000
912 )))|(% style="width:124px" %)Set the button sound time to 1000**ms**|(% style="width:86px" %)OK
913
914 (% style="color:#4f81bd" %)**Downlink Command: 0xA2**
915
916 Format: Command Code (0xA2) followed by 2 bytes mode value.
917
918 * **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
919
920 **~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
921
922
923
924 = 4.  Battery & How to replace =
925
926 == 4.1  Battery Type and replace ==
927
928
929 PB05 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.
930
931 (% style="color:red" %)**Note: **
932
933 1.  The PB05 doesn't have any screw, users can use nail to open it by the middle.
934
935 [[image:image-20220621143535-5.png]]
936
937
938 2.  Make sure the direction is correct when install the AA batteries.
939
940 [[image:image-20220621143535-6.png]]
941
942
943 == 4.2  Power Consumption Analyze ==
944
945
946 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.
947
948 Instruction to use as below:
949
950 (% style="color:blue" %)**Step 1**(%%):  Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
951
952 [[battery calculator>>https://www.dropbox.com/sh/sxrgszkac4ips0q/AAA4XjBI3HAHNpdbU3ALN1j0a/Battery%20Document/Battery_Analyze?dl=0&subfolder_nav_tracking=1]]
953
954
955 (% style="color:blue" %)**Step 2**(%%):  (% style="display:none" %) (%%)Open it and choose
956
957 * Product Model
958 * Uplink Interval
959 * Working Mode
960
961 And the Life expectation in difference case will be shown on the right.
962
963 [[image:image-20220621143643-7.png||height="429" width="1326"]]
964
965
966 = 5.  Accessories =
967
968
969 * (((
970 (% class="wikigeneratedid" id="H5.2A0ProgramConverter28AS-0229" %)
971 **Program Converter (AS-02)**
972 )))
973
974 AS-02 is an optional accessory, it is USB Type-C converter. AS-02 provide below feature:
975
976 1. Access AT console of PB05 when used with USB-TTL adapter. [[See this link>>||anchor="H6.1HowtouseATCommandtoconfigurePB01"]].
977
978 [[image:image-20220621141724-3.png]]
979
980
981 = 6. FAQ =
982
983 == 6.1 How to use AT Command to configure PB05 ==
984
985
986 PB05 supports AT Command set. Users can use a USB to TTL adapter plus the Program Cable to connect to PB05 for using AT command, as below.
987
988 [[image:image-20240511085914-1.png||height="570" width="602"]]
989
990
991 **Connection:**
992
993 * (% style="background-color:yellow" %)USB to TTL GND <~-~-> Program Converter GND pin
994 * (% style="background-color:yellow" %)USB to TTL RXD  <~-~-> Program Converter D+ pin
995 * (% style="background-color:yellow" %)USB to TTL TXD  <~-~-> Program Converter A11 pin
996
997 (((
998 In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console for PB05. 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.
999 )))
1000
1001 (((
1002 Input password and ATZ to activate PB05, as shown below:
1003 )))
1004
1005 [[image:image-20241031160438-2.png||height="541" width="663"]]
1006
1007
1008 == 6.2  AT Command and Downlink ==
1009
1010
1011 (((
1012 Sending ATZ will reboot the node
1013 )))
1014
1015 (((
1016 Sending AT+FDR will restore the node to factory settings
1017 )))
1018
1019 (((
1020 Get the node's AT command setting by sending AT+CFG
1021 )))
1022
1023 (((
1024
1025 )))
1026
1027 (((
1028 **Example:**                                           
1029 )))
1030
1031 (((
1032 AT+DEUI=01 FF FF FF FF FF FF FF
1033
1034 AT+APPEUI=FF FF FF FF FF FF FF 01
1035
1036 AT+APPKEY=11 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
1037
1038 AT+DADDR=FFFFFFFF
1039
1040 AT+APPSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
1041
1042 AT+NWKSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
1043
1044 AT+ADR=1
1045
1046 AT+TXP=0
1047
1048 AT+DR=3
1049
1050 AT+DCS=0
1051
1052 AT+PNM=1
1053
1054 AT+RX2FQ=869525000
1055
1056 AT+RX2DR=0
1057
1058 AT+RX1DL=5000
1059
1060 AT+RX2DL=6000
1061
1062 AT+JN1DL=5000
1063
1064 AT+JN2DL=6000
1065
1066 AT+NJM=1
1067
1068 AT+NWKID=00 00 00 13
1069
1070 AT+FCU=1
1071
1072 AT+FCD=0
1073
1074 AT+CLASS=A
1075
1076 AT+NJS=1
1077
1078 AT+RECVB=0:
1079
1080 AT+RECV=
1081
1082 AT+VER=EU868 v1.0.0
1083
1084 AT+CFM=0,7,0
1085
1086 AT+SNR=0
1087
1088 AT+RSSI=0
1089
1090 AT+TDC=1200000
1091
1092 AT+PORT=2
1093
1094 AT+PWORD=123456
1095
1096 AT+CHS=0
1097
1098 AT+RX1WTO=6
1099
1100 AT+RX2WTO=6
1101
1102 AT+DECRYPT=0
1103
1104 AT+RJTDC=20
1105
1106 AT+RPL=0
1107
1108 AT+TIMESTAMP=systime= 2024/10/31 08:06:05 (1730361965)
1109
1110 AT+LEAPSEC=18
1111
1112 AT+SYNCMOD=1
1113
1114 AT+SYNCTDC=10
1115
1116 AT+SLEEP=0
1117
1118 AT+BAT=3102
1119
1120 AT+ATDC=1
1121
1122 AT+UUID=0002023A01325A04
1123
1124 AT+DDETECT=1,1440,2880
1125
1126 AT+SETMAXNBTRANS=1,0
1127
1128 AT+DISFCNTCHECK=0
1129
1130 AT+DISMACANS=0
1131
1132 AT+PNACKMD=0
1133
1134 AT+SOUND=1,1
1135
1136 AT+STIME=0
1137
1138 AT+OPTION=0
1139 )))
1140
1141 (((
1142 **Example:**
1143 )))
1144
1145 [[image:image-20241031160804-3.png||height="549" width="661"]]
1146
1147
1148 == 6.3  How to upgrade the firmware? ==
1149
1150
1151 PB05 requires a program converter to upload images to PB05, which is used to upload image to PB05 for:
1152
1153 * Support new features
1154 * For bug fix
1155 * Change LoRaWAN bands.
1156
1157 PB05 internal program is divided into bootloader and work program, shipping is included bootloader, the user can choose to directly update the work program.
1158
1159 If the bootloader is erased for some reason, users will need to download the boot program and the work program.
1160
1161
1162 === 6.3.1 Update firmware (Assume device have bootloader) ===
1163
1164
1165 (% style="color:blue" %)**Step 1**(%%):** Connect UART as per FAQ 6.1**
1166
1167 (% style="color:blue" %)**Step 2**(%%):** Update follow [[Instruction for update via DraginoSensorManagerUtility.exe>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H3.2.1UpdateafirmwareviaDraginoSensorManagerUtility.exe]]. **
1168
1169
1170 === 6.3.2 Update firmware (Assume device doesn't have bootloader) ===
1171
1172
1173 Download both the boot program and the worker program** . **After update , device will have bootloader so can use above 6.3.1 method to update woke program.
1174
1175 (% style="color:blue" %)**Step 1**(%%):** **Install [[TremoProgrammer>>url:https://www.dropbox.com/scl/fo/gk1rb5pnnjw4kv5m5cs0z/h?rlkey=906ouvgbvif721f9bj795vfrh&dl=0]]  first.
1176
1177 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LHT65N%20LoRaWAN%20Temperature%20%26%20Humidity%20Sensor%20Manual/WebHome/image-20220615170542-5.png?rev=1.1||alt="image-20220615170542-5.png"]]
1178
1179 (% style="color:blue" %)**Step 2**(%%): Hardware Connection
1180
1181 Connect PC and PB05 via USB-TTL adapter .
1182
1183 (% style="color:red" %)**Note: To download firmware in this way, you need to pull the boot pin(Program Converter D- pin) high to enter the burn mode. After burning, disconnect the boot pin of the node and the 3V3 pin of the USB-TTL adapter, and reset the node to exit the burning mode.**
1184
1185 **Connection:**
1186
1187 * (% style="background-color:yellow" %)USB-TTL GND <~-~-> Program Converter GND pin
1188 * (% style="background-color:yellow" %)USB-TTL RXD  <~-~-> Program Converter D+ pin
1189 * (% style="background-color:yellow" %)USB-TTL TXD  <~-~-> Program Converter A11 pin
1190 * (% style="background-color:yellow" %)USB-TTL 3V3 <~-~-> Program Converter D- pin
1191
1192 (% style="color:blue" %)**Step 3**(%%):** **Select the device port to be connected, baud rate and bin file to be downloaded.
1193
1194 [[image:image-20241031161245-5.png||height="471" width="372"]]
1195
1196 Users need to reset the node to start downloading the program.
1197 ~1. Reinstall the battery to reset the node
1198 2. Hold down the ACT button to reset the node.
1199
1200 When this interface appears, it indicates that the download has been completed.
1201
1202 [[image:image-20241031161608-6.png||height="486" width="375"]]
1203
1204 Finally, Disconnect Program Converter D- pin, reset the node again , and the node exits burning mode.
1205
1206
1207 == 6.4  How to change the LoRa Frequency Bands/Region? ==
1208
1209
1210 User can follow the introduction for [[how to upgrade image>>||anchor="H6.3A0Howtoupgradethefirmware3F"]]. When download the images, choose the required image file for download.
1211
1212
1213 == 6.5 How to design customized sticker? ==
1214
1215
1216 PB05 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.
1217
1218 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.
1219
1220
1221
1222 = 7. Order Info =
1223
1224 == 7.1  Main Device ==
1225
1226
1227 Part Number: (% style="color:#4472c4" %)PB05-XX
1228
1229 (% style="color:#4472c4" %)**XX **(%%): The default frequency band
1230
1231 * (% style="color:red" %)**AS923**(%%)**: **LoRaWAN AS923 band
1232 * (% style="color:red" %)**AU915**(%%)**: **LoRaWAN AU915 band
1233 * (% style="color:red" %)**EU433**(%%)**: **LoRaWAN EU433 band
1234 * (% style="color:red" %)**EU868**(%%)**:** LoRaWAN EU868 band
1235 * (% style="color:red" %)**KR920**(%%)**: **LoRaWAN KR920 band
1236 * (% style="color:red" %)**US915**(%%)**: **LoRaWAN US915 band
1237 * (% style="color:red" %)**IN865**(%%)**:  **LoRaWAN IN865 band
1238 * (% style="color:red" %)**CN470**(%%)**: **LoRaWAN CN470 band
1239
1240 = 7. Packing Info =
1241
1242
1243 **Package Includes**:
1244
1245 * PB05 LoRaWAN Push Button x 1
1246
1247 = 8. Support =
1248
1249
1250 * 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.
1251 * 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]].
1252
1253 = 9.  Reference material =
1254
1255
1256 * [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/scl/fo/y7pvm58wcr8319d5o4ujr/APZtqlbzRCNbHoPWTmmMMWs?rlkey=wfh93x2dhcev3ydn0846rinf0&st=kdp6lg7t&dl=0]]
1257
1258 = 10. FCC Warning =
1259
1260
1261 This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1262
1263 (1) This device may not cause harmful interference;
1264
1265 (2) this device must accept any interference received,including interference that may cause undesired operation.
1266