Changes for page LMDS200 -- LoRaWAN Microwave Radar Distance Sensor User Manual

Last modified by Xiaoling on 2025/04/27 16:45

From version < 150.8 >

edited by Xiaoling
on 2022/06/11 08:37

To version < 120.2 >

edited by Xiaoling
on 2022/06/10 15:44

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 28 removed)

Details

Page properties

Content

@@ -3,7 +3,6 @@
  **Contents:**
--{{toc/}}
@@ -11,7 +11,6 @@
--
  = 1.  Introduction =
  == 1.1  What is LoRaWAN Distance Detection Sensor ==
@@ -35,7 +35,7 @@
  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.
--(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors.
++(% style="color:#4472c4" %) ***** (%%)Actually lifetime depends on network coverage and uplink interval and other factors
  )))
  )))
@@ -47,53 +47,41 @@
  == 1.2  Features ==
  * LoRaWAN 1.0.3 Class A
--* Ultra low power consumption
--* Distance Detection by Ultrasonic technology
--* Flat object range 280mm - 7500mm
--* Accuracy: ±(1cm+S*0.3%) (S: Distance)
--* Cable Length : 25cm
++* Ultra-low power consumption
++* Laser technology for distance detection
++* Operating Range - 0.1m~~12m①
++* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
++* Monitor Battery Level
  * Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
  * AT Commands to change parameters
  * Uplink on periodically
  * Downlink to change configure
--* IP66 Waterproof Enclosure
--* 4000mAh or 8500mAh Battery for long term use
++* 8500mAh Battery for long term use
++== 1.3  Probe Specification ==
++* Storage temperature ：-20℃~~75℃
++* Operating temperature - -20℃~~60℃
++* Operating Range - 0.1m~~12m①
++* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
++* Distance resolution - 5mm
++* Ambient light immunity - 70klux
++* Enclosure rating - IP65
++* Light source - LED
++* Central wavelength - 850nm
++* FOV - 3.6°
++* Material of enclosure - ABS+PC
++* Wire length - 25cm
++== 1.4  Probe Dimension ==
--== 1.3  Specification ==
--=== 1.3.1  Rated environmental conditions ===
++[[image:1654827224480-952.png]]
--[[image:image-20220610154839-1.png]]
--**Remarks: (1)  a. When the ambient temperature is 0-39 ℃, the maximum humidity is 90% (non-condensing);**
--
--**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)**
--
--
--
--=== 1.3.2  Effective measurement range Reference beam pattern ===
--
--**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
--
--
--
--[[image:1654852253176-749.png]]
--
--
--**(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.**
--
--
--[[image:1654852175653-550.png]](% style="display:none" %) ** **
--
--
--
  == 1.5  Applications ==
  * Horizontal distance measurement
--* Liquid level measurement
  * Parking management system
  * Object proximity and presence detection
  * Intelligent trash can management system
@@ -100,29 +100,26 @@
  * Robot obstacle avoidance
  * Automatic control
  * Sewer
--* Bottom water level monitoring
  == 1.6  Pin mapping and power on ==
--[[image:1654847583902-256.png]]
++[[image:1654827332142-133.png]]
++= 2.  Configure LLDS12 to connect to LoRaWAN network =
--= 2.  Configure LDDS75 to connect to LoRaWAN network =
--
  == 2.1  How it works ==
  (((
--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
++The LLDS12 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LLDS12. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
  )))
  (((
--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.
++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="H6.A0UseATCommand"]]to set the keys in the LLDS12.
  )))
--
  == 2.2  Quick guide to connect to LoRaWAN server (OTAA) ==
  (((
@@ -130,7 +130,7 @@
  )))
  (((
--[[image:1654848616367-242.png]]
++[[image:1654827857527-556.png]]
  )))
  (((
@@ -138,57 +138,57 @@
  )))
  (((
--(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
++(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
  )))
  (((
--Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
++Each LSPH01 is shipped with a sticker with the default device EUI as below:
  )))
  [[image:image-20220607170145-1.jpeg]]
--For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
--Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
++You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
--**Add APP EUI in the application**
--[[image:image-20220610161353-4.png]]
++**Register the device**
--[[image:image-20220610161353-5.png]]
--[[image:image-20220610161353-6.png]]
++[[image:1654592600093-601.png]]
--[[image:image-20220610161353-7.png]]
++**Add APP EUI and DEV EUI**
--You can also choose to create the device manually.
++[[image:1654592619856-881.png]]
--                                          [[image:image-20220610161538-8.png]]
++**Add APP EUI in the application**
--**Add APP KEY and DEV EUI**
++[[image:1654592632656-512.png]]
--[[image:image-20220610161538-9.png]]
++**Add APP KEY**
--(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
++[[image:1654592653453-934.png]]
++(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
++
++
  Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
--[[image:image-20220610161724-10.png]]
++[[image:image-20220607170442-2.png]]
  (((
--(% 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.
++(% 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.
  )))
--[[image:1654849068701-275.png]]
++[[image:1654833501679-968.png]]
@@ -195,10 +195,11 @@
  == 2.3  Uplink Payload ==
  (((
--LDDS75 will uplink payload via LoRaWAN with below payload format:
++LLDS12 will uplink payload via LoRaWAN with below payload format:
++)))
--Uplink payload includes in total 4 bytes.
--Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
++(((
++Uplink payload includes in total 11 bytes.
  )))
  (((
@@ -208,23 +208,23 @@
  (% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
  |=(% style="width: 62.5px;" %)(((
  **Size (bytes)**
--)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
--|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
--[[Distance>>||anchor="H2.3.3A0Distance"]]
++)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
++|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
++[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
++)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
++[[Interrupt  flag>>||anchor="H2.3.5A0InterruptPin"]]
++)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
++[[Message Type>>||anchor="H2.3.7A0MessageType"]]
++)))
--(unit: mm)
--)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
--[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
--)))|[[Sensor Flag>>path:#Sensor_Flag]]
++[[image:1654833689380-972.png]]
--[[image:1654850511545-399.png]]
--
  === 2.3.1  Battery Info ===
--Check the battery voltage for LDDS75.
++Check the battery voltage for LLDS12.
  Ex1: 0x0B45 = 2885mV
@@ -232,66 +232,103 @@
--=== 2.3.2  Distance ===
++=== 2.3.2  DS18B20 Temperature sensor ===
--Get the distance. Flat object range 280mm - 7500mm.
++This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
--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.**
++**Example**:
--* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
--* 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.
++If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
--=== 2.3.3  Interrupt Pin ===
++If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
--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.
--**Example:**
--0x00: Normal uplink packet.
++=== 2.3.3  Distance ===
--0x01: Interrupt Uplink Packet.
++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.
++**Example**:
--=== 2.3.4  DS18B20 Temperature sensor ===
++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.
--This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
++
++=== 2.3.4  Distance signal strength ===
++
++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.
++
++
  **Example**:
--If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
++If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
--If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
++Customers can judge whether they need to adjust the environment based on the signal strength.
--(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
++=== 2.3.5  Interrupt Pin ===
--=== 2.3.5  Sensor Flag ===
++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.
--0x01: Detect Ultrasonic Sensor
++Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
--0x00: No Ultrasonic Sensor
++**Example:**
++0x00: Normal uplink packet.
++0x01: Interrupt Uplink Packet.
--=== 2.3.6  Decode payload in The Things Network ===
++
++=== 2.3.6  LiDAR temp ===
++
++Characterize the internal temperature value of the sensor.
++
++**Example: **
++If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
++If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
++
++
++
++=== 2.3.7  Message Type ===
++
++(((
++For a normal uplink payload, the message type is always 0x01.
++)))
++
++(((
++Valid Message Type:
++)))
++
++
++(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
++|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
++|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
++|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
++
++=== 2.3.8  Decode payload in The Things Network ===
++
  While using TTN network, you can add the payload format to decode the payload.
--[[image:1654850829385-439.png]]
++[[image:1654592762713-715.png]]
--The payload decoder function for TTN V3 is here:
++(((
++The payload decoder function for TTN is here:
++)))
--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/]]
++(((
++LLDS12 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Decoder/]]
++)))
  == 2.4  Uplink Interval ==
--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"]]
++The LLDS12 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"]]
@@ -322,25 +322,47 @@
  (% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
--(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
++(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
--[[image:1654851029373-510.png]]
++[[image:1654832691989-514.png]]
--After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
++[[image:1654592833877-762.png]]
--[[image:image-20220610165129-11.png||height="595" width="1088"]]
++[[image:1654832740634-933.png]]
--== 2.6  Frequency Plans ==
  (((
--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.
++(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
  )))
++(((
++
++)))
++[[image:1654833065139-942.png]]
++
++
++[[image:1654833092678-390.png]]
++
++
++
++After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
++
++[[image:1654833163048-332.png]]
++
++
++
++== 2.6  Frequency Plans ==
++
++(((
++The LLDS12 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.
++)))
++
++
  === 2.6.1  EU863-870 (EU868) ===
  (((
@@ -404,51 +404,20 @@
  === 2.6.2  US902-928(US915) ===
  (((
--Used in USA, Canada and South America. Default use CHE=2
++Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
++)))
--(% style="color:blue" %)**Uplink:**
++(((
++To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
++)))
--903.9 - SF7BW125 to SF10BW125
--
--904.1 - SF7BW125 to SF10BW125
--
--904.3 - SF7BW125 to SF10BW125
--
--904.5 - SF7BW125 to SF10BW125
--
--904.7 - SF7BW125 to SF10BW125
--
--904.9 - SF7BW125 to SF10BW125
--
--905.1 - SF7BW125 to SF10BW125
--
--905.3 - SF7BW125 to SF10BW125
--
--
--(% style="color:blue" %)**Downlink:**
--
--923.3 - SF7BW500 to SF12BW500
--
--923.9 - SF7BW500 to SF12BW500
--
--924.5 - SF7BW500 to SF12BW500
--
--925.1 - SF7BW500 to SF12BW500
--
--925.7 - SF7BW500 to SF12BW500
--
--926.3 - SF7BW500 to SF12BW500
--
--926.9 - SF7BW500 to SF12BW500
--
--927.5 - SF7BW500 to SF12BW500
--
--923.3 - SF12BW500(RX2 downlink only)
--
--
--
++(((
++After Join success, the end node will switch to the correct sub band by:
  )))
++* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
++* 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)
++
  === 2.6.3  CN470-510 (CN470) ===
  (((
@@ -537,54 +537,28 @@
++
  === 2.6.4  AU915-928(AU915) ===
  (((
--Default use CHE=2
++Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
++)))
--(% style="color:blue" %)**Uplink:**
++(((
++To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
++)))
--916.8 - SF7BW125 to SF12BW125
--
--917.0 - SF7BW125 to SF12BW125
--
--917.2 - SF7BW125 to SF12BW125
--
--917.4 - SF7BW125 to SF12BW125
--
--917.6 - SF7BW125 to SF12BW125
--
--917.8 - SF7BW125 to SF12BW125
--
--918.0 - SF7BW125 to SF12BW125
--
--918.2 - SF7BW125 to SF12BW125
--
--
--(% style="color:blue" %)**Downlink:**
--
--923.3 - SF7BW500 to SF12BW500
--
--923.9 - SF7BW500 to SF12BW500
--
--924.5 - SF7BW500 to SF12BW500
--
--925.1 - SF7BW500 to SF12BW500
--
--925.7 - SF7BW500 to SF12BW500
--
--926.3 - SF7BW500 to SF12BW500
--
--926.9 - SF7BW500 to SF12BW500
--
--927.5 - SF7BW500 to SF12BW500
--
--923.3 - SF12BW500(RX2 downlink only)
--
--
++(((
  )))
++(((
++After Join success, the end node will switch to the correct sub band by:
++)))
++
++* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
++* 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)
++
  === 2.6.5  AS920-923 & AS923-925 (AS923) ===
  (((
@@ -693,6 +693,7 @@
++
  === 2.6.6  KR920-923 (KR920) ===
  (((
@@ -765,6 +765,7 @@
++
  === 2.6.7  IN865-867 (IN865) ===
  (((
@@ -801,20 +801,18 @@
++
  == 2.7  LED Indicator ==
--The LDDS75 has an internal LED which is to show the status of different state.
++The LLDS12 has an internal LED which is to show the status of different state.
--
--* Blink once when device power on.
--* The device detects the sensor and flashes 5 times.
--* Solid ON for 5 seconds once device successful Join the network.
++* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
  * Blink once when device transmit a packet.
  == 2.8  Firmware Change Log ==
--**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
++**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LLDS12/Firmware/]]
  **Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
@@ -821,58 +821,71 @@
--== 2.9  Mechanical ==
++= 3.  LiDAR ToF Measurement =
++== 3.1  Principle of Distance Measurement ==
--[[image:image-20220610172003-1.png]]
++The LiDAR probe is based on TOF, namely, Time of Flight principle. To be specific, the product emits modulation wave of near infrared ray on a periodic basis, which will be reflected after contacting object. The product obtains the time of flight by measuring round-trip phase difference and then calculates relative range between the product and the detection object, as shown below.
--[[image:image-20220610172003-2.png]]
++[[image:1654831757579-263.png]]
--== 2.10  Battery Analysis ==
--=== 2.10.1  Battery Type ===
++== 3.2  Distance Measurement Characteristics ==
--The LDDS75 battery is a combination of a 4000mAh or 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
++With optimization of light path and algorithm, The LiDAR probe has minimized influence from external environment on distance measurement performance. Despite that, the range of distance measurement may still be affected by the environment illumination intensity and the reflectivity of detection object. As shown in below:
++[[image:1654831774373-275.png]]
--The battery related documents as below:
--* (((
--[[ Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
++(((
++(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
  )))
--* (((
--[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
++
++(((
++(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
  )))
--* (((
--[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
++
++(((
++(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
  )))
-- [[image:image-20220610172400-3.png]]
++(((
++Vertical Coordinates: Represents the radius of light spot for The LiDAR probe at the different distances. The diameter of light spot depends on the FOV of The LiDAR probe (the term of FOV generally refers to the smaller value between the receiving angle and the transmitting angle), which is calculated as follows:
++)))
--=== 2.10.2  Replace the battery ===
++[[image:1654831797521-720.png]]
--(((
--You can change the battery in the LDDS75.The type of battery is not limited as long as the output is between 3v to 3.6v.  On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
--)))
  (((
--
++In the formula above, d is the diameter of light spot; D is detecting range; β is the value of the receiving angle of The LiDAR probe, 3.6°. Correspondence between the diameter of light spot and detecting range is given in Table below.
  )))
++[[image:1654831810009-716.png]]
++
++
  (((
--The default battery pack of LDDS75 includes a ER18505 plus super capacitor. If user can’t find this pack locally, they can find ER18505 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
++If the light spot reaches two objects with different distances, as shown in Figure 3, the output distance value will be a value between the actual distance values of the two objects. For a high accuracy requirement in practice, the above situation should be noticed to avoid the measurement error.
  )))
--= 3.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
++== 3.3  Notice of usage: ==
++Possible invalid /wrong reading for LiDAR ToF tech:
++
++* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
++* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
++* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
++* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
++
++= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
++
  (((
  (((
--Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
++Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
  )))
  )))
@@ -893,7 +893,7 @@
  )))
  (((
--There are two kinds of commands to configure LDDS75, they are:
++There are two kinds of commands to configure LLDS12, they are:
  )))
  )))
@@ -934,150 +934,352 @@
  * (((
  (((
--(% style="color:#4f81bd" %)** Commands special design for LDDS75**
++(% style="color:#4f81bd" %)** Commands special design for LLDS12**
  )))
  )))
  (((
  (((
--These commands only valid for LDDS75, as below:
++These commands only valid for LLDS12, as below:
  )))
  )))
--== 3.1  Access AT Commands ==
++== 4.1  Set Transmit Interval Time ==
--LDDS75 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LDDS75 for using AT command, as below.
++Feature: Change LoRaWAN End Node Transmit Interval.
--[[image:image-20220610172924-4.png||height="483" width="988"]]
++(% style="color:#037691" %)**AT Command: AT+TDC**
++[[image:image-20220607171554-8.png]]
--Or if you have below board, use below connection:
++(((
++(% style="color:#037691" %)**Downlink Command: 0x01**
++)))
--[[image:image-20220610172924-5.png]]
++(((
++Format: Command Code (0x01) followed by 3 bytes time value.
++)))
++(((
++If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
++)))
--In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LDDS75. LDDS75 will output system info once power on as below:
++* (((
++Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
++)))
++* (((
++Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
++)))
++== 4.2  Set Interrupt Mode ==
-- [[image:image-20220610172924-6.png||height="601" width="860"]]
++Feature, Set Interrupt mode for GPIO_EXIT.
++(% style="color:#037691" %)**AT Command: AT+INTMOD**
++[[image:image-20220610105806-2.png]]
--== 3.2  Set Transmit Interval Time ==
--Feature: Change LoRaWAN End Node Transmit Interval.
++(((
++(% style="color:#037691" %)**Downlink Command: 0x06**
++)))
--(% style="color:#037691" %)**AT Command: AT+TDC**
++(((
++Format: Command Code (0x06) followed by 3 bytes.
++)))
--[[image:image-20220610173409-7.png]]
++(((
++This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
++)))
++* (((
++Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
++)))
++* (((
++Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
++)))
++== 4.3  Get Firmware Version Info ==
++
++Feature: use downlink to get firmware version.
++
++(% style="color:#037691" %)**Downlink Command: 0x26**
++
++[[image:image-20220607171917-10.png]]
++
++* Reply to the confirmation package: 26 01
++* Reply to non-confirmed packet: 26 00
++
++Device will send an uplink after got this downlink command. With below payload:
++
++Configures info payload:
++
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
++|=(((
++**Size(bytes)**
++)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
++|**Value**|Software Type|(((
++Frequency
++
++Band
++)))|Sub-band|(((
++Firmware
++
++Version
++)))|Sensor Type|Reserve|(((
++[[Message Type>>||anchor="H2.3.7A0MessageType"]]
++Always 0x02
++)))
++
++**Software Type**: Always 0x03 for LLDS12
++
++
++**Frequency Band**:
++
++*0x01: EU868
++
++*0x02: US915
++
++*0x03: IN865
++
++*0x04: AU915
++
++*0x05: KZ865
++
++*0x06: RU864
++
++*0x07: AS923
++
++*0x08: AS923-1
++
++*0x09: AS923-2
++
++*0xa0: AS923-3
++
++
++**Sub-Band**: value 0x00 ~~ 0x08
++
++
++**Firmware Version**: 0x0100, Means: v1.0.0 version
++
++
++**Sensor Type**:
++
++0x01: LSE01
++
++0x02: LDDS75
++
++0x03: LDDS20
++
++0x04: LLMS01
++
++0x05: LSPH01
++
++0x06: LSNPK01
++
++0x07: LLDS12
++
++
++
++= 5.  Battery & How to replace =
++
++== 5.1  Battery Type ==
++
  (((
--(% style="color:#037691" %)**Downlink Command: 0x01**
++LLDS12 is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.
  )))
  (((
++The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
++)))
++
++[[image:1654593587246-335.png]]
++
++
++Minimum Working Voltage for the LLDS12:
++
++LLDS12:  2.45v ~~ 3.6v
++
++
++
++== 5.2  Replace Battery ==
++
  (((
--Format: Command Code (0x01) followed by 3 bytes time value.
++Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
++)))
--If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
++(((
++And make sure the positive and negative pins match.
++)))
--* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
--* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
++
++
++== 5.3  Power Consumption Analyze ==
++
++(((
++Dragino Battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
  )))
++(((
++Instruction to use as below:
++)))
--
++
++**Step 1**: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
++
++[[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
++
++
++**Step 2**: Open it and choose
++
++* Product Model
++* Uplink Interval
++* Working Mode
++
++And the Life expectation in difference case will be shown on the right.
++
++[[image:1654593605679-189.png]]
++
++
++The battery related documents as below:
++
++* (((
++[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
  )))
++* (((
++[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
++)))
++* (((
++[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
++)))
--== 3.3  Set Interrupt Mode ==
++[[image:image-20220607172042-11.png]]
--Feature, Set Interrupt mode for GPIO_EXIT.
--(% style="color:#037691" %)**Downlink Command: AT+INTMOD**
--[[image:image-20220610174917-9.png]]
++=== 5.3.1  Battery Note ===
++(((
++The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
++)))
--(% style="color:#037691" %)**Downlink Command: 0x06**
--Format: Command Code (0x06) followed by 3 bytes.
--This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
++=== 5.3.2  Replace the battery ===
--* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
--* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
++(((
++You can change the battery in the LLDS12.The type of battery is not limited as long as the output is between 3v to 3.6v.  On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
++)))
++(((
++The default battery pack of LLDS12 includes a ER26500 plus super capacitor. If user can’t find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
++)))
--= 4.  FAQ =
--== 4.1  What is the frequency plan for LDDS75? ==
--LDDS75 use the same frequency as other Dragino products. User can see the detail from this link:  [[Introduction>>doc:Main.End Device Frequency Band.WebHome||anchor="H1.Introduction"]]
++= 6.  Use AT Command =
++== 6.1  Access AT Commands ==
++LLDS12 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LLDS12 for using AT command, as below.
--== 4.2  How to change the LoRa Frequency Bands/Region ==
++[[image:1654593668970-604.png]]
--You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
--When downloading the images, choose the required image file for download.
++**Connection:**
++(% style="background-color:yellow" %)** USB TTL GND <~-~-~-~-> GND**
++(% style="background-color:yellow" %)** USB TTL TXD  <~-~-~-~-> UART_RXD**
--== 4.3  Can I use LDDS75 in condensation environment? ==
++(% style="background-color:yellow" %)** USB TTL RXD  <~-~-~-~-> UART_TXD**
--LDDS75 is not suitable to be used in condensation environment. Condensation on the LDDS75 probe will affect the reading and always got 0.
++(((
++(((
++In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LLDS12.
++)))
++(((
++LLDS12 will output system info once power on as below:
++)))
++)))
--= 5.  Trouble Shooting =
--== 5.1  Why I can’t join TTN V3 in US915 / AU915 bands? ==
++ [[image:1654593712276-618.png]]
--It is due to channel mapping. Please see below link:  [[Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
++Valid AT Command please check [[Configure Device>>||anchor="H4.A0ConfigureLLDS12viaATCommandorLoRaWANDownlink"]].
--== 5.2  AT Command input doesn't work ==
++= 7.  FAQ =
++== 7.1  How to change the LoRa Frequency Bands/Region ==
++
++You can follow the instructions for [[how to upgrade image>>||anchor="H2.8A0200BFirmwareChangeLog"]].
++When downloading the images, choose the required image file for download.
++
++
++= 8.  Trouble Shooting =
++
++== 8.1  AT Commands input doesn’t work ==
++
++
++(((
  In the case if user can see the console output but can’t type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn’t send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
++)))
++
++== 8.2  Significant error between the output distant value of LiDAR and actual distance ==
++
++
  (((
++(% style="color:blue" %)**Cause ①**(%%)**：**Due to the physical principles of The LiDAR probe, the above phenomenon is likely to occur if the detection object is the material with high reflectivity (such as mirror, smooth floor tile, etc.) or transparent substance (such as glass and water, etc.)
++)))
++
++(((
++Troubleshooting: Please avoid use of this product under such circumstance in practice.
++)))
++
++(((
  )))
++(((
++(% style="color:blue" %)**Cause ②**(%%)**: **The IR-pass filters are blocked.
++)))
--= 6.  Order Info =
++(((
++Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
++)))
--Part Number **:** (% style="color:blue" %)**LDDS75-XX-YY**
++= 9.  Order Info =
--(% style="color:blue" %)**XX**(%%)**: **The default frequency band
--* (% style="color:red" %)**AS923 **(%%)**:** LoRaWAN AS923 band
--* (% style="color:red" %)**AU915 **(%%)**:** LoRaWAN AU915 band
--* (% style="color:red" %)**EU433 **(%%)**:** LoRaWAN EU433 band
--* (% style="color:red" %)**EU868 **(%%)**:** LoRaWAN EU868 band
--* (% style="color:red" %)**KR920 **(%%)**:** LoRaWAN KR920 band
--* (% style="color:red" %)**US915 **(%%)**:** LoRaWAN US915 band
--* (% style="color:red" %)**IN865 **(%%)**:**  LoRaWAN IN865 band
--* (% style="color:red" %)**CN470 **(%%)**:** LoRaWAN CN470 band
++Part Number: (% style="color:blue" %)**LLDS12-XX**
--(% style="color:blue" %)**YY**(%%): Battery Option
--* (% style="color:red" %)**4 **(%%)**: **4000mAh battery
--* (% style="color:red" %)**8 **(%%)**:** 8500mAh battery
++(% style="color:blue" %)**XX**(%%): The default frequency band
++* (% style="color:red" %)**AS923**(%%):  LoRaWAN AS923 band
++* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
++* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
++* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
++* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
++* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
++* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
++* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
--= 7.  Packing Info =
++= 10.  Packing Info =
++
  **Package Includes**:
--* LDDS75 LoRaWAN Distance Detection Sensor x 1
++* LLDS12 LoRaWAN LiDAR Distance Sensor x 1
  **Dimension and weight**:
@@ -1087,7 +1087,7 @@
  * Weight / pcs : g
--= 8.  Support =
++= 11.  Support =
  * 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.
  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]].

1654847583902-256.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-492.6 KB

Content

1654848616367-242.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-76.8 KB

Content

1654849068701-275.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-88.3 KB

Content

1654850511545-399.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-88.3 KB

Content

1654850829385-439.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-59.2 KB

Content

1654851029373-510.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-92.0 KB

Content

1654852175653-550.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-106.2 KB

Content

1654852253176-749.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-106.6 KB

Content

image-20220610154839-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-11.3 KB

Content

image-20220610155021-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-164.8 KB

Content

image-20220610155021-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-181.8 KB

Content

image-20220610161353-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-32.2 KB

Content

image-20220610161353-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-42.7 KB

Content

image-20220610161353-6.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-36.3 KB

Content

image-20220610161353-7.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-19.1 KB

Content

image-20220610161538-8.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-27.2 KB

Content

image-20220610161538-9.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-28.7 KB

Content

image-20220610161724-10.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-180.0 KB

Content

image-20220610165129-11.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-50.5 KB

Content

image-20220610172003-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-5.9 KB

Content

image-20220610172003-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-18.6 KB

Content

image-20220610172400-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-370.3 KB

Content

image-20220610172924-4.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-1.5 MB

Content

image-20220610172924-5.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-901.4 KB

Content

image-20220610172924-6.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-68.6 KB

Content

image-20220610173409-7.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-11.8 KB

Content

image-20220610174836-8.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-34.3 KB

Content

image-20220610174917-9.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-34.3 KB

Content

Changes for page LMDS200 -- LoRaWAN Microwave Radar Distance Sensor User Manual

Summary

Details

Applications

Navigation