Wiki source code of LLDS12-LoRaWAN LiDAR ToF Distance Sensor User Manual

Version 113.12 by Xiaoling on 2022/06/10 15:08

version	line-number	content
2.2	1	(% style="text-align:center" %)
87.2	2	[[image:image-20220610095606-1.png]]
1.1	3
	4
14.8	5	Contents:
1.1	6
109.9	7	{{toc/}}
1.1	8
85.30	9
	10
	11
	12
87.3	13
109.9	14
91.2	15	= 1. Introduction =
2.2	16
91.2	17	== 1.1 What is LoRaWAN LiDAR ToF Distance Sensor ==
2.2	18
73.13	19	(((
88.2	20
2.2	21
109.10	22	(((
88.2	23	The Dragino LLDS12 is a (% style="color:blue" %)LoRaWAN LiDAR ToF (Time of Flight) Distance Sensor(%%) for Internet of Things solution. It is capable to measure the distance to an object as close as 10 centimeters (+/- 5cm up to 6m) and as far as 12 meters (+/-1% starting at 6m)!. The LiDAR probe uses laser induction technology for distance measurement.
109.10	24	)))
2.2	25
109.10	26	(((
88.2	27	The LLDS12 can be applied to scenarios such as horizontal distance measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, etc.
109.10	28	)))
2.2	29
109.10	30	(((
88.2	31	It detects the distance between the measured object and the sensor, and uploads the value via wireless to LoRaWAN IoT Server.
109.10	32	)))
2.2	33
109.10	34	(((
88.2	35	The LoRa wireless technology used in LLDS12 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
109.10	36	)))
88.2	37
109.10	38	(((
88.2	39	LLDS12 is powered by (% style="color:blue" %)8500mAh Li-SOCI2 battery(%%), it is designed for long term use up to 5 years.
109.10	40	)))
88.2	41
109.10	42	(((
88.2	43	Each LLDS12 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
73.13	44	)))
109.10	45	)))
2.2	46
	47
88.2	48	[[image:1654826306458-414.png]]
2.2	49
	50
	51
91.2	52	== 1.2 Features ==
3.2	53
2.2	54	* LoRaWAN 1.0.3 Class A
	55	* Ultra-low power consumption
88.3	56	* Laser technology for distance detection
	57	* Operating Range - 0.1m~~12m①
	58	* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
2.2	59	* Monitor Battery Level
	60	* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
	61	* AT Commands to change parameters
	62	* Uplink on periodically
	63	* Downlink to change configure
	64	* 8500mAh Battery for long term use
	65
113.2	66
	67
	68
91.2	69	== 1.3 Probe Specification ==
2.2	70
88.5	71	* Storage temperature ：-20℃~~75℃
	72	* Operating temperature - -20℃~~60℃
	73	* Operating Range - 0.1m~~12m①
	74	* Accuracy - ±5cm@(0.1-6m), ±1%@(6m-12m)
	75	* Distance resolution - 5mm
	76	* Ambient light immunity - 70klux
	77	* Enclosure rating - IP65
	78	* Light source - LED
	79	* Central wavelength - 850nm
	80	* FOV - 3.6°
	81	* Material of enclosure - ABS+PC
	82	* Wire length - 25cm
3.3	83
113.3	84
	85
	86
91.2	87	== 1.4 Probe Dimension ==
89.3	88
90.2	89
	90	[[image:1654827224480-952.png]]
	91
	92
91.2	93	== 1.5 Applications ==
90.2	94
91.2	95	* Horizontal distance measurement
	96	* Parking management system
	97	* Object proximity and presence detection
	98	* Intelligent trash can management system
	99	* Robot obstacle avoidance
	100	* Automatic control
	101	* Sewer
2.2	102
113.4	103
	104
	105
108.3	106	== 1.6 Pin mapping and power on ==
	107
	108
91.2	109	[[image:1654827332142-133.png]]
	110
	111
108.3	112	= 2. Configure LLDS12 to connect to LoRaWAN network =
2.2	113
108.3	114	== 2.1 How it works ==
	115
5.3	116	(((
93.2	117	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.
5.3	118	)))
2.2	119
5.3	120	(((
111.4	121	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.
5.3	122	)))
2.2	123
	124
108.3	125	== 2.2 Quick guide to connect to LoRaWAN server (OTAA) ==
2.2	126
6.3	127	(((
2.2	128	Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.
6.3	129	)))
2.2	130
6.3	131	(((
93.2	132	[[image:1654827857527-556.png]]
6.3	133	)))
2.2	134
6.3	135	(((
2.2	136	The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
6.3	137	)))
2.2	138
6.3	139	(((
23.5	140	(% style="color:blue" %)Step 1(%%): Create a device in TTN with the OTAA keys from LSPH01.
6.3	141	)))
2.2	142
6.3	143	(((
2.2	144	Each LSPH01 is shipped with a sticker with the default device EUI as below:
6.3	145	)))
2.2	146
41.3	147	[[image:image-20220607170145-1.jpeg]]
2.2	148
	149
	150
	151	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
	152
	153
	154	Register the device
	155
	156
43.2	157	[[image:1654592600093-601.png]]
2.2	158
9.2	159
108.2	160
2.2	161	Add APP EUI and DEV EUI
	162
43.2	163	[[image:1654592619856-881.png]]
2.2	164
	165
108.2	166
2.2	167	Add APP EUI in the application
	168
44.2	169	[[image:1654592632656-512.png]]
2.2	170
	171
10.2	172
2.2	173	Add APP KEY
	174
45.2	175	[[image:1654592653453-934.png]]
2.2	176
	177
108.2	178	(% style="color:blue" %)Step 2(%%): Power on LLDS12
2.2	179
	180
	181	Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
	182
46.2	183	[[image:image-20220607170442-2.png]]
2.2	184
	185
73.14	186	(((
108.2	187	(% 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.
73.14	188	)))
2.2	189
108.2	190	[[image:1654833501679-968.png]]
2.2	191
	192
	193
108.4	194	== 2.3 Uplink Payload ==
2.2	195
73.14	196	(((
109.2	197	LLDS12 will uplink payload via LoRaWAN with below payload format:
73.14	198	)))
2.2	199
73.14	200	(((
2.2	201	Uplink payload includes in total 11 bytes.
73.14	202	)))
2.2	203
73.14	204	(((
109.2	205
73.14	206	)))
2.2	207
13.2	208	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
85.8	209	\|=(% style="width: 62.5px;" %)(((
	210	Size (bytes)
	211	)))\|=(% style="width: 62.5px;" %)2\|=(% style="width: 62.5px;" %)2\|=2\|=2\|=1\|=1\|=1
111.5	212	\|(% style="width:62.5px" %)Value\|(% style="width:62.5px" %)[[BAT>>\|\|anchor="H2.3.1A0BatteryInfo"]]\|(% style="width:62.5px" %)(((
111.6	213	[[Temperature DS18B20>>\|\|anchor="H2.3.2A0DS18B20Temperaturesensor"]]
	214	)))\|[[Distance>>\|\|anchor="H2.3.3A0Distance"]]\|[[Distance signal strength>>\|\|anchor="H2.3.4A0Distancesignalstrength"]]\|(((
	215	[[Interrupt flag>>\|\|anchor="H2.3.5A0InterruptPin"]]
	216	)))\|[[LiDAR temp>>\|\|anchor="H2.3.6A0LiDARtemp"]]\|(((
	217	[[Message Type>>\|\|anchor="H2.3.7A0MessageType"]]
2.2	218	)))
	219
109.2	220	[[image:1654833689380-972.png]]
2.2	221
	222
	223
109.4	224	=== 2.3.1 Battery Info ===
2.2	225
13.2	226
109.4	227	Check the battery voltage for LLDS12.
2.2	228
	229	Ex1: 0x0B45 = 2885mV
	230
	231	Ex2: 0x0B49 = 2889mV
	232
	233
	234
109.5	235	=== 2.3.2 DS18B20 Temperature sensor ===
2.2	236
13.2	237	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.2	238
13.2	239
2.2	240	Example:
	241
	242	If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
	243
	244	If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
	245
	246
	247
109.5	248	=== 2.3.3 Distance ===
2.2	249
109.5	250	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.
2.2	251
	252
109.5	253	Example:
2.2	254
109.5	255	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.
2.2	256
	257
109.5	258
109.6	259	=== 2.3.4 Distance signal strength ===
13.3	260
109.6	261	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.
2.2	262
	263
	264	Example:
	265
109.6	266	If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
2.2	267
109.6	268	Customers can judge whether they need to adjust the environment based on the signal strength.
2.2	269
	270
	271
109.7	272	=== 2.3.5 Interrupt Pin ===
2.2	273
111.7	274	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.
2.2	275
111.7	276	Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>\|\|anchor="H1.6A0Pinmappingandpoweron"]].
2.2	277
13.3	278	Example:
2.2	279
	280	0x00: Normal uplink packet.
	281
	282	0x01: Interrupt Uplink Packet.
	283
	284
	285
109.7	286	=== 2.3.6 LiDAR temp ===
13.3	287
109.7	288	Characterize the internal temperature value of the sensor.
	289
	290	Example:
	291	If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
	292	If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
	293
	294
	295
	296	=== 2.3.7 Message Type ===
	297
73.15	298	(((
2.2	299	For a normal uplink payload, the message type is always 0x01.
73.15	300	)))
2.2	301
73.15	302	(((
2.2	303	Valid Message Type:
73.15	304	)))
2.2	305
	306
85.8	307	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
	308	\|=(% style="width: 160px;" %)Message Type Code\|=(% style="width: 163px;" %)Description\|=(% style="width: 173px;" %)Payload
111.9	309	\|(% style="width:160px" %)0x01\|(% style="width:163px" %)Normal Uplink\|(% style="width:173px" %)[[Normal Uplink Payload>>\|\|anchor="H2.3A0200BUplinkPayload"]]
111.8	310	\|(% style="width:160px" %)0x02\|(% style="width:163px" %)Reply configures info\|(% style="width:173px" %)[[Configure Info Payload>>\|\|anchor="H4.3A0GetFirmwareVersionInfo"]]
2.2	311
113.5	312
	313
	314
109.7	315	=== 2.3.8 Decode payload in The Things Network ===
13.6	316
2.2	317	While using TTN network, you can add the payload format to decode the payload.
	318
	319
49.2	320	[[image:1654592762713-715.png]]
2.2	321
14.2	322	(((
2.2	323	The payload decoder function for TTN is here:
14.2	324	)))
2.2	325
14.2	326	(((
111.11	327	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/]]
14.2	328	)))
2.2	329
	330
	331
107.4	332	== 2.4 Uplink Interval ==
14.3	333
107.4	334	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"]]
2.2	335
	336
	337
107.4	338	== 2.5 Show Data in DataCake IoT Server ==
2.2	339
74.2	340	(((
2.2	341	[[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:
74.2	342	)))
2.2	343
74.2	344	(((
	345
	346	)))
2.2	347
74.2	348	(((
23.5	349	(% style="color:blue" %)Step 1(%%): Be sure that your device is programmed and properly connected to the network at this time.
74.2	350	)))
2.2	351
74.2	352	(((
23.5	353	(% 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:
74.2	354	)))
2.2	355
	356
50.2	357	[[image:1654592790040-760.png]]
2.2	358
	359
51.3	360	[[image:1654592800389-571.png]]
2.2	361
	362
23.5	363	(% style="color:blue" %)Step 3(%%): Create an account or log in Datacake.
2.2	364
107.2	365	(% style="color:blue" %)Step 4(%%): Create LLDS12 product.
2.2	366
107.2	367	[[image:1654832691989-514.png]]
2.2	368
	369
53.2	370	[[image:1654592833877-762.png]]
2.2	371
	372
107.2	373	[[image:1654832740634-933.png]]
2.2	374
	375
107.2	376
74.3	377	(((
23.5	378	(% style="color:blue" %)Step 5(%%): add payload decode
74.3	379	)))
2.2	380
74.3	381	(((
107.2	382
74.3	383	)))
2.2	384
107.2	385	[[image:1654833065139-942.png]]
2.2	386
	387
	388
107.2	389	[[image:1654833092678-390.png]]
2.2	390
	391
	392
107.2	393	After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
2.2	394
107.2	395	[[image:1654833163048-332.png]]
2.2	396
	397
	398
100.7	399	== 2.6 Frequency Plans ==
	400
26.6	401	(((
100.7	402	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.
26.6	403	)))
2.2	404
	405
100.7	406	=== 2.6.1 EU863-870 (EU868) ===
2.2	407
74.10	408	(((
26.5	409	(% style="color:blue" %)Uplink:
74.10	410	)))
26.5	411
74.10	412	(((
2.2	413	868.1 - SF7BW125 to SF12BW125
74.10	414	)))
2.2	415
74.10	416	(((
2.2	417	868.3 - SF7BW125 to SF12BW125 and SF7BW250
74.10	418	)))
2.2	419
74.10	420	(((
2.2	421	868.5 - SF7BW125 to SF12BW125
74.10	422	)))
2.2	423
74.10	424	(((
2.2	425	867.1 - SF7BW125 to SF12BW125
74.10	426	)))
2.2	427
74.10	428	(((
2.2	429	867.3 - SF7BW125 to SF12BW125
74.10	430	)))
2.2	431
74.10	432	(((
2.2	433	867.5 - SF7BW125 to SF12BW125
74.10	434	)))
2.2	435
74.10	436	(((
2.2	437	867.7 - SF7BW125 to SF12BW125
74.10	438	)))
2.2	439
74.10	440	(((
2.2	441	867.9 - SF7BW125 to SF12BW125
74.10	442	)))
2.2	443
74.10	444	(((
2.2	445	868.8 - FSK
74.10	446	)))
2.2	447
74.10	448	(((
	449
	450	)))
2.2	451
74.10	452	(((
26.5	453	(% style="color:blue" %)Downlink:
74.10	454	)))
2.2	455
74.10	456	(((
2.2	457	Uplink channels 1-9 (RX1)
74.10	458	)))
2.2	459
74.10	460	(((
2.2	461	869.525 - SF9BW125 (RX2 downlink only)
74.10	462	)))
2.2	463
	464
	465
100.9	466	=== 2.6.2 US902-928(US915) ===
26.5	467
	468	(((
2.2	469	Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
26.5	470	)))
2.2	471
26.5	472	(((
2.2	473	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.
26.5	474	)))
2.2	475
26.5	476	(((
2.2	477	After Join success, the end node will switch to the correct sub band by:
26.5	478	)))
2.2	479
	480	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	481	* 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)
	482
113.6	483
	484
	485
109.9	486	=== 2.6.3 CN470-510 (CN470) ===
100.9	487
74.11	488	(((
2.2	489	Used in China, Default use CHE=1
74.11	490	)))
2.2	491
74.11	492	(((
26.5	493	(% style="color:blue" %)Uplink:
74.11	494	)))
2.2	495
74.11	496	(((
2.2	497	486.3 - SF7BW125 to SF12BW125
74.11	498	)))
2.2	499
74.11	500	(((
2.2	501	486.5 - SF7BW125 to SF12BW125
74.11	502	)))
2.2	503
74.11	504	(((
2.2	505	486.7 - SF7BW125 to SF12BW125
74.11	506	)))
2.2	507
74.11	508	(((
2.2	509	486.9 - SF7BW125 to SF12BW125
74.11	510	)))
2.2	511
74.11	512	(((
2.2	513	487.1 - SF7BW125 to SF12BW125
74.11	514	)))
2.2	515
74.11	516	(((
2.2	517	487.3 - SF7BW125 to SF12BW125
74.11	518	)))
2.2	519
74.11	520	(((
2.2	521	487.5 - SF7BW125 to SF12BW125
74.11	522	)))
2.2	523
74.11	524	(((
2.2	525	487.7 - SF7BW125 to SF12BW125
74.11	526	)))
2.2	527
74.11	528	(((
	529
	530	)))
2.2	531
74.11	532	(((
26.5	533	(% style="color:blue" %)Downlink:
74.11	534	)))
2.2	535
74.11	536	(((
2.2	537	506.7 - SF7BW125 to SF12BW125
74.11	538	)))
2.2	539
74.11	540	(((
2.2	541	506.9 - SF7BW125 to SF12BW125
74.11	542	)))
2.2	543
74.11	544	(((
2.2	545	507.1 - SF7BW125 to SF12BW125
74.11	546	)))
2.2	547
74.11	548	(((
2.2	549	507.3 - SF7BW125 to SF12BW125
74.11	550	)))
2.2	551
74.11	552	(((
2.2	553	507.5 - SF7BW125 to SF12BW125
74.11	554	)))
2.2	555
74.11	556	(((
2.2	557	507.7 - SF7BW125 to SF12BW125
74.11	558	)))
2.2	559
74.11	560	(((
2.2	561	507.9 - SF7BW125 to SF12BW125
74.11	562	)))
2.2	563
74.11	564	(((
2.2	565	508.1 - SF7BW125 to SF12BW125
74.11	566	)))
2.2	567
74.11	568	(((
2.2	569	505.3 - SF12BW125 (RX2 downlink only)
74.11	570	)))
2.2	571
	572
	573
26.5	574
109.9	575	=== 2.6.4 AU915-928(AU915) ===
100.9	576
26.5	577	(((
2.2	578	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
26.5	579	)))
2.2	580
26.5	581	(((
2.2	582	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.
26.5	583	)))
2.2	584
26.5	585	(((
	586
	587	)))
2.2	588
26.5	589	(((
2.2	590	After Join success, the end node will switch to the correct sub band by:
26.5	591	)))
2.2	592
	593	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	594	* 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)
	595
113.7	596
	597
	598
109.9	599	=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
100.9	600
74.9	601	(((
26.7	602	(% style="color:blue" %)Default Uplink channel:
74.9	603	)))
2.2	604
74.9	605	(((
2.2	606	923.2 - SF7BW125 to SF10BW125
74.9	607	)))
2.2	608
74.9	609	(((
2.2	610	923.4 - SF7BW125 to SF10BW125
74.9	611	)))
2.2	612
74.9	613	(((
	614
	615	)))
2.2	616
74.9	617	(((
26.7	618	(% style="color:blue" %)Additional Uplink Channel:
74.9	619	)))
2.2	620
74.9	621	(((
2.2	622	(OTAA mode, channel added by JoinAccept message)
74.9	623	)))
2.2	624
74.9	625	(((
	626
	627	)))
2.2	628
74.9	629	(((
26.7	630	(% style="color:blue" %)AS920~~AS923 for Japan, Malaysia, Singapore:
74.9	631	)))
26.7	632
74.9	633	(((
2.2	634	922.2 - SF7BW125 to SF10BW125
74.9	635	)))
2.2	636
74.9	637	(((
2.2	638	922.4 - SF7BW125 to SF10BW125
74.9	639	)))
2.2	640
74.9	641	(((
2.2	642	922.6 - SF7BW125 to SF10BW125
74.9	643	)))
2.2	644
74.9	645	(((
2.2	646	922.8 - SF7BW125 to SF10BW125
74.9	647	)))
2.2	648
74.9	649	(((
2.2	650	923.0 - SF7BW125 to SF10BW125
74.9	651	)))
2.2	652
74.9	653	(((
2.2	654	922.0 - SF7BW125 to SF10BW125
74.9	655	)))
2.2	656
74.9	657	(((
	658
	659	)))
2.2	660
74.9	661	(((
26.7	662	(% style="color:blue" %)AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam:
74.9	663	)))
2.2	664
74.9	665	(((
2.2	666	923.6 - SF7BW125 to SF10BW125
74.9	667	)))
2.2	668
74.9	669	(((
2.2	670	923.8 - SF7BW125 to SF10BW125
74.9	671	)))
2.2	672
74.9	673	(((
2.2	674	924.0 - SF7BW125 to SF10BW125
74.9	675	)))
2.2	676
74.9	677	(((
2.2	678	924.2 - SF7BW125 to SF10BW125
74.9	679	)))
2.2	680
74.9	681	(((
2.2	682	924.4 - SF7BW125 to SF10BW125
74.9	683	)))
2.2	684
74.9	685	(((
2.2	686	924.6 - SF7BW125 to SF10BW125
74.9	687	)))
2.2	688
74.9	689	(((
	690
	691	)))
2.2	692
74.9	693	(((
26.7	694	(% style="color:blue" %)Downlink:
74.9	695	)))
2.2	696
74.9	697	(((
2.2	698	Uplink channels 1-8 (RX1)
74.9	699	)))
2.2	700
74.9	701	(((
2.2	702	923.2 - SF10BW125 (RX2)
74.9	703	)))
2.2	704
	705
	706
	707
109.9	708	=== 2.6.6 KR920-923 (KR920) ===
100.9	709
74.12	710	(((
26.7	711	(% style="color:blue" %)Default channel:
74.12	712	)))
26.7	713
74.12	714	(((
2.2	715	922.1 - SF7BW125 to SF12BW125
74.12	716	)))
2.2	717
74.12	718	(((
2.2	719	922.3 - SF7BW125 to SF12BW125
74.12	720	)))
2.2	721
74.12	722	(((
2.2	723	922.5 - SF7BW125 to SF12BW125
74.12	724	)))
2.2	725
74.12	726	(((
	727
	728	)))
2.2	729
74.12	730	(((
26.7	731	(% style="color:blue" %)Uplink: (OTAA mode, channel added by JoinAccept message)
74.12	732	)))
2.2	733
74.12	734	(((
2.2	735	922.1 - SF7BW125 to SF12BW125
74.12	736	)))
2.2	737
74.12	738	(((
2.2	739	922.3 - SF7BW125 to SF12BW125
74.12	740	)))
2.2	741
74.12	742	(((
2.2	743	922.5 - SF7BW125 to SF12BW125
74.12	744	)))
2.2	745
74.12	746	(((
2.2	747	922.7 - SF7BW125 to SF12BW125
74.12	748	)))
2.2	749
74.12	750	(((
2.2	751	922.9 - SF7BW125 to SF12BW125
74.12	752	)))
2.2	753
74.12	754	(((
2.2	755	923.1 - SF7BW125 to SF12BW125
74.12	756	)))
2.2	757
74.12	758	(((
2.2	759	923.3 - SF7BW125 to SF12BW125
74.12	760	)))
2.2	761
74.12	762	(((
	763
	764	)))
2.2	765
74.12	766	(((
26.7	767	(% style="color:blue" %)Downlink:
74.12	768	)))
2.2	769
74.12	770	(((
2.2	771	Uplink channels 1-7(RX1)
74.12	772	)))
2.2	773
74.12	774	(((
2.2	775	921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
74.12	776	)))
2.2	777
	778
35.6	779
2.2	780
109.9	781	=== 2.6.7 IN865-867 (IN865) ===
100.9	782
74.13	783	(((
26.7	784	(% style="color:blue" %)Uplink:
74.13	785	)))
2.2	786
74.13	787	(((
2.2	788	865.0625 - SF7BW125 to SF12BW125
74.13	789	)))
2.2	790
74.13	791	(((
2.2	792	865.4025 - SF7BW125 to SF12BW125
74.13	793	)))
2.2	794
74.13	795	(((
2.2	796	865.9850 - SF7BW125 to SF12BW125
74.13	797	)))
2.2	798
74.13	799	(((
	800
	801	)))
2.2	802
74.13	803	(((
26.7	804	(% style="color:blue" %)Downlink:
74.13	805	)))
2.2	806
74.13	807	(((
2.2	808	Uplink channels 1-3 (RX1)
74.13	809	)))
2.2	810
74.13	811	(((
2.2	812	866.550 - SF10BW125 (RX2)
74.13	813	)))
2.2	814
	815
	816
100.9	817
100.5	818	== 2.7 LED Indicator ==
26.7	819
100.5	820	The LLDS12 has an internal LED which is to show the status of different state.
2.2	821
	822	* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
	823	* Blink once when device transmit a packet.
	824
113.8	825
	826
	827
100.4	828	== 2.8 Firmware Change Log ==
2.2	829
26.15	830
100.4	831	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/]]
2.2	832
	833
111.17	834	Firmware Upgrade Method: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2.2	835
	836
100.4	837
95.5	838	= 3. LiDAR ToF Measurement =
2.2	839
95.5	840	== 3.1 Principle of Distance Measurement ==
	841
	842	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.
	843
100.1	844	[[image:1654831757579-263.png]]
95.5	845
	846
	847
	848	== 3.2 Distance Measurement Characteristics ==
	849
	850	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:
	851
100.1	852	[[image:1654831774373-275.png]]
95.5	853
	854
111.31	855	(((
111.30	856	(% style="color:blue" %)① (%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
111.31	857	)))
95.5	858
111.31	859	(((
111.30	860	(% style="color:blue" %)② (%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
111.31	861	)))
95.5	862
111.31	863	(((
111.30	864	(% style="color:blue" %)③ (%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
111.31	865	)))
95.5	866
	867
111.31	868	(((
95.5	869	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:
111.31	870	)))
95.5	871
	872
100.1	873	[[image:1654831797521-720.png]]
95.5	874
	875
111.31	876	(((
95.5	877	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.
111.31	878	)))
95.5	879
100.1	880	[[image:1654831810009-716.png]]
95.5	881
	882
111.31	883	(((
95.5	884	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.
111.31	885	)))
95.5	886
	887
	888
	889	== 3.3 Notice of usage: ==
	890
	891	Possible invalid /wrong reading for LiDAR ToF tech:
	892
	893	* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
	894	* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
	895	* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
	896	* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
	897
113.9	898
	899
	900
94.6	901	= 4. Configure LLDS12 via AT Command or LoRaWAN Downlink =
2.2	902
74.14	903	(((
111.32	904	(((
94.6	905	Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
74.14	906	)))
111.32	907	)))
2.2	908
74.14	909	* (((
111.32	910	(((
111.16	911	AT Command Connection: See [[FAQ>>\|\|anchor="H7.A0FAQ"]].
74.14	912	)))
111.32	913	)))
74.14	914	* (((
111.32	915	(((
111.17	916	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
74.14	917	)))
111.32	918	)))
2.2	919
74.14	920	(((
111.32	921	(((
94.6	922
111.32	923	)))
94.6	924
111.32	925	(((
94.9	926	There are two kinds of commands to configure LLDS12, they are:
74.14	927	)))
111.32	928	)))
2.2	929
74.14	930	* (((
111.32	931	(((
74.14	932	(% style="color:#4f81bd" %) General Commands.
	933	)))
111.32	934	)))
2.2	935
74.14	936	(((
111.32	937	(((
2.2	938	These commands are to configure:
74.14	939	)))
111.32	940	)))
2.2	941
74.14	942	* (((
111.32	943	(((
74.14	944	General system settings like: uplink interval.
	945	)))
111.32	946	)))
74.14	947	* (((
111.32	948	(((
74.14	949	LoRaWAN protocol & radio related command.
	950	)))
111.32	951	)))
2.2	952
74.14	953	(((
111.32	954	(((
111.17	955	They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
74.14	956	)))
111.32	957	)))
2.2	958
74.14	959	(((
111.32	960	(((
74.14	961
	962	)))
111.32	963	)))
2.2	964
74.14	965	* (((
111.32	966	(((
94.7	967	(% style="color:#4f81bd" %) Commands special design for LLDS12
74.14	968	)))
111.32	969	)))
2.2	970
74.14	971	(((
111.32	972	(((
94.9	973	These commands only valid for LLDS12, as below:
74.14	974	)))
111.32	975	)))
2.2	976
	977
	978
94.8	979	== 4.1 Set Transmit Interval Time ==
27.2	980
2.2	981	Feature: Change LoRaWAN End Node Transmit Interval.
	982
27.2	983	(% style="color:#037691" %)AT Command: AT+TDC
2.2	984
65.2	985	[[image:image-20220607171554-8.png]]
27.2	986
2.2	987
74.16	988	(((
27.2	989	(% style="color:#037691" %)Downlink Command: 0x01
74.16	990	)))
2.2	991
74.16	992	(((
2.2	993	Format: Command Code (0x01) followed by 3 bytes time value.
74.16	994	)))
2.2	995
74.15	996	(((
2.2	997	If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
74.15	998	)))
2.2	999
74.16	1000	* (((
	1001	Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	1002	)))
	1003	* (((
	1004	Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
76.2	1005
	1006
	1007
74.16	1008	)))
2.2	1009
111.37	1010
113.10	1011
	1012
94.8	1013	== 4.2 Set Interrupt Mode ==
27.3	1014
2.2	1015	Feature, Set Interrupt mode for GPIO_EXIT.
	1016
27.3	1017	(% style="color:#037691" %)AT Command: AT+INTMOD
2.2	1018
95.2	1019	[[image:image-20220610105806-2.png]]
2.2	1020
	1021
74.16	1022	(((
27.3	1023	(% style="color:#037691" %)Downlink Command: 0x06
74.16	1024	)))
2.2	1025
74.16	1026	(((
2.2	1027	Format: Command Code (0x06) followed by 3 bytes.
74.16	1028	)))
2.2	1029
74.16	1030	(((
2.2	1031	This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
74.16	1032	)))
2.2	1033
74.16	1034	* (((
	1035	Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	1036	)))
	1037	* (((
	1038	Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	1039	)))
2.2	1040
111.36	1041
113.11	1042
	1043
94.8	1044	== 4.3 Get Firmware Version Info ==
74.17	1045
2.2	1046	Feature: use downlink to get firmware version.
	1047
27.3	1048	(% style="color:#037691" %)Downlink Command: 0x26
2.2	1049
67.2	1050	[[image:image-20220607171917-10.png]]
2.2	1051
	1052	* Reply to the confirmation package: 26 01
	1053	* Reply to non-confirmed packet: 26 00
	1054
	1055	Device will send an uplink after got this downlink command. With below payload:
	1056
	1057	Configures info payload:
	1058
29.4	1059	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
	1060	\|=(((
	1061	Size(bytes)
	1062	)))\|=1\|=1\|=1\|=1\|=1\|=5\|=1
2.2	1063	\|Value\|Software Type\|(((
	1064	Frequency
	1065
	1066	Band
	1067	)))\|Sub-band\|(((
	1068	Firmware
	1069
	1070	Version
	1071	)))\|Sensor Type\|Reserve\|(((
111.22	1072	[[Message Type>>\|\|anchor="H2.3.7A0MessageType"]]
2.2	1073	Always 0x02
	1074	)))
	1075
95.4	1076	Software Type: Always 0x03 for LLDS12
2.2	1077
	1078
	1079	Frequency Band:
	1080
	1081	*0x01: EU868
	1082
	1083	*0x02: US915
	1084
	1085	*0x03: IN865
	1086
	1087	*0x04: AU915
	1088
	1089	*0x05: KZ865
	1090
	1091	*0x06: RU864
	1092
	1093	*0x07: AS923
	1094
	1095	*0x08: AS923-1
	1096
	1097	*0x09: AS923-2
	1098
	1099	*0xa0: AS923-3
	1100
	1101
	1102	Sub-Band: value 0x00 ~~ 0x08
	1103
	1104
	1105	Firmware Version: 0x0100, Means: v1.0.0 version
	1106
	1107
	1108	Sensor Type:
	1109
	1110	0x01: LSE01
	1111
	1112	0x02: LDDS75
	1113
	1114	0x03: LDDS20
	1115
	1116	0x04: LLMS01
	1117
	1118	0x05: LSPH01
	1119
	1120	0x06: LSNPK01
	1121
95.4	1122	0x07: LLDS12
2.2	1123
	1124
	1125
94.5	1126	= 5. Battery & How to replace =
2.2	1127
94.5	1128	== 5.1 Battery Type ==
2.2	1129
30.2	1130	(((
94.5	1131	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.
30.2	1132	)))
2.2	1133
30.2	1134	(((
2.2	1135	The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
30.2	1136	)))
2.2	1137
68.2	1138	[[image:1654593587246-335.png]]
2.2	1139
	1140
94.5	1141	Minimum Working Voltage for the LLDS12:
2.2	1142
94.5	1143	LLDS12: 2.45v ~~ 3.6v
2.2	1144
	1145
	1146
94.5	1147	== 5.2 Replace Battery ==
30.3	1148
30.5	1149	(((
2.2	1150	Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
30.5	1151	)))
2.2	1152
30.5	1153	(((
2.2	1154	And make sure the positive and negative pins match.
30.5	1155	)))
2.2	1156
	1157
	1158
94.5	1159	== 5.3 Power Consumption Analyze ==
2.2	1160
30.5	1161	(((
2.2	1162	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.
30.5	1163	)))
2.2	1164
30.5	1165	(((
2.2	1166	Instruction to use as below:
30.5	1167	)))
2.2	1168
	1169
32.3	1170	Step 1: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
2.2	1171
	1172	[[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/]]
	1173
	1174
32.3	1175	Step 2: Open it and choose
2.2	1176
	1177	* Product Model
	1178	* Uplink Interval
	1179	* Working Mode
	1180
	1181	And the Life expectation in difference case will be shown on the right.
	1182
69.2	1183	[[image:1654593605679-189.png]]
2.2	1184
	1185
	1186	The battery related documents as below:
	1187
32.2	1188	* (((
	1189	[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
2.2	1190	)))
32.2	1191	* (((
	1192	[[Lithium-Thionyl Chloride Battery datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
	1193	)))
	1194	* (((
	1195	[[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]]
	1196	)))
2.2	1197
70.2	1198	[[image:image-20220607172042-11.png]]
2.2	1199
	1200
	1201
94.5	1202	=== 5.3.1 Battery Note ===
2.2	1203
32.4	1204	(((
2.2	1205	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.
32.4	1206	)))
2.2	1207
	1208
	1209
94.5	1210	=== 5.3.2 Replace the battery ===
32.4	1211
74.20	1212	(((
94.5	1213	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.
74.20	1214	)))
2.2	1215
74.20	1216	(((
94.5	1217	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)
74.20	1218	)))
2.2	1219
	1220
	1221
94.4	1222	= 6. Use AT Command =
2.2	1223
94.4	1224	== 6.1 Access AT Commands ==
2.2	1225
94.5	1226	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.
2.2	1227
72.2	1228	[[image:1654593668970-604.png]]
2.2	1229
34.6	1230	Connection:
2.2	1231
34.2	1232	(% style="background-color:yellow" %) USB TTL GND <~-~-~-~-> GND
2.2	1233
34.2	1234	(% style="background-color:yellow" %) USB TTL TXD <~-~-~-~-> UART_RXD
2.2	1235
34.2	1236	(% style="background-color:yellow" %) USB TTL RXD <~-~-~-~-> UART_TXD
2.2	1237
	1238
74.21	1239	(((
111.33	1240	(((
111.23	1241	In the PC, you need to set the serial baud rate to (% style="color:green" %)9600(%%) to access the serial console for LLDS12.
111.33	1242	)))
111.23	1243
111.33	1244	(((
111.23	1245	LLDS12 will output system info once power on as below:
74.21	1246	)))
111.33	1247	)))
2.2	1248
	1249
72.2	1250	[[image:1654593712276-618.png]]
2.2	1251
111.25	1252	Valid AT Command please check [[Configure Device>>\|\|anchor="H4.A0ConfigureLLDS12viaATCommandorLoRaWANDownlink"]].
2.2	1253
	1254
94.3	1255	= 7. FAQ =
2.2	1256
94.3	1257	== 7.1 How to change the LoRa Frequency Bands/Region ==
34.7	1258
111.26	1259	You can follow the instructions for [[how to upgrade image>>\|\|anchor="H2.8A0200BFirmwareChangeLog"]].
2.2	1260	When downloading the images, choose the required image file for download.
	1261
	1262
93.7	1263	= 8. Trouble Shooting =
2.2	1264
93.6	1265	== 8.1 AT Commands input doesn’t work ==
34.7	1266
93.12	1267
111.34	1268	(((
34.9	1269	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.
111.34	1270	)))
2.2	1271
	1272
93.6	1273	== 8.2 Significant error between the output distant value of LiDAR and actual distance ==
85.21	1274
2.2	1275
93.10	1276	(((
	1277	(% 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.)
	1278	)))
93.9	1279
93.10	1280	(((
93.6	1281	Troubleshooting: Please avoid use of this product under such circumstance in practice.
93.10	1282	)))
93.6	1283
93.10	1284	(((
	1285
	1286	)))
93.6	1287
93.10	1288	(((
	1289	(% style="color:blue" %)Cause ②(%%): The IR-pass filters are blocked.
	1290	)))
93.6	1291
93.10	1292	(((
	1293	Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
	1294	)))
93.6	1295
	1296
93.11	1297
93.6	1298	= 9. Order Info =
	1299
93.13	1300
93.5	1301	Part Number: (% style="color:blue" %)LLDS12-XX
2.2	1302
	1303
34.9	1304	(% style="color:blue" %)XX(%%): The default frequency band
2.2	1305
34.13	1306	* (% style="color:red" %)AS923(%%): LoRaWAN AS923 band
34.9	1307	* (% style="color:red" %)AU915(%%): LoRaWAN AU915 band
	1308	* (% style="color:red" %)EU433(%%): LoRaWAN EU433 band
	1309	* (% style="color:red" %)EU868(%%): LoRaWAN EU868 band
	1310	* (% style="color:red" %)KR920(%%): LoRaWAN KR920 band
	1311	* (% style="color:red" %)US915(%%): LoRaWAN US915 band
34.13	1312	* (% style="color:red" %)IN865(%%): LoRaWAN IN865 band
34.9	1313	* (% style="color:red" %)CN470(%%): LoRaWAN CN470 band
2.2	1314
113.12	1315
	1316
	1317
93.6	1318	= 10. Packing Info =
34.9	1319
	1320
2.2	1321	Package Includes:
	1322
93.4	1323	* LLDS12 LoRaWAN LiDAR Distance Sensor x 1
2.2	1324
	1325	Dimension and weight:
	1326
	1327	* Device Size: cm
	1328	* Device Weight: g
	1329	* Package Size / pcs : cm
	1330	* Weight / pcs : g
	1331
113.12	1332
	1333
	1334
93.6	1335	= 11. Support =
2.2	1336
	1337	* 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.
34.12	1338	* 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]].

Wiki source code of LLDS12-LoRaWAN LiDAR ToF Distance Sensor User Manual

Applications

Navigation