Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 22 removed)
  • 1654848616367-242.png
  • 1654849068701-275.png
  • 1654850511545-399.png
  • 1654850829385-439.png
  • 1654851029373-510.png
  • 1654852175653-550.png
  • 1654852253176-749.png
  • image-20220610161353-4.png
  • image-20220610161353-5.png
  • image-20220610161353-6.png
  • image-20220610161353-7.png
  • image-20220610161538-8.png
  • image-20220610161538-9.png
  • image-20220610161724-10.png
  • image-20220610165129-11.png
  • image-20220610172003-1.png
  • image-20220610172003-2.png
  • image-20220610172400-3.png
  • image-20220610172924-4.png
  • image-20220610172924-5.png
  • image-20220610172924-6.png
  • image-20220610173409-7.png

Details

Page properties

Content

...	...	@@ -33,7 +33,7 @@
33	33	Each LDDS75 pre-loads with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect if there is network coverage, after power on.
34	34
35	35
36		-(% style="color:#4472c4" %) * (%%)Actually lifetime depends on network coverage and uplink interval and other factors
	36	+(% style="color:#4472c4" %) ***** (%%)Actually lifetime depends on network coverage and uplink interval and other factors
37	37	)))
38	38	)))
39	39
...	...	@@ -57,6 +57,7 @@
57	57	* IP66 Waterproof Enclosure
58	58	* 4000mAh or 8500mAh Battery for long term use
59	59
	60	+
60	60	== 1.3  Specification ==
61	61
62	62	=== 1.3.1  Rated environmental conditions ===
...	...	@@ -71,20 +71,15 @@
71	71
72	72	=== 1.3.2  Effective measurement range Reference beam pattern ===
73	73
74		-**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**
	75	+**(1) The tested object is a white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm.**[[image:image-20220610155021-2.png||height="440" width="1189"]]
75	75
76	76
77	77
78		-[[image:1654852253176-749.png]]
	79	+**(2)** The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.[[image:image-20220610155021-3.png||height="437" width="1192"]]
79	79
	81	+(% style="display:none" %) (%%)
80	80
81		-**(2)** **The object to be tested is a "corrugated cardboard box" perpendicular to the central axis of 0 °, and the length * width is 60cm * 50cm.**
82	82
83		-
84		-[[image:1654852175653-550.png]](% style="display:none" %) ** **
85		-
86		-
87		-
88	88	== 1.5 ​ Applications ==
89	89
90	90	* Horizontal distance measurement
...	...	@@ -97,6 +97,8 @@
97	97	* Sewer
98	98	* Bottom water level monitoring
99	99
	96	+
	97	+
100	100	== 1.6  Pin mapping and power on ==
101	101
102	102
...	...	@@ -103,7 +103,6 @@
103	103	[[image:1654847583902-256.png]]
104	104
105	105
106		-
107	107	= 2.  Configure LDDS75 to connect to LoRaWAN network =
108	108
109	109	== 2.1  How it works ==
...	...	@@ -113,11 +113,10 @@
113	113	)))
114	114
115	115	(((
116		-In case you can't set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.A0ConfigureLDDS75viaATCommandorLoRaWANDownlink"]]to set the keys in the LDDS75.
	113	+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 LDDS75.
117	117	)))
118	118
119	119
120		-
121	121	== 2.2  ​Quick guide to connect to LoRaWAN server (OTAA) ==
122	122
123	123	(((
...	...	@@ -125,7 +125,7 @@
125	125	)))
126	126
127	127	(((
128		-[[image:1654848616367-242.png]]
	124	+[[image:1654827857527-556.png]]
129	129	)))
130	130
131	131	(((
...	...	@@ -133,57 +133,57 @@
133	133	)))
134	134
135	135	(((
136		-(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LDDS75.
	132	+(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSPH01.
137	137	)))
138	138
139	139	(((
140		-Each LDDS75 is shipped with a sticker with the default device keys, user can find this sticker in the box. it looks like below.
	136	+Each LSPH01 is shipped with a sticker with the default device EUI as below:
141	141	)))
142	142
143	143	[[image:image-20220607170145-1.jpeg]]
144	144
145	145
146		-For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
147	147
148		-Enter these keys in the LoRaWAN Server portal. Below is TTN V3 screen shot:
	143	+You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
149	149
150		-**Add APP EUI in the application**
151	151
152		-[[image:image-20220610161353-4.png]]
	146	+**Register the device**
153	153
154		-[[image:image-20220610161353-5.png]]
155	155
156		-[[image:image-20220610161353-6.png]]
	149	+[[image:1654592600093-601.png]]
157	157
158	158
159		-[[image:image-20220610161353-7.png]]
160	160
	153	+**Add APP EUI and DEV EUI**
161	161
162		-You can also choose to create the device manually.
	155	+[[image:1654592619856-881.png]]
163	163
164		- [[image:image-20220610161538-8.png]]
165	165
166	166
	159	+**Add APP EUI in the application**
167	167
168		-**Add APP KEY and DEV EUI**
	161	+[[image:1654592632656-512.png]]
169	169
170		-[[image:image-20220610161538-9.png]]
171	171
172	172
	165	+**Add APP KEY**
173	173
174		-(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
	167	+[[image:1654592653453-934.png]]
175	175
176	176
	170	+(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
	171	+
	172	+
177	177	Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
178	178
179		-[[image:image-20220610161724-10.png]]
	175	+[[image:image-20220607170442-2.png]]
180	180
181	181
182	182	(((
183		-(% style="color:blue" %)**Step 3**(%%)**:** The LDDS75 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
	179	+(% 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.
184	184	)))
185	185
186		-[[image:1654849068701-275.png]]
	182	+[[image:1654833501679-968.png]]
187	187
188	188
189	189
...	...	@@ -190,10 +190,11 @@
190	190	== 2.3  ​Uplink Payload ==
191	191
192	192	(((
193		-LDDS75 will uplink payload via LoRaWAN with below payload format:
	189	+LLDS12 will uplink payload via LoRaWAN with below payload format:
	190	+)))
194	194
195		-Uplink payload includes in total 4 bytes.
196		-Payload for firmware version v1.1.4. . Before v1.1.3, there is on two fields: BAT and Distance
	192	+(((
	193	+Uplink payload includes in total 11 bytes.
197	197	)))
198	198
199	199	(((
...	...	@@ -203,23 +203,23 @@
203	203	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
204	204	|=(% style="width: 62.5px;" %)(((
205	205	**Size (bytes)**
206		-)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
207		-|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
208		-[[Distance>>||anchor="H2.3.3A0Distance"]]
	203	+)))|=(% style="width: 62.5px;" %)**2**|=(% style="width: 62.5px;" %)**2**|=**2**|=**2**|=**1**|=**1**|=**1**
	204	+|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:62.5px" %)(((
	205	+[[Temperature DS18B20>>||anchor="H2.3.2A0DS18B20Temperaturesensor"]]
	206	+)))|[[Distance>>||anchor="H2.3.3A0Distance"]]|[[Distance signal strength>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
	207	+[[Interrupt flag>>||anchor="H2.3.5A0InterruptPin"]]
	208	+)))|[[LiDAR temp>>||anchor="H2.3.6A0LiDARtemp"]]|(((
	209	+[[Message Type>>||anchor="H2.3.7A0MessageType"]]
	210	+)))
209	209
210		-(unit: mm)
211		-)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
212		-[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
213		-)))|[[Sensor Flag>>path:#Sensor_Flag]]
	212	+[[image:1654833689380-972.png]]
214	214
215		-[[image:1654850511545-399.png]]
216	216
217	217
218		-
219	219	=== 2.3.1  Battery Info ===
220	220
221	221
222		-Check the battery voltage for LDDS75.
	219	+Check the battery voltage for LLDS12.
223	223
224	224	Ex1: 0x0B45 = 2885mV
225	225
...	...	@@ -227,20 +227,49 @@
227	227
228	228
229	229
230		-=== 2.3.2  Distance ===
	227	+=== 2.3.2  DS18B20 Temperature sensor ===
231	231
232		-Get the distance. Flat object range 280mm - 7500mm.
	229	+This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
233	233
234		-For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is(% style="color:#4472c4" %)** 0B05(H) = 2821 (D) = 2821 mm.**
235	235
	232	+**Example**:
236	236
237		-* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
238		-* If the sensor value lower than 0x0118 (280mm), the sensor value will be invalid. Since v1.1.4, all value lower than 280mm will be set to 0x0014(20mm) which means the value is invalid.
	234	+If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
239	239
240		-=== 2.3.3  Interrupt Pin ===
	236	+If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
241	241
	238	+
	239	+
	240	+=== 2.3.3  Distance ===
	241	+
	242	+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.
	243	+
	244	+
	245	+**Example**:
	246	+
	247	+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.
	248	+
	249	+
	250	+
	251	+=== 2.3.4  Distance signal strength ===
	252	+
	253	+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.
	254	+
	255	+
	256	+**Example**:
	257	+
	258	+If payload is: 01D7(H)=471(D), distance signal strength=471, 471>100,471≠65535, the measured value of Dist is considered credible.
	259	+
	260	+Customers can judge whether they need to adjust the environment based on the signal strength.
	261	+
	262	+
	263	+
	264	+=== 2.3.5  Interrupt Pin ===
	265	+
242	242	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.
243	243
	268	+Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
	269	+
244	244	**Example:**
245	245
246	246	0x00: Normal uplink packet.
...	...	@@ -249,44 +249,52 @@
249	249
250	250
251	251
252		-=== 2.3.4  DS18B20 Temperature sensor ===
	278	+=== 2.3.6  LiDAR temp ===
253	253
254		-This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
	280	+Characterize the internal temperature value of the sensor.
255	255
256		-**Example**:
	282	+**Example: **
	283	+If payload is: 1C(H) <<24>>24=28(D),LiDAR temp=28℃.
	284	+If payload is: F2(H) <<24>>24=-14(D),LiDAR temp=-14℃.
257	257
258		-If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
259	259
260		-If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
261	261
262		-(% style="color:red" %)Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
	288	+=== 2.3.7  Message Type ===
263	263
	290	+(((
	291	+For a normal uplink payload, the message type is always 0x01.
	292	+)))
264	264
	294	+(((
	295	+Valid Message Type:
	296	+)))
265	265
266		-=== 2.3.5  Sensor Flag ===
267	267
268		-0x01: Detect Ultrasonic Sensor
	299	+(% border="1" cellspacing="10" style="background-color:#ffffcc; width:499px" %)
	300	+|=(% style="width: 160px;" %)**Message Type Code**|=(% style="width: 163px;" %)**Description**|=(% style="width: 173px;" %)**Payload**
	301	+|(% style="width:160px" %)0x01|(% style="width:163px" %)Normal Uplink|(% style="width:173px" %)[[Normal Uplink Payload>>||anchor="H2.3A0200BUplinkPayload"]]
	302	+|(% style="width:160px" %)0x02|(% style="width:163px" %)Reply configures info|(% style="width:173px" %)[[Configure Info Payload>>||anchor="H4.3A0GetFirmwareVersionInfo"]]
269	269
270		-0x00: No Ultrasonic Sensor
	304	+=== 2.3.8  Decode payload in The Things Network ===
271	271
272		-
273		-===
274		-(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
275		-
276	276	While using TTN network, you can add the payload format to decode the payload.
277	277
278	278
279		-[[image:1654850829385-439.png]]
	309	+[[image:1654592762713-715.png]]
280	280
281		-The payload decoder function for TTN V3 is here:
	311	+(((
	312	+The payload decoder function for TTN is here:
	313	+)))
282	282
283		-LDDS75 TTN V3 Payload Decoder: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDDS75/Payload_Decoder/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Payload_Decoder/]]
	315	+(((
	316	+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/]]
	317	+)))
284	284
285	285
286	286
287	287	== 2.4  Uplink Interval ==
288	288
289		-The LDDS75 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]
	323	+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"]]
290	290
291	291
292	292
...	...	@@ -317,25 +317,47 @@
317	317
318	318	(% style="color:blue" %)**Step 3**(%%)**: Create an account or log in Datacake.**
319	319
320		-(% style="color:blue" %)**Step 4**(%%)**: Search the LDDS75 and add DevEUI.**
	354	+(% style="color:blue" %)**Step 4**(%%)**: Create LLDS12 product.**
321	321
322		-[[image:1654851029373-510.png]]
	356	+[[image:1654832691989-514.png]]
323	323
324	324
325		-After added, the sensor data arrive TTN V3, it will also arrive and show in Datacake.
	359	+[[image:1654592833877-762.png]]
326	326
327		-[[image:image-20220610165129-11.png||height="595" width="1088"]]
328	328
	362	+[[image:1654832740634-933.png]]
329	329
330	330
331		-== 2.6  Frequency Plans ==
332	332
333	333	(((
334		-The LDDS75 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
	367	+(% style="color:blue" %)**Step 5**(%%)**: add payload decode**
335	335	)))
336	336
	370	+(((
	371	+
	372	+)))
337	337
	374	+[[image:1654833065139-942.png]]
338	338
	376	+
	377	+
	378	+[[image:1654833092678-390.png]]
	379	+
	380	+
	381	+
	382	+After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
	383	+
	384	+[[image:1654833163048-332.png]]
	385	+
	386	+
	387	+
	388	+== 2.6  Frequency Plans ==
	389	+
	390	+(((
	391	+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.
	392	+)))
	393	+
	394	+
339	339	=== 2.6.1  EU863-870 (EU868) ===
340	340
341	341	(((
...	...	@@ -399,51 +399,20 @@
399	399	=== 2.6.2  US902-928(US915) ===
400	400
401	401	(((
402		-Used in USA, Canada and South America. Default use CHE=2
	458	+Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	459	+)))
403	403
404		-(% style="color:blue" %)**Uplink:**
	461	+(((
	462	+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.
	463	+)))
405	405
406		-903.9 - SF7BW125 to SF10BW125
407		-
408		-904.1 - SF7BW125 to SF10BW125
409		-
410		-904.3 - SF7BW125 to SF10BW125
411		-
412		-904.5 - SF7BW125 to SF10BW125
413		-
414		-904.7 - SF7BW125 to SF10BW125
415		-
416		-904.9 - SF7BW125 to SF10BW125
417		-
418		-905.1 - SF7BW125 to SF10BW125
419		-
420		-905.3 - SF7BW125 to SF10BW125
421		-
422		-
423		-(% style="color:blue" %)**Downlink:**
424		-
425		-923.3 - SF7BW500 to SF12BW500
426		-
427		-923.9 - SF7BW500 to SF12BW500
428		-
429		-924.5 - SF7BW500 to SF12BW500
430		-
431		-925.1 - SF7BW500 to SF12BW500
432		-
433		-925.7 - SF7BW500 to SF12BW500
434		-
435		-926.3 - SF7BW500 to SF12BW500
436		-
437		-926.9 - SF7BW500 to SF12BW500
438		-
439		-927.5 - SF7BW500 to SF12BW500
440		-
441		-923.3 - SF12BW500(RX2 downlink only)
442		-
443		-
444		-
	465	+(((
	466	+After Join success, the end node will switch to the correct sub band by:
445	445	)))
446	446
	469	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	470	+* 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)
	471	+
447	447	=== 2.6.3  CN470-510 (CN470) ===
448	448
449	449	(((
...	...	@@ -532,54 +532,28 @@
532	532
533	533
534	534
	560	+
535	535	=== 2.6.4  AU915-928(AU915) ===
536	536
537	537	(((
538		-Default use CHE=2
	564	+Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
	565	+)))
539	539
540		-(% style="color:blue" %)**Uplink:**
	567	+(((
	568	+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.
	569	+)))
541	541
542		-916.8 - SF7BW125 to SF12BW125
543		-
544		-917.0 - SF7BW125 to SF12BW125
545		-
546		-917.2 - SF7BW125 to SF12BW125
547		-
548		-917.4 - SF7BW125 to SF12BW125
549		-
550		-917.6 - SF7BW125 to SF12BW125
551		-
552		-917.8 - SF7BW125 to SF12BW125
553		-
554		-918.0 - SF7BW125 to SF12BW125
555		-
556		-918.2 - SF7BW125 to SF12BW125
557		-
558		-
559		-(% style="color:blue" %)**Downlink:**
560		-
561		-923.3 - SF7BW500 to SF12BW500
562		-
563		-923.9 - SF7BW500 to SF12BW500
564		-
565		-924.5 - SF7BW500 to SF12BW500
566		-
567		-925.1 - SF7BW500 to SF12BW500
568		-
569		-925.7 - SF7BW500 to SF12BW500
570		-
571		-926.3 - SF7BW500 to SF12BW500
572		-
573		-926.9 - SF7BW500 to SF12BW500
574		-
575		-927.5 - SF7BW500 to SF12BW500
576		-
577		-923.3 - SF12BW500(RX2 downlink only)
578		-
579		-
	571	+(((
580	580
581	581	)))
582	582
	575	+(((
	576	+After Join success, the end node will switch to the correct sub band by:
	577	+)))
	578	+
	579	+* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	580	+* 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)
	581	+
583	583	=== 2.6.5  AS920-923 & AS923-925 (AS923) ===
584	584
585	585	(((
...	...	@@ -688,6 +688,7 @@
688	688
689	689
690	690
	690	+
691	691	=== 2.6.6  KR920-923 (KR920) ===
692	692
693	693	(((
...	...	@@ -760,6 +760,7 @@
760	760
761	761
762	762
	763	+
763	763	=== 2.6.7  IN865-867 (IN865) ===
764	764
765	765	(((
...	...	@@ -796,20 +796,18 @@
796	796
797	797
798	798
	800	+
799	799	== 2.7  LED Indicator ==
800	800
801		-The LDDS75 has an internal LED which is to show the status of different state.
	803	+The LLDS12 has an internal LED which is to show the status of different state.
802	802
803		-
804		-* Blink once when device power on.
805		-* The device detects the sensor and flashes 5 times.
806		-* Solid ON for 5 seconds once device successful Join the network.
	805	+* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
807	807	* Blink once when device transmit a packet.
808	808
809	809	== 2.8  ​Firmware Change Log ==
810	810
811	811
812		-**Firmware download link: **[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
	811	+**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/]]
813	813
814	814
815	815	**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
...	...	@@ -816,58 +816,71 @@
816	816
817	817
818	818
819		-== 2.9  Mechanical ==
	818	+= 3.  LiDAR ToF Measurement =
820	820
	820	+== 3.1 Principle of Distance Measurement ==
821	821
822		-[[image:image-20220610172003-1.png]]
	822	+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.
823	823
824		-[[image:image-20220610172003-2.png]]
	824	+[[image:1654831757579-263.png]]
825	825
826	826
827		-== 2.10  Battery Analysis ==
828	828
829		-=== 2.10.1  Battery Type ===
	828	+== 3.2 Distance Measurement Characteristics ==
830	830
831		-The LDDS75 battery is a combination of a 4000mAh or 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
	830	+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:
832	832
	832	+[[image:1654831774373-275.png]]
833	833
834		-The battery related documents as below:
835	835
836		-* (((
837		-[[ Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
	835	+(((
	836	+(% style="color:blue" %)**① **(%%)Represents the detection blind zone of The LiDAR probe, 0-10cm, within which the output data is unreliable.
838	838	)))
839		-* (((
840		-[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
	838	+
	839	+(((
	840	+(% style="color:blue" %)**② **(%%)Represents the operating range of The LiDAR probe detecting black target with 10% reflectivity, 0.1-5m.
841	841	)))
842		-* (((
843		-[[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]]
	842	+
	843	+(((
	844	+(% style="color:blue" %)**③ **(%%)Represents the operating range of The LiDAR probe detecting white target with 90% reflectivity, 0.1-12m.
844	844	)))
845	845
846		- [[image:image-20220610172400-3.png]]
847	847
	848	+(((
	849	+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:
	850	+)))
848	848
849	849
850		-=== 2.10.2  Replace the battery ===
	853	+[[image:1654831797521-720.png]]
851	851
852		-(((
853		-You can change the battery in the LDDS75.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
854		-)))
855	855
856	856	(((
857		-
	857	+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.
858	858	)))
859	859
	860	+[[image:1654831810009-716.png]]
	861	+
	862	+
860	860	(((
861		-The default battery pack of LDDS75 includes a ER18505 plus super capacitor. If user can’t find this pack locally, they can find ER18505 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
	864	+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.
862	862	)))
863	863
864	864
865	865
866		-= 3.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
	869	+== 3.3 Notice of usage: ==
867	867
	871	+Possible invalid /wrong reading for LiDAR ToF tech:
	872	+
	873	+* Measure high reflectivity object such as: Mirror, Smooth ceramic tile, static milk surface, will have possible wrong readings.
	874	+* While there is transparent object such as glass, water drop between the measured object and the LiDAR sensor, the reading might wrong.
	875	+* The LiDAR probe is cover by dirty things; the reading might be wrong. In this case, need to clean the probe.
	876	+* The sensor window is made by Acrylic. Don’t touch it with alcohol material. This will destroy the sensor window.
	877	+
	878	+= 4.  Configure LLDS12 via AT Command or LoRaWAN Downlink =
	879	+
868	868	(((
869	869	(((
870		-Use can configure LDDS75 via AT Command or LoRaWAN Downlink.
	882	+Use can configure LLDS12 via AT Command or LoRaWAN Downlink.
871	871	)))
872	872	)))
873	873
...	...	@@ -888,7 +888,7 @@
888	888	)))
889	889
890	890	(((
891		-There are two kinds of commands to configure LDDS75, they are:
	903	+There are two kinds of commands to configure LLDS12, they are:
892	892	)))
893	893	)))
894	894
...	...	@@ -929,84 +929,156 @@
929	929
930	930	* (((
931	931	(((
932		-(% style="color:#4f81bd" %)** Commands special design for LDDS75**
	944	+(% style="color:#4f81bd" %)** Commands special design for LLDS12**
933	933	)))
934	934	)))
935	935
936	936	(((
937	937	(((
938		-These commands only valid for LDDS75, as below:
	950	+These commands only valid for LLDS12, as below:
939	939	)))
940	940	)))
941	941
942	942
943	943
944		-== 3.1  Access AT Commands ==
	956	+== 4.1  Set Transmit Interval Time ==
945	945
946		-LDDS75 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LDDS75 for using AT command, as below.
	958	+Feature: Change LoRaWAN End Node Transmit Interval.
947	947
948		-[[image:image-20220610172924-4.png||height="483" width="988"]]
	960	+(% style="color:#037691" %)**AT Command: AT+TDC**
949	949
	962	+[[image:image-20220607171554-8.png]]
950	950
951		-Or if you have below board, use below connection:
952	952
	965	+(((
	966	+(% style="color:#037691" %)**Downlink Command: 0x01**
	967	+)))
953	953
954		-[[image:image-20220610172924-5.png]]
	969	+(((
	970	+Format: Command Code (0x01) followed by 3 bytes time value.
	971	+)))
955	955
	973	+(((
	974	+If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
	975	+)))
956	956
957		-In the PC, you need to set the serial baud rate to (% style="color:green" %)**9600**(%%) to access the serial console for LDDS75. LDDS75 will output system info once power on as below:
	977	+* (((
	978	+Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	979	+)))
	980	+* (((
	981	+Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	982	+)))
958	958
	984	+== 4.2  Set Interrupt Mode ==
959	959
960		- [[image:image-20220610172924-6.png||height="601" width="860"]]
	986	+Feature, Set Interrupt mode for GPIO_EXIT.
961	961
	988	+(% style="color:#037691" %)**AT Command: AT+INTMOD**
962	962
	990	+[[image:image-20220610105806-2.png]]
963	963
964		-== 3.2  Set Transmit Interval Time ==
965	965
966		-Feature: Change LoRaWAN End Node Transmit Interval.
	993	+(((
	994	+(% style="color:#037691" %)**Downlink Command: 0x06**
	995	+)))
967	967
968		-(% style="color:#037691" %)**AT Command: AT+TDC**
969		-
970		-[[image:image-20220610173409-7.png]]
971		-
972		-
973	973	(((
974		-(% style="color:#037691" %)**Downlink Command: 0x01**
	998	+Format: Command Code (0x06) followed by 3 bytes.
975	975	)))
976	976
977	977	(((
978		-(((
979		-Format: Command Code (0x01) followed by 3 bytes time value.
	1002	+This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	1003	+)))
980	980
981		-If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
982		-
983		-* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
984		-* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	1005	+* (((
	1006	+Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
985	985	)))
	1008	+* (((
	1009	+Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	1010	+)))
986	986
	1012	+== 4.3  Get Firmware Version Info ==
987	987
988		-
	1014	+Feature: use downlink to get firmware version.
	1015	+
	1016	+(% style="color:#037691" %)**Downlink Command: 0x26**
	1017	+
	1018	+[[image:image-20220607171917-10.png]]
	1019	+
	1020	+* Reply to the confirmation package: 26 01
	1021	+* Reply to non-confirmed packet: 26 00
	1022	+
	1023	+Device will send an uplink after got this downlink command. With below payload:
	1024	+
	1025	+Configures info payload:
	1026	+
	1027	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
	1028	+|=(((
	1029	+**Size(bytes)**
	1030	+)))|=**1**|=**1**|=**1**|=**1**|=**1**|=**5**|=**1**
	1031	+|**Value**|Software Type|(((
	1032	+Frequency
	1033	+
	1034	+Band
	1035	+)))|Sub-band|(((
	1036	+Firmware
	1037	+
	1038	+Version
	1039	+)))|Sensor Type|Reserve|(((
	1040	+[[Message Type>>||anchor="H2.3.7A0MessageType"]]
	1041	+Always 0x02
989	989	)))
990	990
991		-== 3.3  Set Interrupt Mode ==
	1044	+**Software Type**: Always 0x03 for LLDS12
992	992
993		-Feature, Set Interrupt mode for GPIO_EXIT.
994	994
995		-(% style="color:#037691" %)**Downlink Command: AT+INTMOD**
	1047	+**Frequency Band**:
996	996
997		-[[image:image-20220610105907-1.png]]
	1049	+*0x01: EU868
998	998
	1051	+*0x02: US915
999	999
1000		-(% style="color:#037691" %)**Downlink Command: 0x06**
	1053	+*0x03: IN865
1001	1001
1002		-Format: Command Code (0x06) followed by 3 bytes.
	1055	+*0x04: AU915
1003	1003
1004		-This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	1057	+*0x05: KZ865
1005	1005
1006		-* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
1007		-* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	1059	+*0x06: RU864
1008	1008
	1061	+*0x07: AS923
1009	1009
	1063	+*0x08: AS923-1
	1064	+
	1065	+*0x09: AS923-2
	1066	+
	1067	+*0xa0: AS923-3
	1068	+
	1069	+
	1070	+**Sub-Band**: value 0x00 ~~ 0x08
	1071	+
	1072	+
	1073	+**Firmware Version**: 0x0100, Means: v1.0.0 version
	1074	+
	1075	+
	1076	+**Sensor Type**:
	1077	+
	1078	+0x01: LSE01
	1079	+
	1080	+0x02: LDDS75
	1081	+
	1082	+0x03: LDDS20
	1083	+
	1084	+0x04: LLMS01
	1085	+
	1086	+0x05: LSPH01
	1087	+
	1088	+0x06: LSNPK01
	1089	+
	1090	+0x07: LLDS12
	1091	+
	1092	+
	1093	+
1010	1010	= 5.  Battery & How to replace =
1011	1011
1012	1012	== 5.1  Battery Type ==
...	...	@@ -1196,6 +1196,7 @@
1196	1196	* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1197	1197	* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1198	1198
	1283	+
1199	1199	= 10. ​ Packing Info =
1200	1200
1201	1201
...	...	@@ -1210,6 +1210,7 @@
1210	1210	* Package Size / pcs : cm
1211	1211	* Weight / pcs : g
1212	1212
	1298	+
1213	1213	= 11.  ​Support =
1214	1214
1215	1215	* 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.

1654848616367-242.png

Author

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

Size

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

Content

1654849068701-275.png

Author

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

Size

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

Content

1654850511545-399.png

Author

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

Size

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

Content

1654850829385-439.png

Author

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

Size

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

Content

1654851029373-510.png

Author

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

Size

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

Content

1654852175653-550.png

Author

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

Size

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

Content

1654852253176-749.png

Author

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

Size

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

Content

image-20220610161353-4.png

Author

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

Size

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

Content

image-20220610161353-5.png

Author

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

Size

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

Content

image-20220610161353-6.png

Author

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

Size

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

Content

image-20220610161353-7.png

Author

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

Size

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

Content

image-20220610161538-8.png

Author

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

Size

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

Content

image-20220610161538-9.png

Author

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

Size

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

Content

image-20220610161724-10.png

Author

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

Size

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

Content

image-20220610165129-11.png

Author

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

Size

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

Content

image-20220610172003-1.png

Author

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

Size

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

Content

image-20220610172003-2.png

Author

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

Size

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

Content

image-20220610172400-3.png

Author

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

Size

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

Content

image-20220610172924-4.png

Author

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

Size

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

Content

image-20220610172924-5.png

Author

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

Size

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

Content

image-20220610172924-6.png

Author

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

Size

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

Content

image-20220610173409-7.png

Author

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

Size

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

Content