Skip to Content
Last modified by Mengting Qiu on 2025/08/06 17:02
From version 173.6
edited by Xiaoling
on 2022/06/15 10:15
Change comment: There is no comment for this version
To version 157.1
edited by Xiaoling
on 2022/06/15 09:09
Change comment: Uploaded new attachment "image-20220615090910-2.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -100,128 +100,70 @@
100 100  * IP66 Waterproof Enclosure
101 101  * 8500mAh Battery for long term use
102 102  
103 -== 1.3  Suitable Container & Liquid ==
104 104  
105 -* Solid Wall container such as: steel, iron, glass, ceramics, non-foaming plastics etc.
106 -* Container shape is regular, and surface is smooth.
107 -* Container Thickness:
108 -** Pure metal material.  2~~8mm, best is 3~~5mm
109 -** Pure non metal material: <10 mm
110 -* Pure liquid without irregular deposition.
111 111  
112 -== 1.4  Mechanical ==
105 +== 1.3  Specification ==
113 113  
114 -[[image:image-20220615090910-1.png]]
107 +=== 1.3.1  Rated environmental conditions ===
115 115  
109 +[[image:image-20220610154839-1.png]]
116 116  
117 -[[image:image-20220615090910-2.png]]
111 +(((
112 +**Remarks: (1) a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);       **
118 118  
114 +**~ b. When the ambient temperature is 40-50 ℃, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation)**
115 +)))
119 119  
120 120  
121 -== 1.5  Install LDDS20 ==
122 122  
119 +=== 1.3.2  Effective measurement range Reference beam pattern ===
123 123  
124 -(% style="color:blue" %)**Step 1**(%%):  Choose the installation point.
121 +**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
125 125  
126 -LDDS20 (% style="color:red" %)**MUST**(%%) be installed on the container bottom middle position.
127 127  
128 -[[image:image-20220615091045-3.png]]
129 129  
125 +[[image:1654852253176-749.png]]
130 130  
131 131  
132 -(% style="color:blue" %)**Step 2**(%%):  Polish the installation point.
133 133  
134 -For Metal Surface with paint, it is important to polish the surface, first use crude sand paper to polish the paint level , then use exquisite sand paper to polish the metal level to make it shine & smooth.
129 +(((
130 +**(2)** **The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.**
131 +)))
135 135  
136 -[[image:image-20220615092010-11.png]]
137 137  
134 +[[image:1654852175653-550.png]](% style="display:none" %) ** **
138 138  
139 -No polish needed if the container is shine metal surface without paint or non-metal container.
140 140  
141 -[[image:image-20220615092044-12.png]]
142 142  
138 +== 1.5 ​ Applications ==
143 143  
140 +* Horizontal distance measurement
141 +* Liquid level measurement
142 +* Parking management system
143 +* Object proximity and presence detection
144 +* Intelligent trash can management system
145 +* Robot obstacle avoidance
146 +* Automatic control
147 +* Sewer
148 +* Bottom water level monitoring
144 144  
145 -(% style="color:blue" %)**Step3:   **(%%)Test the installation point.
150 +== 1.6  Pin mapping and power on ==
146 146  
147 -Power on LDDS75, check if the blue LED is on, If the blue LED is on, means the sensor works. Then put ultrasonic coupling paste on the sensor and put it tightly on the installation point.
148 148  
153 +[[image:1654847583902-256.png]]
149 149  
150 -It is necessary to put the coupling paste between the sensor and the container, otherwise LDDS20 won’t detect the liquid level.
151 151  
152 -[[image:1655256160324-178.png]][[image:image-20220615092327-13.png]]
153 153  
157 += 2.  Configure LDDS75 to connect to LoRaWAN network =
154 154  
155 -After paste the LDDS20 well, power on LDDS20. In the first 30 seconds of booting, device will check the sensors status and BLUE LED will show the status as below. After 30 seconds, BLUE LED will be off to save battery life.
156 -
157 -
158 -(% style="color:red" %)**LED Status:**
159 -
160 -* Onboard LED: When power on device, the onboard LED will fast blink 4 times which means detect the sensor well.
161 -
162 -* (% style="color:blue" %)BLUE LED(% style="color:red" %) always ON(%%): Sensor is power on but doesn’t detect liquid. There is problem in installation point.
163 -* (% style="color:blue" %)BLUE LED(% style="color:red" %) slowly blinking(%%): Sensor detects Liquid Level, The installation point is good.
164 -
165 -LDDS20 will enter into low power mode at 30 seconds after system reset or power on, Blue LED will be off after that.
166 -
167 -
168 -(% style="color:red" %)**Note 2:**
169 -
170 -(% style="color:red" %)Ultrasonic coupling paste (%%) is subjected in most shipping way. So the default package doesn’t include it and user needs to purchase locally.
171 -
172 -
173 -
174 -(% style="color:blue" %)**Step4:   **(%%)Install use Epoxy ab glue.
175 -
176 -Prepare Eproxy AB glue.
177 -
178 -Put Eproxy AB glue in the sensor and press it hard on the container installation point.
179 -
180 -Reset LDDS20 and see if the BLUE LED is slowly blinking.
181 -
182 -[[image:image-20220615091045-8.png||height="226" width="380"]] [[image:image-20220615091045-9.png||height="239" width="339"]]
183 -
184 -
185 -(% style="color:red" %)**Note 1:**
186 -
187 -Eproxy AB glue needs 3~~ 5 minutes to stable attached. we can use other glue material to keep it in the position.
188 -
189 -
190 -(% style="color:red" %)**Note 2:**
191 -
192 -(% style="color:red" %)Eproxy AB glue(%%) is subjected in most shipping way. So the default package doesn’t include it and user needs to purchase locally.
193 -
194 -
195 -
196 -== 1.6 ​ Applications ==
197 -
198 -* Smart liquid control solution.
199 -* Smart liquefied gas solution.
200 -
201 -== 1.7  Precautions ==
202 -
203 -* At room temperature, containers of different materials, such as steel, glass, iron, ceramics, non-foamed plastics and other dense materials, have different detection blind areas and detection limit heights.
204 -* For containers of the same material at room temperature, the detection blind zone and detection limit height are also different for the thickness of the container.
205 -* When the detected liquid level exceeds the effective detection value of the sensor, and the liquid level of the liquid to be measured shakes or tilts, the detected liquid height is unstable.
206 -
207 -== 1.8  Pin mapping and power on ==
208 -
209 -
210 -[[image:1655257026882-201.png]]
211 -
212 -
213 -
214 -= 2.  Configure LDDS20 to connect to LoRaWAN network =
215 -
216 -
217 217  == 2.1  How it works ==
218 218  
219 219  (((
220 -The LDDS20 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS20. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value.
162 +The LDDS75 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS75. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value
221 221  )))
222 222  
223 223  (((
224 -In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.A0UsingtheATCommands"]]to set the keys in the LDDS20.
166 +In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.A0ConfigureLDDS75viaATCommandorLoRaWANDownlink"]]to set the keys in the LDDS75.
225 225  )))
226 226  
227 227  
... ... @@ -233,7 +233,7 @@
233 233  )))
234 234  
235 235  (((
236 -[[image:1655257698953-697.png]]
178 +[[image:1654848616367-242.png]]
237 237  )))
238 238  
239 239  (((
... ... @@ -243,11 +243,11 @@
243 243  (((
244 244  
245 245  
246 -(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS20.
188 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
247 247  )))
248 248  
249 249  (((
250 -Each LDDS20 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
192 +Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
251 251  )))
252 252  
253 253  [[image:image-20220607170145-1.jpeg]]
... ... @@ -277,7 +277,6 @@
277 277  [[image:image-20220610161353-7.png]]
278 278  
279 279  
280 -
281 281  You can also choose to create the device manually.
282 282  
283 283   [[image:image-20220610161538-8.png]]
... ... @@ -290,17 +290,16 @@
290 290  
291 291  
292 292  
293 -(% style="color:blue" %)**Step 2**(%%):  Power on LDDS20
234 +(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
294 294  
295 295  
296 296  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
297 297  
298 -[[image:image-20220615095102-14.png]]
239 +[[image:image-20220610161724-10.png]]
299 299  
300 300  
301 -
302 302  (((
303 -(% style="color:blue" %)**Step 3**(%%)**:**  The LDDS20 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.
243 +(% 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.
304 304  )))
305 305  
306 306  [[image:1654849068701-275.png]]
... ... @@ -311,10 +311,12 @@
311 311  
312 312  (((
313 313  (((
314 -LDDS20 will uplink payload via LoRaWAN with below payload format: 
254 +LDDS75 will uplink payload via LoRaWAN with below payload format: 
255 +)))
315 315  
316 -Uplink payload includes in total 8 bytes.
317 -Payload for firmware version v1.1.4. . Before v1.1.3, there is only 5 bytes: BAT and Distance(Please check manual v1.2.0 if you have 5 bytes payload).
257 +(((
258 +Uplink payload includes in total 4 bytes.
259 +Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
318 318  )))
319 319  )))
320 320  
... ... @@ -341,7 +341,7 @@
341 341  === 2.3.1  Battery Info ===
342 342  
343 343  
344 -Check the battery voltage for LDDS20.
286 +Check the battery voltage for LDDS75.
345 345  
346 346  Ex1: 0x0B45 = 2885mV
347 347  
... ... @@ -352,19 +352,20 @@
352 352  === 2.3.2  Distance ===
353 353  
354 354  (((
355 -Get the distance. Flat object range 20mm - 2000mm.
297 +Get the distance. Flat object range 280mm - 7500mm.
356 356  )))
357 357  
358 358  (((
359 -For example, if the data you get from the register is __0x06 0x05__, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0605(H) = 1541 (D) = 1541 mm.**
301 +For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0B05(H) = 2821 (D) = 2821 mm.**
360 360  )))
361 361  
362 -* If the sensor value is 0x0000, it means system doesn't detect ultrasonic sensor.
363 -* If the sensor value lower than 0x0014 (20mm), the sensor value will be invalid.
364 364  
305 +* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
306 +* 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.
307 +
365 365  === 2.3.3  Interrupt Pin ===
366 366  
367 -This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.2A0SetInterruptMode"]] for the hardware and software set up.
310 +This data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H3.3A0SetInterruptMode"]] for the hardware and software set up.
368 368  
369 369  **Example:**
370 370  
... ... @@ -410,91 +410,533 @@
410 410  The payload decoder function for TTN V3 is here:
411 411  
412 412  (((
413 -LDDS20 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS20/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
356 +LDDS75 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS75/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
414 414  )))
415 415  
416 416  
417 417  
418 -== 2.4  Downlink Payload ==
361 +== 2.4  Uplink Interval ==
419 419  
420 -By default, LDDS20 prints the downlink payload to console port.
363 +The LDDS75 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
421 421  
422 -[[image:image-20220615100930-15.png]]
423 423  
424 424  
425 -**Examples:**
367 +== 2.5  ​Show Data in DataCake IoT Server ==
426 426  
369 +(((
370 +[[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:
371 +)))
427 427  
428 -* (% style="color:blue" %)**Set TDC**
373 +(((
374 +
375 +)))
429 429  
430 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
377 +(((
378 +(% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.**
379 +)))
431 431  
432 -Payload:    01 00 00 1E    TDC=30S
381 +(((
382 +(% 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:**
383 +)))
433 433  
434 -Payload:    01 00 00 3C    TDC=60S
435 435  
386 +[[image:1654592790040-760.png]]
436 436  
437 -* (% style="color:blue" %)**Reset**
438 438  
439 -If payload = 0x04FF, it will reset the LDDS20
389 +[[image:1654592800389-571.png]]
440 440  
441 441  
442 -* (% style="color:blue" %)**CFM**
392 +(% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
443 443  
444 -Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
394 +(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
445 445  
396 +[[image:1654851029373-510.png]]
446 446  
447 447  
448 -== 2.5  ​Show Data in DataCake IoT Server ==
399 +After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
449 449  
401 +[[image:image-20220610165129-11.png||height="595" width="1088"]]
402 +
403 +
404 +
405 +== 2.6  Frequency Plans ==
406 +
450 450  (((
451 -[[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:
408 +The LDDS75 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
452 452  )))
453 453  
411 +
412 +
413 +=== 2.6.1  EU863-870 (EU868) ===
414 +
454 454  (((
416 +(% style="color:blue" %)**Uplink:**
417 +)))
418 +
419 +(((
420 +868.1 - SF7BW125 to SF12BW125
421 +)))
422 +
423 +(((
424 +868.3 - SF7BW125 to SF12BW125 and SF7BW250
425 +)))
426 +
427 +(((
428 +868.5 - SF7BW125 to SF12BW125
429 +)))
430 +
431 +(((
432 +867.1 - SF7BW125 to SF12BW125
433 +)))
434 +
435 +(((
436 +867.3 - SF7BW125 to SF12BW125
437 +)))
438 +
439 +(((
440 +867.5 - SF7BW125 to SF12BW125
441 +)))
442 +
443 +(((
444 +867.7 - SF7BW125 to SF12BW125
445 +)))
446 +
447 +(((
448 +867.9 - SF7BW125 to SF12BW125
449 +)))
450 +
451 +(((
452 +868.8 - FSK
453 +)))
454 +
455 +(((
455 455  
456 456  )))
457 457  
458 458  (((
459 -(% style="color:blue" %)**Step 1**(%%)**: Be sure that your device is programmed and properly connected to the network at this time.**
460 +(% style="color:blue" %)**Downlink:**
460 460  )))
461 461  
462 462  (((
463 -(% 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:**
464 +Uplink channels 1-9 (RX1)
464 464  )))
465 465  
467 +(((
468 +869.525 - SF9BW125 (RX2 downlink only)
469 +)))
466 466  
467 -[[image:1654592790040-760.png]]
468 468  
469 469  
470 -[[image:1654592800389-571.png]]
473 +=== 2.6.2  US902-928(US915) ===
471 471  
475 +(((
476 +Used in USA, Canada and South America. Default use CHE=2
472 472  
473 -(% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
478 +(% style="color:blue" %)**Uplink:**
474 474  
475 -(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.(% style="color:red" %)(Note: LDDS20 use same payload as LDDS75)(%%)**
480 +903.9 - SF7BW125 to SF10BW125
476 476  
477 -[[image:1654851029373-510.png]]
482 +904.1 - SF7BW125 to SF10BW125
478 478  
484 +904.3 - SF7BW125 to SF10BW125
479 479  
480 -After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
486 +904.5 - SF7BW125 to SF10BW125
481 481  
482 -[[image:image-20220610165129-11.png||height="595" width="1088"]]
488 +904.7 - SF7BW125 to SF10BW125
483 483  
490 +904.9 - SF7BW125 to SF10BW125
484 484  
492 +905.1 - SF7BW125 to SF10BW125
485 485  
486 -== 2.6  LED Indicator ==
494 +905.3 - SF7BW125 to SF10BW125
487 487  
488 -The LDDS20 has an internal LED which is to show the status of different state.
489 489  
497 +(% style="color:blue" %)**Downlink:**
490 490  
499 +923.3 - SF7BW500 to SF12BW500
500 +
501 +923.9 - SF7BW500 to SF12BW500
502 +
503 +924.5 - SF7BW500 to SF12BW500
504 +
505 +925.1 - SF7BW500 to SF12BW500
506 +
507 +925.7 - SF7BW500 to SF12BW500
508 +
509 +926.3 - SF7BW500 to SF12BW500
510 +
511 +926.9 - SF7BW500 to SF12BW500
512 +
513 +927.5 - SF7BW500 to SF12BW500
514 +
515 +923.3 - SF12BW500(RX2 downlink only)
516 +
517 +
518 +
519 +)))
520 +
521 +=== 2.6.3  CN470-510 (CN470) ===
522 +
523 +(((
524 +Used in China, Default use CHE=1
525 +)))
526 +
527 +(((
528 +(% style="color:blue" %)**Uplink:**
529 +)))
530 +
531 +(((
532 +486.3 - SF7BW125 to SF12BW125
533 +)))
534 +
535 +(((
536 +486.5 - SF7BW125 to SF12BW125
537 +)))
538 +
539 +(((
540 +486.7 - SF7BW125 to SF12BW125
541 +)))
542 +
543 +(((
544 +486.9 - SF7BW125 to SF12BW125
545 +)))
546 +
547 +(((
548 +487.1 - SF7BW125 to SF12BW125
549 +)))
550 +
551 +(((
552 +487.3 - SF7BW125 to SF12BW125
553 +)))
554 +
555 +(((
556 +487.5 - SF7BW125 to SF12BW125
557 +)))
558 +
559 +(((
560 +487.7 - SF7BW125 to SF12BW125
561 +)))
562 +
563 +(((
564 +
565 +)))
566 +
567 +(((
568 +(% style="color:blue" %)**Downlink:**
569 +)))
570 +
571 +(((
572 +506.7 - SF7BW125 to SF12BW125
573 +)))
574 +
575 +(((
576 +506.9 - SF7BW125 to SF12BW125
577 +)))
578 +
579 +(((
580 +507.1 - SF7BW125 to SF12BW125
581 +)))
582 +
583 +(((
584 +507.3 - SF7BW125 to SF12BW125
585 +)))
586 +
587 +(((
588 +507.5 - SF7BW125 to SF12BW125
589 +)))
590 +
591 +(((
592 +507.7 - SF7BW125 to SF12BW125
593 +)))
594 +
595 +(((
596 +507.9 - SF7BW125 to SF12BW125
597 +)))
598 +
599 +(((
600 +508.1 - SF7BW125 to SF12BW125
601 +)))
602 +
603 +(((
604 +505.3 - SF12BW125 (RX2 downlink only)
605 +)))
606 +
607 +
608 +
609 +=== 2.6.4  AU915-928(AU915) ===
610 +
611 +(((
612 +Default use CHE=2
613 +
614 +(% style="color:blue" %)**Uplink:**
615 +
616 +916.8 - SF7BW125 to SF12BW125
617 +
618 +917.0 - SF7BW125 to SF12BW125
619 +
620 +917.2 - SF7BW125 to SF12BW125
621 +
622 +917.4 - SF7BW125 to SF12BW125
623 +
624 +917.6 - SF7BW125 to SF12BW125
625 +
626 +917.8 - SF7BW125 to SF12BW125
627 +
628 +918.0 - SF7BW125 to SF12BW125
629 +
630 +918.2 - SF7BW125 to SF12BW125
631 +
632 +
633 +(% style="color:blue" %)**Downlink:**
634 +
635 +923.3 - SF7BW500 to SF12BW500
636 +
637 +923.9 - SF7BW500 to SF12BW500
638 +
639 +924.5 - SF7BW500 to SF12BW500
640 +
641 +925.1 - SF7BW500 to SF12BW500
642 +
643 +925.7 - SF7BW500 to SF12BW500
644 +
645 +926.3 - SF7BW500 to SF12BW500
646 +
647 +926.9 - SF7BW500 to SF12BW500
648 +
649 +927.5 - SF7BW500 to SF12BW500
650 +
651 +923.3 - SF12BW500(RX2 downlink only)
652 +
653 +
654 +
655 +)))
656 +
657 +=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
658 +
659 +(((
660 +(% style="color:blue" %)**Default Uplink channel:**
661 +)))
662 +
663 +(((
664 +923.2 - SF7BW125 to SF10BW125
665 +)))
666 +
667 +(((
668 +923.4 - SF7BW125 to SF10BW125
669 +)))
670 +
671 +(((
672 +
673 +)))
674 +
675 +(((
676 +(% style="color:blue" %)**Additional Uplink Channel**:
677 +)))
678 +
679 +(((
680 +(OTAA mode, channel added by JoinAccept message)
681 +)))
682 +
683 +(((
684 +
685 +)))
686 +
687 +(((
688 +(% style="color:blue" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
689 +)))
690 +
691 +(((
692 +922.2 - SF7BW125 to SF10BW125
693 +)))
694 +
695 +(((
696 +922.4 - SF7BW125 to SF10BW125
697 +)))
698 +
699 +(((
700 +922.6 - SF7BW125 to SF10BW125
701 +)))
702 +
703 +(((
704 +922.8 - SF7BW125 to SF10BW125
705 +)))
706 +
707 +(((
708 +923.0 - SF7BW125 to SF10BW125
709 +)))
710 +
711 +(((
712 +922.0 - SF7BW125 to SF10BW125
713 +)))
714 +
715 +(((
716 +
717 +)))
718 +
719 +(((
720 +(% style="color:blue" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
721 +)))
722 +
723 +(((
724 +923.6 - SF7BW125 to SF10BW125
725 +)))
726 +
727 +(((
728 +923.8 - SF7BW125 to SF10BW125
729 +)))
730 +
731 +(((
732 +924.0 - SF7BW125 to SF10BW125
733 +)))
734 +
735 +(((
736 +924.2 - SF7BW125 to SF10BW125
737 +)))
738 +
739 +(((
740 +924.4 - SF7BW125 to SF10BW125
741 +)))
742 +
743 +(((
744 +924.6 - SF7BW125 to SF10BW125
745 +)))
746 +
747 +(((
748 +
749 +)))
750 +
751 +(((
752 +(% style="color:blue" %)**Downlink:**
753 +)))
754 +
755 +(((
756 +Uplink channels 1-8 (RX1)
757 +)))
758 +
759 +(((
760 +923.2 - SF10BW125 (RX2)
761 +)))
762 +
763 +
764 +
765 +=== 2.6.6  KR920-923 (KR920) ===
766 +
767 +(((
768 +(% style="color:blue" %)**Default channel:**
769 +)))
770 +
771 +(((
772 +922.1 - SF7BW125 to SF12BW125
773 +)))
774 +
775 +(((
776 +922.3 - SF7BW125 to SF12BW125
777 +)))
778 +
779 +(((
780 +922.5 - SF7BW125 to SF12BW125
781 +)))
782 +
783 +(((
784 +
785 +)))
786 +
787 +(((
788 +(% style="color:blue" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
789 +)))
790 +
791 +(((
792 +922.1 - SF7BW125 to SF12BW125
793 +)))
794 +
795 +(((
796 +922.3 - SF7BW125 to SF12BW125
797 +)))
798 +
799 +(((
800 +922.5 - SF7BW125 to SF12BW125
801 +)))
802 +
803 +(((
804 +922.7 - SF7BW125 to SF12BW125
805 +)))
806 +
807 +(((
808 +922.9 - SF7BW125 to SF12BW125
809 +)))
810 +
811 +(((
812 +923.1 - SF7BW125 to SF12BW125
813 +)))
814 +
815 +(((
816 +923.3 - SF7BW125 to SF12BW125
817 +)))
818 +
819 +(((
820 +
821 +)))
822 +
823 +(((
824 +(% style="color:blue" %)**Downlink:**
825 +)))
826 +
827 +(((
828 +Uplink channels 1-7(RX1)
829 +)))
830 +
831 +(((
832 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
833 +)))
834 +
835 +
836 +
837 +=== 2.6.7  IN865-867 (IN865) ===
838 +
839 +(((
840 +(% style="color:blue" %)**Uplink:**
841 +)))
842 +
843 +(((
844 +865.0625 - SF7BW125 to SF12BW125
845 +)))
846 +
847 +(((
848 +865.4025 - SF7BW125 to SF12BW125
849 +)))
850 +
851 +(((
852 +865.9850 - SF7BW125 to SF12BW125
853 +)))
854 +
855 +(((
856 +
857 +)))
858 +
859 +(((
860 +(% style="color:blue" %)**Downlink:**
861 +)))
862 +
863 +(((
864 +Uplink channels 1-3 (RX1)
865 +)))
866 +
867 +(((
868 +866.550 - SF10BW125 (RX2)
869 +)))
870 +
871 +
872 +
873 +== 2.7  LED Indicator ==
874 +
875 +The LDDS75 has an internal LED which is to show the status of different state.
876 +
877 +
491 491  * Blink once when device power on.
492 492  * The device detects the sensor and flashes 5 times.
493 493  * Solid ON for 5 seconds once device successful Join the network.
494 494  * Blink once when device transmit a packet.
495 495  
496 -
497 -
498 498  == 2.8  ​Firmware Change Log ==
499 499  
500 500  
1655256160324-178.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -177.0 KB
Content
1655257026882-201.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1655257698953-697.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -101.7 KB
Content
image-20220615091045-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -209.8 KB
Content
image-20220615091045-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.9 KB
Content
image-20220615091045-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 KB
Content
image-20220615091045-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -196.0 KB
Content
image-20220615091045-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -371.1 KB
Content
image-20220615091045-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -206.3 KB
Content
image-20220615091045-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -115.0 KB
Content
image-20220615091929-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -37.7 KB
Content
image-20220615092010-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -37.3 KB
Content
image-20220615092044-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -63.5 KB
Content
image-20220615092327-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -66.3 KB
Content
image-20220615095102-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -179.0 KB
Content
image-20220615100930-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -10.5 KB
Content