<
From version < 131.1 >
edited by Xiaoling
on 2022/06/10 16:15
To version < 133.5 >
edited by Xiaoling
on 2022/06/10 16:39
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -141,44 +141,43 @@
141 141  
142 142  Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
143 143  
144 +**Add APP EUI in the application**
144 144  
145 -**Register the device**
146 +[[image:image-20220610161353-4.png]]
146 146  
148 +[[image:image-20220610161353-5.png]]
147 147  
148 -[[image:1654592600093-601.png]]
150 +[[image:image-20220610161353-6.png]]
149 149  
150 150  
153 +[[image:image-20220610161353-7.png]]
151 151  
152 -**Add APP EUI and DEV EUI**
153 153  
154 -[[image:1654592619856-881.png]]
156 +You can also choose to create the device manually.
155 155  
158 + [[image:image-20220610161538-8.png]]
156 156  
157 157  
158 -**Add APP EUI in the application**
159 159  
160 -[[image:1654592632656-512.png]]
162 +**Add APP KEY and DEV EUI**
161 161  
164 +[[image:image-20220610161538-9.png]]
162 162  
163 163  
164 -**Add APP KEY**
165 165  
166 -[[image:1654592653453-934.png]]
168 +(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
167 167  
168 168  
169 -(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
170 -
171 -
172 172  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
173 173  
174 -[[image:image-20220607170442-2.png]]
173 +[[image:image-20220610161724-10.png]]
175 175  
176 176  
177 177  (((
178 -(% style="color:blue" %)**Step 3**(%%)**:** The LLDS12 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.
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.
179 179  )))
180 180  
181 -[[image:1654833501679-968.png]]
180 +[[image:1654849068701-275.png]]
182 182  
183 183  
184 184  
... ... @@ -185,11 +185,10 @@
185 185  == 2.3  ​Uplink Payload ==
186 186  
187 187  (((
188 -LLDS12 will uplink payload via LoRaWAN with below payload format: 
189 -)))
187 +LDDS75 will uplink payload via LoRaWAN with below payload format:
190 190  
191 -(((
192 -Uplink payload includes in total 11 bytes.
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
193 193  )))
194 194  
195 195  (((
... ... @@ -199,15 +199,15 @@
199 199  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
200 200  |=(% style="width: 62.5px;" %)(((
201 201  **Size (bytes)**
202 -)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
203 -|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
204 -[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
205 -)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
206 -[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
207 -)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
208 -[[Message Type>>||anchor="H2.3.7A0MessageType"]]
209 -)))
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"]]
210 210  
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 +
211 211  [[image:1654833689380-972.png]]
212 212  
213 213  
... ... @@ -215,7 +215,7 @@
215 215  === 2.3.1  Battery Info ===
216 216  
217 217  
218 -Check the battery voltage for LLDS12.
216 +Check the battery voltage for LDDS75.
219 219  
220 220  Ex1: 0x0B45 = 2885mV
221 221  
... ... @@ -223,49 +223,23 @@
223 223  
224 224  
225 225  
226 -=== 2.3.2  DS18B20 Temperature sensor ===
224 +=== 2.3.2  Distance ===
227 227  
228 -This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
226 +Get the distance. Flat object range 280mm - 7500mm.
229 229  
228 +For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is
230 230  
231 -**Example**:
230 +**0B05(H) = 2821 (D) = 2821 mm.**
232 232  
233 -If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
234 234  
235 -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.
236 236  
237 237  
237 +=== 2.3.3  Interrupt Pin ===
238 238  
239 -=== 2.3.3  Distance ===
240 -
241 -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.
242 -
243 -
244 -**Example**:
245 -
246 -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.
247 -
248 -
249 -
250 -=== 2.3.4  Distance signal strength ===
251 -
252 -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.
253 -
254 -
255 -**Example**:
256 -
257 -If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
258 -
259 -Customers can judge whether they need to adjust the environment based on the signal strength.
260 -
261 -
262 -
263 -=== 2.3.5  Interrupt Pin ===
264 -
265 265  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.
266 266  
267 -Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
268 -
269 269  **Example:**
270 270  
271 271  0x00: Normal uplink packet.
... ... @@ -273,35 +273,28 @@
273 273  0x01: Interrupt Uplink Packet.
274 274  
275 275  
248 +=== 2.3.4  DS18B20 Temperature sensor ===
276 276  
277 -=== 2.3. LiDAR temp ===
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.
278 278  
279 -Characterize the internal temperature value of the sensor.
252 +**Example**:
280 280  
281 -**Example: **
282 -If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
283 -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
284 284  
256 +If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
285 285  
258 +Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
286 286  
287 -=== 2.3.7  Message Type ===
260 +=== 2.3.5  Sensor Flag ===
288 288  
289 -(((
290 -For a normal uplink payload, the message type is always 0x01.
291 -)))
262 +0x01: Detect Ultrasonic Sensor
292 292  
293 -(((
294 -Valid Message Type:
295 -)))
264 +0x00: No Ultrasonic Sensor
296 296  
297 297  
298 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
299 -|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
300 -|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
301 -|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
267 +===
268 +(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
302 302  
303 -=== 2.3.8  Decode payload in The Things Network ===
304 -
305 305  While using TTN network, you can add the payload format to decode the payload.
306 306  
307 307  
1654849068701-275.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +88.3 KB
Content
image-20220610161724-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +180.0 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0