Wiki source code of PS-LB -- LoRaWAN Air Water Pressure Sensor User Manual
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | [[image:image-20230131115217-1.png]] | ||
| 2 | |||
| 3 | |||
| 4 | |||
| 5 | **Table of Contents：** | ||
| 6 | |||
| 7 | {{toc/}} | ||
| 8 | |||
| 9 | |||
| 10 | |||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | = 1. Introduction = | ||
| 15 | |||
| 16 | == 1.1 What is LoRaWAN Pressure Sensor == | ||
| 17 | |||
| 18 | |||
| 19 | ((( | ||
| 20 | The Dragino PS-LB series sensors are (% style="color:blue" %)**LoRaWAN Pressure Sensor**(%%) for Internet of Things solution. PS-LB can measure Air, Water pressure and liquid level and upload the sensor data via wireless to LoRaWAN IoT server. | ||
| 21 | ))) | ||
| 22 | |||
| 23 | ((( | ||
| 24 | The PS-LB series sensors include (% style="color:blue" %)**Thread Installation Type**(%%) and (% style="color:blue" %)**Immersion Type**(%%), it supports different pressure range which can be used for different measurement requirement. | ||
| 25 | ))) | ||
| 26 | |||
| 27 | ((( | ||
| 28 | The LoRa wireless technology used in PS-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. | ||
| 29 | ))) | ||
| 30 | |||
| 31 | ((( | ||
| 32 | PS-LB supports BLE configure and wireless OTA update which make user easy to use. | ||
| 33 | ))) | ||
| 34 | |||
| 35 | ((( | ||
| 36 | PS-LB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years. | ||
| 37 | ))) | ||
| 38 | |||
| 39 | ((( | ||
| 40 | Each PS-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. | ||
| 41 | ))) | ||
| 42 | |||
| 43 | [[image:1675071321348-194.png]] | ||
| 44 | |||
| 45 | |||
| 46 | == 1.2 Features == | ||
| 47 | |||
| 48 | |||
| 49 | * LoRaWAN 1.0.3 Class A | ||
| 50 | * Ultra-low power consumption | ||
| 51 | * Measure air / gas or water pressure | ||
| 52 | * Different pressure range available | ||
| 53 | * Thread Installation Type or Immersion Type | ||
| 54 | * Monitor Battery Level | ||
| 55 | * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865 | ||
| 56 | * Support Bluetooth v5.1 and LoRaWAN remote configure | ||
| 57 | * Support wireless OTA update firmware | ||
| 58 | * Uplink on periodically | ||
| 59 | * Downlink to change configure | ||
| 60 | * 8500mAh Battery for long term use | ||
| 61 | * Controllable 3.3v,5v and 12v output to power external sensor | ||
| 62 | |||
| 63 | |||
| 64 | == 1.3 Specification == | ||
| 65 | |||
| 66 | |||
| 67 | (% style="color:#037691" %)**Micro Controller:** | ||
| 68 | |||
| 69 | * MCU: 48Mhz ARM | ||
| 70 | * Flash: 256KB | ||
| 71 | * RAM: 64KB | ||
| 72 | |||
| 73 | (% style="color:#037691" %)**Common DC Characteristics:** | ||
| 74 | |||
| 75 | * Supply Voltage: 2.5v ~~ 3.6v | ||
| 76 | * Operating Temperature: -40 ~~ 85°C | ||
| 77 | |||
| 78 | (% style="color:#037691" %)**LoRa Spec:** | ||
| 79 | |||
| 80 | * Frequency Range, Band 1 (HF): 862 ~~ 1020 Mhz | ||
| 81 | * Max +22 dBm constant RF output vs. | ||
| 82 | * RX sensitivity: down to -139 dBm. | ||
| 83 | * Excellent blocking immunity | ||
| 84 | |||
| 85 | (% style="color:#037691" %)**Current Input Measuring :** | ||
| 86 | |||
| 87 | * Range: 0 ~~ 20mA | ||
| 88 | * Accuracy: 0.02mA | ||
| 89 | * Resolution: 0.001mA | ||
| 90 | |||
| 91 | (% style="color:#037691" %)**Voltage Input Measuring:** | ||
| 92 | |||
| 93 | * Range: 0 ~~ 30v | ||
| 94 | * Accuracy: 0.02v | ||
| 95 | * Resolution: 0.001v | ||
| 96 | |||
| 97 | (% style="color:#037691" %)**Battery:** | ||
| 98 | |||
| 99 | * Li/SOCI2 un-chargeable battery | ||
| 100 | * Capacity: 8500mAh | ||
| 101 | * Self-Discharge: <1% / Year @ 25°C | ||
| 102 | * Max continuously current: 130mA | ||
| 103 | * Max boost current: 2A, 1 second | ||
| 104 | |||
| 105 | (% style="color:#037691" %)**Power Consumption** | ||
| 106 | |||
| 107 | * Sleep Mode: 5uA @ 3.3v | ||
| 108 | * LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm | ||
| 109 | |||
| 110 | |||
| 111 | == 1.4 Probe Types == | ||
| 112 | |||
| 113 | === 1.4.1 Thread Installation Type === | ||
| 114 | |||
| 115 | |||
| 116 | [[image:1675071448299-229.png]] | ||
| 117 | |||
| 118 | * Hersman Pressure Transmitter | ||
| 119 | * Measuring Range: -0.1 ~~ 0 ~~ 60MPa, see order info. | ||
| 120 | * Accuracy: 0.2% F.S | ||
| 121 | * Long-Term Stability: 0.2% F.S ±0.05% | ||
| 122 | * Overload 200% F.S | ||
| 123 | * Zero Temperature Drift: 0.03% FS/℃(≤100Kpa), 0.02%FS/℃(＞100Kpa) | ||
| 124 | * FS Temperature Drift: 0.003% FS/℃(≤100Kpa), 0.002%FS/℃(＞100Kpa) | ||
| 125 | * Storage temperature: -30℃~~80℃ | ||
| 126 | * Operating temperature: -20℃~~60℃ | ||
| 127 | * Connector Type: Various Types, see order info | ||
| 128 | |||
| 129 | |||
| 130 | === 1.4.2 Immersion Type === | ||
| 131 | |||
| 132 | |||
| 133 | [[image:1675071521308-426.png]] | ||
| 134 | |||
| 135 | * Immersion Type, Probe IP Level: IP68 | ||
| 136 | * Measuring Range: Measure range can be customized, up to 100m. | ||
| 137 | * Accuracy: 0.2% F.S | ||
| 138 | * Long-Term Stability: ±0.2% F.S / Year | ||
| 139 | * Storage temperature: -30℃~~80℃ | ||
| 140 | * Operating temperature: 0℃~~50℃ | ||
| 141 | * Material: 316 stainless steels | ||
| 142 | |||
| 143 | |||
| 144 | == 1.5 Probe Dimension == | ||
| 145 | |||
| 146 | |||
| 147 | |||
| 148 | == 1.6 Application and Installation == | ||
| 149 | |||
| 150 | === 1.6.1 Thread Installation Type === | ||
| 151 | |||
| 152 | |||
| 153 | (% style="color:blue" %)**Application:** | ||
| 154 | |||
| 155 | * Hydraulic Pressure | ||
| 156 | * Petrochemical Industry | ||
| 157 | * Health and Medical | ||
| 158 | * Food & Beverage Processing | ||
| 159 | * Auto-controlling house | ||
| 160 | * Constant Pressure Water Supply | ||
| 161 | * Liquid Pressure measuring | ||
| 162 | |||
| 163 | Order the suitable thread size and install to measure the air / liquid pressure | ||
| 164 | |||
| 165 | [[image:1675071670469-145.png]] | ||
| 166 | |||
| 167 | |||
| 168 | === 1.6.2 Immersion Type === | ||
| 169 | |||
| 170 | |||
| 171 | (% style="color:blue" %)**Application:** | ||
| 172 | |||
| 173 | Liquid & Water Pressure / Level detect. | ||
| 174 | |||
| 175 | [[image:1675071725288-579.png]] | ||
| 176 | |||
| 177 | |||
| 178 | The Immersion Type pressure sensor is shipped with the probe and device separately. When user got the device, below is the wiring to for connect the probe to the device. | ||
| 179 | |||
| 180 | |||
| 181 | [[image:1675071736646-450.png]] | ||
| 182 | |||
| 183 | |||
| 184 | [[image:1675071776102-240.png]] | ||
| 185 | |||
| 186 | |||
| 187 | == 1.7 Sleep mode and working mode == | ||
| 188 | |||
| 189 | |||
| 190 | (% 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. | ||
| 191 | |||
| 192 | (% 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. | ||
| 193 | |||
| 194 | |||
| 195 | == 1.8 Button & LEDs == | ||
| 196 | |||
| 197 | |||
| 198 | [[image:1675071855856-879.png]] | ||
| 199 | |||
| 200 | |||
| 201 | (% border="1" cellspacing="4" style="width:510px" %) | ||
| 202 | |=(% style="width: 167px;background-color:#D9E2F3;color:#0070C0" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 225px;background-color:#D9E2F3;color:#0070C0" %)**Action** | ||
| 203 | |(% 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" %)((( | ||
| 204 | If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once. | ||
| 205 | Meanwhile, BLE module will be active and user can connect via BLE to configure device. | ||
| 206 | ))) | ||
| 207 | |(% 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" %)((( | ||
| 208 | (% 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. | ||
| 209 | (% style="background-color:#f2f2f2; color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network. | ||
| 210 | 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. | ||
| 211 | ))) | ||
| 212 | |(% 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 PS-LB-NA is in Deep Sleep Mode. | ||
| 213 | |||
| 214 | |||
| 215 | == 1.9 Pin Mapping == | ||
| 216 | |||
| 217 | |||
| 218 | [[image:1675072568006-274.png]] | ||
| 219 | |||
| 220 | |||
| 221 | == 1.10 BLE connection == | ||
| 222 | |||
| 223 | |||
| 224 | PS-LB support BLE remote configure. | ||
| 225 | |||
| 226 | |||
| 227 | 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: | ||
| 228 | |||
| 229 | * Press button to send an uplink | ||
| 230 | * Press button to active device. | ||
| 231 | * Device Power on or reset. | ||
| 232 | |||
| 233 | If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode. | ||
| 234 | |||
| 235 | |||
| 236 | == 1.11 Mechanical == | ||
| 237 | |||
| 238 | |||
| 239 | [[image:1675143884058-338.png]] | ||
| 240 | |||
| 241 | |||
| 242 | [[image:1675143899218-599.png]] | ||
| 243 | |||
| 244 | |||
| 245 | [[image:1675143909447-639.png]] | ||
| 246 | |||
| 247 | |||
| 248 | = 2. Configure PS-LB to connect to LoRaWAN network = | ||
| 249 | |||
| 250 | == 2.1 How it works == | ||
| 251 | |||
| 252 | |||
| 253 | The PS-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 PS-LB. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes. | ||
| 254 | |||
| 255 | |||
| 256 | == 2.2 Quick guide to connect to LoRaWAN server (OTAA) == | ||
| 257 | |||
| 258 | |||
| 259 | 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. | ||
| 260 | |||
| 261 | |||
| 262 | [[image:1675144005218-297.png]] | ||
| 263 | |||
| 264 | |||
| 265 | 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. | ||
| 266 | |||
| 267 | |||
| 268 | (% style="color:blue" %)**Step 1:**(%%) Create a device in TTN with the OTAA keys from PS-LB. | ||
| 269 | |||
| 270 | Each PS-LB is shipped with a sticker with the default device EUI as below: | ||
| 271 | |||
| 272 | [[image:image-20230131134744-2.jpeg]] | ||
| 273 | |||
| 274 | |||
| 275 | |||
| 276 | You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot: | ||
| 277 | |||
| 278 | |||
| 279 | (% style="color:blue" %)**Register the device** | ||
| 280 | |||
| 281 | [[image:1675144099263-405.png]] | ||
| 282 | |||
| 283 | |||
| 284 | (% style="color:blue" %)**Add APP EUI and DEV EUI** | ||
| 285 | |||
| 286 | [[image:1675144117571-832.png]] | ||
| 287 | |||
| 288 | |||
| 289 | (% style="color:blue" %)**Add APP EUI in the application** | ||
| 290 | |||
| 291 | |||
| 292 | [[image:1675144143021-195.png]] | ||
| 293 | |||
| 294 | |||
| 295 | (% style="color:blue" %)**Add APP KEY** | ||
| 296 | |||
| 297 | [[image:1675144157838-392.png]] | ||
| 298 | |||
| 299 | (% style="color:blue" %)**Step 2:**(%%) Activate on PS-LB | ||
| 300 | |||
| 301 | |||
| 302 | Press the button for 5 seconds to activate the PS-LB. | ||
| 303 | |||
| 304 | (% 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. | ||
| 305 | |||
| 306 | After join success, it will start to upload messages to TTN and you can see the messages in the panel. | ||
| 307 | |||
| 308 | |||
| 309 | == 2.3 Uplink Payload == | ||
| 310 | |||
| 311 | === 2.3.1 Device Status, FPORT~=5 === | ||
| 312 | |||
| 313 | |||
| 314 | Include device configure status. Once PS-LB Joined the network, it will uplink this message to the server. | ||
| 315 | |||
| 316 | Users can also use the downlink command(0x26 01) to ask PS-LB to resend this uplink. | ||
| 317 | |||
| 318 | |||
| 319 | (% border="1" cellspacing="4" style="width:510px" %) | ||
| 320 | |(% colspan="6" style="background-color:#d9e2f3; color:#0070c0" %)**Device Status (FPORT=5)** | ||
| 321 | |(% 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** | ||
| 322 | |(% 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 | ||
| 323 | |||
| 324 | Example parse in TTNv3 | ||
| 325 | |||
| 326 | [[image:1675144504430-490.png]] | ||
| 327 | |||
| 328 | |||
| 329 | (% style="color:#037691" %)**Sensor Model**(%%): For PS-LB, this value is 0x16 | ||
| 330 | |||
| 331 | (% style="color:#037691" %)**Firmware Version**(%%): 0x0100, Means: v1.0.0 version | ||
| 332 | |||
| 333 | (% style="color:#037691" %)**Frequency Band**: | ||
| 334 | |||
| 335 | *0x01: EU868 | ||
| 336 | |||
| 337 | *0x02: US915 | ||
| 338 | |||
| 339 | *0x03: IN865 | ||
| 340 | |||
| 341 | *0x04: AU915 | ||
| 342 | |||
| 343 | *0x05: KZ865 | ||
| 344 | |||
| 345 | *0x06: RU864 | ||
| 346 | |||
| 347 | *0x07: AS923 | ||
| 348 | |||
| 349 | *0x08: AS923-1 | ||
| 350 | |||
| 351 | *0x09: AS923-2 | ||
| 352 | |||
| 353 | *0x0a: AS923-3 | ||
| 354 | |||
| 355 | *0x0b: CN470 | ||
| 356 | |||
| 357 | *0x0c: EU433 | ||
| 358 | |||
| 359 | *0x0d: KR920 | ||
| 360 | |||
| 361 | *0x0e: MA869 | ||
| 362 | |||
| 363 | |||
| 364 | (% style="color:#037691" %)**Sub-Band**: | ||
| 365 | |||
| 366 | AU915 and US915:value 0x00 ~~ 0x08 | ||
| 367 | |||
| 368 | CN470: value 0x0B ~~ 0x0C | ||
| 369 | |||
| 370 | Other Bands: Always 0x00 | ||
| 371 | |||
| 372 | |||
| 373 | (% style="color:#037691" %)**Battery Info**: | ||
| 374 | |||
| 375 | Check the battery voltage. | ||
| 376 | |||
| 377 | Ex1: 0x0B45 = 2885mV | ||
| 378 | |||
| 379 | Ex2: 0x0B49 = 2889mV | ||
| 380 | |||
| 381 | |||
| 382 | === 2.3.2 Sensor value, FPORT~=2 === | ||
| 383 | |||
| 384 | |||
| 385 | Uplink payload includes in total 9 bytes. | ||
| 386 | |||
| 387 | |||
| 388 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) | ||
| 389 | |(% style="width:97px" %)((( | ||
| 390 | **Size(bytes)** | ||
| 391 | )))|(% style="width:48px" %)**2**|(% style="width:71px" %)**2**|(% style="width:98px" %)**2**|(% style="width:73px" %)**2**|(% style="width:122px" %)**1** | ||
| 392 | |(% style="width:97px" %)**Value**|(% style="width:48px" %)[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(% style="width:71px" %)[[Probe Model>>||anchor="H2.3.4ProbeModel"]]|(% style="width:98px" %)[[0 ~~~~ 20mA value>>||anchor="H2.3.507E20mAvalue28IDC_IN29"]]|(% style="width:73px" %)[[0 ~~~~ 30v value>>||anchor="H2.3.607E30Vvalue28pinVDC_IN29"]]|(% style="width:122px" %)[[IN1 &IN2 Interrupt flag>>||anchor="H2.3.7IN126IN226INTpin"]] | ||
| 393 | |||
| 394 | [[image:1675144608950-310.png]] | ||
| 395 | |||
| 396 | |||
| 397 | === 2.3.3 Battery Info === | ||
| 398 | |||
| 399 | |||
| 400 | Check the battery voltage for PS-LB. | ||
| 401 | |||
| 402 | Ex1: 0x0B45 = 2885mV | ||
| 403 | |||
| 404 | Ex2: 0x0B49 = 2889mV | ||
| 405 | |||
| 406 | |||
| 407 | === 2.3.4 Probe Model === | ||
| 408 | |||
| 409 | |||
| 410 | PS-LB has different kind of probe, 4~~20mA represent the full scale of the measuring range. So a 12mA output means different meaning for different probe. | ||
| 411 | |||
| 412 | |||
| 413 | **For example.** | ||
| 414 | |||
| 415 | (% border="1" cellspacing="4" style="width:510px" %) | ||
| 416 | |(% style="background-color:#d9e2f3; color:#0070c0" %)**Part Number**|(% style="background-color:#d9e2f3; color:#0070c0" %)**Probe Used**|(% style="background-color:#d9e2f3; color:#0070c0" %)**4~~20mA scale**|(% style="background-color:#d9e2f3; color:#0070c0" %)**Example: 12mA meaning** | ||
| 417 | |(% style="background-color:#f2f2f2" %)PS-LB-I3|(% style="background-color:#f2f2f2" %)immersion type with 3 meters cable|(% style="background-color:#f2f2f2" %)0~~3 meters|(% style="background-color:#f2f2f2" %)1.5 meters pure water | ||
| 418 | |(% style="background-color:#f2f2f2" %)PS-LB-I5|(% style="background-color:#f2f2f2" %)immersion type with 5 meters cable|(% style="background-color:#f2f2f2" %)0~~5 meters|(% style="background-color:#f2f2f2" %)2.5 meters pure water | ||
| 419 | |(% style="background-color:#f2f2f2" %)PS-LB-T20-B|(% style="background-color:#f2f2f2" %)T20 threaded probe|(% style="background-color:#f2f2f2" %)0~~1MPa|(% style="background-color:#f2f2f2" %)0.5MPa air / gas or water pressure | ||
| 420 | |||
| 421 | The probe model field provides the convenient for server to identical how it should parse the 4~~20mA sensor value and get the correct value. | ||
| 422 | |||
| 423 | |||
| 424 | === 2.3.5 0~~20mA value (IDC_IN) === | ||
| 425 | |||
| 426 | |||
| 427 | The output value from **Pressure Probe**, use together with Probe Model to get the pressure value or water level. | ||
| 428 | |||
| 429 | (% style="color:#037691" %)**Example**: | ||
| 430 | |||
| 431 | 27AE(H) = 10158 (D)/1000 = 10.158mA. | ||
| 432 | |||
| 433 | |||
| 434 | Instead of pressure probe, User can also connect a general 4~~20mA in this port to support different types of 4~~20mA sensors. below is the connection example: | ||
| 435 | |||
| 436 | [[image:image-20230225154759-1.png||height="408" width="741"]] | ||
| 437 | |||
| 438 | |||
| 439 | === 2.3.6 0~~30V value ( pin VDC_IN) === | ||
| 440 | |||
| 441 | |||
| 442 | Measure the voltage value. The range is 0 to 30V. | ||
| 443 | |||
| 444 | (% style="color:#037691" %)**Example**: | ||
| 445 | |||
| 446 | 138E(H) = 5006(D)/1000= 5.006V | ||
| 447 | |||
| 448 | |||
| 449 | === 2.3.7 IN1&IN2&INT pin === | ||
| 450 | |||
| 451 | |||
| 452 | IN1 and IN2 are used as digital input pins. | ||
| 453 | |||
| 454 | (% style="color:#037691" %)**Example**: | ||
| 455 | |||
| 456 | 09 (H): (0x09&0x08)>>3=1 IN1 pin is high level. | ||
| 457 | |||
| 458 | 09 (H): (0x09&0x04)>>2=0 IN2 pin is low level. | ||
| 459 | |||
| 460 | |||
| 461 | This data field shows if this packet is generated by (% style="color:blue" %)**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. | ||
| 462 | |||
| 463 | (% style="color:#037691" %)**Example:** | ||
| 464 | |||
| 465 | 09 (H): (0x09&0x02)>>1=1 The level of the interrupt pin. | ||
| 466 | |||
| 467 | 09 (H): 0x09&0x01=1 0x00: Normal uplink packet. | ||
| 468 | |||
| 469 | 0x01: Interrupt Uplink Packet. | ||
| 470 | |||
| 471 | |||
| 472 | === (% id="cke_bm_109176S" style="display:none" %) (%%)2.3.8 Sensor value, FPORT~=7 === | ||
| 473 | |||
| 474 | |||
| 475 | (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:508.222px" %) | ||
| 476 | |(% style="width:94px" %)((( | ||
| 477 | **Size(bytes)** | ||
| 478 | )))|(% style="width:43px" %)2|(% style="width:367px" %)n | ||
| 479 | |(% style="width:94px" %)**Value**|(% style="width:43px" %)[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(% style="width:367px" %)((( | ||
| 480 | Voltage value, each 2 bytes is a set of voltage values. | ||
| 481 | ))) | ||
| 482 | |||
| 483 | [[image:image-20230220171300-1.png||height="207" width="863"]] | ||
| 484 | |||
| 485 | Multiple sets of data collected are displayed in this form： | ||
| 486 | |||
| 487 | [voltage value1], [voltage value2], [voltage value3],…[voltage value n/2] | ||
| 488 | |||
| 489 | |||
| 490 | === 2.3.9 Decode payload in The Things Network === | ||
| 491 | |||
| 492 | |||
| 493 | While using TTN network, you can add the payload format to decode the payload. | ||
| 494 | |||
| 495 | |||
| 496 | [[image:1675144839454-913.png]] | ||
| 497 | |||
| 498 | |||
| 499 | PS-LB TTN Payload Decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>url:https://github.com/dragino/dragino-end-node-decoder]] | ||
| 500 | |||
| 501 | |||
| 502 | == 2.4 Uplink Interval == | ||
| 503 | |||
| 504 | |||
| 505 | The PS-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);"]] | ||
| 506 | |||
| 507 | |||
| 508 | == 2.5 Show Data in DataCake IoT Server == | ||
| 509 | |||
| 510 | |||
| 511 | [[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: | ||
| 512 | |||
| 513 | |||
| 514 | (% style="color:blue" %)**Step 1: **(%%)Be sure that your device is programmed and properly connected to the network at this time. | ||
| 515 | |||
| 516 | (% 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: | ||
| 517 | |||
| 518 | |||
| 519 | [[image:1675144951092-237.png]] | ||
| 520 | |||
| 521 | |||
| 522 | [[image:1675144960452-126.png]] | ||
| 523 | |||
| 524 | |||
| 525 | (% style="color:blue" %)**Step 3:**(%%) Create an account or log in Datacake. | ||
| 526 | |||
| 527 | (% style="color:blue" %)**Step 4:** (%%)Create PS-LB product. | ||
| 528 | |||
| 529 | [[image:1675145004465-869.png]] | ||
| 530 | |||
| 531 | |||
| 532 | [[image:1675145018212-853.png]] | ||
| 533 | |||
| 534 | |||
| 535 | |||
| 536 | |||
| 537 | [[image:1675145029119-717.png]] | ||
| 538 | |||
| 539 | |||
| 540 | (% style="color:blue" %)**Step 5: **(%%)add payload decode | ||
| 541 | |||
| 542 | [[image:1675145051360-659.png]] | ||
| 543 | |||
| 544 | |||
| 545 | [[image:1675145060812-420.png]] | ||
| 546 | |||
| 547 | |||
| 548 | After added, the sensor data arrive TTN, it will also arrive and show in Datacake. | ||
| 549 | |||
| 550 | |||
| 551 | [[image:1675145081239-376.png]] | ||
| 552 | |||
| 553 | |||
| 554 | == 2.6 Frequency Plans == | ||
| 555 | |||
| 556 | |||
| 557 | The PS-LB uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets. | ||
| 558 | |||
| 559 | [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]] | ||
| 560 | |||
| 561 | |||
| 562 | == 2.7 Firmware Change Log == | ||
| 563 | |||
| 564 | |||
| 565 | **Firmware download link:** | ||
| 566 | |||
| 567 | [[https:~~/~~/www.dropbox.com/sh/gf1glloczbzz19h/AABbuYI4WY6VdAmpXo6o1V2Ka?dl=0>>url:https://www.dropbox.com/sh/gf1glloczbzz19h/AABbuYI4WY6VdAmpXo6o1V2Ka?dl=0]] | ||
| 568 | |||
| 569 | |||
| 570 | = 3. Configure PS-LB = | ||
| 571 | |||
| 572 | == 3.1 Configure Methods == | ||
| 573 | |||
| 574 | |||
| 575 | PS-LB-NA supports below configure method: | ||
| 576 | |||
| 577 | * AT Command via Bluetooth Connection (**Recommand Way**): [[BLE Configure Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]]. | ||
| 578 | * AT Command via UART Connection : See [[FAQ>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/#H7.FAQ]]. | ||
| 579 | * LoRaWAN Downlink. Instruction for different platforms: See [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] section. | ||
| 580 | |||
| 581 | |||
| 582 | == 3.2 General Commands == | ||
| 583 | |||
| 584 | |||
| 585 | These commands are to configure: | ||
| 586 | |||
| 587 | * General system settings like: uplink interval. | ||
| 588 | * LoRaWAN protocol & radio related command. | ||
| 589 | |||
| 590 | They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: | ||
| 591 | |||
| 592 | [[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/]] | ||
| 593 | |||
| 594 | |||
| 595 | == 3.3 Commands special design for PS-LB == | ||
| 596 | |||
| 597 | |||
| 598 | These commands only valid for PS-LB, as below: | ||
| 599 | |||
| 600 | |||
| 601 | === 3.3.1 Set Transmit Interval Time === | ||
| 602 | |||
| 603 | |||
| 604 | Feature: Change LoRaWAN End Node Transmit Interval. | ||
| 605 | |||
| 606 | (% style="color:blue" %)**AT Command: AT+TDC** | ||
| 607 | |||
| 608 | (% border="1" cellspacing="4" style="width:510px" %) | ||
| 609 | |=(% style="width: 160px; background-color: rgb(217, 226, 243); color: rgb(0, 112, 192);" %)**Command Example**|=(% style="width: 160px; background-color: rgb(217, 226, 243); color: rgb(0, 112, 192);" %)**Function**|=(% style="width: 190px;background-color:#D9E2F3;color:#0070C0" %)**Response** | ||
| 610 | |(% style="background-color:#f2f2f2; width:157px" %)AT+TDC=?|(% style="background-color:#f2f2f2; width:166px" %)Show current transmit Interval|(% style="background-color:#f2f2f2" %)((( | ||
| 611 | 30000 | ||
| 612 | OK | ||
| 613 | the interval is 30000ms = 30s | ||
| 614 | ))) | ||
| 615 | |(% style="background-color:#f2f2f2; width:157px" %)AT+TDC=60000|(% style="background-color:#f2f2f2; width:166px" %)Set Transmit Interval|(% style="background-color:#f2f2f2" %)((( | ||
| 616 | OK | ||
| 617 | Set transmit interval to 60000ms = 60 seconds | ||
| 618 | ))) | ||
| 619 | |||
| 620 | (% style="color:blue" %)**Downlink Command: 0x01** | ||
| 621 | |||
| 622 | Format: Command Code (0x01) followed by 3 bytes time value. | ||
| 623 | |||
| 624 | If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01. | ||
| 625 | |||
| 626 | * Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds | ||
| 627 | * Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds | ||
| 628 | |||
| 629 | |||
| 630 | === 3.3.2 Set Interrupt Mode === | ||
| 631 | |||
| 632 | |||
| 633 | Feature, Set Interrupt mode for GPIO_EXIT. | ||
| 634 | |||
| 635 | (% style="color:blue" %)**AT Command: AT+INTMOD** | ||
| 636 | |||
| 637 | (% border="1" cellspacing="4" style="width:510px" %) | ||
| 638 | |=(% style="width: 154px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 196px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 157px;background-color:#D9E2F3;color:#0070C0" %)**Response** | ||
| 639 | |(% style="background-color:#f2f2f2; width:154px" %)AT+INTMOD=?|(% style="background-color:#f2f2f2; width:196px" %)Show current interrupt mode|(% style="background-color:#f2f2f2; width:157px" %)((( | ||
| 640 | 0 | ||
| 641 | OK | ||
| 642 | the mode is 0 =Disable Interrupt | ||
| 643 | ))) | ||
| 644 | |(% style="background-color:#f2f2f2; width:154px" %)AT+INTMOD=2|(% style="background-color:#f2f2f2; width:196px" %)((( | ||
| 645 | Set Transmit Interval | ||
| 646 | 0. (Disable Interrupt), | ||
| 647 | ~1. (Trigger by rising and falling edge) | ||
| 648 | 2. (Trigger by falling edge) | ||
| 649 | 3. (Trigger by rising edge) | ||
| 650 | )))|(% style="background-color:#f2f2f2; width:157px" %)OK | ||
| 651 | |||
| 652 | (% style="color:blue" %)**Downlink Command: 0x06** | ||
| 653 | |||
| 654 | Format: Command Code (0x06) followed by 3 bytes. | ||
| 655 | |||
| 656 | This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06. | ||
| 657 | |||
| 658 | * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode | ||
| 659 | * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger | ||
| 660 | |||
| 661 | |||
| 662 | === 3.3.3 Set the output time === | ||
| 663 | |||
| 664 | |||
| 665 | Feature, Control the output 3V3 , 5V or 12V. | ||
| 666 | |||
| 667 | (% style="color:blue" %)**AT Command: AT+3V3T** | ||
| 668 | |||
| 669 | (% border="1" cellspacing="4" style="width:474px" %) | ||
| 670 | |=(% style="width: 154px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 201px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 116px;background-color:#D9E2F3;color:#0070C0" %)**Response** | ||
| 671 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=?|(% style="background-color:#f2f2f2; width:201px" %)Show 3V3 open time.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
| 672 | 0 | ||
| 673 | OK | ||
| 674 | ))) | ||
| 675 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=0|(% style="background-color:#f2f2f2; width:201px" %)Normally open 3V3 power supply.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
| 676 | OK | ||
| 677 | default setting | ||
| 678 | ))) | ||
| 679 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=1000|(% style="background-color:#f2f2f2; width:201px" %)Close after a delay of 1000 milliseconds.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
| 680 | OK | ||
| 681 | ))) | ||
| 682 | |(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=65535|(% style="background-color:#f2f2f2; width:201px" %)Normally closed 3V3 power supply.|(% style="background-color:#f2f2f2; width:116px" %)((( | ||
| 683 | OK | ||
| 684 | ))) | ||
| 685 | |||
| 686 | (% style="color:blue" %)**AT Command: AT+5VT** | ||
| 687 | |||
| 688 | (% border="1" cellspacing="4" style="width:470px" %) | ||
| 689 | |=(% style="width: 155px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 196px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 114px;background-color:#D9E2F3;color:#0070C0" %)**Response** | ||
| 690 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=?|(% style="background-color:#f2f2f2; width:196px" %)Show 5V open time.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
| 691 | 0 | ||
| 692 | OK | ||
| 693 | ))) | ||
| 694 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=0|(% style="background-color:#f2f2f2; width:196px" %)Normally closed 5V power supply.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
| 695 | OK | ||
| 696 | default setting | ||
| 697 | ))) | ||
| 698 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=1000|(% style="background-color:#f2f2f2; width:196px" %)Close after a delay of 1000 milliseconds.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
| 699 | OK | ||
| 700 | ))) | ||
| 701 | |(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=65535|(% style="background-color:#f2f2f2; width:196px" %)Normally open 5V power supply.|(% style="background-color:#f2f2f2; width:114px" %)((( | ||
| 702 | OK | ||
| 703 | ))) | ||
| 704 | |||
| 705 | (% style="color:blue" %)**AT Command: AT+12VT** | ||
| 706 | |||
| 707 | (% border="1" cellspacing="4" style="width:443px" %) | ||
| 708 | |=(% style="width: 156px;background-color:#D9E2F3;color:#0070C0" %)**Command Example**|=(% style="width: 199px;background-color:#D9E2F3;color:#0070C0" %)**Function**|=(% style="width: 83px;background-color:#D9E2F3;color:#0070C0" %)**Response** | ||
| 709 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=?|(% style="background-color:#f2f2f2; width:199px" %)Show 12V open time.|(% style="background-color:#f2f2f2; width:83px" %)((( | ||
| 710 | 0 | ||
| 711 | OK | ||
| 712 | ))) | ||
| 713 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=0|(% style="background-color:#f2f2f2; width:199px" %)Normally closed 12V power supply.|(% style="background-color:#f2f2f2; width:83px" %)OK | ||
| 714 | |(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=500|(% style="background-color:#f2f2f2; width:199px" %)Close after a delay of 500 milliseconds.|(% style="background-color:#f2f2f2; width:83px" %)((( | ||
| 715 | OK | ||
| 716 | ))) | ||
| 717 | |||
| 718 | (% style="color:blue" %)**Downlink Command: 0x07** | ||
| 719 | |||
| 720 | Format: Command Code (0x07) followed by 3 bytes. | ||
| 721 | |||
| 722 | The first byte is which power, the second and third bytes are the time to turn on. | ||
| 723 | |||
| 724 | * Example 1: Downlink Payload: 070101F4 **~-~-->** AT+3V3T=500 | ||
| 725 | * Example 2: Downlink Payload: 0701FFFF **~-~-->** AT+3V3T=65535 | ||
| 726 | * Example 3: Downlink Payload: 070203E8 **~-~-->** AT+5VT=1000 | ||
| 727 | * Example 4: Downlink Payload: 07020000 **~-~-->** AT+5VT=0 | ||
| 728 | * Example 5: Downlink Payload: 070301F4 **~-~-->** AT+12VT=500 | ||
| 729 | * Example 6: Downlink Payload: 07030000 **~-~-->** AT+12VT=0 | ||
| 730 | |||
| 731 | |||
| 732 | === 3.3.4 Set the Probe Model === | ||
| 733 | |||
| 734 | |||
| 735 | Users need to configure this parameter according to the type of external probe. In this way, the server can decode according to this value, and convert the current value output by the sensor into water depth or pressure value. | ||
| 736 | |||
| 737 | **AT Command: AT** **+PROBE** | ||
| 738 | |||
| 739 | AT+PROBE=aabb | ||
| 740 | |||
| 741 | When aa=00, it is the water depth mode, and the current is converted into the water depth value; bb is the probe at a depth of several meters. | ||
| 742 | |||
| 743 | When aa=01, it is the pressure mode, which converts the current into a pressure value; | ||
| 744 | |||
| 745 | bb represents which type of pressure sensor it is. | ||
| 746 | |||
| 747 | (A->01,B->02,C->03,D->04,E->05,F->06,G->07,H->08,I->09,J->0A,K->0B,L->0C) | ||
| 748 | |||
| 749 | (% border="1" cellspacing="4" style="width:510px" %) | ||
| 750 | |(% style="background-color:#d9e2f3; color:#0070c0; width:154px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:269px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0" %)**Response** | ||
| 751 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =?|(% style="background-color:#f2f2f2; width:269px" %)Get or Set the probe model.|(% style="background-color:#f2f2f2" %)0 | ||
| 752 | OK | ||
| 753 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0003|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 3m type.|(% style="background-color:#f2f2f2" %)OK | ||
| 754 | |(% style="background-color:#f2f2f2; width:154px" %)((( | ||
| 755 | AT +PROBE =000A | ||
| 756 | |||
| 757 | |||
| 758 | )))|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 10m type.|(% style="background-color:#f2f2f2" %)OK | ||
| 759 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0101|(% style="background-color:#f2f2f2; width:269px" %)Set pressure transmitters mode, first type(A).|(% style="background-color:#f2f2f2" %)OK | ||
| 760 | |(% style="background-color:#f2f2f2; width:154px" %)AT +PROBE =0000|(% style="background-color:#f2f2f2; width:269px" %)Initial state, no settings.|(% style="background-color:#f2f2f2" %)OK | ||
| 761 | |||
| 762 | **Downlink Command: 0x08** | ||
| 763 | |||
| 764 | Format: Command Code (0x08) followed by 2 bytes. | ||
| 765 | |||
| 766 | * Example 1: Downlink Payload: 080003 **~-~-->** AT+PROBE=0003 | ||
| 767 | * Example 2: Downlink Payload: 080101 **~-~-->** AT+PROBE=0101 | ||
| 768 | |||
| 769 | |||
| 770 | === 3.3.5 Multiple collections are one uplink（Since firmware V1.1） === | ||
| 771 | |||
| 772 | |||
| 773 | Added AT+STDC command to collect the voltage of VDC_INPUT multiple times and upload it at one time. | ||
| 774 | |||
| 775 | (% style="color:blue" %)**AT Command: AT** **+STDC** | ||
| 776 | |||
| 777 | AT+STDC=aa,bb,bb | ||
| 778 | |||
| 779 | (% style="color:#037691" %)**aa:**(%%) | ||
| 780 | **0:** means disable this function and use TDC to send packets. | ||
| 781 | **1:** means enable this function, use the method of multiple acquisitions to send packets. | ||
| 782 | (% style="color:#037691" %)**bb:**(%%) Each collection interval (s), the value is 1~~65535 | ||
| 783 | (% style="color:#037691" %)**cc:**(%%)** **the number of collection times, the value is 1~~120 | ||
| 784 | |||
| 785 | (% border="1" cellspacing="4" style="width:510px" %) | ||
| 786 | |(% style="background-color:#d9e2f3; color:#0070c0; width:160px" %)**Command Example**|(% style="background-color:#d9e2f3; color:#0070c0; width:215px" %)**Function**|(% style="background-color:#d9e2f3; color:#0070c0" %)**Response** | ||
| 787 | |(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=?|(% style="background-color:#f2f2f2; width:215px" %)Get the mode of multiple acquisitions and one uplink.|(% style="background-color:#f2f2f2" %)1,10,18 | ||
| 788 | OK | ||
| 789 | |(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=1,10,18|(% style="background-color:#f2f2f2; width:215px" %)Set the mode of multiple acquisitions and one uplink, collect once every 10 seconds, and report after 18 times.|(% style="background-color:#f2f2f2" %)((( | ||
| 790 | Attention:Take effect after ATZ | ||
| 791 | |||
| 792 | OK | ||
| 793 | ))) | ||
| 794 | |(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=0, 0,0|(% style="background-color:#f2f2f2; width:215px" %)((( | ||
| 795 | Use the TDC interval to send packets.(default) | ||
| 796 | |||
| 797 | |||
| 798 | )))|(% style="background-color:#f2f2f2" %)((( | ||
| 799 | Attention:Take effect after ATZ | ||
| 800 | |||
| 801 | OK | ||
| 802 | ))) | ||
| 803 | |||
| 804 | (% style="color:blue" %)**Downlink Command: 0xAE** | ||
| 805 | |||
| 806 | Format: Command Code (0x08) followed by 5 bytes. | ||
| 807 | |||
| 808 | * Example 1: Downlink Payload: AE 01 02 58 12** ~-~-->** AT+STDC=1,600,18 | ||
| 809 | |||
| 810 | |||
| 811 | = 4. Battery & Power Consumption = | ||
| 812 | |||
| 813 | |||
| 814 | PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. | ||
| 815 | |||
| 816 | [[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . | ||
| 817 | |||
| 818 | |||
| 819 | = 5. OTA firmware update = | ||
| 820 | |||
| 821 | |||
| 822 | 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/]] | ||
| 823 | |||
| 824 | |||
| 825 | = 6. FAQ = | ||
| 826 | |||
| 827 | == 6.1 How to use AT Command via UART to access device? == | ||
| 828 | |||
| 829 | |||
| 830 | 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]] | ||
| 831 | |||
| 832 | |||
| 833 | == 6.2 How to update firmware via UART port? == | ||
| 834 | |||
| 835 | |||
| 836 | 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]] | ||
| 837 | |||
| 838 | |||
| 839 | == 6.3 How to change the LoRa Frequency Bands/Region? == | ||
| 840 | |||
| 841 | |||
| 842 | You can follow the instructions for [[how to upgrade image>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]. | ||
| 843 | When downloading the images, choose the required image file for download. | ||
| 844 | |||
| 845 | |||
| 846 | = 7. Order Info = | ||
| 847 | |||
| 848 | |||
| 849 | [[image:image-20230131153105-4.png]] | ||
| 850 | |||
| 851 | |||
| 852 | = 8. Packing Info = | ||
| 853 | |||
| 854 | |||
| 855 | (% style="color:#037691" %)**Package Includes**: | ||
| 856 | |||
| 857 | * PS-LB LoRaWAN Pressure Sensor | ||
| 858 | |||
| 859 | (% style="color:#037691" %)**Dimension and weight**: | ||
| 860 | |||
| 861 | * Device Size: cm | ||
| 862 | * Device Weight: g | ||
| 863 | * Package Size / pcs : cm | ||
| 864 | * Weight / pcs : g | ||
| 865 | |||
| 866 | |||
| 867 | = 9. Support = | ||
| 868 | |||
| 869 | |||
| 870 | * 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. | ||
| 871 | |||
| 872 | * 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:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] | ||
| 873 | |||
| 874 |