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

Version 107.4 by Xiaoling on 2022/06/10 11:55

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
107.4	297	== 2.4 Uplink Interval ==
14.3	298
107.4	299	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	300
	301
	302
107.4	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
107.2	330	(% style="color:blue" %)Step 4(%%): Create LLDS12 product.
2.2	331
107.2	332	[[image:1654832691989-514.png]]
2.2	333
	334
53.2	335	[[image:1654592833877-762.png]]
2.2	336
	337
107.2	338	[[image:1654832740634-933.png]]
2.2	339
	340
107.2	341
74.3	342	(((
23.5	343	(% style="color:blue" %)Step 5(%%): add payload decode
74.3	344	)))
2.2	345
74.3	346	(((
107.2	347
74.3	348	)))
2.2	349
107.2	350	[[image:1654833065139-942.png]]
2.2	351
	352
	353
107.2	354	[[image:1654833092678-390.png]]
2.2	355
	356
	357
107.2	358	After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
2.2	359
107.2	360	[[image:1654833163048-332.png]]
2.2	361
	362
	363
100.7	364	== 2.6 Frequency Plans ==
	365
26.6	366	(((
100.7	367	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	368	)))
2.2	369
	370
100.7	371	=== 2.6.1 EU863-870 (EU868) ===
2.2	372
74.10	373	(((
26.5	374	(% style="color:blue" %)Uplink:
74.10	375	)))
26.5	376
74.10	377	(((
2.2	378	868.1 - SF7BW125 to SF12BW125
74.10	379	)))
2.2	380
74.10	381	(((
2.2	382	868.3 - SF7BW125 to SF12BW125 and SF7BW250
74.10	383	)))
2.2	384
74.10	385	(((
2.2	386	868.5 - SF7BW125 to SF12BW125
74.10	387	)))
2.2	388
74.10	389	(((
2.2	390	867.1 - SF7BW125 to SF12BW125
74.10	391	)))
2.2	392
74.10	393	(((
2.2	394	867.3 - SF7BW125 to SF12BW125
74.10	395	)))
2.2	396
74.10	397	(((
2.2	398	867.5 - SF7BW125 to SF12BW125
74.10	399	)))
2.2	400
74.10	401	(((
2.2	402	867.7 - SF7BW125 to SF12BW125
74.10	403	)))
2.2	404
74.10	405	(((
2.2	406	867.9 - SF7BW125 to SF12BW125
74.10	407	)))
2.2	408
74.10	409	(((
2.2	410	868.8 - FSK
74.10	411	)))
2.2	412
74.10	413	(((
	414
	415	)))
2.2	416
74.10	417	(((
26.5	418	(% style="color:blue" %)Downlink:
74.10	419	)))
2.2	420
74.10	421	(((
2.2	422	Uplink channels 1-9 (RX1)
74.10	423	)))
2.2	424
74.10	425	(((
2.2	426	869.525 - SF9BW125 (RX2 downlink only)
74.10	427	)))
2.2	428
	429
	430
100.9	431	=== 2.6.2 US902-928(US915) ===
26.5	432
	433	(((
2.2	434	Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
26.5	435	)))
2.2	436
26.5	437	(((
2.2	438	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	439	)))
2.2	440
26.5	441	(((
2.2	442	After Join success, the end node will switch to the correct sub band by:
26.5	443	)))
2.2	444
	445	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	446	* 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)
	447
26.5	448
100.9	449	=== 2.6.3 CN470-510 (CN470) ===
	450
74.11	451	(((
2.2	452	Used in China, Default use CHE=1
74.11	453	)))
2.2	454
74.11	455	(((
26.5	456	(% style="color:blue" %)Uplink:
74.11	457	)))
2.2	458
74.11	459	(((
2.2	460	486.3 - SF7BW125 to SF12BW125
74.11	461	)))
2.2	462
74.11	463	(((
2.2	464	486.5 - SF7BW125 to SF12BW125
74.11	465	)))
2.2	466
74.11	467	(((
2.2	468	486.7 - SF7BW125 to SF12BW125
74.11	469	)))
2.2	470
74.11	471	(((
2.2	472	486.9 - SF7BW125 to SF12BW125
74.11	473	)))
2.2	474
74.11	475	(((
2.2	476	487.1 - SF7BW125 to SF12BW125
74.11	477	)))
2.2	478
74.11	479	(((
2.2	480	487.3 - SF7BW125 to SF12BW125
74.11	481	)))
2.2	482
74.11	483	(((
2.2	484	487.5 - SF7BW125 to SF12BW125
74.11	485	)))
2.2	486
74.11	487	(((
2.2	488	487.7 - SF7BW125 to SF12BW125
74.11	489	)))
2.2	490
74.11	491	(((
	492
	493	)))
2.2	494
74.11	495	(((
26.5	496	(% style="color:blue" %)Downlink:
74.11	497	)))
2.2	498
74.11	499	(((
2.2	500	506.7 - SF7BW125 to SF12BW125
74.11	501	)))
2.2	502
74.11	503	(((
2.2	504	506.9 - SF7BW125 to SF12BW125
74.11	505	)))
2.2	506
74.11	507	(((
2.2	508	507.1 - SF7BW125 to SF12BW125
74.11	509	)))
2.2	510
74.11	511	(((
2.2	512	507.3 - SF7BW125 to SF12BW125
74.11	513	)))
2.2	514
74.11	515	(((
2.2	516	507.5 - SF7BW125 to SF12BW125
74.11	517	)))
2.2	518
74.11	519	(((
2.2	520	507.7 - SF7BW125 to SF12BW125
74.11	521	)))
2.2	522
74.11	523	(((
2.2	524	507.9 - SF7BW125 to SF12BW125
74.11	525	)))
2.2	526
74.11	527	(((
2.2	528	508.1 - SF7BW125 to SF12BW125
74.11	529	)))
2.2	530
74.11	531	(((
2.2	532	505.3 - SF12BW125 (RX2 downlink only)
74.11	533	)))
2.2	534
	535
	536
26.5	537
100.9	538	=== 2.6.4 AU915-928(AU915) ===
	539
26.5	540	(((
2.2	541	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
26.5	542	)))
2.2	543
26.5	544	(((
2.2	545	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	546	)))
2.2	547
26.5	548	(((
	549
	550	)))
2.2	551
26.5	552	(((
2.2	553	After Join success, the end node will switch to the correct sub band by:
26.5	554	)))
2.2	555
	556	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	557	* 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)
	558
100.9	559	=== 2.6.5 AS920-923 & AS923-925 (AS923) ===
	560
74.9	561	(((
26.7	562	(% style="color:blue" %)Default Uplink channel:
74.9	563	)))
2.2	564
74.9	565	(((
2.2	566	923.2 - SF7BW125 to SF10BW125
74.9	567	)))
2.2	568
74.9	569	(((
2.2	570	923.4 - SF7BW125 to SF10BW125
74.9	571	)))
2.2	572
74.9	573	(((
	574
	575	)))
2.2	576
74.9	577	(((
26.7	578	(% style="color:blue" %)Additional Uplink Channel:
74.9	579	)))
2.2	580
74.9	581	(((
2.2	582	(OTAA mode, channel added by JoinAccept message)
74.9	583	)))
2.2	584
74.9	585	(((
	586
	587	)))
2.2	588
74.9	589	(((
26.7	590	(% style="color:blue" %)AS920~~AS923 for Japan, Malaysia, Singapore:
74.9	591	)))
26.7	592
74.9	593	(((
2.2	594	922.2 - SF7BW125 to SF10BW125
74.9	595	)))
2.2	596
74.9	597	(((
2.2	598	922.4 - SF7BW125 to SF10BW125
74.9	599	)))
2.2	600
74.9	601	(((
2.2	602	922.6 - SF7BW125 to SF10BW125
74.9	603	)))
2.2	604
74.9	605	(((
2.2	606	922.8 - SF7BW125 to SF10BW125
74.9	607	)))
2.2	608
74.9	609	(((
2.2	610	923.0 - SF7BW125 to SF10BW125
74.9	611	)))
2.2	612
74.9	613	(((
2.2	614	922.0 - SF7BW125 to SF10BW125
74.9	615	)))
2.2	616
74.9	617	(((
	618
	619	)))
2.2	620
74.9	621	(((
26.7	622	(% style="color:blue" %)AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam:
74.9	623	)))
2.2	624
74.9	625	(((
2.2	626	923.6 - SF7BW125 to SF10BW125
74.9	627	)))
2.2	628
74.9	629	(((
2.2	630	923.8 - SF7BW125 to SF10BW125
74.9	631	)))
2.2	632
74.9	633	(((
2.2	634	924.0 - SF7BW125 to SF10BW125
74.9	635	)))
2.2	636
74.9	637	(((
2.2	638	924.2 - SF7BW125 to SF10BW125
74.9	639	)))
2.2	640
74.9	641	(((
2.2	642	924.4 - SF7BW125 to SF10BW125
74.9	643	)))
2.2	644
74.9	645	(((
2.2	646	924.6 - SF7BW125 to SF10BW125
74.9	647	)))
2.2	648
74.9	649	(((
	650
	651	)))
2.2	652
74.9	653	(((
26.7	654	(% style="color:blue" %)Downlink:
74.9	655	)))
2.2	656
74.9	657	(((
2.2	658	Uplink channels 1-8 (RX1)
74.9	659	)))
2.2	660
74.9	661	(((
2.2	662	923.2 - SF10BW125 (RX2)
74.9	663	)))
2.2	664
	665
	666
	667
100.9	668	=== 2.6.6 KR920-923 (KR920) ===
	669
74.12	670	(((
26.7	671	(% style="color:blue" %)Default channel:
74.12	672	)))
26.7	673
74.12	674	(((
2.2	675	922.1 - SF7BW125 to SF12BW125
74.12	676	)))
2.2	677
74.12	678	(((
2.2	679	922.3 - SF7BW125 to SF12BW125
74.12	680	)))
2.2	681
74.12	682	(((
2.2	683	922.5 - SF7BW125 to SF12BW125
74.12	684	)))
2.2	685
74.12	686	(((
	687
	688	)))
2.2	689
74.12	690	(((
26.7	691	(% style="color:blue" %)Uplink: (OTAA mode, channel added by JoinAccept message)
74.12	692	)))
2.2	693
74.12	694	(((
2.2	695	922.1 - SF7BW125 to SF12BW125
74.12	696	)))
2.2	697
74.12	698	(((
2.2	699	922.3 - SF7BW125 to SF12BW125
74.12	700	)))
2.2	701
74.12	702	(((
2.2	703	922.5 - SF7BW125 to SF12BW125
74.12	704	)))
2.2	705
74.12	706	(((
2.2	707	922.7 - SF7BW125 to SF12BW125
74.12	708	)))
2.2	709
74.12	710	(((
2.2	711	922.9 - SF7BW125 to SF12BW125
74.12	712	)))
2.2	713
74.12	714	(((
2.2	715	923.1 - SF7BW125 to SF12BW125
74.12	716	)))
2.2	717
74.12	718	(((
2.2	719	923.3 - SF7BW125 to SF12BW125
74.12	720	)))
2.2	721
74.12	722	(((
	723
	724	)))
2.2	725
74.12	726	(((
26.7	727	(% style="color:blue" %)Downlink:
74.12	728	)))
2.2	729
74.12	730	(((
2.2	731	Uplink channels 1-7(RX1)
74.12	732	)))
2.2	733
74.12	734	(((
2.2	735	921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
74.12	736	)))
2.2	737
	738
35.6	739
2.2	740
100.9	741	=== 2.6.7 IN865-867 (IN865) ===
	742
74.13	743	(((
26.7	744	(% style="color:blue" %)Uplink:
74.13	745	)))
2.2	746
74.13	747	(((
2.2	748	865.0625 - SF7BW125 to SF12BW125
74.13	749	)))
2.2	750
74.13	751	(((
2.2	752	865.4025 - SF7BW125 to SF12BW125
74.13	753	)))
2.2	754
74.13	755	(((
2.2	756	865.9850 - SF7BW125 to SF12BW125
74.13	757	)))
2.2	758
74.13	759	(((
	760
	761	)))
2.2	762
74.13	763	(((
26.7	764	(% style="color:blue" %)Downlink:
74.13	765	)))
2.2	766
74.13	767	(((
2.2	768	Uplink channels 1-3 (RX1)
74.13	769	)))
2.2	770
74.13	771	(((
2.2	772	866.550 - SF10BW125 (RX2)
74.13	773	)))
2.2	774
	775
	776
100.9	777
100.5	778	== 2.7 LED Indicator ==
26.7	779
100.5	780	The LLDS12 has an internal LED which is to show the status of different state.
2.2	781
	782	* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
	783	* Blink once when device transmit a packet.
	784
101.2	785
	786
100.4	787	== 2.8 Firmware Change Log ==
2.2	788
26.15	789
100.4	790	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	791
	792
36.1	793	Firmware Upgrade Method: [[Firmware Upgrade Instruction>>path:/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/]]
2.2	794
	795
100.4	796
95.5	797	= 3. LiDAR ToF Measurement =
2.2	798
95.5	799	== 3.1 Principle of Distance Measurement ==
	800
	801	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.
	802
100.1	803	[[image:1654831757579-263.png]]
95.5	804
	805
	806
	807	== 3.2 Distance Measurement Characteristics ==
	808
	809	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:
	810
100.1	811	[[image:1654831774373-275.png]]
95.5	812
	813
	814	①Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
	815
	816	②Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
	817
	818	③Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
	819
	820
	821	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:
	822
	823
100.1	824	[[image:1654831797521-720.png]]
95.5	825
	826
	827	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.
	828
100.1	829	[[image:1654831810009-716.png]]
95.5	830
	831
	832	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.
	833
	834
	835
	836	== 3.3 Notice of usage: ==
	837
	838	Possible invalid /wrong reading for LiDAR ToF tech:
	839
	840	* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
	841	* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
	842	* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
	843	* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
	844
94.6	845	= 4. Configure LLDS12 via AT Command or LoRaWAN Downlink =
2.2	846
74.14	847	(((
94.6	848	Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
74.14	849	)))
2.2	850
74.14	851	* (((
85.3	852	AT Command Connection: See [[FAQ>>\|\|anchor="H6.FAQ"]].
74.14	853	)))
	854	* (((
	855	LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>path:/xwiki/bin/view/Main/]]
	856	)))
2.2	857
74.14	858	(((
94.6	859
	860
94.9	861	There are two kinds of commands to configure LLDS12, they are:
74.14	862	)))
2.2	863
74.14	864	* (((
	865	(% style="color:#4f81bd" %) General Commands.
	866	)))
2.2	867
74.14	868	(((
2.2	869	These commands are to configure:
74.14	870	)))
2.2	871
74.14	872	* (((
	873	General system settings like: uplink interval.
	874	)))
	875	* (((
	876	LoRaWAN protocol & radio related command.
	877	)))
2.2	878
74.14	879	(((
94.7	880	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	881	)))
2.2	882
74.14	883	(((
	884
	885	)))
2.2	886
74.14	887	* (((
94.7	888	(% style="color:#4f81bd" %) Commands special design for LLDS12
74.14	889	)))
2.2	890
74.14	891	(((
94.9	892	These commands only valid for LLDS12, as below:
74.14	893	)))
2.2	894
	895
	896
94.8	897	== 4.1 Set Transmit Interval Time ==
27.2	898
2.2	899	Feature: Change LoRaWAN End Node Transmit Interval.
	900
27.2	901	(% style="color:#037691" %)AT Command: AT+TDC
2.2	902
65.2	903	[[image:image-20220607171554-8.png]]
27.2	904
2.2	905
	906
74.16	907	(((
27.2	908	(% style="color:#037691" %)Downlink Command: 0x01
74.16	909	)))
2.2	910
74.16	911	(((
2.2	912	Format: Command Code (0x01) followed by 3 bytes time value.
74.16	913	)))
2.2	914
74.15	915	(((
2.2	916	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	917	)))
2.2	918
74.16	919	* (((
	920	Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	921	)))
	922	* (((
	923	Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
76.2	924
	925
	926
74.16	927	)))
2.2	928
94.8	929	== 4.2 Set Interrupt Mode ==
27.3	930
2.2	931	Feature, Set Interrupt mode for GPIO_EXIT.
	932
27.3	933	(% style="color:#037691" %)AT Command: AT+INTMOD
2.2	934
95.2	935	[[image:image-20220610105806-2.png]]
2.2	936
	937
95.2	938
	939
74.16	940	(((
27.3	941	(% style="color:#037691" %)Downlink Command: 0x06
74.16	942	)))
2.2	943
74.16	944	(((
2.2	945	Format: Command Code (0x06) followed by 3 bytes.
74.16	946	)))
2.2	947
74.16	948	(((
2.2	949	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	950	)))
2.2	951
74.16	952	* (((
	953	Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	954	)))
	955	* (((
	956	Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	957	)))
2.2	958
94.8	959	== 4.3 Get Firmware Version Info ==
74.17	960
2.2	961	Feature: use downlink to get firmware version.
	962
27.3	963	(% style="color:#037691" %)Downlink Command: 0x26
2.2	964
67.2	965	[[image:image-20220607171917-10.png]]
2.2	966
	967	* Reply to the confirmation package: 26 01
	968	* Reply to non-confirmed packet: 26 00
	969
	970	Device will send an uplink after got this downlink command. With below payload:
	971
	972	Configures info payload:
	973
29.4	974	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
	975	\|=(((
	976	Size(bytes)
	977	)))\|=1\|=1\|=1\|=1\|=1\|=5\|=1
2.2	978	\|Value\|Software Type\|(((
	979	Frequency
	980
	981	Band
	982	)))\|Sub-band\|(((
	983	Firmware
	984
	985	Version
	986	)))\|Sensor Type\|Reserve\|(((
85.3	987	[[Message Type>>\|\|anchor="H2.3.6MessageType"]]
2.2	988	Always 0x02
	989	)))
	990
95.4	991	Software Type: Always 0x03 for LLDS12
2.2	992
	993
	994	Frequency Band:
	995
	996	*0x01: EU868
	997
	998	*0x02: US915
	999
	1000	*0x03: IN865
	1001
	1002	*0x04: AU915
	1003
	1004	*0x05: KZ865
	1005
	1006	*0x06: RU864
	1007
	1008	*0x07: AS923
	1009
	1010	*0x08: AS923-1
	1011
	1012	*0x09: AS923-2
	1013
	1014	*0xa0: AS923-3
	1015
	1016
	1017	Sub-Band: value 0x00 ~~ 0x08
	1018
	1019
	1020	Firmware Version: 0x0100, Means: v1.0.0 version
	1021
	1022
	1023	Sensor Type:
	1024
	1025	0x01: LSE01
	1026
	1027	0x02: LDDS75
	1028
	1029	0x03: LDDS20
	1030
	1031	0x04: LLMS01
	1032
	1033	0x05: LSPH01
	1034
	1035	0x06: LSNPK01
	1036
95.4	1037	0x07: LLDS12
2.2	1038
	1039
	1040
94.5	1041	= 5. Battery & How to replace =
2.2	1042
94.5	1043	== 5.1 Battery Type ==
2.2	1044
30.2	1045	(((
94.5	1046	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	1047	)))
2.2	1048
30.2	1049	(((
2.2	1050	The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
30.2	1051	)))
2.2	1052
68.2	1053	[[image:1654593587246-335.png]]
2.2	1054
	1055
94.5	1056	Minimum Working Voltage for the LLDS12:
2.2	1057
94.5	1058	LLDS12: 2.45v ~~ 3.6v
2.2	1059
	1060
	1061
94.5	1062	== 5.2 Replace Battery ==
30.3	1063
30.5	1064	(((
2.2	1065	Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
30.5	1066	)))
2.2	1067
30.5	1068	(((
2.2	1069	And make sure the positive and negative pins match.
30.5	1070	)))
2.2	1071
	1072
	1073
94.5	1074	== 5.3 Power Consumption Analyze ==
2.2	1075
30.5	1076	(((
2.2	1077	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	1078	)))
2.2	1079
30.5	1080	(((
2.2	1081	Instruction to use as below:
30.5	1082	)))
2.2	1083
	1084
32.3	1085	Step 1: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
2.2	1086
	1087	[[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/]]
	1088
	1089
32.3	1090	Step 2: Open it and choose
2.2	1091
	1092	* Product Model
	1093	* Uplink Interval
	1094	* Working Mode
	1095
	1096	And the Life expectation in difference case will be shown on the right.
	1097
69.2	1098	[[image:1654593605679-189.png]]
2.2	1099
	1100
	1101	The battery related documents as below:
	1102
32.2	1103	* (((
	1104	[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
2.2	1105	)))
32.2	1106	* (((
	1107	[[Lithium-Thionyl Chloride Battery datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
	1108	)))
	1109	* (((
	1110	[[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]]
	1111	)))
2.2	1112
70.2	1113	[[image:image-20220607172042-11.png]]
2.2	1114
	1115
	1116
94.5	1117	=== 5.3.1 Battery Note ===
2.2	1118
32.4	1119	(((
2.2	1120	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	1121	)))
2.2	1122
	1123
	1124
94.5	1125	=== 5.3.2 Replace the battery ===
32.4	1126
74.20	1127	(((
94.5	1128	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	1129	)))
2.2	1130
74.20	1131	(((
94.5	1132	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	1133	)))
2.2	1134
	1135
	1136
94.4	1137	= 6. Use AT Command =
2.2	1138
94.4	1139	== 6.1 Access AT Commands ==
2.2	1140
94.5	1141	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	1142
72.2	1143	[[image:1654593668970-604.png]]
2.2	1144
34.6	1145	Connection:
2.2	1146
34.2	1147	(% style="background-color:yellow" %) USB TTL GND <~-~-~-~-> GND
2.2	1148
34.2	1149	(% style="background-color:yellow" %) USB TTL TXD <~-~-~-~-> UART_RXD
2.2	1150
34.2	1151	(% style="background-color:yellow" %) USB TTL RXD <~-~-~-~-> UART_TXD
2.2	1152
	1153
74.21	1154	(((
34.6	1155	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	1156	)))
2.2	1157
	1158
72.2	1159	[[image:1654593712276-618.png]]
2.2	1160
85.3	1161	Valid AT Command please check [[Configure Device>>\|\|anchor="H3.ConfigureLSPH01viaATCommandorLoRaWANDownlink"]].
2.2	1162
	1163
94.3	1164	= 7. FAQ =
2.2	1165
94.3	1166	== 7.1 How to change the LoRa Frequency Bands/Region ==
34.7	1167
85.3	1168	You can follow the instructions for [[how to upgrade image>>\|\|anchor="H2.10200BFirmwareChangeLog"]].
2.2	1169	When downloading the images, choose the required image file for download.
	1170
	1171
93.7	1172	= 8. Trouble Shooting =
2.2	1173
93.6	1174	== 8.1 AT Commands input doesn’t work ==
34.7	1175
93.12	1176
34.9	1177	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	1178
	1179
93.6	1180	== 8.2 Significant error between the output distant value of LiDAR and actual distance ==
85.21	1181
2.2	1182
93.10	1183	(((
	1184	(% 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.)
	1185	)))
93.9	1186
93.10	1187	(((
93.6	1188	Troubleshooting: Please avoid use of this product under such circumstance in practice.
93.10	1189	)))
93.6	1190
93.10	1191	(((
	1192
	1193	)))
93.6	1194
93.10	1195	(((
	1196	(% style="color:blue" %)Cause ②(%%): The IR-pass filters are blocked.
	1197	)))
93.6	1198
93.10	1199	(((
	1200	Troubleshooting: please use dry dust-free cloth to gently remove the foreign matter.
	1201	)))
93.6	1202
	1203
93.11	1204
93.6	1205	= 9. Order Info =
	1206
93.13	1207
93.5	1208	Part Number: (% style="color:blue" %)LLDS12-XX
2.2	1209
	1210
34.9	1211	(% style="color:blue" %)XX(%%): The default frequency band
2.2	1212
34.13	1213	* (% style="color:red" %)AS923(%%): LoRaWAN AS923 band
34.9	1214	* (% style="color:red" %)AU915(%%): LoRaWAN AU915 band
	1215	* (% style="color:red" %)EU433(%%): LoRaWAN EU433 band
	1216	* (% style="color:red" %)EU868(%%): LoRaWAN EU868 band
	1217	* (% style="color:red" %)KR920(%%): LoRaWAN KR920 band
	1218	* (% style="color:red" %)US915(%%): LoRaWAN US915 band
34.13	1219	* (% style="color:red" %)IN865(%%): LoRaWAN IN865 band
34.9	1220	* (% style="color:red" %)CN470(%%): LoRaWAN CN470 band
2.2	1221
93.6	1222	= 10. Packing Info =
34.9	1223
	1224
2.2	1225	Package Includes:
	1226
93.4	1227	* LLDS12 LoRaWAN LiDAR Distance Sensor x 1
2.2	1228
	1229	Dimension and weight:
	1230
	1231	* Device Size: cm
	1232	* Device Weight: g
	1233	* Package Size / pcs : cm
	1234	* Weight / pcs : g
	1235
93.6	1236	= 11. Support =
2.2	1237
	1238	* 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	1239	* 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	1240
107.3	1241

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

Applications

Navigation