Changes for page LSN50v2-D20-D22-D23 LoRaWAN Temperature Sensor User Manual
Last modified by Xiaoling on 2024/01/17 16:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -72,25 +72,15 @@ 72 72 73 73 == 1.1 What is LoRaWAN Soil pH Sensor == 74 74 75 -((( 76 76 The Dragino LSPH01 is a (% style="color:#4f81bd" %)**LoRaWAN Soil pH Sensor**(%%) for IoT of Agriculture. It is designed to measure the soil PH and soil temperature, so to send to the platform to analyze the soil acid or alkali level. The probe is IP68 waterproof. 77 -))) 78 78 79 -((( 80 80 LSPH01 probe is made by Solid AgCl reference electrode and Pure metal pH sensitive electrode. It can detect soil's** (% style="color:#4f81bd" %)pH (%%)**with high accuracy and stable value. The LSPH01 probe can be buried into soil for long time use. 81 -))) 82 82 83 -((( 84 84 The LoRa wireless technology used in LSPH01 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. 85 -))) 86 86 87 -((( 88 88 LSPH01 is powered by (% style="color:#4f81bd" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years. 89 -))) 90 90 91 -((( 92 92 Each LSPH01 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. 93 -))) 94 94 95 95 96 96 [[image:1654592435432-887.png]] ... ... @@ -221,9 +221,7 @@ 221 221 [[image:image-20220607170442-2.png]] 222 222 223 223 224 -((( 225 225 (% style="color:blue" %)**Step 3**(%%)**:** The LSPH01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel. 226 -))) 227 227 228 228 [[image:1654592697690-910.png]] 229 229 ... ... @@ -231,17 +231,11 @@ 231 231 232 232 == 2.3 Uplink Payload == 233 233 234 -((( 235 235 LSPH01 will uplink payload via LoRaWAN with below payload format: 236 -))) 237 237 238 -((( 239 239 Uplink payload includes in total 11 bytes. 240 -))) 241 241 242 -((( 243 243 Normal uplink payload: 244 -))) 245 245 246 246 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 247 247 |((( ... ... @@ -325,17 +325,13 @@ 325 325 326 326 === 2.3.6 Message Type === 327 327 328 -((( 329 329 For a normal uplink payload, the message type is always 0x01. 330 -))) 331 331 332 -((( 333 333 Valid Message Type: 334 -))) 335 335 336 336 337 337 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 338 -| =**Message Type Code**|=**Description**|=**Payload**316 +|**Message Type Code**|**Description**|**Payload** 339 339 |0x01|Normal Uplink|[[Normal Uplink Payload>>path:#H2.3200BUplinkPayload]] 340 340 |0x02|Reply configures info|[[Configure Info Payload>>path:#H3.4GetFirmwareVersionInfo]] 341 341 |0x03|Reply Calibration Info|[[Calibration Payload>>path:#H2.7Calibration]] ... ... @@ -755,7 +755,6 @@ 755 755 * Blink once when device transmit a packet. 756 756 757 757 758 - 759 759 == 2.10 Firmware Change Log == 760 760 761 761