Last modified by Dilisi S on 2025/02/26 19:24
<
From version < 4.12 >
edited by Edwin Chen
on 2024/09/16 09:37
To version < 31.1 >
edited by BoYang Xie
on 2024/09/28 09:00
>
Change comment: Uploaded new attachment "1727485251053-655.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.xieby
Content
... ... @@ -40,7 +40,6 @@
40 40  * 5V DC power
41 41  * IP Rating: IP52
42 42  
43 -
44 44  == 1.3  Specification ==
45 45  
46 46  **LoRa**:
... ... @@ -68,19 +68,15 @@
68 68  * RGB color.
69 69  * Display Area: 120.7*75.80 mm
70 70  
71 -
72 -
73 73  == 1.4  Power Consumption ==
74 74  
75 75  * External 5V DC power adapter
76 76  
77 -
78 78  == 1.5  Storage & Operation Temperature ==
79 79  
80 80  * Operation Temperature: -20 ~~ 70°C  (No Dew)
81 81  * Storage Temperature: -30 ~~ 70°C  (No Dew)
82 82  
83 -
84 84  == 1.6  Applications ==
85 85  
86 86  * Smart Buildings & Home Automation
... ... @@ -90,722 +90,141 @@
90 90  * Smart Cities
91 91  * Smart Factory
92 92  
88 += 2.  Getting Start with Hello World =
93 93  
94 -= 2.  Operation Mode =
90 +== 2.1  About this demo ==
95 95  
96 -== 2.1  How it work? ==
92 +In this Getting Start Example, we will show how to design a simple Display UI and upload it to LTS5. This UI has  a button , when user click the button. The Web UI will jump to a new page.
97 97  
94 +== 2.2  Install Software Running Environment ==
98 98  
99 -Each PB01 is shipped with a worldwide unique set of LoRaWAN OTAA keys. To use PB01 in a LoRaWAN network, user needs to input the OTAA keys in LoRaWAN network server. After this, if PB01 is under this LoRaWAN network coverage, PB01 can join the LoRaWAN network and start to transmit sensor data. The default period for each uplink is** 20 minutes**.
96 +The ESP MCU can be developed using ESP-IDF, Arduino, or MicroPython. For this project, we utilize ESP-IDF for compilation and Visual Studio Code (VSCode) for editing.
100 100  
98 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
101 101  
102 -== 2.2  How to Activate PB01? ==
100 +Firstly, download and install VSCode for your computer's operating system from the official website: [[Download Visual Studio Code - Mac, Linux, Windows>>url:https://code.visualstudio.com/download]].
103 103  
102 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
104 104  
105 -(% style="color:red" %)** 1.  Open enclosure from below position.**
104 +[[image:1727229396732-319.png]]
106 106  
107 -[[image:image-20220621093835-1.png]]
106 + image 1 ESP-IDF extension install
108 108  
108 +Links for reference: [[Install ESP32 ESP-IDF on Windows and Integrate with VS code (esp32tutorials.com)>>url:https://esp32tutorials.com/install-esp32-esp-idf-windows-integrate-vs-code/#:~~:text=In%20this%20tutorial,%20we%20will%20show%20you%20how%20to%20install]]
109 109  
110 -(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
110 +=== 2.2.2 Install SquareLine Studio ===
111 111  
112 -[[image:image-20220621093835-2.png]]
112 +The version we are utilizing for this software is 1.4.2. You can download it from the official link: [[SquareLine Studio - Download the current version of SquareLine Studio>>url:https://squareline.io/downloads#lastRelease]].
113 113  
114 +Please note that this software necessitates the registration of a license prior to usage, and various licenses come with distinct limitations. For instance, the free version imposes restrictions such as a limit of 1 component, 150 widgets, and 10 screens. However, for first-time downloads, you are granted unrestricted access for a period of 30 days without the need for immediate registration.
114 114  
115 -(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
116 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
116 116  
117 -[[image:image-20220621093835-3.png]]
118 +After launching and logging in to this software, create a project as shown in the following image 2. The version of LVGL is 8.3.11.
118 118  
119 119  
120 -User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
121 +[[image:1727233636007-933.png]]
121 121  
123 + image 2 create a SquareLine project
122 122  
123 -== 2.3  Example to join LoRaWAN network ==
125 +Next, we need to make some settings for this project. By clicking in the specified order on image 3, we can see the page as shown in image 4.
124 124  
127 +[[image:1727229582471-566.png]]
125 125  
126 -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.
129 + image 3 project settings
127 127  
128 -(% _mstvisible="1" class="wikigeneratedid" %)
129 -Assume the LPS8v2 is already set to connect to [[TTN V3 network >>url:https://eu1.cloud.thethings.network/]]. We need to add the PB01 device in TTN V3 portal. 
131 +[[image:1727229618724-758.png]]
130 130  
131 -[[image:image-20240705094824-4.png]]
133 + image 4 modify project settings
132 132  
133 -(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
135 +Now we can start to use this software. The steps for creating this UI are shown in image 5-10.
134 134  
135 -Each PB01 is shipped with a sticker with the default DEV EUI as below:
137 +[[image:1727229653254-680.png]]
136 136  
137 -[[image:image-20230426083617-1.png||height="294" width="633"]]
139 + image 5 create a UI(1)
138 138  
141 +[[image:1727231038705-173.png]]
139 139  
140 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
143 + image 6 create a UI(2)
141 141  
142 -Create application.
145 +[[image:1727229682537-381.png]]
143 143  
144 -choose to create the device manually.
147 + image 7 create a UI(3)
145 145  
146 -Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
149 +We repeat the steps of screen1 in screen2. Then we get screen2 as shown in image 8.
147 147  
148 -[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
149 -
151 +[[image:1727229715361-392.png]]
150 150  
151 -[[image:image-20240507142157-2.png||height="559" width="1147"]]
153 + image 8 create a UI(4)
152 152  
153 -[[image:image-20240507142401-3.png||height="693" width="1202"]]
155 +Finally, we add click event for screen change to button1 in screen1(shown in image 9) and button2 in screen2.
154 154  
155 -[[image:image-20240507142651-4.png||height="760" width="1190"]]
157 +[[image:1727229740592-843.png]]
156 156  
157 -**Default mode OTAA**(% style="display:none" %)
159 + image 9 create a UI(5)
158 158  
161 +The event settings of button1 are as image 10 shown. The event adding operation of button2 is similar to button1.
159 159  
160 -(% style="color:blue" %)**Step 2**(%%):  Use ACT button to activate PB01 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.
163 +[[image:1727229760857-521.png]]
161 161  
162 -[[image:image-20240507143104-5.png||height="434" width="1398"]]
165 + image 10 create a UI(6)
163 163  
167 +== 2.4 Integrate UI Code to ESP-IDF Project ==
164 164  
165 -== 2.4  Uplink Payload ==
169 +To achieve the integrating, we first need to export the UI code, then make some modifications, and finally relocate the UI code to a specific position within the project.
166 166  
171 +[[image:1727229798126-306.png]]
167 167  
168 -Uplink payloads include two types: Valid Sensor Value and other status / control command.
173 + image 11 export UI file
169 169  
170 -* Valid Sensor Value: Use FPORT=2
171 -* Other control command: Use FPORT other than 2.
175 +[[image:1727229821582-258.png]]
172 172  
173 -=== 2.4.1  Uplink FPORT~=5, Device Status ===
177 + image 12 exported UI file
174 174  
179 +Create a empty directory entitled ‘ui’ in path “basic_prj/app_components/ui/”, and then copy all UI code exported to this directory.
175 175  
176 -Users can  get the Device Status uplink through the downlink command:
181 +[[image:1727229845835-509.png]]
177 177  
178 -(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
183 + image 13 open CMakeLists.txt
179 179  
180 -Uplink the device configures with FPORT=5.
185 +[[image:1727229892636-154.png]]
181 181  
182 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:370px" %)
183 -|=(% 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**
184 -|(% 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
187 + image 14 modify CMakeLists.txt
185 185  
186 -[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
189 +The last step of integrating is adding two lines of code in main.c file.
187 187  
188 -Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
191 +[[image:1727229926561-300.png]]
189 189  
193 + image 15 add “ui.h”
190 190  
191 -(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
195 +[[image:1727229955611-607.png]]
192 192  
193 -(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
197 + image 16 add “ui_init()”
194 194  
195 -(% style="color:#4472c4" %)**Frequency Band**:
199 +== 2.5 Test Result ==
196 196  
197 -*0x01: EU868
201 +By pressing the button lying bottom right, the screen can switch to another as expected. This indicates that the UI file has been successfully integrated into the project and is now effective.
198 198  
199 -*0x02: US915
203 +[[image:1727229990795-405.png]]
200 200  
201 -*0x03: IN865
205 + image 17 screen1
202 202  
203 -*0x04: AU915
207 +[[image:1727230012478-930.png]]
204 204  
205 -*0x05: KZ865
209 + image 18 screen2
206 206  
207 -*0x06: RU864
211 += 3. Example Project 1: LoRa Central Display =
208 208  
209 -*0x07: AS923
213 +[[image:image-20240916101737-1.png||height="468" width="683"]]
210 210  
211 -*0x08: AS923-1
212 212  
213 -*0x09: AS923-2
214 214  
215 -*0x0a: AS923-3
217 += 4. Example Project 2: LoRaWAN RS485 Alarm =
216 216  
217 217  
218 -(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
219 -
220 -(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
221 -
222 -(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
223 -
224 -
225 -=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
226 -
227 -
228 -PB01 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"]].
229 -
230 -Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
231 -
232 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:460px" %)
233 -|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
234 -**Size(bytes)**
235 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)2|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
236 -**1**
237 -)))|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
238 -**1**
239 -)))|=(% style="width: 90px;background-color:#4F81BD;color:white" %)(((
240 -**2**
241 -)))|=(% style="width: 40px;background-color:#4F81BD;color:white" %)(((
242 -**2**
243 -)))
244 -|(% style="width:97px" %)(((
245 -Value
246 -)))|(% style="width:39px" %)Battery|(% style="width:39px" %)(((
247 -Sound_ACK
248 -
249 -&Sound_key
250 -)))|(% style="width:100px" %)(((
251 -(((
252 -Alarm
253 -)))
254 -)))|(% style="width:77px" %)(((
255 -(((
256 -Temperature
257 -)))
258 -)))|(% style="width:47px" %)(((
259 -Humidity
260 -)))
261 -
262 -Example in TTN.
263 -
264 -[[image:image-20240507150155-11.png||height="549" width="1261"]]
265 -
266 -Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
267 -
268 -==== (% style="color:blue" %)**Battery:**(%%) ====
269 -
270 -Check the battery voltage.
271 -
272 -* Ex1: 0x0CEA = 3306mV
273 -* Ex2: 0x0D08 = 3336mV
274 -
275 -==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
276 -
277 -Key sound and ACK sound are enabled by default.
278 -
279 -* Example1: 0x03
280 -
281 - Sound_ACK: (03>>1) & 0x01=1, OPEN.
282 -
283 -**~ ** Sound_key:  03 & 0x01=1, OPEN.
284 -
285 -* Example2: 0x01
286 -
287 - Sound_ACK: (01>>1) & 0x01=0, CLOSE.
288 -
289 -**~ ** Sound_key:  01 & 0x01=1, OPEN.
290 -
291 -
292 -==== (% style="color:blue" %)**Alarm:**(%%) ====
293 -
294 -Key alarm.
295 -
296 -* Ex1: 0x01 & 0x01=1, TRUE.
297 -* Ex2: 0x00 & 0x01=0, FALSE.
298 -
299 -==== (% style="color:blue" %)**Temperature:**(%%) ====
300 -
301 -* Example1:  0x0111/10=27.3℃
302 -* Example2:  (0xFF0D-65536)/10=-24.3℃
303 -
304 -If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
305 -
306 -（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
307 -
308 -
309 -==== (% style="color:blue" %)**Humidity:**(%%) ====
310 -
311 -* Humidity:    0x02A8/10=68.0%
312 -
313 -=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
314 -
315 -
316 -PB01 stores sensor value and user can retrieve these history value via downlink command. The Datalog sensor value are sent via FPORT=3.
317 -
318 -[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
319 -
320 -
321 -* Each data entry is 11 bytes, to save airtime and battery, PB01 will send max bytes according to the current DR and Frequency bands.(% style="display:none" %)
322 -
323 -For example, in US915 band, the max payload for different DR is:
324 -
325 -1. **DR0**: max is 11 bytes so one entry of data
326 -1. **DR1**: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
327 -1. **DR2**: total payload includes 11 entries of data
328 -1. **DR3**: total payload includes 22 entries of data.
329 -
330 -(% style="color:red" %)**Notice: PB01 will save 178 set of history data, If device doesn't have any data in the polling time. Device will uplink 11 bytes of 0.**
331 -
332 -See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
333 -
334 -(% style="display:none" %) (%%)
335 -
336 -=== 2.4.4  Decoder in TTN V3 ===
337 -
338 -
339 -In LoRaWAN protocol, the uplink payload is HEX format, user need to add a payload formatter/decoder in LoRaWAN Server to get human friendly string.
340 -
341 -In TTN , add formatter as below:
342 -
343 -[[image:image-20240507162814-16.png||height="778" width="1135"]]
344 -
345 -(((
346 -Please check the decoder from this link:  [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>https://github.com/dragino/dragino-end-node-decoder]]
347 -)))
348 -
349 -(((
350 -
351 -)))
352 -
353 -== 2.5 Show data on Datacake ==
354 -
355 -
356 -(((
357 -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:
358 -)))
359 -
360 -(((
361 -
362 -)))
363 -
364 -(((
365 -(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
366 -)))
367 -
368 -(((
369 -(% 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.
370 -)))
371 -
372 -(((
373 -~1. Add Datacake:
374 -)))
375 -
376 -(((
377 -2. Select default key as Access Key:
378 -)))
379 -
380 -(((
381 -3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
382 -)))
383 -
384 -(((
385 - Please refer to the figure below.
386 -)))
387 -
388 -[[image:image-20240510150924-2.png||height="612" width="1186"]]
389 -
390 -
391 -Log in to DATACAKE, copy the API under the account.
392 -
393 -[[image:image-20240510151944-3.png||height="581" width="1191"]]
394 -
395 -
396 -
397 -[[image:image-20240510152150-4.png||height="697" width="1188"]]
398 -
399 -
400 -[[image:image-20240510152300-5.png||height="298" width="1191"]]
401 -
402 -
403 -[[image:image-20240510152355-6.png||height="782" width="1193"]]
404 -
405 -[[image:image-20240510152542-8.png||height="545" width="739"]]
406 -
407 -[[image:image-20240510152634-9.png||height="748" width="740"]]
408 -
409 -
410 -[[image:image-20240510152809-10.png||height="607" width="732"]]
411 -
412 -[[image:image-20240510153934-14.png||height="460" width="1199"]]
413 -
414 -
415 -[[image:image-20240510153435-12.png||height="428" width="1197"]]
416 -
417 -
418 -Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
419 -
420 -[[image:image-20240510153624-13.png||height="468" width="1195"]]
421 -
422 -
423 -Visual widgets please read the DATACAKE documentation.
424 -
425 -(% style="display:none" %) (%%)
426 -
427 -== 2.6  Datalog Feature ==
428 -
429 -
430 -(% _msthash="315262" _msttexthash="32283004" _mstvisible="1" %)
431 -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.
432 -
433 -
434 -=== 2.6.1  Unix TimeStamp ===
435 -
436 -
437 -Unix TimeStamp shows the sampling time of uplink payload. format base on
438 -
439 -[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
440 -
441 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
442 -
443 -For example: if the Unix Timestamp we got is hex 0x60137afd, we can convert it to Decimal: 1611889405. and then convert to the time: 2021 – Jan ~-~- 29 Friday 03:03:25 (GMT)
444 -
445 -
446 -[[image:1655782409139-256.png]]
447 -
448 -
449 -=== 2.6.2  Poll sensor value ===
450 -
451 -
452 -(((
453 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
454 -)))
455 -
456 -(((
457 -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.
458 -)))
459 -
460 -(((
461 -For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
462 -)))
463 -
464 -(((
465 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
466 -)))
467 -
468 -(((
469 -Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
470 -)))
471 -
472 -
473 -=== 2.6.3  Datalog Uplink payload ===
474 -
475 -
476 -See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
477 -
478 -(% style="display:none" %) (%%) (% style="display:none" %)
479 -
480 -== 2.7 Button ==
481 -
482 -
483 -* ACT button
484 -
485 -Long press this button PB01 will reset and join network again.
486 -
487 -[[image:image-20240510161626-17.png||height="192" width="224"]]
488 -
489 -* Alarm button
490 -
491 -Press the button PB01 will immediately uplink data, and alarm is "TRUE".
492 -
493 -[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
494 -
495 -
496 -== 2.8 LED Indicator ==
497 -
498 -
499 -(((
500 -The PB01 has a triple color LED which for easy showing different stage.
501 -)))
502 -
503 -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
504 -
505 -(((
506 -(% style="color:#037691" %)**In a normal working state**:
507 -)))
508 -
509 -* 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" %)**.**
510 -* During OTAA Join:
511 -** **For each Join Request uplink:** the (% style="color:green" %)**GREEN LED** (%%)will blink once.
512 -** **Once Join Successful:** the (% style="color:green" %)**GREEN LED**(%%) will be solid on for 5 seconds.
513 -* After joined, for each uplink, the (% style="color:blue" %)**BLUE LED**(%%) or (% style="color:green" %)**GREEN LED** (%%)will blink once.
514 -* 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.
515 -
516 -(((
517 -
518 -)))
519 -
520 -== 2.9 Buzzer ==
521 -
522 -
523 -The PB01 has** button sound** and** ACK sound** and users can turn on or off both sounds by using [[AT+SOUND>>||anchor="H3.3A0Setbuttonsoundandbuttonalarm"]].
524 -
525 -* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
526 -
527 - Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
528 -
529 -* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
530 -
531 -= 3.  Configure PB01 via AT command or LoRaWAN downlink =
532 -
533 -
534 -Users can configure PB01 via AT Command or LoRaWAN Downlink.
535 -
536 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
537 -
538 -* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
539 -
540 -There are two kinds of commands to configure PB01, they are:
541 -
542 -* (% style="color:#4f81bd" %)**General Commands:**
543 -
544 -These commands are to configure:
545 -
546 -* General system settings like: uplink interval.
547 -
548 -* LoRaWAN protocol & radio-related commands.
549 -
550 -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]]
551 -
552 -
553 -* (% style="color:#4f81bd" %)**Commands special design for PB01**
554 -
555 -These commands are only valid for PB01, as below:
556 -
557 -(% style="display:none" %) (%%)
558 -
559 -== 3.1  Downlink Command Set ==
560 -
561 -
562 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
563 -|=(% 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**
564 -|(% style="width:130px" %)AT+TDC=?|(% style="width:151px" %)(((
565 -
566 -
567 -View current TDC time
568 -)))|(% style="width:92px" %)(((
569 -1200000
570 -OK
571 -)))|(% style="width:206px" %)Default 1200000(ms)
572 -|(% style="width:130px" %)AT+TDC=300000|(% style="width:151px" %)Set TDC time|(% style="width:92px" %)OK|(% style="width:206px" %)(((
573 -(((
574 -0X0100012C:
575 -01: fixed command
576 -00012C: 0X00012C=
577 -
578 -300(seconds)
579 -)))
580 -
581 -(((
582 -
583 -)))
584 -)))
585 -|(% style="width:130px" %)ATZ|(% style="width:151px" %)Reset node|(% style="width:92px" %) |(% style="width:206px" %)0x04FF
586 -|(% style="width:130px" %)AT+FDR|(% style="width:151px" %)Restore factory settings|(% style="width:92px" %) |(% style="width:206px" %)0X04FE
587 -|(% style="width:130px" %)AT+CFM=?|(% style="width:151px" %)View the current confirmation mode status|(% style="width:92px" %)(((
588 -0,7,0
589 -
590 -OK
591 -)))|(% style="width:206px" %)Default 0,7,0
592 -|(% style="width:130px" %)AT+CFM=1,7,1|(% style="width:151px" %)(((
593 -Confirmed uplink mode, the maximum number of retries is seven, and uplink fcnt increase by 1 for each retry
594 -)))|(% style="width:92px" %)(((
595 -OK
596 -)))|(% style="width:206px" %)(((
597 -05010701
598 -
599 -05: fixed command
600 -
601 -01:confirmed uplink
602 -
603 -07: retry 7 times
604 -
605 -01: fcnt count plus 1
606 -)))
607 -|(% style="width:130px" %)AT+NJM=?|(% style="width:151px" %)(((
608 -Check the current network connection method
609 -)))|(% style="width:92px" %)(((
610 -1
611 -OK
612 -)))|(% style="width:206px" %)Default 1
613 -|(% style="width:130px" %)AT+NJM=0|(% style="width:151px" %)Change the network connection method to ABP|(% style="width:92px" %)(((
614 -Attention:Take effect after ATZ
615 -OK
616 -)))|(% style="width:206px" %)(((
617 -0X2000: ABP
618 -0x2001: OTAA
619 -20: fixed command
620 -)))
621 -|(% style="width:130px" %)AT+RPL=?|(% style="width:151px" %)View current RPL settings|(% style="width:92px" %)(((
622 -0
623 -OK
624 -)))|(% style="width:206px" %)Default 0
625 -|(% style="width:130px" %)AT+RPL=1|(% style="width:151px" %)set RPL=1    |(% style="width:92px" %)OK|(% style="width:206px" %)(((
626 -0x2101:
627 -21: fixed command
628 -01: for details, check wiki
629 -)))
630 -|(% style="width:130px" %)AT+ADR=?|(% style="width:151px" %)View current ADR status|(% style="width:92px" %)(((
631 -1
632 -OK
633 -)))|(% style="width:206px" %)Default 0
634 -|(% style="width:130px" %)AT+ADR=0|(% style="width:151px" %)Set the ADR state to off|(% style="width:92px" %)OK|(% style="width:206px" %)(((
635 -0x2200: close
636 -0x2201: open
637 -22: fixed command
638 -)))
639 -|(% style="width:130px" %)AT+DR=?|(% style="width:151px" %)View the current DR settings|(% style="width:92px" %)OK|(% style="width:206px" %)
640 -|(% style="width:130px" %)AT+DR=1|(% style="width:151px" %)(((
641 -set DR to 1
642 -It takes effect only when ADR=0
643 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
644 -0X22000101:
645 -00: ADR=0
646 -01: DR=1
647 -01: TXP=1
648 -22: fixed command
649 -)))
650 -|(% style="width:130px" %)AT+TXP=?|(% style="width:151px" %)View the current TXP|(% style="width:92px" %)OK|(% style="width:206px" %)
651 -|(% style="width:130px" %)AT+TXP=1|(% style="width:151px" %)(((
652 -set TXP to 1
653 -It takes effect only when ADR=0
654 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
655 -0X22000101:
656 -00: ADR=0
657 -01: DR=1
658 -01: TXP=1
659 -22: fixed command
660 -)))
661 -|(% style="width:130px" %)AT+RJTDC=10|(% style="width:151px" %)Set RJTDC time interval|(% style="width:92px" %)OK|(% style="width:206px" %)(((
662 -0X26000A:
663 -26: fixed command
664 -000A: 0X000A=10(min)
665 -for details, check wiki
666 -)))
667 -|(% style="width:130px" %) |(% style="width:151px" %)(((
668 -(((
669 -~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_~_
670 -
671 -Retrieve stored data for a specified period of time
672 -)))
673 -
674 -(((
675 -
676 -)))
677 -)))|(% style="width:92px" %) |(% style="width:206px" %)(((
678 -0X3161DE7C7061DE8A800A:
679 -31: fixed command
680 -61DE7C70:0X61DE7C70=2022/1/12 15:00:00
681 -61DE8A80:0X61DE8A80=2022/1/12 16:00:00
682 -0A: 0X0A=10(second)
683 -View details 2.6.2
684 -)))
685 -|(% style="width:130px" %)AT+DDETECT=?|(% style="width:151px" %)View the current DDETECT setting status and time|(% style="width:92px" %)(((
686 -1,1440,2880
687 -OK
688 -)))|(% style="width:206px" %)Default 1,1440,2880(min)
689 -|(% style="width:130px" %)AT+DDETECT=(((
690 -1,1440,2880
691 -)))|(% style="width:151px" %)(((
692 -Set DDETECT setting status and time
693 -((% style="color:red" %)When the node does not receive the downlink packet within the set time, it will re-enter the network(%%))
694 -)))|(% style="width:92px" %)OK|(% style="width:206px" %)(((
695 -0X320005A0: close
696 -0X320105A0: open
697 -32: fixed command
698 -05A0: 0X05A0=1440(min)
699 -)))
700 -
701 -== 3.2  Set Password ==
702 -
703 -
704 -Feature: Set device password, max 9 digits.
705 -
706 -(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
707 -
708 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
709 -|(% 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**
710 -|(% style="width:155px" %)AT+PWORD=?|(% style="width:124px" %)Show password|(% style="width:86px" %)(((
711 -123456
712 -OK
713 -)))
714 -|(% style="width:155px" %)AT+PWORD=999999|(% style="width:124px" %)Set password|(% style="width:86px" %)OK
715 -
716 -(% style="color:#4f81bd" %)**Downlink Command:**
717 -
718 -No downlink command for this feature.
719 -
720 -
721 -== 3.3  Set button sound and ACK sound ==
722 -
723 -
724 -Feature: Turn on/off button sound and ACK alarm.
725 -
726 -(% style="color:#4f81bd" %)**AT Command: AT+SOUND**
727 -
728 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
729 -|(% 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**
730 -|(% style="width:155px" %)(((
731 -AT+SOUND=?
732 -)))|(% style="width:124px" %)Get the current status of button sound and ACK sound|(% style="width:86px" %)(((
733 -1,1
734 -OK
735 -)))
736 -|(% style="width:155px" %)(((
737 -AT+SOUND=0,1
738 -)))|(% style="width:124px" %)Turn off the button sound and turn on ACK sound|(% style="width:86px" %)OK
739 -
740 -(% style="color:#4f81bd" %)**Downlink Command: 0xA1 **
741 -
742 -Format: Command Code (0xA1) followed by 2 bytes mode value.
743 -
744 -The first byte after 0XA1 sets the button sound, and the second byte after 0XA1 sets the ACK sound.** (0: off, 1: on)**
745 -
746 -* **Example: **Downlink Payload: A10001  ~/~/ Set AT+SOUND=0,1  Turn off the button sound and turn on ACK sound.
747 -
748 -== 3.4  Set buzzer music type(0~~4) ==
749 -
750 -
751 -Feature: Set different alarm key response sounds.There are five different types of button music.
752 -
753 -(% style="color:#4f81bd" %)**AT Command: AT+OPTION**
754 -
755 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
756 -|(% 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**
757 -|(% style="width:155px" %)(((
758 -AT+OPTION=?
759 -)))|(% style="width:124px" %)(((
760 -Get the buzzer music type
761 -)))|(% style="width:86px" %)(((
762 -3
763 -
764 -OK
765 -)))
766 -|(% style="width:155px" %)AT+OPTION=1|(% style="width:124px" %)Set the buzzer music to type 1|(% style="width:86px" %)OK
767 -
768 -(% style="color:#4f81bd" %)**Downlink Command: 0xA3**
769 -
770 -Format: Command Code (0xA3) followed by 1 byte mode value.
771 -
772 -* **Example: **Downlink Payload: A300  ~/~/ Set AT+OPTION=0  Set the buzzer music to type 0.
773 -
774 -== 3.5  Set Valid Push Time ==
775 -
776 -
777 -Feature: Set the holding time for pressing the alarm button to avoid miscontact. Values range from** 0 ~~1000ms**.
778 -
779 -(% style="color:#4f81bd" %)**AT Command: AT+STIME**
780 -
781 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:372px" %)
782 -|(% 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**
783 -|(% style="width:155px" %)(((
784 -AT+STIME=?
785 -)))|(% style="width:124px" %)(((
786 -Get the button sound time
787 -)))|(% style="width:86px" %)(((
788 -0
789 -OK
790 -)))
791 -|(% style="width:155px" %)(((
792 -AT+STIME=1000
793 -)))|(% style="width:124px" %)Set the button sound time to 1000**ms**|(% style="width:86px" %)OK
794 -
795 -(% style="color:#4f81bd" %)**Downlink Command: 0xA2**
796 -
797 -Format: Command Code (0xA2) followed by 2 bytes mode value.
798 -
799 -* **Example: **Downlink Payload: A203E8  ~/~/ Set AT+STIME=1000  
800 -
801 -**~ Explain: **Hold the alarm button for 10 seconds before the node will send the alarm packet.
802 -
803 -
804 -
805 -
806 806  = 6. FAQ =
807 807  
808 -== 6.1 ==
222 +== 6.1 ==
809 809  
810 810  
811 811  = 7. Order Info =
... ... @@ -814,7 +814,6 @@
814 814  
815 815  Part Number: (% style="color:#4472c4" %)LTS5
816 816  
817 -
818 818  
819 819  == 7.2  Packing Info ==
820 820  
... ... @@ -824,13 +824,11 @@
824 824  * 5V,2A DC Power Adapter.
825 825  * USB Type C Program Cable
826 826  
827 -
828 828  = 8. Support =
829 829  
830 830  * 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.
831 831  * 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]].
832 832  
833 -
834 834  = 9.  Reference material =
835 835  
836 836  * Datasheet
... ... @@ -837,7 +837,6 @@
837 837  * Source Code
838 838  * Mechinical
839 839  
840 -
841 841  = 10. FCC Warning =
842 842  
843 843  
1727229396732-319.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +197.2 KB
Content
1727229550717-684.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +113.9 KB
Content
1727229582471-566.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +73.6 KB
Content
1727229618724-758.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +118.7 KB
Content
1727229653254-680.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +116.2 KB
Content
1727229682537-381.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +51.5 KB
Content
1727229715361-392.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +75.2 KB
Content
1727229740592-843.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +87.3 KB
Content
1727229760857-521.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +24.7 KB
Content
1727229798126-306.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +53.6 KB
Content
1727229821582-258.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1727229845835-509.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +68.3 KB
Content
1727229892636-154.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +192.0 KB
Content
1727229926561-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +178.0 KB
Content
1727229955611-607.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +100.4 KB
Content
1727229990795-405.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +383.6 KB
Content
1727230012478-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +477.1 KB
Content
1727231038705-173.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +94.6 KB
Content
1727233636007-933.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +114.8 KB
Content
1727484665746-713.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +94.9 KB
Content
1727485118799-984.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +11.8 KB
Content
1727485251053-655.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +20.4 KB
Content
image-20240916101737-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +156.7 KB
Content
image-20240925110638-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +262.7 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0