Skip to Content
Last modified by BoYang Xie on 2025/07/17 15:54
From version 4.12
edited by Edwin Chen
on 2024/09/16 09:37
Change comment: There is no comment for this version
To version 115.1
edited by Xiaoling
on 2024/12/17 17:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,9 +1,14 @@
1 -
1 +(% style="text-align:center" %)
2 2  [[image:image-20240915231842-1.png]]
3 3  
4 4  
5 +
6 +
7 +
8 +
9 +
5 5  (% _mstvisible="1" %)
6 -(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents：**
11 +(% _msthash="315238" _msttexthash="18964465" _mstvisible="3" %)**Table of Contents:**
7 7  
8 8  {{toc/}}
9 9  
... ... @@ -18,11 +18,12 @@
18 18  
19 19  == 1.1  What is LTS5 LoRa HMI touch screen ==
20 20  
21 -LTS5 is a (% style="color:blue" %)LoRa / LoRaWAN HMI Touch Screen(%%) designed for display purpose of IoT project. It have a 5.0" HMI touch screen, and support WiFi, Bluetooch, LoRa wireless protocol.
22 22  
27 +LTS5 is a (% style="color:blue" %)**LoRa / LoRaWAN HMI Touch Screen**(%%) designed for display purpose of IoT project. It have a **5.0" HMI touch screen**, and **support WiFi, Bluetooch, LoRa wireless protocol**.
28 +
23 23  LTS5 is an Open Source software project. The MCU is ESP32 and Dragino LA66 LoRa module. There are lots of development source for ESP32 which can greatly reduce the development time.
24 24  
25 -The HMI touch screen of LTS5 supports drap & drop design. Developer can use SquareLine to easily customize the display UI for different application.
31 +The HMI touch screen of LTS5 **supports drap & drop design**. Developer can use SquareLine to easily customize the display UI for different application.
26 26  
27 27  LTS5 use LA66 LoRa module, this module can be program to support private LoRa protocol or LoRaWAN protocol.
28 28  
... ... @@ -29,7 +29,9 @@
29 29  
30 30  == 1.2  Features ==
31 31  
32 -* ESP32-WROOM MCU + Dragino LA66 LoRa Module
38 +
39 +* ESP32-WROOM MCU: 8MB RAM & 16MB ROM
40 +* Dragino LA66 LoRa Module
33 33  * Support Private LoRa protocol or LoRaWAN protocol
34 34  * Support WiFi & BLE wireless protocol
35 35  * 5.0" HMI touch screen
... ... @@ -40,11 +40,17 @@
40 40  * 5V DC power
41 41  * IP Rating: IP52
42 42  
43 -
44 44  == 1.3  Specification ==
45 45  
53 +
46 46  **LoRa**:
47 47  
56 +* Frequency Range: 870 MHz ~~ 960 MHz
57 +* TCXO crystal to ensure RF performance on low temperature
58 +* Maximum Power +22 dBm constant RF output
59 +* High sensitivity: -148 dBm
60 +* LoRa Tx Current: <90 mA at +17 dBm, 108 mA at +22 dBm
61 +* LoRa Rx current: <9 mA
48 48  
49 49  **WiFi:**
50 50  
... ... @@ -68,15 +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  
87 +
75 75  * External 5V DC power adapter
76 76  
77 77  
78 78  == 1.5  Storage & Operation Temperature ==
79 79  
93 +
80 80  * Operation Temperature: -20 ~~ 70°C  (No Dew)
81 81  * Storage Temperature: -30 ~~ 70°C  (No Dew)
82 82  
... ... @@ -83,6 +83,7 @@
83 83  
84 84  == 1.6  Applications ==
85 85  
100 +
86 86  * Smart Buildings & Home Automation
87 87  * Logistics and Supply Chain Management
88 88  * Smart Metering
... ... @@ -91,721 +91,439 @@
91 91  * Smart Factory
92 92  
93 93  
94 -= 2.  Operation Mode =
109 += 2.  Getting Started with Hello World =
95 95  
96 -== 2.1  How it work? ==
111 +== 2.1  About this demo ==
97 97  
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**.
114 +In this Getting Started 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.
100 100  
101 101  
102 -== 2.2  How to Activate PB01? ==
117 +== 2.2  Install Software Running Environment ==
103 103  
104 104  
105 -(% style="color:red" %)** 1.  Open enclosure from below position.**
120 +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.
106 106  
107 -[[image:image-20220621093835-1.png]]
108 108  
123 +=== 2.2.1 Install VSCode and ESP-IDF extension ===
109 109  
110 -(% style="color:red" %)** 2.  Insert 2 x AAA LR03 batteries and the node is activated.**
111 111  
112 -[[image:image-20220621093835-2.png]]
126 +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]].
113 113  
128 +Next, you need to install the ESP-IDF extension within VSCode. The detailed operation steps are illustrated in image 1.
114 114  
115 -(% style="color:red" %)** 3. Under the above conditions, users can also reactivate the node by long pressing the ACT button.**
130 +[[image:image-20240928110211-5.png||height="508" width="866"]]
116 116  
117 -[[image:image-20220621093835-3.png]]
132 + image 1 ESP-IDF extension install
118 118  
134 +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]]
119 119  
120 -User can check [[LED Status>>||anchor="H2.8LEDIndicator"]] to know the working state of PB01.
121 121  
137 +=== 2.2.2 Install SquareLine Studio ===
122 122  
123 -== 2.3  Example to join LoRaWAN network ==
124 124  
140 +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]].
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.
142 +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.
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. 
130 130  
131 -[[image:image-20240705094824-4.png]]
145 +== 2.3 Simple usage of SquareLine Studio and export UI code ==
132 132  
133 -(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN V3 with the OTAA keys from PB01.
134 134  
135 -Each PB01 is shipped with a sticker with the default DEV EUI as below:
148 +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.
136 136  
137 -[[image:image-20230426083617-1.png||height="294" width="633"]]
150 +[[image:image-20240928103357-2.png||height="680" width="708"]]
138 138  
152 + image 2 create a SquareLine project
139 139  
140 -Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
154 +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.
141 141  
142 -Create application.
156 +[[image:1727229582471-566.png]]
143 143  
144 -choose to create the device manually.
158 + image 3 project settings
145 145  
146 -Add JoinEUI(AppEUI), DevEUI, AppKey.(% style="display:none" %)
160 +[[image:image-20240928105309-4.png||height="526" width="556"]]
147 147  
148 -[[image:image-20240507142116-1.png||height="410" width="1138"]](% style="display:none" %) (%%)
149 -
162 + image 4 modify project settings
150 150  
151 -[[image:image-20240507142157-2.png||height="559" width="1147"]]
164 +Now we can start to use this software. Here are some usage information for this software.
152 152  
153 -[[image:image-20240507142401-3.png||height="693" width="1202"]]
166 +**~1. add widget**
154 154  
155 -[[image:image-20240507142651-4.png||height="760" width="1190"]]
168 +To add a widget, you should click a widget you want to add at the area entitled “Widgets”. In image , demonstrate a add process of label, button, and image 5.
156 156  
157 -**Default mode OTAA**(% style="display:none" %)
170 +[[image:image-20240928111412-6.png||height="526" width="864"]]
158 158  
172 + image 5 add widgets
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.
174 +**2. modify widget**
161 161  
162 -[[image:image-20240507143104-5.png||height="434" width="1398"]]
176 +The area for modifying widgets is called "Inspector". There are four parts in the "Inspector" tab. We use three of them more frequently, excluding "COMPONENT". The second part is aimed at adjusting the layout, size, position, alignment, flags, and states, etc. of widgets. The name of the second part indicates the type of widget it is representing, and in image 6, it is "BUTTON".
163 163  
178 +[[image:1727485118799-984.png]]
164 164  
165 -== 2.4  Uplink Payload ==
180 + image 6 the button widget's "Inspector" tab
166 166  
182 +Second part: "Layout" means a auto position-management for widgets contained in the parent widget. "Transform" includes size, position and align modification.
167 167  
168 -Uplink payloads include two types: Valid Sensor Value and other status / control command.
184 +[[image:1727485251053-655.png]]
169 169  
170 -* Valid Sensor Value: Use FPORT=2
171 -* Other control command: Use FPORT other than 2.
186 +image 7 the button widget's "BUTTON" tab
172 172  
173 -=== 2.4.1  Uplink FPORT~=5, Device Status ===
188 +Third part: It is an area of style setting.
174 174  
190 +Fourth part: It is an area for adding events. In image 8, it is adding a click event to a button. If the button is clicked after the click event is added as shown in image 8, the current screen will fade into another specified screen, and the switching process will last 500ms.
175 175  
176 -Users can  get the Device Status uplink through the downlink command:
192 +[[image:1727485480434-713.png||height="395" width="290"]]
177 177  
178 -(% style="color:#4472c4" %)**Downlink:  **(%%)**0x2601**
194 + image 8 add event for button
179 179  
180 -Uplink the device configures with FPORT=5.
196 +**3. change label widget content**
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
198 +Modify the content in text as shown in image 9, the text content of label widget will be changed accordingly.
185 185  
186 -[[image:image-20240507152130-12.png||height="469" width="1366"]](% style="display:none" %)
200 +[[image:image-20240928090825-1.png||height="327" width="391"]]
187 187  
188 -Example Payload (FPort=5):  [[image:image-20240507152254-13.png||height="26" width="130"]]
202 + image 9 modify text content of label widget
189 189  
204 +**4. Add image into project**
190 190  
191 -(% style="color:#4472c4" %)**Sensor Model**(%%): For PB01, this value is 0x35.
206 +To use the image widget, you should first add an image to your project. The image format must be PNG, and its resolution should not exceed 800x480 pixels. There are two ways to add an image file. One way is to move your image into the folder "…/squareline project/assets/", as shown in image 10. The other way is to click the "ADD FILE INTO ASSETS" button, then select an image from your computer to import. After adding, you can see the image in the "assets" area in SquareLine Studio, as demonstrated in image 11.
192 192  
193 -(% style="color:#4472c4" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version.
208 +[[image:image-20240928113424-9.png||height="355" width="505"]]
194 194  
195 -(% style="color:#4472c4" %)**Frequency Band**:
210 + image 10 add image file into SquareLine Studio project
196 196  
197 -*0x01: EU868
212 +[[image:image-20240928114139-10.png||height="559" width="810"]]
198 198  
199 -*0x02: US915
214 + image 11 use image widget in SquareLine Studio
200 200  
201 -*0x03: IN865
216 +**5. The relationship between widgets**
202 202  
203 -*0x04: AU915
218 +There are two common relationships between widgets: one is parallel, the other is parent-child. The parallel relationship means that widgets' relative position is based on a collective object of reference. In parent-child relationship, the parts of the child object that are outside the boundaries of the parent object are not visible by default. Therefore, we need to adjust the position of the child object so that it falls within the range of the parent object, allowing it to be seen as illustrated in image 13.
204 204  
205 -*0x05: KZ865
220 +[[image:1727486567182-334.png||height="318" width="278"]]
206 206  
207 -*0x06: RU864
222 +image 12 move label1 to make label1 widget be a child of button1 widget(1)
208 208  
209 -*0x07: AS923
224 +[[image:image-20240928112001-8.png||height="431" width="796"]]
210 210  
211 -*0x08: AS923-1
226 + image 13 move label1 to make label1 widget be a child of button1 widget(2)
212 212  
213 -*0x09: AS923-2
228 +**6. Preview the final effect**
214 214  
215 -*0x0a: AS923-3
230 +An advantage of this kind of software is that you can edit the UI with quick previews. In other words, it provides a way of combining graphical programming with simulation immediately.
216 216  
232 +[[image:1727487368023-281.png]]
217 217  
218 -(% style="color:#4472c4" %)**Sub-Band**(%%): value 0x00 ~~ 0x08(only for CN470, AU915,US915. Others are0x00)
234 + image 14 click on the triangle icon to start or end the simulation
219 219  
220 -(% style="color:#4472c4" %)**BAT**(%%): shows the battery voltage for PB01.
236 +For more detailed usage, please visit the official link: [[SquareLine Studio 1.4.2 Documentation ~| SquareLine Studio>>url:https://docs.squareline.io/docs/squareline/]].
221 221  
222 -(% style="color:#4472c4" %)**Ex1**(%%): 0x0C DE = 3294mV
223 223  
239 +== 2.4 Integrate UI Code to ESP-IDF Project ==
224 224  
225 -=== 2.4.2  Uplink FPORT~=2, Real time sensor value ===
226 226  
242 +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.
227 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"]].
244 +[[image:1727229798126-306.png]]
229 229  
230 -Uplink uses FPORT=2 and every 20 minutes send one uplink by default.
246 + image 15 export UI file
231 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 +[[image:1727229821582-258.png||height="333" width="662"]]
248 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 -)))
250 + image 16 exported UI file
261 261  
262 -Example in TTN.
252 +Create a empty directory entitled "ui" in path "basic_prj/app_components/ui/", and then copy all UI code exported to this directory.
263 263  
264 -[[image:image-20240507150155-11.png||height="549" width="1261"]]
254 +[[image:image-20240928144830-11.png]]
265 265  
266 -Example Payload (FPort=2):  (% style="background-color:yellow" %)**0C EA 03 01 01 11 02 A8**
256 + image 17 open CMakeLists.txt
267 267  
268 -==== (% style="color:blue" %)**Battery:**(%%) ====
258 +[[image:1727229892636-154.png||height="521" width="407"]]
269 269  
270 -Check the battery voltage.
260 + image 18 modify CMakeLists.txt
271 271  
272 -* Ex1: 0x0CEA = 3306mV
273 -* Ex2: 0x0D08 = 3336mV
262 +The last step of integrating is adding two lines of code in main.c file.
274 274  
275 -==== (% style="color:blue" %)**Sound_ACK & Sound_key:**(%%) ====
264 +[[image:1727229926561-300.png]]
276 276  
277 -Key sound and ACK sound are enabled by default.
266 + image 19 add "ui.h"
278 278  
279 -* Example1: 0x03
268 +[[image:1727229955611-607.png]]
280 280  
281 - Sound_ACK: (03>>1) & 0x01=1, OPEN.
270 + image 20 add "ui_init()"
282 282  
283 -**~ ** Sound_key:  03 & 0x01=1, OPEN.
284 284  
285 -* Example2: 0x01
273 +== 2.5 Brief introduction of hello world project ==
286 286  
287 - Sound_ACK: (01>>1) & 0x01=0, CLOSE.
288 288  
289 -**~ ** Sound_key:  01 & 0x01=1, OPEN.
276 +The project consists of two screens. The first screen displays the company's logo, the project name, and a button to navigate to the next screen. The second screen presents some information about this HMI screen product through an image and includes a button to return to the previous screen.
290 290  
291 291  
292 -==== (% style="color:blue" %)**Alarm:**(%%) ====
279 +== 2.6 Test Result ==
293 293  
294 -Key alarm.
295 295  
296 -* Ex1: 0x01 & 0x01=1, TRUE.
297 -* Ex2: 0x00 & 0x01=0, FALSE.
282 +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.
298 298  
299 -==== (% style="color:blue" %)**Temperature:**(%%) ====
284 +[[image:1727488067077-684.png||height="402" width="574"]]
300 300  
301 -* Example1:  0x0111/10=27.3℃
302 -* Example2:  (0xFF0D-65536)/10=-24.3℃
286 + image 21 screen1
303 303  
304 -If payload is: FF0D :  (FF0D & 8000 == 1) , temp = (FF0D - 65536)/100 =-24.3℃
288 +[[image:1727488157579-949.png||height="397" width="572"]]
305 305  
306 -（FF0D & 8000：Judge whether the highest bit is 1, when the highest bit is 1, it is negative）
290 + image 22 screen2
307 307  
308 308  
309 -==== (% style="color:blue" %)**Humidity:**(%%) ====
293 += 3. Example Project 1: LoRa Central Display =
310 310  
311 -* Humidity:    0x02A8/10=68.0%
295 +[[image:image-20240916101737-1.png||height="468" width="683"]]
312 312  
313 -=== 2.4.3  Uplink FPORT~=3, Datalog sensor value ===
314 314  
298 += 4. Example Project 2: LoRaWAN RS485 Alarm =
315 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.
300 += 5.  The way to add a new panel to project =
317 317  
318 -[[image:image-20240510144912-1.png||height="471" width="1178"]](% style="display:none" %)
302 +**~1. Design a panel in SquareLine Studio, using image 5.1 below as a reference.**
319 319  
304 +[[image:image-20241121113445-1.png||height="584" width="934"]]
320 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" %)
306 + image 5.1 a panel about water_leak
322 322  
323 -For example, in US915 band, the max payload for different DR is:
308 +**2. Export the ui file.** You need  to adjust the export path first, then click "Export->Export UI Files". This step had been introduced before. Then you can get the ui files as shown in image 5.2.
324 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.
310 +[[image:image-20241121141120-4.png||height="383" width="795"]]
329 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.**
312 + image 5.2 ui files exported
331 331  
332 -See more info about the [[Datalog feature>>||anchor="H2.6A0DatalogFeature"]].
314 +**3. Delete or rename some file.** Here are the steps:
333 333  
334 -(% style="display:none" %) (%%)
316 + Step1 Delete the 'components' directory.
317 + Step2 Delete 'filelist.txt'.
318 + Step3 Delete 'ui_helpers.c' and 'ui_helpers.h'.
319 + Step4 Rename 'ui_ScreenMain.c' in the 'screens' directory to 'ui_water_leak_style.c'.
320 + Step5 Rename the 'screens' directory to 'styles'.
335 335  
336 -=== 2.4.4  Decoder in TTN V3 ===
322 +[[image:image-20241121151934-10.png||height="303" width="792"]]
337 337  
324 + image 5.3 rest file (1)
338 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.
326 +[[image:image-20241121142925-7.png||height="141" width="793"]]
340 340  
341 -In TTN , add formatter as below:
328 + image 5.4 rest file (2)
342 342  
343 -[[image:image-20240507162814-16.png||height="778" width="1135"]]
330 +**4. Open this project in vscode.**
344 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 -)))
332 +5. Add file include path about water_leak in extra_lib/CMakeLists.txt as shown in image 5.5, 5.6, and its format is similar to the tem_hum or door.
348 348  
349 -(((
350 -
351 -)))
334 +[[image:image-20241121181957-17.png||height="438" width="516"]]
352 352  
353 -== 2.5 Show data on Datacake ==
336 + image 5.5 extra_lib/CMakeLists.txt before add
354 354  
338 +[[image:image-20241121182239-18.png||height="520" width="518"]]
355 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 -)))
340 + image 5.6 extra_lib/CMakeLists.txt after add
359 359  
360 -(((
361 -
362 -)))
342 +**6. Modify header file include in fonts and images directory.** Open the fonts/ui_font_Font12.c file, as shown in image 5.7, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.8 is the modified image. Other font file need to be modified in same way.
363 363  
364 -(((
365 -(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the LoRaWAN network.
366 -)))
344 +[[image:image-20241121171629-11.png]]
367 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 -)))
346 + image 5.7 before-modified font file
371 371  
372 -(((
373 -~1. Add Datacake:
374 -)))
348 +[[image:image-20241121171901-12.png]]
375 375  
376 -(((
377 -2. Select default key as Access Key:
378 -)))
350 + image 5.8 modified font file
379 379  
380 -(((
381 -3. In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add PB01:
382 -)))
352 +Open the images/ui_img_battery_empty_png.c file, as shown in image 5.9, then modify the '#include "../ui.h"' to '#include "../ui_water_leak.h"', the image 5.10 is the modified image. Other image file need to be modified in same way.
383 383  
384 -(((
385 - Please refer to the figure below.
386 -)))
354 +[[image:image-20241121172714-13.png]]
387 387  
388 -[[image:image-20240510150924-2.png||height="612" width="1186"]]
356 + image 5.9 before-modified image file
389 389  
358 +[[image:image-20241121172908-14.png]]
390 390  
391 -Log in to DATACAKE, copy the API under the account.
360 + image 5.10 modified image file
392 392  
393 -[[image:image-20240510151944-3.png||height="581" width="1191"]]
362 +**7. Modify the ui_water_leak/CMakeLists.txt.** Open this file, and modify it from image 5.11 to image 5.12.
394 394  
364 +[[image:image-20241121180030-15.png]]
395 395  
366 + image 5.11 ui_water_leak/CMakeLists.txt before modification
396 396  
397 -[[image:image-20240510152150-4.png||height="697" width="1188"]]
368 +[[image:image-20241121180517-16.png]]
398 398  
370 + image 5.12 ui_water_leak/CMakeLists.txt after modification
399 399  
400 -[[image:image-20240510152300-5.png||height="298" width="1191"]]
372 +**8. Modify ui_water_leak.h file.** The image 5.13, 5.14 show the code before modification, and the image 5.15, 5.16 show the code after modification.
401 401  
374 +[[image:image-20241122094200-23.png]]
402 402  
403 -[[image:image-20240510152355-6.png||height="782" width="1193"]]
376 + image 5.13 ui_water_leak.h (1) before modification
404 404  
405 -[[image:image-20240510152542-8.png||height="545" width="739"]]
378 +[[image:image-20241122094320-24.png||height="852" width="554"]]
406 406  
407 -[[image:image-20240510152634-9.png||height="748" width="740"]]
380 + image 5.14 ui_water_leak.h (2) before modification
408 408  
382 +[[image:image-20241122094600-25.png||height="1078" width="554"]]
409 409  
410 -[[image:image-20240510152809-10.png||height="607" width="732"]]
384 + image 5.15 ui_water_leak.h (1) after modification
411 411  
412 -[[image:image-20240510153934-14.png||height="460" width="1199"]]
386 +[[image:image-20241122094719-26.png||height="941" width="583"]]
413 413  
388 + image 5.16 ui_water_leak.h (2) before modification
414 414  
415 -[[image:image-20240510153435-12.png||height="428" width="1197"]]
390 +**9. Modify ui_water_leak.c file.** The image 5.17, 5.18, 5.19 show the code before modification, and the image 5.20, 5.21, 5.22 show the code after modification.
416 416  
392 +_ui_flag_modify( ((lv_obj_t *)(e->user_data)), LV_OBJ_FLAG_HIDDEN, _UI_MODIFY_FLAG_TOGGLE);  This code replaces 4 lines of code in ui_water_leak.c, so it is pasted here for convenience.
417 417  
418 -Copy and paste the [[TTN decoder>>https://github.com/dragino/dragino-end-node-decoder]] here and save.
394 +[[image:image-20241122102929-27.png||height="619" width="426"]]
419 419  
420 -[[image:image-20240510153624-13.png||height="468" width="1195"]]
396 + image 5.17 ui_water_leak.c (1) before modification
421 421  
398 +[[image:image-20241122112838-30.png||height="551" width="628"]]
422 422  
423 -Visual widgets please read the DATACAKE documentation.
400 + image 5.18 ui_water_leak.c (2) before modification
424 424  
425 -(% style="display:none" %) (%%)
402 +[[image:image-20241122110815-29.png||height="725" width="712"]]
426 426  
427 -== 2.6  Datalog Feature ==
404 + image 5.19 ui_water_leak.c (3) before modification
428 428  
406 +[[image:image-20241122113158-31.png||height="872" width="677"]]
429 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.
408 + image 5.20 ui_water_leak.c (1) after modification
432 432  
410 +[[image:image-20241122113259-33.png||height="874" width="724"]]
433 433  
434 -=== 2.6.1  Unix TimeStamp ===
412 + image 5.21 ui_water_leak.c (2) after modification
435 435  
414 +[[image:image-20241122113359-34.png||height="804" width="746"]]
436 436  
437 -Unix TimeStamp shows the sampling time of uplink payload. format base on
416 + image 5.22 ui_water_leak.c (3) after modification
438 438  
439 -[[image:image-20220523001219-11.png||_mstalt="450450" _mstvisible="3" height="97" width="627"]]
418 +**10. Modify ui_water_leak_events.h file.** The image 5.23 show the code before modification, and the image 5.24 show the code after modification.
440 440  
441 -User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/||_mstvisible="3"]] :
420 +[[image:image-20241122134113-35.png||height="380" width="421"]]
442 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)
422 + image 5.23 ui_water_leak_events_.h before modification
444 444  
424 +[[image:image-20241122134420-37.png||height="201" width="283"]]
445 445  
446 -[[image:1655782409139-256.png]]
426 +image 5.24 ui_water_leak_events_.h after modification
447 447  
428 +**11. Modify ui_water_leak_events.c file.** The image 5.25 show the code before modification, and the image 5.26 show the code after modification.
448 448  
449 -=== 2.6.2  Poll sensor value ===
430 +Step1. '#include "ui.h"'~-~->'#include "ui_water_leak.h"'
450 450  
432 +Step2. add code  below in delete_object() function definition.
451 451  
452 -(((
453 -User can poll sensor value based on timestamps from the server. Below is the downlink command.
454 -)))
434 + panel_all * panel = find_upper_by_SensorPanel(&arr,((lv_obj_t *)(e->user_data~)~)~);
455 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 -)))
436 + size_t index = panel->panel_obj_index;
459 459  
460 -(((
461 -For example, downlink command [[image:image-20220621113526-13.png]] (% _mstvisible="3" style="display:none" %)
462 -)))
438 + deleteElement(&arr, index);
463 463  
464 -(((
465 -Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00's data
466 -)))
440 +[[image:image-20241122135023-38.png||height="358" width="372"]]
467 467  
468 -(((
469 -Uplink Internal =5s，means PB01 will send one packet every 5s. range 5~~255s.
470 -)))
442 + image 5.25 ui_water_leak_events_.c before modification
471 471  
444 +[[image:image-20241122135258-39.png||height="403" width="559"]]
472 472  
473 -=== 2.6.3  Datalog Uplink payload ===
446 + image 5.26 ui_water_leak_events_.c after modification
474 474  
448 +**12. Modify ui_water_leak_style.c file.**
475 475  
476 -See [[Uplink FPORT=3, Datalog sensor value>>||anchor="H2.4.3A0UplinkFPORT3D32CDatalogsensorvalue"]]
450 +Step1. '#include "../ui.h"'~-~->#include '"../ui_water_leak.h"'
477 477  
478 -(% style="display:none" %) (%%) (% style="display:none" %)
452 + add '#include "../../sort.h"'
479 479  
480 -== 2.7 Button ==
454 + add '#include "ui.h"'
481 481  
456 +[[image:image-20241122141536-41.png||height="361" width="612"]]
482 482  
483 -* ACT button
458 + image 5.27 ui_water_leak_style.c (1) before modification
484 484  
485 -Long press this button PB01 will reset and join network again.
460 +[[image:image-20241122142129-42.png||height="386" width="613"]]
486 486  
487 -[[image:image-20240510161626-17.png||height="192" width="224"]]
462 + image 5.28 ui_water_leak_style.c (1) after modification
488 488  
489 -* Alarm button
464 +Step2. modify 'void ui_ScreenMain_screen_init(void)'~-~->'panel_with_type create_water_leak(uint8_t index)'
490 490  
491 -Press the button PB01 will immediately uplink data, and alarm is "TRUE".
466 + delete code as shown in image 5.29
492 492  
493 -[[image:image-20240705095149-5.png||height="164" width="162"]](% style="display:none" %)
468 +[[image:image-20241122145620-44.png||height="757" width="671"]]
494 494  
470 + image 5.29 ui_water_leak_style.c (2)
495 495  
496 -== 2.8 LED Indicator ==
472 +Step3. The image 5.30, 5.31 show the change.
497 497  
474 +[[image:image-20241122152026-45.png||height="277" width="828"]]
498 498  
499 -(((
500 -The PB01 has a triple color LED which for easy showing different stage.
501 -)))
476 + image 5.30 ui_water_leak_style.c (3) before modification
502 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
478 +[[image:image-20241122152542-46.png||height="293" width="830"]]
504 504  
505 -(((
506 -(% style="color:#037691" %)**In a normal working state**:
507 -)))
480 + image 5.31 ui_water_leak_style.c (3) after modification
508 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.
482 +Step4. Copy partly the code in ui_water_leak.c, paste at extra_lib/sort.h(The process is shown in image 5.32, 5.33).
515 515  
516 -(((
517 -
518 -)))
484 +[[image:image-20241122153958-47.png]]
519 519  
520 -== 2.9 Buzzer ==
486 + image 5.32 ui_water_leak_style.c (4)
521 521  
488 +[[image:image-20241122154755-49.png||height="864" width="513"]]
522 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"]].
490 + image 5.33 ui_water_leak_style.c (4)
524 524  
525 -* (% style="color:#4f81bd" %)**Button sound**(%%)** **is the music produced by the node after the alarm button is pressed.
492 +Step5. Delete event function in code which was just pasted in extra_lib/sort.h(The process is shown in image 5.34).
526 526  
527 - Users can use[[ AT+OPTION>>||anchor="H3.4A0Setbuzzermusic2807E429"]] to set different button sounds.
494 +[[image:image-20241122155650-50.png||height="922" width="513"]]
528 528  
529 -* (% style="color:#4f81bd" %)**ACK sound **(%%)is the notification tone that the node receives ACK.
496 + image 5.34 ui_water_leak_style.c (5)
530 530  
531 -= 3.  Configure PB01 via AT command or LoRaWAN downlink =
498 +Step6. Add some lines of code in extra_lib/sort.h as shown in image 5.35.
532 532  
500 +[[image:image-20241122161934-51.png]]
533 533  
534 -Users can configure PB01 via AT Command or LoRaWAN Downlink.
502 + image 5.35
535 535  
536 -* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
504 +Step7. Add a line of code in extra_lib/sort.h as shown in image 5.36.
537 537  
538 -* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
506 +[[image:image-20241122162852-53.png||height="330" width="529"]]
539 539  
540 -There are two kinds of commands to configure PB01, they are:
508 + image 5.37
541 541  
542 -* (% style="color:#4f81bd" %)**General Commands:**
510 +Step8. Add some code in ui_water_leak_style.c as shown in image 5.38 from line534 to line 576 in detail.
543 543  
544 -These commands are to configure:
512 +panel_with_type union_sensor;
545 545  
546 -* General system settings like: uplink interval.
514 +union_sensor.panel_type = WATER_LEAK_TYPE;
547 547  
548 -* LoRaWAN protocol & radio-related commands.
516 +......
549 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]]
518 +lv_obj_set_x(union_sensor.panel_union.door.ui_PanelSensorDoor, x_by_index(index));
551 551  
520 +lv_obj_set_y(union_sensor.panel_union.door.ui_PanelSensorDoor, y_by_index(index));
552 552  
553 -* (% style="color:#4f81bd" %)**Commands special design for PB01**
522 +return union_sensor;
554 554  
555 -These commands are only valid for PB01, as below:
524 +[[image:image-20241122171211-54.png||height="635" width="792"]]
556 556  
557 -(% style="display:none" %) (%%)
526 + image 5.38
558 558  
559 -== 3.1  Downlink Command Set ==
528 +**13. Modify sort.c file.**
560 560  
530 +Add a line of code ~-~-'#include "ui_water_leak.h"' as shown in image 5.39 line 16.
561 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 -
532 +[[image:image-20241122173718-56.png||height="378" width="579"]]
566 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=
534 + image 5.39 sort.c (1)
577 577  
578 -300(seconds)
579 -)))
536 +There are still some changes need to be done in sort.c, and omit here for the moment.
580 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 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 ==
541 +== 6.1 ==
809 809  
810 810  
811 811  = 7. Order Info =
... ... @@ -812,12 +812,13 @@
812 812  
813 813  == 7.1  Part Number ==
814 814  
548 +
815 815  Part Number: (% style="color:#4472c4" %)LTS5
816 816  
817 -
818 818  
819 819  == 7.2  Packing Info ==
820 820  
554 +
821 821  **Package Includes**:
822 822  
823 823  * LTS5 HMI Touch Screen
... ... @@ -824,20 +824,19 @@
824 824  * 5V,2A DC Power Adapter.
825 825  * USB Type C Program Cable
826 826  
827 -
828 828  = 8. Support =
829 829  
563 +
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  
569 +
836 836  * Datasheet
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
1727485480434-713.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +24.7 KB
Content
1727485933579-550.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +55.6 KB
Content
1727485953726-175.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +91.6 KB
Content
1727486567182-334.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +42.6 KB
Content
1727486578489-774.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +66.0 KB
Content
1727487368023-281.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +28.5 KB
Content
1727488067077-684.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +604.7 KB
Content
1727488099947-341.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +877.7 KB
Content
1727488108117-780.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +877.7 KB
Content
1727488157579-949.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +877.7 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
image-20240928090825-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +30.2 KB
Content
image-20240928103357-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +153.7 KB
Content
image-20240928103506-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +197.7 KB
Content
image-20240928105309-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +80.2 KB
Content
image-20240928110211-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +228.0 KB
Content
image-20240928111412-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +150.9 KB
Content
image-20240928111654-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +105.4 KB
Content
image-20240928112001-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +75.6 KB
Content
image-20240928113424-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +50.8 KB
Content
image-20240928114139-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +114.3 KB
Content
image-20240928144830-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +25.5 KB
Content
image-20241121113445-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +250.0 KB
Content
image-20241121120222-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +44.8 KB
Content
image-20241121120830-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +42.6 KB
Content
image-20241121141120-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +41.7 KB
Content
image-20241121141315-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +29.4 KB
Content
image-20241121141329-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +29.4 KB
Content
image-20241121142925-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.8 KB
Content
image-20241121145915-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +61.0 KB
Content
image-20241121150911-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +73.0 KB
Content
image-20241121151934-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +32.9 KB
Content
image-20241121171629-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +16.9 KB
Content
image-20241121171901-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20241121172714-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +26.4 KB
Content
image-20241121172908-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +27.1 KB
Content
image-20241121180030-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
image-20241121180517-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +26.5 KB
Content
image-20241121181957-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +59.3 KB
Content
image-20241121182239-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
image-20241122092239-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +270.9 KB
Content
image-20241122092655-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +251.6 KB
Content
image-20241122093445-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +128.9 KB
Content
image-20241122093601-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +120.0 KB
Content
image-20241122094200-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +289.2 KB
Content
image-20241122094320-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +182.4 KB
Content
image-20241122094600-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +136.0 KB
Content
image-20241122094719-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +129.5 KB
Content
image-20241122102929-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +219.9 KB
Content
image-20241122104344-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +257.1 KB
Content
image-20241122110815-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +246.1 KB
Content
image-20241122112838-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +263.9 KB
Content
image-20241122113158-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +133.7 KB
Content
image-20241122113252-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20241122113259-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +152.3 KB
Content
image-20241122113359-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +126.5 KB
Content
image-20241122134113-35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +69.3 KB
Content
image-20241122134412-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20241122134420-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +14.9 KB
Content
image-20241122135023-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +28.7 KB
Content
image-20241122135258-39.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +40.3 KB
Content
image-20241122141526-40.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20241122141536-41.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20241122142129-42.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20241122143105-43.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +60.2 KB
Content
image-20241122145620-44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +394.0 KB
Content
image-20241122152026-45.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +201.6 KB
Content
image-20241122152542-46.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +95.3 KB
Content
image-20241122153958-47.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +241.1 KB
Content
image-20241122154745-48.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20241122154755-49.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +135.7 KB
Content
image-20241122155650-50.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +104.4 KB
Content
image-20241122161934-51.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +230.3 KB
Content
image-20241122162612-52.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +58.7 KB
Content
image-20241122162852-53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +125.5 KB
Content
image-20241122171211-54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +173.3 KB
Content
image-20241122173706-55.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20241122173718-56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.xieby
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content