Wiki source code of UV254-LB -- LoRaWAN UVC Radiation Sensor User Manual
Last modified by Xiaoling on 2024/01/16 10:20
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | (% style="text-align:center" %) | ||
2 | [[image:image-20230606171857-4.png||height="527" width="425"]] | ||
3 | |||
4 | |||
5 | (% style="display:none" %) (%%) | ||
6 | |||
7 | |||
8 | **Table of Contents:** | ||
9 | |||
10 | {{toc/}} | ||
11 | |||
12 | |||
13 | |||
14 | |||
15 | |||
16 | |||
17 | = 1. Introduction = | ||
18 | |||
19 | == 1.1 What is LoRaWAN UVC Radiation Sensor == | ||
20 | |||
21 | |||
22 | ((( | ||
23 | The Dragino UV254-LB is a (% style="color:blue" %)**LoRaWAN UVC Radiation Sensor**(%%) for Internet of Things solution. UV254-LB is an indoor UVC sensor specially designed for (% style="color:blue" %)**detecting the intensity of ultraviolet lamps**(%%). UV254-LB will convert the UVC Intensity to LoRaWAN wireless data and send to IoT platform via LoRaWAN gateway. | ||
24 | |||
25 | UVC is harmful to human health, and UVC lamp will lose efficacy after long time use. With UV254-LB, administrator can know if the UVC lamp is operate efficacy and make sure it won't work in unexpected time. | ||
26 | |||
27 | The LoRa wireless technology used in UV254-LB allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. | ||
28 | ))) | ||
29 | |||
30 | ((( | ||
31 | UV254-LB supports BLE configure and wireless OTA update which make user easy to use. | ||
32 | ))) | ||
33 | |||
34 | ((( | ||
35 | UV254-LB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years. | ||
36 | ))) | ||
37 | |||
38 | ((( | ||
39 | Each UV254-LB is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on. | ||
40 | ))) | ||
41 | |||
42 | [[image:1686041140110-589.png]] | ||
43 | |||
44 | |||
45 | == 1.2 Features == | ||
46 | |||
47 | |||
48 | * LoRaWAN 1.0.3 Class A | ||
49 | * Ultra-low power consumption | ||
50 | * Detect UVC lamp working status | ||
51 | * Detect UVC lamp working efficiency | ||
52 | * Peak response spectrum 254nm | ||
53 | * Monitor Battery Level | ||
54 | * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865 | ||
55 | * Support Bluetooth v5.1 and LoRaWAN remote configure | ||
56 | * Support wireless OTA update firmware | ||
57 | * Uplink on periodically | ||
58 | * Downlink to change configure | ||
59 | * 8500mAh Battery for long term use | ||
60 | |||
61 | == 1.3 Specification == | ||
62 | |||
63 | |||
64 | (% style="color:#037691" %)**Common DC Characteristics:** | ||
65 | |||
66 | * Supply Voltage: 2.5v ~~ 3.6v | ||
67 | * Operating Temperature: -40 ~~ 85°C | ||
68 | |||
69 | (% style="color:#037691" %)**Probe Spec :** | ||
70 | |||
71 | * Measuring range 0~5mw/cm ² | ||
72 | * Response spectrum range 254nm±5nm | ||
73 | * Peak response spectrum 254nm | ||
74 | |||
75 | (% style="color:#037691" %)**LoRa Spec:** | ||
76 | |||
77 | * Frequency Range, Band 1 (HF): 862 ~~ 1020 Mhz,Band 2 (LF): 410 ~~ 528 Mhz | ||
78 | * Max +22 dBm constant RF output vs. | ||
79 | * RX sensitivity: down to -139 dBm. | ||
80 | * Excellent blocking immunity | ||
81 | |||
82 | (% style="color:#037691" %)**Battery:** | ||
83 | |||
84 | * Li/SOCI2 un-chargeable battery | ||
85 | * Capacity: 8500mAh | ||
86 | * Self-Discharge: <1% / Year @ 25°C | ||
87 | * Max continuously current: 130mA | ||
88 | * Max boost current: 2A, 1 second | ||
89 | |||
90 | (% style="color:#037691" %)**Power Consumption** | ||
91 | |||
92 | * Sleep Mode: 5uA @ 3.3v | ||
93 | * LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm | ||
94 | |||
95 | == 1.4 Use Environment == | ||
96 | |||
97 | |||
98 | Detect UV Lamps Status in difference environment as below | ||
99 | |||
100 | [[image:image-20230606165517-3.png]] | ||
101 | |||
102 | |||
103 | == 1.5 Sleep mode and working mode == | ||
104 | |||
105 | |||
106 | (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life. | ||
107 | |||
108 | (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode. | ||
109 | |||
110 | |||
111 | == 1.6 Button & LEDs == | ||
112 | |||
113 | |||
114 | [[image:1675071855856-879.png]] | ||
115 | |||
116 | |||
117 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
118 | |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 226px;background-color:#4F81BD;color:white" %)**Action** | ||
119 | |(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT between 1s < time < 3s|(% style="background-color:#f2f2f2; width:117px" %)Send an uplink|(% style="background-color:#f2f2f2; width:225px" %)((( | ||
120 | If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
121 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
122 | ))) | ||
123 | |(% style="background-color:#f2f2f2; width:167px" %)Pressing ACT for more than 3s|(% style="background-color:#f2f2f2; width:117px" %)Active Device|(% style="background-color:#f2f2f2; width:225px" %)((( | ||
124 | (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to JOIN LoRaWAN network. | ||
125 | (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
126 | Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network. | ||
127 | ))) | ||
128 | |(% style="background-color:#f2f2f2; width:167px" %)Fast press ACT 5 times.|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device|(% style="background-color:#f2f2f2; width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means UV254-LB is in Deep Sleep Mode. | ||
129 | |||
130 | == 1.7 BLE connection == | ||
131 | |||
132 | |||
133 | UV254-LB support BLE remote configure. | ||
134 | |||
135 | BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case: | ||
136 | |||
137 | * Press button to send an uplink | ||
138 | * Press button to active device. | ||
139 | * Device Power on or reset. | ||
140 | |||
141 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
142 | |||
143 | |||
144 | == 1.8 Mechanical == | ||
145 | |||
146 | |||
147 | [[image:1675143884058-338.png]] | ||
148 | |||
149 | |||
150 | [[image:1675143899218-599.png]] | ||
151 | |||
152 | |||
153 | [[image:1675143909447-639.png]] | ||
154 | |||
155 | |||
156 | = 2. Configure UV254-LB to connect to LoRaWAN network = | ||
157 | |||
158 | == 2.1 How it works == | ||
159 | |||
160 | |||
161 | The UV254-LB is configured as (% style="color:#037691" %)**LoRaWAN OTAA Class A**(%%) mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and activate the UV254-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes. | ||
162 | |||
163 | |||
164 | == 2.2 Quick guide to connect to LoRaWAN server (OTAA) == | ||
165 | |||
166 | |||
167 | Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example. | ||
168 | |||
169 | [[image:1686043201033-441.png]] | ||
170 | |||
171 | |||
172 | The LPS8V2 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server. | ||
173 | |||
174 | |||
175 | (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from UV254-LB. | ||
176 | |||
177 | Each UV254-LB is shipped with a sticker with the default device EUI as below: | ||
178 | |||
179 | [[image:image-20230426085320-1.png||height="234" width="504"]] | ||
180 | |||
181 | |||
182 | You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot: | ||
183 | |||
184 | |||
185 | (% style="color:blue" %)**Register the device** | ||
186 | |||
187 | [[image:1675144099263-405.png]] | ||
188 | |||
189 | |||
190 | (% style="color:blue" %)**Add APP EUI and DEV EUI** | ||
191 | |||
192 | [[image:1675144117571-832.png]] | ||
193 | |||
194 | |||
195 | (% style="color:blue" %)**Add APP EUI in the application** | ||
196 | |||
197 | |||
198 | [[image:1675144143021-195.png]] | ||
199 | |||
200 | |||
201 | (% style="color:blue" %)**Add APP KEY** | ||
202 | |||
203 | [[image:1675144157838-392.png]] | ||
204 | |||
205 | (% style="color:blue" %)**Step 2:**(%%) Activate on UV254-LB | ||
206 | |||
207 | |||
208 | Press the button for 5 seconds to activate the UV254-LB. | ||
209 | |||
210 | (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:blue" %)**OTA mode**(%%) for 3 seconds. And then start to JOIN LoRaWAN network. (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
211 | |||
212 | After join success, it will start to upload messages to TTN and you can see the messages in the panel. | ||
213 | |||
214 | |||
215 | == 2.3 Uplink Payload == | ||
216 | |||
217 | === 2.3.1 Device Status, FPORT~=5 === | ||
218 | |||
219 | |||
220 | Include device configure status. Once UV254-LB Joined the network, it will uplink this message to the server. | ||
221 | |||
222 | Users can also use the downlink command(0x26 01) to ask UV254-LB to resend this uplink. | ||
223 | |||
224 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
225 | |(% colspan="6" style="background-color:#4f81bd; color:white" %)**Device Status (FPORT=5)** | ||
226 | |(% style="background-color:#f2f2f2; width:103px" %)**Size (bytes)**|(% style="background-color:#f2f2f2; width:72px" %)**1**|(% style="background-color:#f2f2f2" %)**2**|(% style="background-color:#f2f2f2; width:91px" %)**1**|(% style="background-color:#f2f2f2; width:86px" %)**1**|(% style="background-color:#f2f2f2; width:44px" %)**2** | ||
227 | |(% style="background-color:#f2f2f2; width:103px" %)Value|(% style="background-color:#f2f2f2; width:72px" %)Sensor Model|(% style="background-color:#f2f2f2" %)Firmware Version|(% style="background-color:#f2f2f2; width:91px" %)Frequency Band|(% style="background-color:#f2f2f2; width:86px" %)Sub-band|(% style="background-color:#f2f2f2; width:44px" %)BAT | ||
228 | |||
229 | Example parse in TTNv3 | ||
230 | |||
231 | [[image:1675144504430-490.png]] | ||
232 | |||
233 | |||
234 | (% style="color:#037691" %)**Sensor Model**(%%): For UV254-LB, this value is 0x16 | ||
235 | |||
236 | (% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version | ||
237 | |||
238 | (% style="color:#037691" %)**Frequency Band**: | ||
239 | |||
240 | 0x01: EU868 | ||
241 | |||
242 | 0x02: US915 | ||
243 | |||
244 | 0x03: IN865 | ||
245 | |||
246 | 0x04: AU915 | ||
247 | |||
248 | 0x05: KZ865 | ||
249 | |||
250 | 0x06: RU864 | ||
251 | |||
252 | 0x07: AS923 | ||
253 | |||
254 | 0x08: AS923-1 | ||
255 | |||
256 | 0x09: AS923-2 | ||
257 | |||
258 | 0x0a: AS923-3 | ||
259 | |||
260 | 0x0b: CN470 | ||
261 | |||
262 | 0x0c: EU433 | ||
263 | |||
264 | 0x0d: KR920 | ||
265 | |||
266 | 0x0e: MA869 | ||
267 | |||
268 | |||
269 | (% style="color:#037691" %)**Sub-Band**: | ||
270 | |||
271 | AU915 and US915:value 0x00 ~~ 0x08 | ||
272 | |||
273 | CN470: value 0x0B ~~ 0x0C | ||
274 | |||
275 | Other Bands: Always 0x00 | ||
276 | |||
277 | |||
278 | (% style="color:#037691" %)**Battery Info**: | ||
279 | |||
280 | Check the battery voltage. | ||
281 | |||
282 | Ex1: 0x0B45 = 2885mV | ||
283 | |||
284 | Ex2: 0x0B49 = 2889mV | ||
285 | |||
286 | |||
287 | === 2.3.2 Sensor value, FPORT~=2 === | ||
288 | |||
289 | |||
290 | Uplink payload includes in total 9 bytes. | ||
291 | |||
292 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
293 | |(% colspan="6" style="background-color:#4f81bd; color:white" %)**evice Status (FPORT=2)** | ||
294 | |(% style="background-color:#f2f2f2; width:103px" %)**Size (bytes)**|(% style="background-color:#f2f2f2; width:72px" %)**2**|(% style="background-color:#f2f2f2" %)**2**|(% style="background-color:#f2f2f2; width:91px" %)**2**|(% style="background-color:#f2f2f2; width:86px" %)**2**|(% style="background-color:#f2f2f2; width:44px" %)**1** | ||
295 | |(% style="background-color:#f2f2f2; width:103px" %)Value|(% style="background-color:#f2f2f2; width:72px" %)BAT|(% style="background-color:#f2f2f2" %)Probe Model|(% style="background-color:#f2f2f2; width:91px" %)0 ~~ 20mA value|(% style="background-color:#f2f2f2; width:86px" %)((( | ||
296 | UVC Value(0 ~~ 5v value) | ||
297 | )))|(% style="background-color:#f2f2f2; width:44px" %)IN1 &IN2 Interrupt flag | ||
298 | |||
299 | (% class="wikigeneratedid" id="H" %) | ||
300 | [[image:image-20230607180529-1.png||height="181" width="1101"]] | ||
301 | |||
302 | |||
303 | === 2.3.3 Battery Info === | ||
304 | |||
305 | |||
306 | Check the battery voltage for UV254-LB. | ||
307 | |||
308 | Ex1: 0x0B45 = 2885mV | ||
309 | |||
310 | Ex2: 0x0B49 = 2889mV | ||
311 | |||
312 | |||
313 | === 2.3.4 UVC Value 0~~5V value ( pin VDC_IN) === | ||
314 | |||
315 | |||
316 | The UVC detect probed is connected to the VDC_IN pint. The probe has a 0~~5v output and map to 0~5mw/cm² | ||
317 | |||
318 | **Example**: | ||
319 | |||
320 | 0x625(H) = 1573(D)/1000= 1.573 V... Which means 1.537mw/cm² | ||
321 | |||
322 | |||
323 | === 2.3.5 IN1&IN2&INT pin === | ||
324 | |||
325 | |||
326 | IN1 and IN2 are used as digital input pins. | ||
327 | |||
328 | **Example**: | ||
329 | |||
330 | 09 (H): (0x09&0x08)>>3=1 IN1 pin is high level. | ||
331 | |||
332 | 09 (H): (0x09&0x04)>>2=0 IN2 pin is low level. | ||
333 | |||
334 | This data field shows if this packet is generated by **Interrupt Pin** or not. [[Click here>>||anchor="H3.3.2SetInterruptMode"]] for the hardware and software set up. Note: The Internet Pin is a separate pin in the screw terminal. | ||
335 | |||
336 | |||
337 | **Example:** | ||
338 | |||
339 | 09 (H): (0x09&0x02)>>1=1 The level of the interrupt pin. | ||
340 | |||
341 | 09 (H): 0x09&0x01=1 0x00: Normal uplink packet. | ||
342 | |||
343 | 0x01: Interrupt Uplink Packet. | ||
344 | |||
345 | |||
346 | === 2.3.6 Decode payload in The Things Network === | ||
347 | |||
348 | |||
349 | While using TTN network, you can add the payload format to decode the payload. | ||
350 | |||
351 | |||
352 | [[image:1675144839454-913.png]] | ||
353 | |||
354 | |||
355 | UV254-LB TTN Payload Decoder: [[dragino-end-node-decoder/UV254-LB at main · dragino/dragino-end-node-decoder · GitHub>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/UV254-LB]] | ||
356 | |||
357 | |||
358 | == 2.4 Uplink Interval == | ||
359 | |||
360 | |||
361 | The UV254-LB by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.1ChangeUplinkInterval>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.1ChangeUplinkInterval||style="background-color: rgb(255, 255, 255);"]] | ||
362 | |||
363 | |||
364 | == 2.5 Show Data in DataCake IoT Server == | ||
365 | |||
366 | |||
367 | [[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps: | ||
368 | |||
369 | |||
370 | (% style="color:blue" %)**Step 1: **(%%)Be sure that your device is programmed and properly connected to the network at this time. | ||
371 | |||
372 | (% style="color:blue" %)**Step 2:**(%%) To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps: | ||
373 | |||
374 | |||
375 | [[image:1675144951092-237.png]] | ||
376 | |||
377 | |||
378 | [[image:1675144960452-126.png]] | ||
379 | |||
380 | |||
381 | (% style="color:blue" %)**Step 3:**(%%) Create an account or log in Datacake. | ||
382 | |||
383 | (% style="color:blue" %)**Step 4:** (%%)Create UV254-LB product. | ||
384 | |||
385 | [[image:image-20230626144149-1.png]] | ||
386 | |||
387 | |||
388 | [[image:1675145018212-853.png]] | ||
389 | |||
390 | |||
391 | |||
392 | [[image:image-20230626144435-2.png||height="691" width="837"]] | ||
393 | |||
394 | |||
395 | (% style="color:blue" %)**Step 5: **(%%)add payload decode | ||
396 | |||
397 | [[image:image-20230626144658-3.png||height="561" width="854"]] | ||
398 | |||
399 | |||
400 | [[image:1675145060812-420.png]] | ||
401 | |||
402 | |||
403 | After added, the sensor data arrive TTN, it will also arrive and show in Datacake. | ||
404 | |||
405 | |||
406 | [[image:image-20230626164334-4.png||height="359" width="949"]] | ||
407 | |||
408 | |||
409 | == 2.6 Frequency Plans == | ||
410 | |||
411 | |||
412 | The UV254-LB uses OTAA mode and below frequency plans by default. Each frequency band use different firmware, user update the firmware to the corresponding band for their country. | ||
413 | |||
414 | [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]] | ||
415 | |||
416 | |||
417 | == 2.7 Firmware Change Log == | ||
418 | |||
419 | |||
420 | **Firmware download link: **[[https:~~/~~/www.dropbox.com/sh/hk4dpwtttyz8lpi/AAA6axLQ7u0hKcr8Cmz3yxaga?dl=0>>https://www.dropbox.com/sh/hk4dpwtttyz8lpi/AAA6axLQ7u0hKcr8Cmz3yxaga?dl=0]] | ||
421 | |||
422 | |||
423 | = 3. Configure UV254-LB = | ||
424 | |||
425 | == 3.1 Configure Methods == | ||
426 | |||
427 | |||
428 | UV254-LB supports below configure method: | ||
429 | |||
430 | * AT Command via Bluetooth Connection (**Recommand Way**): [[BLE Configure Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
431 | |||
432 | * AT Command via UART Connection : See [[FAQ>>||anchor="H6.FAQ"]]. | ||
433 | |||
434 | * LoRaWAN Downlink. Instruction for different platforms: See [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] section. | ||
435 | |||
436 | == 3.2 General Commands == | ||
437 | |||
438 | |||
439 | These commands are to configure: | ||
440 | |||
441 | * General system settings like: uplink interval. | ||
442 | |||
443 | * LoRaWAN protocol & radio related command. | ||
444 | |||
445 | They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: | ||
446 | |||
447 | [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]] | ||
448 | |||
449 | |||
450 | == 3.3 Commands special design for UV254-LB == | ||
451 | |||
452 | |||
453 | These commands only valid for UV254-LB, as below: | ||
454 | |||
455 | |||
456 | === 3.3.1 Set Transmit Interval Time === | ||
457 | |||
458 | |||
459 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
460 | |||
461 | (% style="color:blue" %)**AT Command: AT+TDC** | ||
462 | |||
463 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
464 | |=(% style="width: 160px; background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 160px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 190px;background-color:#4F81BD;color:white" %)**Response** | ||
465 | |(% style="background-color:#f2f2f2; width:157px" %)AT+TDC=?|(% style="background-color:#f2f2f2; width:166px" %)Show current transmit Interval|(% style="background-color:#f2f2f2" %)((( | ||
466 | 30000 | ||
467 | OK | ||
468 | the interval is 30000ms = 30s | ||
469 | ))) | ||
470 | |(% style="background-color:#f2f2f2; width:157px" %)AT+TDC=60000|(% style="background-color:#f2f2f2; width:166px" %)Set Transmit Interval|(% style="background-color:#f2f2f2" %)((( | ||
471 | OK | ||
472 | Set transmit interval to 60000ms = 60 seconds | ||
473 | ))) | ||
474 | |||
475 | (% style="color:blue" %)**Downlink Command: 0x01** | ||
476 | |||
477 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
478 | |||
479 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
480 | |||
481 | * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
482 | * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
483 | |||
484 | === 3.3.2 Set Interrupt Mode === | ||
485 | |||
486 | |||
487 | Feature, Set Interrupt mode for GPIO_EXIT. | ||
488 | |||
489 | (% style="color:blue" %)**AT Command: AT+INTMOD** | ||
490 | |||
491 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
492 | |=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 197px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 158px;background-color:#4F81BD;color:white" %)**Response** | ||
493 | |(% style="background-color:#f2f2f2; width:154px" %)AT+INTMOD=?|(% style="background-color:#f2f2f2; width:196px" %)Show current interrupt mode|(% style="background-color:#f2f2f2; width:157px" %)((( | ||
494 | 0 | ||
495 | OK | ||
496 | the mode is 0 =Disable Interrupt | ||
497 | ))) | ||
498 | |(% style="background-color:#f2f2f2; width:154px" %)AT+INTMOD=2|(% style="background-color:#f2f2f2; width:196px" %)((( | ||
499 | Set Transmit Interval | ||
500 | 0. (Disable Interrupt), | ||
501 | ~1. (Trigger by rising and falling edge) | ||
502 | 2. (Trigger by falling edge) | ||
503 | 3. (Trigger by rising edge) | ||
504 | )))|(% style="background-color:#f2f2f2; width:157px" %)OK | ||
505 | |||
506 | (% style="color:blue" %)**Downlink Command: 0x06** | ||
507 | |||
508 | Format: Command Code (0x06) followed by 3 bytes. | ||
509 | |||
510 | This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. | ||
511 | |||
512 | * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode | ||
513 | * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger | ||
514 | |||
515 | = 4. Battery & Power Consumption = | ||
516 | |||
517 | |||
518 | UV254-LB uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
519 | |||
520 | [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
521 | |||
522 | |||
523 | = 5. OTA firmware update = | ||
524 | |||
525 | |||
526 | User can change firmware UV254-LB to: | ||
527 | |||
528 | * Change Frequency band/ region. | ||
529 | * Update with new features. | ||
530 | * Fix bugs. | ||
531 | |||
532 | Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/gf1glloczbzz19h/AABbuYI4WY6VdAmpXo6o1V2Ka?dl=0]]** | ||
533 | |||
534 | Methods to Update Firmware: | ||
535 | |||
536 | * (Recommanded way) OTA firmware update via wireless: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]** | ||
537 | * Update through UART TTL interface. **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**. | ||
538 | |||
539 | Please see this link for how to do OTA firmware update: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]** | ||
540 | |||
541 | |||
542 | = 6. FAQ = | ||
543 | |||
544 | == 6.1 How to use AT Command via UART to access device? == | ||
545 | |||
546 | |||
547 | See: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]] | ||
548 | |||
549 | |||
550 | == 6.2 How to update firmware via UART port? == | ||
551 | |||
552 | |||
553 | See: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]] | ||
554 | |||
555 | |||
556 | = 8. Order Info = | ||
557 | |||
558 | |||
559 | Part Number: (% style="color:blue" %)**UV254-LB-XX** | ||
560 | |||
561 | (% style="color:blue" %)**XX**(%%): The default frequency band | ||
562 | |||
563 | * (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band | ||
564 | * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band | ||
565 | * (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band | ||
566 | * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band | ||
567 | * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band | ||
568 | * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band | ||
569 | * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band | ||
570 | * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band | ||
571 | |||
572 | = 9. Packing Info = | ||
573 | |||
574 | |||
575 | (% style="color:#037691" %)**Package Includes**: | ||
576 | |||
577 | * UV254-LB UVC Radiation Sensor x 1 | ||
578 | |||
579 | (% style="color:#037691" %)**Dimension and weight**: | ||
580 | |||
581 | * Device Size: cm | ||
582 | |||
583 | * Device Weight: g | ||
584 | |||
585 | * Package Size / pcs : cm | ||
586 | |||
587 | * Weight / pcs : g | ||
588 | |||
589 | = 10. Support = | ||
590 | |||
591 | |||
592 | * 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. | ||
593 | |||
594 | * 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.cc>>mailto:Support@dragino.cc]]. |