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)
-
Attachments (0 modified, 8 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -33,7 +33,7 @@ 33 33 Each LDDS75 pre-loads with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect if there is network coverage, after power on. 34 34 35 35 36 -(% style="color:#4472c4" %) * ****(%%)Actually lifetime depends on network coverage and uplink interval and other factors36 +(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors 37 37 ))) 38 38 ))) 39 39 ... ... @@ -57,7 +57,6 @@ 57 57 * IP66 Waterproof Enclosure 58 58 * 4000mAh or 8500mAh Battery for long term use 59 59 60 - 61 61 == 1.3 Specification == 62 62 63 63 === 1.3.1 Rated environmental conditions === ... ... @@ -94,7 +94,6 @@ 94 94 * Bottom water level monitoring 95 95 96 96 97 - 98 98 == 1.6 Pin mapping and power on == 99 99 100 100 ... ... @@ -121,7 +121,7 @@ 121 121 ))) 122 122 123 123 ((( 124 -[[image:16548 27857527-556.png]]122 +[[image:1654848616367-242.png]] 125 125 ))) 126 126 127 127 ((( ... ... @@ -129,57 +129,57 @@ 129 129 ))) 130 130 131 131 ((( 132 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LS PH01.130 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75. 133 133 ))) 134 134 135 135 ((( 136 -Each LS PH01is shipped with a sticker with the default deviceEUIas below:134 +Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below. 137 137 ))) 138 138 139 139 [[image:image-20220607170145-1.jpeg]] 140 140 141 141 140 +For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI. 142 142 143 - You canenter this key in the LoRaWAN Server portal. Below is TTN screen shot:142 +Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot: 144 144 144 +**Add APP EUI in the application** 145 145 146 - **Register the device**146 +[[image:image-20220610161353-4.png]] 147 147 148 +[[image:image-20220610161353-5.png]] 148 148 149 -[[image: 1654592600093-601.png]]150 +[[image:image-20220610161353-6.png]] 150 150 151 151 153 +[[image:image-20220610161353-7.png]] 152 152 153 -**Add APP EUI and DEV EUI** 154 154 155 - [[image:1654592619856-881.png]]156 +You can also choose to create the device manually. 156 156 158 + [[image:image-20220610161538-8.png]] 157 157 158 158 159 -**Add APP EUI in the application** 160 160 161 - [[image:1654592632656-512.png]]162 +**Add APP KEY and DEV EUI** 162 162 164 +[[image:image-20220610161538-9.png]] 163 163 164 164 165 -**Add APP KEY** 166 166 167 - [[image:1654592653453-934.png]]168 +(% style="color:blue" %)**Step 2**(%%): Power on LDDS75 168 168 169 169 170 -(% style="color:blue" %)**Step 2**(%%): Power on LLDS12 171 - 172 - 173 173 Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position). 174 174 175 -[[image:image-2022060 7170442-2.png]]173 +[[image:image-20220610161724-10.png]] 176 176 177 177 178 178 ((( 179 -(% style="color:blue" %)**Step 3**(%%)**:** The L LDS12will 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.177 +(% style="color:blue" %)**Step 3**(%%)**:** The LDDS75 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. 180 180 ))) 181 181 182 -[[image:16548 33501679-968.png]]180 +[[image:1654849068701-275.png]] 183 183 184 184 185 185 ... ... @@ -186,11 +186,10 @@ 186 186 == 2.3 Uplink Payload == 187 187 188 188 ((( 189 -LLDS12 will uplink payload via LoRaWAN with below payload format: 190 -))) 187 +LDDS75 will uplink payload via LoRaWAN with below payload format: 191 191 192 - (((193 - Uplink payload includesintotal11bytes.189 +Uplink payload includes in total 4 bytes. 190 +Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance 194 194 ))) 195 195 196 196 ((( ... ... @@ -200,15 +200,15 @@ 200 200 (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %) 201 201 |=(% style="width: 62.5px;" %)((( 202 202 **Size (bytes)** 203 -)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1** 204 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)((( 205 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]] 206 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|((( 207 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]] 208 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|((( 209 -[[Message Type>>||anchor="H2.3.7A0MessageType"]] 210 -))) 200 +)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1** 201 +|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|((( 202 +[[Distance>>||anchor="H2.3.3A0Distance"]] 211 211 204 +(unit: mm) 205 +)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|((( 206 +[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]] 207 +)))|[[Sensor Flag>>path:#Sensor_Flag]] 208 + 212 212 [[image:1654833689380-972.png]] 213 213 214 214 ... ... @@ -216,7 +216,7 @@ 216 216 === 2.3.1 Battery Info === 217 217 218 218 219 -Check the battery voltage for L LDS12.216 +Check the battery voltage for LDDS75. 220 220 221 221 Ex1: 0x0B45 = 2885mV 222 222 ... ... @@ -224,49 +224,23 @@ 224 224 225 225 226 226 227 -=== 2.3.2 D S18B20 Temperaturesensor===224 +=== 2.3.2 Distance === 228 228 229 - Thisisoptional, usercanconnectexternalDS18B20sensor to the +3.3v, 1-wireand GND pin . and this field will report temperature.226 +Get the distance. Flat object range 280mm - 7500mm. 230 230 228 +For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is 231 231 232 -** Example**:230 +**0B05(H) = 2821 (D) = 2821 mm.** 233 233 234 -If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 235 235 236 -If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 233 +* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor. 234 +* If the sensor value lower than 0x0118 (280mm), the sensor value will be invalid. Since v1.1.4, all value lower than 280mm will be set to 0x0014(20mm) which means the value is invalid. 237 237 238 238 237 +=== 2.3.3 Interrupt Pin === 239 239 240 -=== 2.3.3 Distance === 241 - 242 -Represents the distance value of the measurement output, the default unit is cm, and the value range parsed as a decimal number is 0-1200. In actual use, when the signal strength value Strength. 243 - 244 - 245 -**Example**: 246 - 247 -If the data you get from the register is 0x0B 0xEA, the distance between the sensor and the measured object is 0BEA(H) = 3050 (D)/10 = 305cm. 248 - 249 - 250 - 251 -=== 2.3.4 Distance signal strength === 252 - 253 -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. 254 - 255 - 256 -**Example**: 257 - 258 -If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible. 259 - 260 -Customers can judge whether they need to adjust the environment based on the signal strength. 261 - 262 - 263 - 264 -=== 2.3.5 Interrupt Pin === 265 - 266 266 This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H4.2A0SetInterruptMode"]] for the hardware and software set up. 267 267 268 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]]. 269 - 270 270 **Example:** 271 271 272 272 0x00: Normal uplink packet. ... ... @@ -274,35 +274,30 @@ 274 274 0x01: Interrupt Uplink Packet. 275 275 276 276 248 +=== 2.3.4 DS18B20 Temperature sensor === 277 277 278 - ===2.3.6LiDARtemp===250 +This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature. 279 279 280 - Characterize the internal temperature valueof the sensor.252 +**Example**: 281 281 282 -**Example: ** 283 -If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃. 284 -If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃. 254 +If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree 285 285 256 +If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees. 286 286 258 +(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021. 287 287 288 -=== 2.3.7 Message Type === 289 289 290 -((( 291 -For a normal uplink payload, the message type is always 0x01. 292 -))) 293 293 294 -((( 295 -Valid Message Type: 296 -))) 262 +=== 2.3.5 Sensor Flag === 297 297 264 +0x01: Detect Ultrasonic Sensor 298 298 299 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %) 300 -|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload** 301 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]] 302 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]] 266 +0x00: No Ultrasonic Sensor 303 303 304 -=== 2.3.8 Decode payload in The Things Network === 305 305 269 +=== 270 +(% style="color:inherit; font-family:inherit" %)2.3.6 Decode payload in The Things Network(%%) === 271 + 306 306 While using TTN network, you can add the payload format to decode the payload. 307 307 308 308 ... ... @@ -1280,7 +1280,6 @@ 1280 1280 * (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 1281 1281 * (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 1282 1282 1283 - 1284 1284 = 10. Packing Info = 1285 1285 1286 1286 ... ... @@ -1295,7 +1295,6 @@ 1295 1295 * Package Size / pcs : cm 1296 1296 * Weight / pcs : g 1297 1297 1298 - 1299 1299 = 11. Support = 1300 1300 1301 1301 * 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.
- 1654849068701-275.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +88.3 KB - Content
- image-20220610161353-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.2 KB - Content
- image-20220610161353-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +42.7 KB - Content
- image-20220610161353-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +36.3 KB - Content
- image-20220610161353-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +19.1 KB - Content
- image-20220610161538-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.2 KB - Content
- image-20220610161538-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +28.7 KB - Content
- image-20220610161724-10.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +180.0 KB - Content