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

Version 94.9 by Xiaoling on 2022/06/10 10:50

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

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

Applications

Navigation