Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 9 removed)
  • 1654848616367-242.png
  • 1654849068701-275.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

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 ===
...	...	@@ -93,6 +93,7 @@
93	93	* Bottom water level monitoring
94	94
95	95
	97	+
96	96	== 1.6  Pin mapping and power on ==
97	97
98	98
...	...	@@ -104,11 +104,11 @@
104	104	== 2.1  How it works ==
105	105
106	106	(((
107		-The LDDS75 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LDDS75. If there is coverage of the LoRaWAN network, it will automatically join the network via OTAA and start to send the sensor value
	109	+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.
108	108	)))
109	109
110	110	(((
111		-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 LLDS12.
112	112	)))
113	113
114	114
...	...	@@ -119,7 +119,7 @@
119	119	)))
120	120
121	121	(((
122		-[[image:1654848616367-242.png]]
	124	+[[image:1654827857527-556.png]]
123	123	)))
124	124
125	125	(((
...	...	@@ -127,57 +127,57 @@
127	127	)))
128	128
129	129	(((
130		-(% 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.
131	131	)))
132	132
133	133	(((
134		-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:
135	135	)))
136	136
137	137	[[image:image-20220607170145-1.jpeg]]
138	138
139	139
140		-For OTAA registration, we need to set **APP EUI/ APP KEY/ DEV EUI**. Some server might no need to set APP EUI.
141	141
142		-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:
143	143
144		-**Add APP EUI in the application**
145	145
146		-[[image:image-20220610161353-4.png]]
	146	+**Register the device**
147	147
148		-[[image:image-20220610161353-5.png]]
149	149
150		-[[image:image-20220610161353-6.png]]
	149	+[[image:1654592600093-601.png]]
151	151
152	152
153		-[[image:image-20220610161353-7.png]]
154	154
	153	+**Add APP EUI and DEV EUI**
155	155
156		-You can also choose to create the device manually.
	155	+[[image:1654592619856-881.png]]
157	157
158		- [[image:image-20220610161538-8.png]]
159	159
160	160
	159	+**Add APP EUI in the application**
161	161
162		-**Add APP KEY and DEV EUI**
	161	+[[image:1654592632656-512.png]]
163	163
164		-[[image:image-20220610161538-9.png]]
165	165
166	166
	165	+**Add APP KEY**
167	167
168		-(% style="color:blue" %)**Step 2**(%%): Power on LDDS75
	167	+[[image:1654592653453-934.png]]
169	169
170	170
	170	+(% style="color:blue" %)**Step 2**(%%): Power on LLDS12
	171	+
	172	+
171	171	Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
172	172
173		-[[image:image-20220610161724-10.png]]
	175	+[[image:image-20220607170442-2.png]]
174	174
175	175
176	176	(((
177		-(% 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.
178	178	)))
179	179
180		-[[image:1654849068701-275.png]]
	182	+[[image:1654833501679-968.png]]
181	181
182	182
183	183
...	...	@@ -184,10 +184,11 @@
184	184	== 2.3  ​Uplink Payload ==
185	185
186	186	(((
187		-LDDS75 will uplink payload via LoRaWAN with below payload format:
	189	+LLDS12 will uplink payload via LoRaWAN with below payload format:
	190	+)))
188	188
189		-Uplink payload includes in total 4 bytes.
190		-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.
191	191	)))
192	192
193	193	(((
...	...	@@ -197,15 +197,15 @@
197	197	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
198	198	|=(% style="width: 62.5px;" %)(((
199	199	**Size (bytes)**
200		-)))|=(% style="width: 62.5px;" %)**2**|=**2**|=1|=2|=**1**
201		-|(% style="width:62.5px" %)**Value**|(% style="width:62.5px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(((
202		-[[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	+)))
203	203
204		-(unit: mm)
205		-)))|[[Digital Interrupt (Optional)>>||anchor="H2.3.4A0Distancesignalstrength"]]|(((
206		-[[Temperature (Optional )>>||anchor="H2.3.5A0InterruptPin"]]
207		-)))|[[Sensor Flag>>path:#Sensor_Flag]]
208		-
209	209	[[image:1654833689380-972.png]]
210	210
211	211
...	...	@@ -213,7 +213,7 @@
213	213	=== 2.3.1  Battery Info ===
214	214
215	215
216		-Check the battery voltage for LDDS75.
	219	+Check the battery voltage for LLDS12.
217	217
218	218	Ex1: 0x0B45 = 2885mV
219	219
...	...	@@ -221,23 +221,49 @@
221	221
222	222
223	223
224		-=== 2.3.2  Distance ===
	227	+=== 2.3.2  DS18B20 Temperature sensor ===
225	225
226		-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.
227	227
228		-For example, if the data you get from the register is 0x0B 0x05, the distance between the sensor and the measured object is
229	229
230		-**0B05(H) = 2821 (D) = 2821 mm.**
	232	+**Example**:
231	231
	234	+If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
232	232
233		-* If the sensor value is 0x0000, it means system doesn’t detect ultrasonic sensor.
234		-* 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.
	236	+If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
235	235
236	236
237		-=== 2.3.3  Interrupt Pin ===
238	238
	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	+
239	239	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.
240	240
	268	+Note: The Internet Pin is a separate pin in the screw terminal. See [[pin mapping>>||anchor="H1.6A0Pinmappingandpoweron"]].
	269	+
241	241	**Example:**
242	242
243	243	0x00: Normal uplink packet.
...	...	@@ -245,28 +245,35 @@
245	245	0x01: Interrupt Uplink Packet.
246	246
247	247
248		-=== 2.3.4  DS18B20 Temperature sensor ===
249	249
250		-This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
	278	+=== 2.3.6  LiDAR temp ===
251	251
252		-**Example**:
	280	+Characterize the internal temperature value of the sensor.
253	253
254		-If payload is: 0105H:  (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
	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℃.
255	255
256		-If payload is: FF3FH :  (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
257	257
258		-Note: DS18B20 feature is supported in the hardware version > v1.3 which made since early of 2021.
259	259
260		-=== 2.3.5  Sensor Flag ===
	288	+=== 2.3.7  Message Type ===
261	261
262		-0x01: Detect Ultrasonic Sensor
	290	+(((
	291	+For a normal uplink payload, the message type is always 0x01.
	292	+)))
263	263
264		-0x00: No Ultrasonic Sensor
	294	+(((
	295	+Valid Message Type:
	296	+)))
265	265
266	266
267		-===
268		-(% style="color:inherit; font-family:inherit" %)2.3.6  Decode payload in The Things Network(%%) ===
	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
	304	+=== 2.3.8  Decode payload in The Things Network ===
	305	+
270	270	While using TTN network, you can add the payload format to decode the payload.
271	271
272	272
...	...	@@ -1244,6 +1244,7 @@
1244	1244	* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1245	1245	* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1246	1246
	1283	+
1247	1247	= 10. ​ Packing Info =
1248	1248
1249	1249
...	...	@@ -1258,6 +1258,7 @@
1258	1258	* Package Size / pcs : cm
1259	1259	* Weight / pcs : g
1260	1260
	1298	+
1261	1261	= 11.  ​Support =
1262	1262
1263	1263	* 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

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