Changes for page LDDS45 - LoRaWAN Distance Detection Sensor User Manual
Last modified by Mengting Qiu on 2025/02/26 15:04
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -238,23 +238,24 @@ 238 238 239 239 240 240 241 -=== 2.3.4 Soil Temperature ===241 +=== 2.3.4 Distance signal strength === 242 242 243 - GetSoilTemperature243 +Refers to the signal strength, the default output value will be between 0-65535. When the distance measurement gear is fixed, the farther the distance measurement is, the lower the signal strength; the lower the target reflectivity, the lower the signal strength. When Strength is greater than 100 and not equal to 65535, the measured value of Dist is considered credible. 244 244 245 245 246 246 **Example**: 247 247 248 -If payload is: **0105H**:(0105&FC00==0), temp=0105H/10=26.1degree248 +If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible. 249 249 250 - If payload is:**FF3FH**:(FF3F&FC00==1),temp=(FF3FH- 65536)/10 = -19.3 degrees.250 +Customers can judge whether they need to adjust the environment based on the signal strength. 251 251 252 252 253 253 254 -=== 2.3.5 Interrupt Pin === 254 +=== 2.3.5 Interrupt Pin === 255 255 256 256 This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.2SetInterruptMode"]] for the hardware and software set up. 257 257 258 +Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>path:#pins]]. 258 258 259 259 **Example:** 260 260 ... ... @@ -264,8 +264,18 @@ 264 264 265 265 266 266 267 -=== 2.3.6 MessageType ===268 +=== 2.3.6 LiDAR temp === 268 268 270 +Characterize the internal temperature value of the sensor. 271 + 272 +**Example: ** 273 +If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃. 274 +If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃. 275 + 276 + 277 + 278 +=== 2.3.7 Message Type === 279 + 269 269 ((( 270 270 For a normal uplink payload, the message type is always 0x01. 271 271 ))) ... ... @@ -279,9 +279,8 @@ 279 279 |=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload** 280 280 |(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3200BUplinkPayload"]] 281 281 |(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H3.4GetFirmwareVersionInfo"]] 282 -|(% style="width:160px" %)0x03|(% style="width:163px" %)Reply Calibration Info|(% style="width:173px" %)[[Calibration Payload>>||anchor="H2.7Calibration"]] 283 283 284 -=== 2.3. 7Decode payload in The Things Network ===294 +=== 2.3.8 Decode payload in The Things Network === 285 285 286 286 While using TTN network, you can add the payload format to decode the payload. 287 287