Version 119.1 by Mengting Qiu on 2025/02/11 11:56
Show last authors
1
2
3 (% style="text-align:center" %)
4 [[image:1654679359875-169.png]]
5
6
7
8
9
10
11
12
13
14 **Table of Contents:**
15
16 {{toc/}}
17
18
19
20
21
22
23
24
25 = 1. Introduction =
26
27 == 1.1 What is the LDS02 LoRaWAN Door Sensor? ==
28
29
30 (((
31 (((
32 The** Dragino LDS02 **is a **LoRaWAN Door Sensor** designed to detect door open/close status and send data to a LoRaWAN Network Server. Users can view the door status, open time, and open counts in an IoT platform by integrating it with the LoRaWAN Network Server.
33 )))
34
35 (((
36 The sensor is powered by **two AAA batteries**, making it suitable for long-term use. These batteries can provide approximately 16,000 to 70,000 uplink packets. When the batteries run out, users can easily open the enclosure and replace them with standard AAA batteries.
37
38 The device sends data periodically every day and for each door open/close action. It also **counts the number of door openings** and **calculates the duration of the last door opening**. Users can disable the uplink for each open/close event if preferred. In this mode, the device will count each event and upload the data periodically instead.
39
40 The LDS02 **features an open alarm**, which can be configured to send an alarm if the door remains open for a specified duration.
41
42 Each sensor comes with information (keys and identifiers) for LoRaWAN Network registration. Registering these keys with a LoRaWAN server allows the device to connect automatically upon powering on.
43
44
45 The following figure shows how the LDS02 is connected to a typical LoRaWAN network server.
46
47 [[image:LDS02-lorawan.jpg]]
48
49
50 )))
51 )))
52
53
54 == 1.2 Features ==
55
56
57 * LoRaWAN Class A v1.0.3
58 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
59 * Door Open/Close detect
60 * Door open/close statistics
61 * 2 x AAA LR03 Batteries
62 * AT Commands to change parameters
63 * Uplink on periodically and open/close action
64 * Remote configure parameters via LoRa Downlink
65 * Firmware upgradable via program port
66
67 == 1.3 Storage & Operation Temperature ==
68
69
70 -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on the battery type, see [[FAQ>>||anchor="H7.6Whyiseedifferentworkingtemperatureforthedevice3F"]])
71
72
73 == 1.4 Applications ==
74
75
76 * Smart Buildings & Home Automation
77 * Logistics and Supply Chain Management
78 * Smart Metering
79 * Smart Agriculture
80 * Smart Cities
81 * Smart Factory
82
83 == 1.5 Dimension ==
84
85
86 Units in mm
87
88 [[image:1654680563545-120.png]]
89
90
91 [[image:1654680510816-654.png]]
92
93
94 == 1.6 Firmware Change Log ==
95
96
97 (((
98 (((
99 LDS02 uses the same firmware as LDS01：[[LDS02 Image files – Download link>>https://www.dropbox.com/sh/9j35mnsxnz0y3ye/AACj5gHGOURGEHCpj-E861Mua?dl=0]]
100 )))
101 )))
102
103
104 = 2. Power ON LDS02 =
105
106
107 When receive the LDS02, open the enclosure and insert two AAA batteries to power it. The [[LED>>||anchor="H4.7LEDs"]] will blink when the device is powered on.
108
109
110 = 3. How to Install LDS02 =
111
112
113 The LDS02 has two parts: sensor and the magnet. These parts can be attached to a surface using either screws or double sided tapes.For example, if you install it to detect door open/close events, the sensor part can be attached to the door frame, and the magnet can be attached to the door panel.
114
115
116 Fixing with screws:
117
118 * Each part has a bottom lid that can be detached from its enclosure. Detach the bottom lids of both the sensor and the magnet enclosures. You will notice two holes on each bottom lid for inserting screws. First, attach the bottom lids to the surface using screws, ensuring a minimal gap between them. Then snap the top part of the enclosure onto the bottom. You will hear a clicking sound once they are securely fitted together.
119
120 [[image:image-20231222111730-1.jpeg||height="428" width="686"]]
121
122
123 Fixing with double-sided adhesive pads:
124
125 * The double-sided adhesive pad included with the LDS01 has a pre-cut section that can be attached to the bottom of the magnet enclosure (first remove the protective backing of one side only). The remaining section should be affixed to the bottom of the sensor enclosure. Once the tape is in place, remove the protective backing and secure both enclosures to the surface, ensuring a minimal gap between them.
126
127 [[image:image-20231222111834-2.jpeg||height="443" width="685"]]
128
129
130 (((
131 (((
132 When installing the LDS02, make sure to install it as shown below so that the marks align closely when the door is closed.
133 )))
134
135 (((
136 Open/Close threshold range (the minimum gap between sensor enclosure and the magnet enclosure): ~~ 10mm
137 )))
138 )))
139
140 [[image:1654680716522-793.png||height="505" width="497"]]
141
142
143 = 4. Operation Mode =
144
145 == 4.1 How It Works? ==
146
147
148 (((
149 The LDS02 is configured as a LoRaWAN Class A device by default. It contains a DevEUI, AppEUI, and AppKey, which allow it to join a LoRaWAN network using OTAA (Over-The-Air Activation). To connect the LDS02 to a LoRaWAN network, you need to configure these keys and identifiers with the LoRaWAN network server first, and then [[power on>>||anchor="H2.PowerONLDS02"]] the LDS02. The device will automatically join the network using OTAA. This device information can be found in your package, printed on a sticker.
150
151 [[image:image-20230426084924-1.png||height="229" width="493"]]
152
153 If you cannot set the device registration information, such as the DevEUI, AppEUI, and AppKey, in the network server, you must use the information generated by the network server, which differs from the information already stored on the device. In this case, you can use [[AT Command>>||anchor="H6.UseATCommand"]]s to write the new information to the device.
154 )))
155
156
157 == 4.2 Example of Joining a LoRaWAN Network ==
158
159
160 The following figure shows how the LDS02 connects to [[The Things Stack>>https://eu1.cloud.thethings.network/]]. The LDS02 sends messages (uplinks) to The Things Stack via a LoRaWAN gateway (e.g., Dragino LPS8N) and can also receive messages (downlinks) from The Things Stack. The Things Stack can be integrated with ThingsEye, allowing it to forward uplinks to ThingsEye. ThingsEye is an IoT platform used for visualizing and analyzing sensor data. You can also send downlinks from ThingsEye (via The Things Stack) to the LDS02.
161
162
163 [[image:LDS02-tts.jpg]]
164
165
166
167 === 4.2.1 Prerequisites: ===
168
169 (((
170 * The LDS02 is installed with the magnet on the door and the sensor part on the door frame to detect open/close events and send the status to the LoRaWAN server. The LDS02 will uplink two types of messages to the server:
171 ** A keep-alive message, which is sent once per day.
172 ** A door event message when a door is opened or closed ([[Alarm event can be disabled>>||anchor="H7.3CanIdisableuplinkforeacheventtosavebatterylife3F"]])
173 * The Things Stack community network coverage, or private LoRaWAN Network Coverage with any The Things Stack deployment plan.
174 )))
175
176
177 ==== 4.2.1.1 Setting up ====
178
179 * Sign up for a free account with [[The Things Stack Sandbox>>url:https://eu1.cloud.thethings.network]] if you do not have one yet.
180 * Log in to your **The Things Stack** account.
181 * Create an **application** with The Things Stack if you do not have one yet.
182 ** On the left navigation, click **Applications**.
183 ** Then click **+ Add Application** button.
184
185 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LWL02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/lwl02-4.png?rev=1.1||alt="lwl02-4.png"]]
186
187
188 * On the **Create Application **page, configure the following:
189 ** **Application ID**: Provide a unique identification for your application within The Things Stack.
190 ** **Application name**: (optional) Provide a descriptive name.
191 ** **Description**: (optional) Provide a description.
192 * Click on **Create application **button.
193
194 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LWL02%20-%20LoRaWAN%20Door%20Sensor%20User%20Manual/WebHome/lwl02-5.png?rev=1.1||alt="lwl02-5.png"]]
195
196
197
198 * Go to your application's page and click on the **End devices** in the left menu.
199 * On the End devices page, click on **+ Register end device**.
200
201 [[image:lds02-step-5.png]]
202
203 * Two registration options are available:
204 ** Using the LoRaWAN Device Repositoty
205 ** Manual registration
206
207 ==== 4.2.1.2 Using the LoRaWAN Device Repository ====
208
209 * On the **Register end device** page:
210 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
211 ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
212 *** **End device brand**: Dragino Technology Co., Limited
213 *** **Model**: LDS02 - Door Sensor
214 *** **Hardware ver**: Unknown
215 *** **Firmware ver**: 1.6
216 *** **Profile (Region)**: Select the region that matches your device.
217 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
218 ** Enter the **AppEUI** in the **JoinEUI** field and click the **Confirm** button. If The Things Stack accepts the JoinEUI you provided, it will display the message 'This end device can be registered on the network.
219
220 [[image:lds02-step-2.png]]
221
222
223
224 * In the **DevEUI** field, enter the **DevEUI**.
225 * In the **AppKey** field, enter the **AppKey.**
226 * In the **End device ID** field, enter a unique name for your LDS02 within this application.
227 * Under **After registration**, select the **View registered end device** option.
228 * Click **Register end device** button.
229
230 [[image:lds02-step-3.png]]
231
232
233 * You will be navigated to the Device overview page.
234
235 [[image:lds02-step-4.png]]
236
237
238 * Click on the Live Data tab and then **[[Power on>>||anchor="H2.PowerONLDS02"]]** the LDS02. It will first join The Things Stack network server. You can confirm this by looking for the Join-request and Join-accept messages. After successfully joining the network, the LDS02 will start sending uplink messages to The Things Stack, and you can see them in the Live Data panel.
239
240 [[image:1654681390551-993.png]]
241
242
243 == 4.3 Uplink Payload ==
244
245 === 4.3.1 Sensor value, Uplink via FPORT~=10 ===
246
247
248 The data is sent in the following cases:
249
250 * TDC (Transmit Time Interval—Keep Alive Interval), the default TDC is 24 hours, so this data is automatically sent every 24 hours.
251 * This data is sent each time the door is opened or closed, [[AT+DISALARM=0(default)>>||anchor="H7.3CanIdisableuplinksforeacheventtosavebatterylife3F
252 "]].
253
254 The uplink payload is a total of 10 bytes.
255
256 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:480px" %)
257 |=(% style="width: 80px;background-color:#4F81BD;color:white" %)**Size (bytes)**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**3**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**3**|=(% style="width: 80px;background-color:#4F81BD;color:white" %)**1**
258 |Value|Door State & BAT|(((
259 MOD
260 Always:0x01
261 )))|Total open door events|(((
262 Last door open
263 duration (unit: min)
264 )))|(((
265 [[Alarm>>||anchor="H4.6AlarmBaseonTimeout"]]
266
267 (Only used in LWL02) Always:0x00
268 )))
269
270 **Example:**
271
272 [[image:image-20250211113735-1.png||height="351" width="1090"]]
273
274
275 [[image:image-20250211113814-2.png]]
276
277 (((
278
279
280 This example uses the payload decoder in The Things Stack V3: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/LDS02>>https://github.com/dragino/dragino-end-node-decoder/tree/main/LDS02]]
281
282 (% style="color:blue" %)**Battery Info**
283
284 Check the battery voltage:
285
286 Example 1: 0x0B88&3FFF = 2952mV
287
288 Example 2: 0xD152&3FFF = 4434mV
289
290
291 (% class="wikigeneratedid" id="H4.3.2Status" %)
292 (% style="color:blue" %)**Status**
293
294 Check the door state:
295
296 **Example**:
297
298 If the payload is: **0B**:  (0000 1011&1000 0000== 0), **DOOR_OPEN_STATUS** is 0（**CLOSE**）
299
300 If the payload is: **D1**: (1101 0001&1000 0000== 1), **DOOR_OPEN_STATUS** is 1（**OPEN**）
301
302
303 (% style="color:blue" %)**MOD**
304
305 Check the working mode (MOD):
306
307 **Example:**
308
309 If the payload is: 01, the MOD is 1.
310
311
312 (% style="color:blue" %)**Total door open events**
313
314 Get the total number of door open events:
315
316 **Example**:
317
318 If payload is: **00 00 93, **the total is 147 events.
319
320 If payload is: **00 00 00, **the total is 0 events.
321
322
323 (% style="color:blue" %)**Last door open duration(unit:min)**
324
325 Get the last door open duration:
326
327 **Example:**
328
329 If the payload is: **00 00 25, **the last door open duration is 37 minutes.
330
331 If payload is: **00 00 01,** the last door open duration is 1 minute.
332
333
334 (% style="color:blue" %)**Alarm(Only used in LWL02) Always:0x00**
335
336 Get alarm status.
337
338 **Example:**
339
340 If the payload is: 01:  (0001 & 0001== 1), the alarm status is 1
341
342 If the payload is: 00:  (0000 & 0001== 0), the alarm status is 0
343
344
345 === 4.3.1 EDC mode value, Uplink via FPORT~=7 ===
346
347
348 When EDC is enabled, LDS02 will send this data.
349
350 The uplink payload is a total of 10 bytes.
351
352
353
354
355 )))
356
357 == 4.4 Downlink Payload ==
358
359
360 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:505px" %)
361 |=(% style="width: 182px;background-color:#4F81BD;color:white" %)**Downlink Control Type**|=(% style="width: 96px;background-color:#4F81BD;color:white" %)**Type Code**|=(% style="width: 227px;background-color:#4F81BD;color:white" %)**Downlink Payload Size (bytes)**
362 |(% style="width:180px" %)TDC (Transmit Time Interval—Keep Alive Interval)|(% style="width:94px" %)0x01|(% style="width:226px" %)4
363 |(% style="width:180px" %)RESET|(% style="width:94px" %)0x04|(% style="width:226px" %)2
364 |(% style="width:180px" %)[[Set confirmed mode>>||anchor="HTypeCode0x05"]]|(% style="width:94px" %)0x05|(% style="width:226px" %)2
365 |(% style="width:180px" %)[[Clear Counting>>||anchor="HTypeCode0xA6"]]|(% style="width:94px" %)0xA6|(% style="width:226px" %)2
366 |(% style="width:180px" %)[[Enable/Disable Alarm>>||anchor="HTypeCode0xA7"]]|(% style="width:94px" %)0xA7|(% style="width:226px" %)2
367 |(% style="width:180px" %)[[Control ADR/DR>>||anchor="HTypeCode0xA8"]]|(% style="width:94px" %)0xA8|(% style="width:226px" %)3
368 |(% style="width:180px" %)[[Set Alarm Timeout>>||anchor="HTypeCode0xA9"]]|(% style="width:94px" %)0xA9|(% style="width:226px" %)4
369
370 The following image illustrates how to send a downlink payload from The Things Stack.
371
372 [[image:1654673412319-976.png]]
373
374
375 === (% style="color:#037691" %)**Type Code 0x01**(%%) ===
376
377 If the payload is **0100003C**, it means controlling the LDS02’s Keep Alive interval to **0x00003C = 60 seconds (s)**.
378
379
380 === (% style="color:#037691" %)**Type Code 0x04**(%%) ===
381
382 If the payload is **0x04FF**, it will reset the LDS02.
383
384
385 === (% style="color:#037691" %)**Type Code 0x05**(%%) ===
386
387 (((
388 **0x05 00**: Set uplink to LoRaWAN unconfirmed mode
389 )))
390
391 (((
392 **0x05 01**: Set uplink to LoRaWAN confirmed mode
393 )))
394
395
396 === (% style="color:#037691" %)**Type Code 0xA6**(%%) ===
397
398 (((
399 **Example:** 0xA601 – Clear Counting
400 For the LDS02: Resets both the count number and time.
401 )))
402
403
404 === (% style="color:#037691" %)**Type Code 0xA7**(%%) ===
405
406 (((
407 **0xA701**: Equivalent to AT+DISALARM=1
408 )))
409
410 (((
411 **0xA700**: Equivalent to AT+DISALARM=0
412 )))
413
414
415 === (% style="color:#037691" %)**Type Code 0xA8**(%%) ===
416
417 (((
418 **Format:** 0xA8 aa bb
419
420 * **aa**: 1 – Enable ADR; 0 – Disable ADR (same as the AT+CADR command)
421 * **bb**: Set DR (same as AT+CDATARATE; only valid after ADR=0)
422
423 **Example:** 0xA80001 – Set ADR=0 and DR=1
424 )))
425
426
427 === (% style="color:#037691" %)**Type Code 0xA9**(%%) ===
428
429 See, [[Alarm Base Timeout>>||anchor="H4.6AlarmBaseonTimeout"]] for details.
430
431
432 == 4.5 Integrate with IoT Platforms ==
433
434
435 The Things Stack can be integrated with many IoT platforms, including ThingsEye and Datacake, for visualizing and analyzing data coming from the LDS02. Most of these IoT platforms also support sending downlinks to the LDS02.
436
437 === 4.5.1 Integrate with ThingsEye ===
438
439
440 The Things Stack application supports integration with ThingsEye.io. Once integrated, ThingsEye.io acts as an MQTT client for The Things Stack MQTT broker, allowing it to subscribe to upstream traffic and publish downlink traffic.
441
442
443 ==== 4.5.1.1 Configuring The Things Stack ====
444
445 We use The Things Stack Sandbox in this example:
446
447 * In **The Things Stack Sandbox**, go to the **Application **for the LDS02 you added.
448 * Select **MQTT** under **Integrations** in the left menu.
449 * In the **Connection information **section, under **Connection credentials**, The Things Stack displays an auto-generated **username**. You can use it or provide a new one.
450 * Click the **Generate new API key** button to generate a password. You can view it by clicking on the **visibility toggle/eye** icon. The API key works as the password.
451
452 {{info}}
453 The username and  password (API key) you created here are required in the next section.
454 {{/info}}
455
456
457 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/tts-mqtt-integration.png?rev=1.1||alt="tts-mqtt-integration.png"]]
458
459
460 ==== 4.5.1.2 Configuring ThingsEye.io ====
461
462 The ThingsEye.io IoT platform is not open for self-registration at the moment. If you are interested in testing the platform, please send your project information to admin@thingseye.io, and we will create an account for you.
463
464 * Login to your [[ThingsEye.io >>url:https://thingseye.io]]account.
465 * Under the **Integrations center**, click **Integrations**.
466 * Click the **Add integration** button (the button with the **+** symbol).
467
468 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/thingseye-io-step-1.png?rev=1.2||alt="thingseye-io-step-1.png"]]
469
470
471 On the **Add integration** window, configure the following:
472
473 **Basic settings:**
474
475 * Select **The Things Stack Community** from the **Integration type** list.
476 * Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
477 * Ensure the following options are turned on.
478 ** Enable integration
479 ** Debug mode
480 ** Allow creating devices or assets
481 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
482
483 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/thingseye-io-step-2.png?rev=1.1||alt="thingseye-io-step-2.png"]]
484
485
486 **Uplink data converter:**
487
488 * Click the **Create new** button if it is not selected by default.
489 * Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
490 * Click the **JavaScript** button.
491 * Paste the uplink decoder function into the text area (first, delete the default code). The demo uplink decoder function can be found [[here>>url:https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Uplink_Converter.js]].
492 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
493
494 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/thingseye-io-step-3.png?rev=1.1||alt="thingseye-io-step-3.png"]]
495
496
497 **Downlink data converter (this is an optional step):**
498
499 * Click the **Create new** button if it is not selected by default.
500 * Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name.
501 * Click the **JavaScript** button.
502 * Paste the downlink decoder function into the text area (first, delete the default code). The demo downlink decoder function can be found [[here>>url:https://raw.githubusercontent.com/ThingsEye-io/te-platform/refs/heads/main/Data%20Converters/The_Things_Network_MQTT_Downlink_Converter.js]].
503 * Click the **Next** button. You will be navigated to the **Connection** tab.
504
505 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/thingseye-io-step-4.png?rev=1.1||alt="thingseye-io-step-4.png"]]
506
507
508 **Connection:**
509
510 * Choose **Region** from the **Host type**.
511 * Enter the **cluster** of your **The Things Stack** in the **Region** textbox. You can find the cluster in the url (e.g., https:~/~/**eu1**.cloud.thethings.network/...).
512 * Enter the **Username** and **Password** of the MQTT integration in the **Credentials** section. The **username **and **password **can be found on the MQTT integration page of your The Things Stack account (see **4.5.1.1 Configuring The Things Stack**).
513 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
514
515 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/message-1.png?rev=1.1||alt="message-1.png"]]
516
517
518 * Click the **Add** button.
519
520 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/thingseye-io-step-5.png?rev=1.1||alt="thingseye-io-step-5.png"]]
521
522
523 Your integration has been added to the** Integrations** list and will be displayed on the **Integrations** page. Check whether the status is shown as **Active**. If not, review your configuration settings and correct any errors.
524
525
526 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/thingseye.io_integrationsCenter_integrations.png?rev=1.2||alt="thingseye.io_integrationsCenter_integrations.png"]]
527
528
529 ==== 4.5.1.3 Viewing integration details ====
530
531
532 Click on your integration from the list. The **Integration details** window will appear with the **Details **tab selected. The **Details **tab shows all the settings you have provided for this integration.
533
534
535 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/integration-details.png?rev=1.1||alt="integration-details.png"]]
536
537
538 If you want to edit the settings you have provided, click on the **Toggle edit mode** button. Once you have done click on the **Apply changes **button.
539
540 {{info}}
541 See also [[ThingsEye documentation>>url:https://wiki.thingseye.io/xwiki/bin/view/Main/]].
542 {{/info}}
543
544
545 ==== 4.5.1.4 Viewing events ====
546
547
548 The **Events **tab displays all the uplink messages from the LDS02.
549
550 * Select **Debug **from the **Event type** dropdown.
551 * Select the** time frame** from the **time window**.
552
553 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LT-22222-L/WebHome/thingseye-events.png?rev=1.1||alt="thingseye-events.png"]]
554
555
556 * To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
557
558 [[image:lds02-thingseye-payload.png]]
559
560
561 ==== 4.5.1.5 Deleting an integration ====
562
563
564 If you want to delete an integration, click the **Delete integration** button on the Integrations page.
565
566
567 ==== 4.5.1.6 Viewing sensor data on a dashboard ====
568
569
570 You can create a dashboard with ThingsEye to visualize the sensor data coming from the LDS02. The following image shows a dashboard created for the LDS02. See **Creating a dashboard** in ThingsEye documentation for more information.
571
572
573 [[image:lds02-thingseye-dashboard.png]]
574
575
576
577
578 === 4.5.2 Integrate with Datacake ===
579
580
581 (((
582 Datacake is a multi-purpose, low-code IoT platform that allows you to integrate sensor data for visualization and analysis. With The Things Stack, you can easily create an integration with Datacake to forward your sensor data to the Datacake IoT platform.
583
584
585 ==== 4.5.2.1 Prerequisites ====
586
587 * The LDS02 device is joined to The Things Stack.
588 * Uplinks from the LDS02 device are being received by The Things Stack.
589 * A Datacake account (a free account is sufficient for this example).
590
591 ==== 4.5.2.2 Procedure ====
592
593
594 * In the Datacake workspace, on the left navigation, click **Account Settings**.
595 * Then click **API Token**.
596 * In the **API Token** tab, click the **Copy** button to copy the API token. You will need this API token when creating a webhook with The Things Stack.
597
598 [[image:datacake-1.png]]
599
600
601 )))
602
603 (((
604 To configure the Application to forward data to Datacake you will need to add integration. To add the Datacake integration, perform the following steps:
605
606 * In The Things Stack console, on the left navigation,
607 ** First select your **application** (**Applications -> <your application>**)
608 ** Then select **Integrations -> Webhooks**
609 * On the **Webhooks** page, click + **Add Webhook** button.
610
611 [[image:tts-webhook-1.png]]
612
613
614 * On the **Choose webhook template** page, select **Datacake**.
615 )))
616
617
618
619 [[image:tts-webhook-2.png]]
620
621
622 * On the Setup webhook for Datacake page,
623 ** **Webhook ID**: provide an unique identifier for this webhook
624 ** **Token**: Paste the **Datacake API Token** when you copied from the Datacake **Account Settings**.
625 * Click on the **Create Datacake webhook** button.
626
627 [[image:tts-webhook-3.png]]
628
629
630 Now the Webhook is created and displayed on the Webhooks page.
631
632 [[image:tts-webhook-4.png]]
633
634
635 * In the Datacake workspace, on the left navigation, click **Devices**.
636 * On the Devices page, click **+Add Device**.
637
638 [[image:datacake-2.png]]
639
640
641 * On the **Add Device** window, click **LoRaWAN** option.
642 * Click on the **Next** button.
643
644 [[image:datacake-3.png]]
645
646
647 * On the **Add LoRaWAN Device** window, **STEP 1**, click on **New Product from template** option.
648 * Under **Device Template**, search **lds02**. Then click on **Dragino LDS02 Door Sensor** option.
649 * Click on the **Next** button.
650
651 [[image:datacake-4.png]]
652
653
654
655
656 * On the **Add LoRaWAN Device** window, **STEP 2**, under **Network Server**, click on **The Things Stack V3** option.
657 * Click on the **Next** button.
658
659 [[image:datacake-5.png]]
660
661
662 * On the **Add LoRaWAN Device** window, **STEP 3**, under **Add Devices**, click **Manual** tab.
663 * In the **DEVEUI** textbox, enter your LDS02's 8 bytes **DevEUI**.
664 * In the **NAME** textbox, enter a suitable name to identify your LDS02.
665 * Click on the **Next** button.
666
667 [[image:datacake-6.png]]
668
669
670 * On the **Add LoRaWAN Device** window, **STEP 4**, select **Individual device plans** tab.
671 * Click **Free** option.
672 * Click on the **Add 1 Device** button.
673
674 [[image:datacake-7.png]]
675
676
677 * The device is now added to the Datacake workspace and is ready to receive uplinks from the LDS02 via The Things Stack.
678 * In the **DEVICE** column, click **lds02**.
679
680 [[image:datacake-8.png]]
681
682
683 You can see the **pre-built dashboard** from our template, displaying the LDS02's sensor data on various **widgets**.
684
685 [[image:datacake-9.png]]
686
687
688 == 4.6 Alarm Based on Timeout ==
689
690
691 (((
692 The LDS02 can monitor the timeout for a status change. This feature can be used to monitor events such as a fridge being left open for too long, etc. You can configure this feature using either AT commands or a downlink command:
693 )))
694
695 (((
696 (% style="color:blue" %)**Using AT Commands**(%%)**:**
697 )))
698
699 (((
700
701
702 * **AT+TTRIG=1,30 ~-~-> **When the status changes from closed to open, and the device remains in the open status for more than 30 seconds, the LDS02 will send an uplink packet. The Alarm bit (the lowest bit of the 10th byte of the payload) in this uplink packet is set to 1.
703 * **AT+TTRIG=0,0 ~-~-> **Default value, disables the timeout alarm.
704 )))
705
706 (((
707 (% style="color:blue" %)**Using Downlink Commands**(%%)**:**
708 )))
709
710 (((
711 **Command:** 0xA9 aa bb cc
712
713 * **A9:** Command Type Code
714 * **aa:** Status to be monitored
715 * **bb cc:** Timeout
716
717 If the user sends **0xA9 01 00 1E**, this is equivalent to **AT+TTRIG=1,30**.
718
719 Or
720
721 **0xA9 00 00 00**, this is equivalent to **AT+TTRIG=0,0**, which disables the timeout alarm.
722 )))
723
724
725 == 4.7 EDC Mode(Since firmware v1.8.2) ==
726
727
728 Feature: Set EDC mode, when the cumulative number of opening/closing reaches the set count value, LDS02 will send the packet.
729
730 (% style="color:blue" %)**AT Command: AT+EDC**
731
732
733 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
734 |=(% style="width: 126px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 196px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 176px; background-color: rgb(79, 129, 189); color: white;" %)**Response/Parameters**
735 |(% style="width:126px" %)AT+EDC?|(% style="width:196px" %)Show current Settings|(% style="width:176px" %)(((
736 0,0 (default)
737
738 OK
739 )))
740 |(% colspan="1" rowspan="2" style="width:126px" %)(((
741
742
743
744
745 AT+EDC=aa,bb
746 )))|(% style="width:196px" %)aa: Set the open/close cumulative packet sending mode|(% style="width:176px" %)(((
747 0: Set the close cumulative packet sending mode
748
749 1: Set the open cumulative packet sending mode
750 )))
751 |(% style="width:196px" %)bb: Set the cumulative count and send packets when the cumulative count is reached|(% style="width:176px" %)
752
753 (% style="color:blue" %)**Downlink Command: 0X02**
754
755 Format: Command Code (0x02) followed by 4 bytes.
756
757 (% style="color:red" %)**Note: To use the EDC mode, you need to set [[AT+DISALARM=1(downlink payload: A701)>>||anchor="H7.3CanIdisableuplinksforeacheventtosavebatterylife3F
758 "]], so that LDS02 will send packets only when the TDC time and cumulative count reach the set value.**
759
760
761 == 4.8 Set count value(Since firmware v1.8.2) ==
762
763
764 Feature: Set the initial count value.
765
766 (% style="color:blue" %)**AT Command: AT+SETCNT**
767
768
769 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
770 |=(% style="width: 154px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 170px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 173px; background-color: rgb(79, 129, 189); color: white;" %)**Response**
771 |(% style="width:154px" %)AT+SETCNT=100|(% style="width:170px" %)Initialize the count value to 100.|(% style="width:173px" %)(((
772 OK
773 )))
774
775 (% style="color:blue" %)**Downlink Command: 0XAA**
776
777
778 The first byte is to select which count value to initialize, and the next four bytes are the count value to be initialized.
779
780 * Example 1: Downlink Payload: 090100000000  **~-~-->**  AT+SETCNT=1,0
781 * Example 2: Downlink Payload: 0902000003E8  **~-~-->**  AT+SETCNT=2,1000
782
783 == 4.9 LEDs ==
784
785
786 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:463px" %)
787 |=(% style="width: 186px;background-color:#4F81BD;color:white" %)**Action**|=(% style="width: 277px;background-color:#4F81BD;color:white" %)**LED behavior**
788 |(% style="width:184px" %)Power On|(% style="width:275px" %)(% style="color:green" %)**GREEN LED on 1s, **(% style="color:red" %)**RED LED on 1s,**(%%)** (% style="color:blue" %)BLUE LED on 1s(%%)**
789 |(% style="width:184px" %)Joined successful|(% style="width:275px" %)(% style="color:green" %)**GRENN LED **(%%)on 5s
790 |(% style="width:184px" %)Send an uplink message|(% style="width:275px" %)(% style="color:green" %)**GREEN LED**(%%) blinks once
791 |(% style="width:184px" %)Received a downlink message|(% style="width:275px" %)(% style="color:blue" %)**BLUE LED**(%%) blinks once
792
793 = 5. Battery & How to replace =
794
795 == 5.1 Battery Type and replace ==
796
797
798 (((
799 The LDS02 is equipped with 2 x AAA LR03 batteries. If the batteries are running low (showing 2.1V on the platform), the user can buy generic AAA batteries and replace them.
800
801 (% style="color:red" %)**Note:**
802
803 1. The LDS02 doesn’t have any screws; you can use a nail to open it from the middle.
804 1. Make sure the direction is correct when installing the AAA batteries.
805 )))
806
807 (((
808 (% style="color:red" %)**Important Note: **(%%)Ensure you use new AAA LR03 batteries, and that the battery surfaces are not damaged.
809 )))
810
811 (((
812
813 )))
814
815 (((
816 Example of AAA LR03 battery:
817 )))
818
819 [[image:1654675278044-307.png]]
820
821
822 == 5.2 Power Consumption Analysis ==
823
824
825 (((
826 Dragino battery-powered products all run in Low Power mode. Users can refer to the guidelines from this [[**link**>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf]] to estimate battery life:
827 )))
828
829
830 = 6. Use AT Commands =
831
832 == 6.1 Access AT Commands ==
833
834
835 The LDS02 supports an AT command set. You can use a USB to TTL adapter to configure the LDS02 via AT commands, as shown below.
836
837 [[image:image-20221226104705-1.png||height="572" width="872"]]
838
839
840 (((
841 On the PC, the user needs to set the **serial tool** (such as [[PuTTY>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]] or SecureCRT) baud rate to **115200** to access the serial console of the LDS02. Below is the output for reference:
842 )))
843
844 (((
845 The AT command access password is (% style="color:red" %)**123456**.
846 )))
847
848 [[image:1654675618022-630.png]]
849
850
851 Each AT command needs to have an **ENTER** key pressed at the end before sending.
852
853 When entering the first command, the **RED LED** will turn on, and the user can now input AT commands. After entering all the required AT commands, input **AT+CLPM=1** to set the device to Low Power mode, and the **RED LED** will turn off.
854
855 More details can be found in the [[AT Command Manual>>http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDS01/]].
856
857
858 = 7. FAQ =
859
860 == 7.1 How to upgrade the image? ==
861
862
863 **~1. Connect the DAPLINK to the LDS02 as below:**
864
865
866
867 **3.3V<~-~-~-~-->VDD**
868
869 **CLK<~-~-~-~-~-~->CLK**
870
871 **DIO<~-~-~-~-~-~->DIO (SWD)**
872
873 **GND<~-~-~-~-~-~->GND**
874
875 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Firmware%20Upgrade%20Instruction/WebHome/image-20220527084230-4.png?rev=1.1||alt="image-20220527084230-4.png"]]
876
877 [[image:image-20230726175624-1.jpeg||height="565" width="753"]]
878
879
880 **2. Install PSoC Programmer 3.27.1**
881
882 Download Link: [[PSoCProgrammer3.27.1>>url:https://www.dragino.com/downloads/index.php?dir=tools/]]
883
884 Then, use PSoC Programmer to upgrade the firmware (**must use this version: PSoC Programmer 3.27.1**).
885
886 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Firmware%20Upgrade%20Instruction/WebHome/image-20220527084537-7.png?rev=1.1||alt="image-20220527084537-7.png"]]
887
888
889 **3. Download Sensor Firmware**
890
891 Downlink [[Firmware Location(same as LDS01)>>url:https://www.dropbox.com/sh/9j35mnsxnz0y3ye/AACj5gHGOURGEHCpj-E861Mua?dl=0]] to prepare the update.
892
893
894 **4. Upgrade Firmware**
895
896 * Open PSoC Programmer, then select the default configuration.
897
898 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Firmware%20Upgrade%20Instruction/WebHome/image-20220527084612-8.png?rev=1.1||alt="image-20220527084612-8.png"]]
899
900 * Click the file icon to select the software to be burned.
901
902 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Firmware%20Upgrade%20Instruction/WebHome/image-20220527084705-9.png?rev=1.1||alt="image-20220527084705-9.png"]]
903
904 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Firmware%20Upgrade%20Instruction/WebHome/image-20220527084739-10.png?width=1034&height=453&rev=1.1||alt="image-20220527084739-10.png" height="453" width="1034"]]
905
906 * Click the download icon, and the progress bar, as shown in the figure below, will appear. When **PASS** appears, it indicates that the burning was successful.
907
908 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Firmware%20Upgrade%20Instruction/WebHome/image-20220527084831-11.png?rev=1.1||alt="image-20220527084831-11.png"]]
909
910 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/Firmware%20Upgrade%20Instruction/WebHome/image-20220527084907-12.png?rev=1.1||alt="image-20220527084907-12.png"]]
911
912
913 **It is very important to press the reset button after the upgrade. This sets the device to work in Low Power mode.**
914
915 **If you change to a different LoRa frequency band/region, you need to use the AT+FDR command to restore the factory data after the program is successfully applied.**
916
917
918 == 7.2 How to change the LoRa Frequency Bands/Region? ==
919
920
921 If you have the US915 frequency and want to change it to the AS923 frequency, you can follow the same instructions mentioned in the [[How to upgrade the image?>>doc:||anchor="How to upgrade the image?"]] section to upgrade the image. When downloading the image, select the required file.
922
923
924 == 7.3 Can I disable uplinks for each event to save battery life? ==
925
926
927 Yes, you can use one of the methods below:
928
929
930 (% style="color:blue" %)**Via AT Command**:
931
932 (% style="color:red" %)**AT+DISALARM=1**(%%) : The end node will only send packets during the TDC time.
933
934 (% style="color:red" %)**AT+DISALARM=0**(%%) : The end node will send packets either during the TDC time or when there is a status change in the door sensor.
935
936
937 (% style="color:blue" %)**Via LoRaWAN downlink Command**:
938
939 (% style="color:red" %)**0xA701**(%%) : Equivalent to AT+DISALARM=1
940
941 (% style="color:red" %)**0xA700**(%%) : Equivalent to AT+DISALARM=0
942
943
944 == 7.4 How can I change the Subband for LDS02? ==
945
946
947 **Before v1.6 firmware:**
948 LDS02 operates in Subband 2 by default in the AU915/US915 band. If the LoRaWAN server operates on another subband, LDS02 may have trouble joining the server. In this case, the user can use the AT command to change the subband. See the AT Command chapter for hardware connection details. Below are the steps to change the subband:
949
950 1. Press the reset button.
951 1. Send the password **123456**.
952 1. Send the command: **AT+CFREQBANDMASK=0006** (use 0001 for Subband 1, 0002 for Subband 2, etc.).
953 1. Press the reset button to restart and switch to the new subband.
954
955 Example output:
956
957 (% class="mark small" %)[3369]DRAGINO LWL01 Device
958 [3370]Frequency Band: US915 v1.5
959 [3373]OTAA
960 [3374]DevEui= 7896785455246354
961 [3377]class type A
962 [3379]freq mode intra
963 [3381]**scan chn mask 0x0002   ~-~-> use subband 2**
964
965 (% class="mark small" %)LM502:~~# [10793]txDone
966 123456       ~-~-> ENTER PASSWORD
967 Correct Password
968
969 (% class="mark small" %)[105115]rxTimeOut
970 **AT+CFREQBANDMASK=0020 ~-~-> Change to Subband6**
971 OK
972
973 (% class="mark small" %)[3371]DRAGINO LWL01 Device
974 [3373]Frequency Band: US915 v1.5
975 [3376]OTAA
976 [3377]DevEui= 7896785455246354
977 [3380]class type A
978 [3382]freq mode intra
979 [3384]**scan chn mask 0x0001  ~-~-> reboot and works on Subband1 now**
980
981 [[image:image-20230103143821-1.png]]
982
983
984 **Since firmware v1.6:**
985
986 LDS02 works with the channel mask 0x0000, which covers all subbands. Therefore, there is no need to use AT commands to change the subband, and it will work for every subband.
987
988
989 == 7.5 My sensor worked for Helium AU915 before, but now it doesn't work. Why? ==
990
991
992 This is a sub-band issue. See chapter 7.4. Helium changed the sub-band for AU915 from subband 2 to subband 6, which caused the sensor to stop working.
993
994
995 == 7.6 Why do I see different working temperatures for the device? ==
996
997
998 The working temperature range of the device depends on the battery the user chooses.
999
1000 * A standard AAA battery can support a working range of -10°C to 50°C.
1001 * A special AAA battery can support a working range of -40°C to 60°C. For example, [[Energizer L92>>url:https://data.energizer.com/pdfs/l92.pdf]]
1002
1003 == 7.7 The device keeps rejoining the network and is not working properly ==
1004
1005
1006 **Cause of the problem:**
1007
1008 When the DR of AU915 and AS923 is 2 or the DR of US915 is 0, upon receiving the MAC Command from the server, the node will enter deep sleep and will not send packets because the attached MAC answer exceeds the number of bytes.
1009
1010 **Solution:**
1011
1012 1. Manually restart the device, then downlink 21 03 (only needs to be set once to be effective).
1013 1. Manually restart the device, then set AT+RPL=3 (only needs to be set once to be effective).
1014 1. Update the firmware to version v1.8 or above.
1015
1016 = 8. Ordering Information =
1017
1018
1019 **Part Number: (% style="color:blue" %)LDS02-XXX(%%)**
1020
1021 (% style="color:blue" %)**XXX:**(%%) The default frequency band
1022
1023 * (% style="color:red" %)**EU433**(%%): frequency  bands EU433
1024 * (% style="color:red" %)**EU868**(%%): frequency  bands EU868
1025 * (% style="color:red" %)**KR920**(%%): frequency  bands KR920
1026 * (% style="color:red" %)**CN470**(%%): frequency bands CN470
1027 * (% style="color:red" %)**AS923**(%%): frequency  bands AS923
1028 * (% style="color:red" %)**AU915**(%%): frequency bands AU915
1029 * (% style="color:red" %)**US915**(%%): frequency bands  US915
1030 * (% style="color:red" %)**IN865**(%%):  frequency bands  IN865
1031 * (% style="color:red" %)**CN779**(%%): frequency bands CN779
1032
1033 = 9. Packaging Information =
1034
1035
1036 (((
1037 **Package Includes**:
1038 )))
1039
1040 * (((
1041 LDS02 x 1
1042 )))
1043
1044 (((
1045 **Dimension and weight**:
1046 )))
1047
1048 * (((
1049 Device Size: 69.2 x 29.2 x 14.8 mm
1050
1051
1052 )))
1053
1054 = 10. Support =
1055
1056
1057 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, we cannot offer live support. However, your questions will be answered as soon as possible during the aforementioned schedule.
1058 * Please provide as much information as possible regarding your inquiry (product models, a clear description of the problem, steps to replicate it, etc.) and send an email to [[support@dragino.com>>mailto:support@dragino.com]].

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0