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
-
... ... @@ -67,22 +67,29 @@ 67 67 68 68 69 69 70 - 71 - 72 - 73 73 = 1. Introduction = 74 74 75 75 == 1.1 What is LoRaWAN Soil pH Sensor == 76 76 74 +((( 77 77 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. 76 +))) 78 78 78 +((( 79 79 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. 80 +))) 80 80 82 +((( 81 81 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. 84 +))) 82 82 86 +((( 83 83 LSPH01 is powered by (% style="color:#4f81bd" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use up to 5 years. 88 +))) 84 84 90 +((( 85 85 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. 92 +))) 86 86 87 87 88 88 [[image:1654592435432-887.png]] ... ... @@ -210,7 +210,9 @@ 210 210 [[image:image-20220607170442-2.png]] 211 211 212 212 220 +((( 213 213 (% 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. 222 +))) 214 214 215 215 [[image:1654592697690-910.png]] 216 216 ... ... @@ -218,11 +218,17 @@ 218 218 219 219 == 2.3 Uplink Payload == 220 220 230 +((( 221 221 LSPH01 will uplink payload via LoRaWAN with below payload format: 232 +))) 222 222 234 +((( 223 223 Uplink payload includes in total 11 bytes. 236 +))) 224 224 238 +((( 225 225 Normal uplink payload: 240 +))) 226 226 227 227 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 228 228 |((( ... ... @@ -306,13 +306,17 @@ 306 306 307 307 === 2.3.6 Message Type === 308 308 324 +((( 309 309 For a normal uplink payload, the message type is always 0x01. 326 +))) 310 310 328 +((( 311 311 Valid Message Type: 330 +))) 312 312 313 313 314 314 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 315 -|**Message Type Code**|**Description**|**Payload** 334 +|=**Message Type Code**|=**Description**|=**Payload** 316 316 |0x01|Normal Uplink|[[Normal Uplink Payload>>path:#H2.3200BUplinkPayload]] 317 317 |0x02|Reply configures info|[[Configure Info Payload>>path:#H3.4GetFirmwareVersionInfo]] 318 318 |0x03|Reply Calibration Info|[[Calibration Payload>>path:#H2.7Calibration]] ... ... @@ -344,12 +344,21 @@ 344 344 345 345 == 2.5 Show Data in DataCake IoT Server == 346 346 366 +((( 347 347 [[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 +))) 348 348 370 +((( 371 + 372 +))) 349 349 374 +((( 350 350 (% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.** 376 +))) 351 351 378 +((( 352 352 (% 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:** 380 +))) 353 353 354 354 355 355 [[image:1654592790040-760.png]] ... ... @@ -481,7 +481,6 @@ 481 481 Always 0x03 482 482 ))) 483 483 484 - 485 485 User can also send 0x14 downlink command to poll the current calibration payload. 486 486 487 487 [[image:image-20220607171416-7.jpeg]] ... ... @@ -547,9 +547,6 @@ 547 547 * Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 548 548 * Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) 549 549 550 - 551 - 552 - 553 553 === 2.8.3 CN470-510 (CN470) === 554 554 555 555 Used in China, Default use CHE=1 ... ... @@ -617,8 +617,6 @@ 617 617 * Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include) 618 618 619 619 620 - 621 - 622 622 === 2.8.5 AS920-923 & AS923-925 (AS923) === 623 623 624 624 (% style="color:blue" %)**Default Uplink channel:** ... ... @@ -734,8 +734,6 @@ 734 734 * Blink once when device transmit a packet. 735 735 736 736 737 - 738 - 739 739 == 2.10 Firmware Change Log == 740 740 741 741 ... ... @@ -812,9 +812,6 @@ 812 812 * Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode 813 813 * Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger 814 814 815 - 816 - 817 - 818 818 == 3.3 Calibrate Sensor == 819 819 820 820 Detail See [[Calibration Guide>>path:#H2.7Calibration]] for the user of 0x13 and 0x14 downlink commands ... ... @@ -832,7 +832,6 @@ 832 832 * Reply to the confirmation package: 26 01 833 833 * Reply to non-confirmed packet: 26 00 834 834 835 - 836 836 Device will send an uplink after got this downlink command. With below payload: 837 837 838 838 Configures info payload: ... ... @@ -1055,9 +1055,6 @@ 1055 1055 * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 1056 1056 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 1057 1057 1058 - 1059 - 1060 - 1061 1061 = 9. Packing Info = 1062 1062 1063 1063 ... ... @@ -1072,9 +1072,6 @@ 1072 1072 * Package Size / pcs : cm 1073 1073 * Weight / pcs : g 1074 1074 1075 - 1076 - 1077 - 1078 1078 = 10. Support = 1079 1079 1080 1080 * 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.