Skip to Content
Last modified by Xiaoling on 2025/05/08 09:22
Show last authors
1
2
3 (% style="text-align:center" %)
4 [[image:1654679359875-169.png]]
5
6
7
8 **Table of Contents:**
9
10 {{toc/}}
11
12
13
14
15
16
17
18
19 = 1. Introduction =
20
21 == 1.1 What is the LDS02 LoRaWAN Door Sensor? ==
22
23
24 (((
25 (((
26 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.
27 )))
28
29 (((
30 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.
31
32 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.
33
34 The LDS02 **features an open alarm**, which can be configured to send an alarm if the door remains open for a specified duration.
35
36 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.
37
38
39 The following figure shows how the LDS02 is connected to a typical LoRaWAN network server.
40
41 [[image:LDS02-lorawan.jpg||height="458" width="1166"]]
42
43
44 )))
45 )))
46
47 == 1.2 Features ==
48
49
50 * LoRaWAN Class A v1.0.3
51 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
52 * Door Open/Close detect
53 * Door open/close statistics
54 * 2 x AAA LR03 Batteries
55 * AT Commands to change parameters
56 * Uplink on periodically and open/close action
57 * Remote configure parameters via LoRa Downlink
58 * Firmware upgradable via program port
59
60 == 1.3 Storage & Operation Temperature ==
61
62
63 -10 ~~ 50 °C  or -40 ~~ 60 °C (depends on the battery type, see [[FAQ>>||anchor="H7.6Whyiseedifferentworkingtemperatureforthedevice3F"]])
64
65
66 == 1.4 Applications ==
67
68
69 * Smart Buildings & Home Automation
70 * Logistics and Supply Chain Management
71 * Smart Metering
72 * Smart Agriculture
73 * Smart Cities
74 * Smart Factory
75
76 == 1.5 Dimension ==
77
78
79 Units in mm
80
81 [[image:1654680563545-120.png]]
82
83
84 [[image:1654680510816-654.png]]
85
86
87 == 1.6 Firmware Change Log ==
88
89
90 (((
91 (((
92 LDS02 uses the same firmware as LDS01：[[LDS02 Image files – Download link>>https://www.dropbox.com/sh/9j35mnsxnz0y3ye/AACj5gHGOURGEHCpj-E861Mua?dl=0]]
93 )))
94 )))
95
96
97 == 1.7 Hardware Variant (Since LDWS v2.4 PCB) ==
98
99
100 Starting from the LDWS v2.4 motherboard, we made adjustments to the button and LED light of LDS02, and the corresponding adjustments were also made to the shell at the same time.
101
102
103 === 1.7.1 How to identify the old and new versions ===
104
105
106 Check the **external enclosure** for these differences:
107
108 ~1. RESET Button Hole
109
110 * New Version: Larger hole (Corresponding to the position of the RESET button on the motherboard).
111 * Old Version: Smaller hole (The original position of the LED).
112
113 2. LED
114
115 * New Version: Thinner circular area below RESET hole (for LED light transmission).
116 * Old Version: The small hole directly above the shell (Corresponding to the position of the LED on the motherboard).
117
118 3. Arrow Marking
119
120 * New Version: Edge-embossed arrow shape.
121 * Old Version: Fully recessed arrow shape.
122
123 (% style="color:blue" %)**Actual appearance comparison picture：**
124
125 [[image:image-20250507161458-4.jpeg||height="456" width="665"]]
126
127
128 === 1.7.2 RESET button & LED Display ===
129
130
131 **1. RESET button**
132
133 Restart the device through the physical reset button.
134
135 It is suitable for rapid restart when the equipment malfunctions (such as communication failure, sensor unresponsiveness).
136
137 * For old version, the RESET button was located inside the device enclosure, requiring the housing to be opened for access.
138 * For new version, the RESET button is located in a small hole in the device's case and can simply be pressed with a thin pin without opening the case.
139
140 Example:
141
142 [[image:image-20250507172832-6.png||height="372" width="274"]]
143
144
145 **2. LED display**
146
147 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:463px" %)
148 |=(% style="width: 186px;background-color:#4F81BD;color:white" %)**Action**|=(% style="width: 277px;background-color:#4F81BD;color:white" %)**LED behavior**
149 |(% 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(%%)**
150 |(% style="width:184px" %)Joined successful|(% style="width:275px" %)(% style="color:green" %)**GRENN LED **(%%)on 5s
151 |(% style="width:184px" %)Send an uplink message|(% style="width:275px" %)(% style="color:green" %)**GREEN LED**(%%) blinks once
152 |(% style="width:184px" %)Received a downlink message|(% style="width:275px" %)(% style="color:blue" %)**BLUE LED**(%%) blinks once
153
154 = (% style="color:inherit; font-family:inherit; font-size:29px" %)2. Power ON LDS02(%%) =
155
156
157 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.
158
159
160 = 3. How to Install LDS02 =
161
162
163 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.
164
165
166 Fixing with screws:
167
168 * 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.
169
170 [[image:image-20231222111730-1.jpeg||height="428" width="686"]]
171
172
173 Fixing with double-sided adhesive pads:
174
175 * 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.
176
177 [[image:image-20231222111834-2.jpeg||height="443" width="685"]]
178
179
180 (((
181 (((
182 When installing the LDS02, make sure to install it as shown below so that the marks align closely when the door is closed.
183 )))
184
185 (((
186 Open/Close threshold range (the minimum gap between sensor enclosure and the magnet enclosure): ~~ 10mm
187 )))
188 )))
189
190 [[image:1654680716522-793.png||height="505" width="497"]]
191
192
193 = 4. Operation Mode =
194
195 == 4.1 How It Works? ==
196
197
198 (((
199 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.
200
201 [[image:image-20230426084924-1.png||height="229" width="493"]]
202
203 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.
204 )))
205
206
207 == 4.2 Example of Joining a LoRaWAN Network ==
208
209
210 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.
211
212
213 [[image:LDS02-tts.jpg||height="333" width="1245"]]
214
215
216 === 4.2.1 Prerequisites ===
217
218
219 (((
220 * 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:
221 ** A keep-alive message, which is sent once per day.
222 ** A door event message when a door is opened or closed ([[Alarm event can be disabled>>||anchor="H7.3CanIdisableuplinkforeacheventtosavebatterylife3F"]])
223 * The Things Stack community network coverage, or private LoRaWAN Network Coverage with any The Things Stack deployment plan.
224 )))
225
226
227 ==== 4.2.1.1 Setting up ====
228
229
230 * Sign up for a free account with [[The Things Stack Sandbox>>url:https://eu1.cloud.thethings.network]] if you do not have one yet.
231 * Log in to your **The Things Stack** account.
232 * Create an **application** with The Things Stack if you do not have one yet.
233 ** On the left navigation, click **Applications**.
234 ** Then click **+ Add Application** button.
235
236 [[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" height="768" width="1230"]]
237
238
239 * On the **Create Application **page, configure the following:
240 ** **Application ID**: Provide a unique identification for your application within The Things Stack.
241 ** **Application name**: (optional) Provide a descriptive name.
242 ** **Description**: (optional) Provide a description.
243 * Click on **Create application **button.
244
245 [[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" height="802" width="1284"]]
246
247
248
249 * Go to your application's page and click on the **End devices** in the left menu.
250 * On the End devices page, click on **+ Register end device**.
251
252 [[image:lds02-step-5.png||height="819" width="1311"]]
253
254 * Two registration options are available:
255 ** Using the LoRaWAN Device Repositoty
256 ** Manual registration
257
258 ==== 4.2.1.2 Using the LoRaWAN Device Repository ====
259
260
261 * On the **Register end device** page:
262 ** Select the option **Select the end device in the LoRaWAN Device Repository **under **Input method**.
263 ** Select the **End device brand**, **Model**, **Hardware version**, **Firmware version**, and **Profile (Region)** from the respective dropdown lists.
264 *** **End device brand**: Dragino Technology Co., Limited
265 *** **Model**: LDS02 - Door Sensor
266 *** **Hardware ver**: Unknown
267 *** **Firmware ver**: 1.6
268 *** **Profile (Region)**: Select the region that matches your device.
269 ** Select the **Frequency plan** that matches your device from the **Frequency plan** dropdown list.
270 ** 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.
271
272 [[image:lds02-step-2.png||height="812" width="1300"]]
273
274
275
276 * In the **DevEUI** field, enter the **DevEUI**.
277 * In the **AppKey** field, enter the **AppKey.**
278 * In the **End device ID** field, enter a unique name for your LDS02 within this application.
279 * Under **After registration**, select the **View registered end device** option.
280 * Click **Register end device** button.
281
282 [[image:lds02-step-3.png||height="797" width="1276"]]
283
284
285 * You will be navigated to the Device overview page.
286
287 [[image:lds02-step-4.png||height="817" width="1308"]]
288
289
290 * 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.
291
292 [[image:1654681390551-993.png]]
293
294
295 == 4.3 Uplink Payload ==
296
297 === 4.3.1 Sensor value, Uplink via FPORT~=10 ===
298
299
300 The data is sent in the following cases:
301
302 * TDC (Transmit Time Interval-Keep Alive Interval), the default TDC is 24 hours, so this data is automatically sent every 24 hours.
303 * This data is sent each time the door is opened or closed, [[AT+DISALARM=0(default)>>||anchor="H7.3CanIdisableuplinksforeacheventtosavebatterylife3F
304 "]].
305
306 The uplink payload is a total of 10 bytes.
307
308 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:480px" %)
309 |=(% 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**
310 |Value|Door State & BAT|(((
311 MOD Always:0x01
312 )))|Total open door events|(((
313 Last door open
314 duration (unit: min)
315 )))|(((
316 [[Alarm>>||anchor="H4.6AlarmBaseonTimeout"]] (Only used in LWL02) Always:0x00
317 )))
318
319 **Example:**
320
321 [[image:image-20250211113735-1.png||height="351" width="1090"]]
322
323
324 [[image:image-20250211113814-2.png]]
325
326 (((
327
328
329 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]]
330
331 (% style="color:blue" %)**Battery Info**
332
333 Check the battery voltage:
334
335 Example 1: 0x0B88&3FFF = 2952mV
336
337 Example 2: 0xD152&3FFF = 4434mV
338
339
340 (% class="wikigeneratedid" id="H4.3.2Status" %)
341 (% style="color:blue" %)**Status**
342
343 Check the door state:
344
345 **Example**:
346
347 If the payload is: **0B**:  (0000 1011&1000 0000== 0), **DOOR_OPEN_STATUS** is 0（**CLOSE**）
348
349 If the payload is: **D1**: (1101 0001&1000 0000== 1), **DOOR_OPEN_STATUS** is 1（**OPEN**）
350
351
352 (% style="color:blue" %)**MOD**
353
354 Check the working mode (MOD):
355
356 **Example:**
357
358 If the payload is: 01, the MOD is 1.
359
360
361 (% style="color:blue" %)**Total door open events**
362
363 Get the total number of door open events:
364
365 **Example**:
366
367 If payload is: **00 00 93, **the total is 147 events.
368
369 If payload is: **00 00 00, **the total is 0 events.
370
371
372 (% style="color:blue" %)**Last door open duration(unit:min)**
373
374 Get the last door open duration:
375
376 **Example:**
377
378 If the payload is: **00 00 25, **the last door open duration is 37 minutes.
379
380 If payload is: **00 00 01,** the last door open duration is 1 minute.
381
382
383 (% style="color:blue" %)**Alarm(Only used in LWL02) Always:0x00**
384
385 Get alarm status.
386
387 **Example:**
388
389 If the payload is: 01:  (0001 & 0001== 1), the alarm status is 1
390
391 If the payload is: 00:  (0000 & 0001== 0), the alarm status is 0
392
393
394 === 4.3.2 EDC mode value, Uplink via FPORT~=7 ===
395
396
397 When **[[EDC>>||anchor="H4.7A0EDCMode28Sincefirmwarev1.8.229"]]** is enabled, LDS02 will send this data.
398
399 The uplink payload is a total of 5 bytes.
400
401 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:320px" %)
402 |=(% style="width: 50px;background-color:#4F81BD;color:white" %)**byte**|=(% style="width: 136px; background-color: rgb(79, 129, 189); color: white;" %)**2**|=(% style="width: 114px; background-color: rgb(79, 129, 189); color: white;" %)**3**
403 |Value|(% style="width:136px" %)EDC_MOD & BAT|(% style="width:114px" %)(((
404 Times
405 )))
406
407 **Example:**
408
409 * (((
410 AT+EDC=1,10
411 )))
412
413 [[image:image-20250211162026-2.png||height="275" width="944"]]
414
415 [[image:image-20250211120039-4.png]]
416
417 * AT+EDC=0,20
418
419 [[image:image-20250211161956-1.png||height="307" width="958"]]
420
421 [[image:image-20250211162046-3.png]]
422
423 (% style="color:blue" %)**Battery Info**
424
425 Check the battery voltage:
426
427 Ex1: (bytes[0]<<8 | bytes[1])&0x3FFF = 0x8C60&3FFF = 3168mV
428
429 Ex2: (bytes[0]<<8 | bytes[1])&0x3FFF = 0xD152&3FFF = 4434mV
430
431
432 (% style="color:blue" %)**EDC_MOD**
433
434 This field is used to indicate whether the EDC mode packet sending condition is dependent on the number of door open accumulations or on the number of door close accumulations.
435
436 Ex1: bytes[0]&0x80 = 8C & 0x80 = **1**000 0000(BIN), "OPEN".
437
438 Ex2: bytes[0]&0x80 = 0C & 0x80 = **0**000 0000(BIN), "CLOSE".
439
440
441 (% style="color:blue" %)**Times**
442
443 This field is used to display the number of open/closed events.
444
445 Ex1: 0x00000A(H) =10
446
447 Ex2: 0x000014(H) =20
448
449
450 )))
451
452 == 4.4 Downlink Payload ==
453
454
455 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:505px" %)
456 |=(% 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)**
457 |(% style="width:180px" %)TDC (Transmit Time Interval—Keep Alive Interval)|(% style="width:94px" %)0x01|(% style="width:226px" %)4
458 |(% style="width:180px" %)RESET|(% style="width:94px" %)0x04|(% style="width:226px" %)2
459 |(% style="width:180px" %)[[Set confirmed mode>>||anchor="HTypeCode0x05"]]|(% style="width:94px" %)0x05|(% style="width:226px" %)2
460 |(% style="width:180px" %)[[Clear Counting>>||anchor="HTypeCode0xA6"]]|(% style="width:94px" %)0xA6|(% style="width:226px" %)2
461 |(% style="width:180px" %)[[Enable/Disable Alarm>>||anchor="HTypeCode0xA7"]]|(% style="width:94px" %)0xA7|(% style="width:226px" %)2
462 |(% style="width:180px" %)[[Control ADR/DR>>||anchor="HTypeCode0xA8"]]|(% style="width:94px" %)0xA8|(% style="width:226px" %)3
463 |(% style="width:180px" %)[[Set Alarm Timeout>>||anchor="HTypeCode0xA9"]]|(% style="width:94px" %)0xA9|(% style="width:226px" %)4
464
465 The following image illustrates how to send a downlink payload from The Things Stack.
466
467 [[image:1654673412319-976.png]]
468
469
470 === (% style="color:#037691" %)**Type Code 0x01**(%%) ===
471
472 If the payload is **0100003C**, it means controlling the LDS02’s Keep Alive interval to **0x00003C = 60 seconds (s)**.
473
474
475 === (% style="color:#037691" %)**Type Code 0x04**(%%) ===
476
477 If the payload is **0x04FF**, it will reset the LDS02.
478
479
480 === (% style="color:#037691" %)**Type Code 0x05**(%%) ===
481
482 (((
483 **0x05 00**: Set uplink to LoRaWAN unconfirmed mode
484 )))
485
486 (((
487 **0x05 01**: Set uplink to LoRaWAN confirmed mode
488 )))
489
490
491 === (% style="color:#037691" %)**Type Code 0xA6**(%%) ===
492
493 (((
494 **Example:** 0xA601 – Clear Counting
495 For the LDS02: Resets both the count number and time.
496 )))
497
498
499 === (% style="color:#037691" %)**Type Code 0xA7**(%%) ===
500
501 (((
502 **0xA701**: Equivalent to AT+DISALARM=1
503 )))
504
505 (((
506 **0xA700**: Equivalent to AT+DISALARM=0
507 )))
508
509
510 === (% style="color:#037691" %)**Type Code 0xA8**(%%) ===
511
512 (((
513 **Format:** 0xA8 aa bb
514
515 * **aa**: 1 – Enable ADR; 0 – Disable ADR (same as the AT+CADR command)
516 * **bb**: Set DR (same as AT+CDATARATE; only valid after ADR=0)
517
518 **Example:** 0xA80001 – Set ADR=0 and DR=1
519 )))
520
521
522 === (% style="color:#037691" %)**Type Code 0xA9**(%%) ===
523
524 See, [[Alarm Base Timeout>>||anchor="H4.6AlarmBaseonTimeout"]] for details.
525
526
527 == 4.5 Integrate with IoT Platforms ==
528
529
530 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.
531
532 === 4.5.1 Integrate with ThingsEye ===
533
534
535 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.
536
537
538 ==== 4.5.1.1 Configuring The Things Stack ====
539
540 We use The Things Stack Sandbox in this example:
541
542 * In **The Things Stack Sandbox**, go to the **Application **for the LDS02 you added.
543 * Select **MQTT** under **Integrations** in the left menu.
544 * 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.
545 * 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.
546
547 {{info}}
548 The username and  password (API key) you created here are required in the next section.
549 {{/info}}
550
551
552 [[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" height="845" width="1353"]]
553
554
555 ==== 4.5.1.2 Configuring ThingsEye.io ====
556
557 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.
558
559 * Login to your [[ThingsEye.io >>url:https://thingseye.io]]account.
560 * Under the **Integrations center**, click **Integrations**.
561 * Click the **Add integration** button (the button with the **+** symbol).
562
563 [[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" height="845" width="1353"]]
564
565
566 On the **Add integration** window, configure the following:
567
568 **Basic settings:**
569
570 * Select **The Things Stack Community** from the **Integration type** list.
571 * Enter a suitable name for your integration in the **Name **text** **box or keep the default name.
572 * Ensure the following options are turned on.
573 ** Enable integration
574 ** Debug mode
575 ** Allow creating devices or assets
576 * Click the **Next** button. you will be navigated to the **Uplink data converter** tab.
577
578 [[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" height="842" width="1348"]]
579
580
581 **Uplink data converter:**
582
583 * Click the **Create new** button if it is not selected by default.
584 * Enter a suitable name for the uplink data converter in the **Name **text** **box or keep the default name.
585 * Click the **JavaScript** button.
586 * 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]].
587 * Click the **Next** button. You will be navigated to the **Downlink data converter **tab.
588
589 [[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" height="842" width="1348"]]
590
591
592 **Downlink data converter (this is an optional step):**
593
594 * Click the **Create new** button if it is not selected by default.
595 * Enter a suitable name for the downlink data converter in the **Name **text** **box or keep the default name.
596 * Click the **JavaScript** button.
597 * 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]].
598 * Click the **Next** button. You will be navigated to the **Connection** tab.
599
600 [[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" height="842" width="1348"]]
601
602
603 **Connection:**
604
605 * Choose **Region** from the **Host type**.
606 * 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/...).
607 * 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**).
608 * Click the **Check connection** button to test the connection. If the connection is successful, you will see the message saying **Connected**.
609
610 [[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"]]
611
612
613 * Click the **Add** button.
614
615 [[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" height="835" width="1337"]]
616
617
618 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.
619
620
621 [[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" height="916" width="1335"]]
622
623
624 ==== 4.5.1.3 Viewing integration details ====
625
626
627 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.
628
629
630 [[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" height="917" width="1336"]]
631
632
633 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.
634
635 {{info}}
636 See also [[ThingsEye documentation>>url:https://wiki.thingseye.io/xwiki/bin/view/Main/]].
637 {{/info}}
638
639
640 ==== 4.5.1.4 Viewing events ====
641
642
643 The **Events **tab displays all the uplink messages from the LDS02.
644
645 * Select **Debug **from the **Event type** dropdown.
646 * Select the** time frame** from the **time window**.
647
648 [[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" height="916" width="1335"]]
649
650
651 * To view the **JSON payload** of a message, click on the **three dots (...)** in the **Message** column of the desired message.
652
653 [[image:lds02-thingseye-payload.png||height="621" width="1335"]]
654
655
656 ==== 4.5.1.5 Deleting an integration ====
657
658
659 If you want to delete an integration, click the **Delete integration** button on the Integrations page.
660
661
662 ==== 4.5.1.6 Viewing sensor data on a dashboard ====
663
664
665 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.
666
667
668 [[image:lds02-thingseye-dashboard.png||height="692" width="1323"]]
669
670
671 === 4.5.2 Integrate with Datacake ===
672
673
674 (((
675 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.
676
677
678 ==== 4.5.2.1 Prerequisites ====
679
680 * The LDS02 device is joined to The Things Stack.
681 * Uplinks from the LDS02 device are being received by The Things Stack.
682 * A Datacake account (a free account is sufficient for this example).
683
684 ==== 4.5.2.2 Procedure ====
685
686
687 * In the Datacake workspace, on the left navigation, click **Account Settings**.
688 * Then click **API Token**.
689 * 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.
690
691 [[image:datacake-1.png||height="816" width="1306"]]
692
693
694 )))
695
696 (((
697 To configure the Application to forward data to Datacake you will need to add integration. To add the Datacake integration, perform the following steps:
698
699 * In The Things Stack console, on the left navigation,
700 ** First select your **application** (**Applications -> <your application>**)
701 ** Then select **Integrations -> Webhooks**
702 * On the **Webhooks** page, click + **Add Webhook** button.
703
704 [[image:tts-webhook-1.png||height="817" width="1308"]]
705
706
707 * On the **Choose webhook template** page, select **Datacake**.
708 )))
709
710
711 [[image:tts-webhook-2.png||height="822" width="1316"]]
712
713
714 * On the Setup webhook for Datacake page,
715 ** **Webhook ID**: provide an unique identifier for this webhook
716 ** **Token**: Paste the **Datacake API Token** when you copied from the Datacake **Account Settings**.
717 * Click on the **Create Datacake webhook** button.
718
719 [[image:tts-webhook-3.png||height="819" width="1311"]]
720
721
722 Now the Webhook is created and displayed on the Webhooks page.
723
724 [[image:tts-webhook-4.png||height="821" width="1314"]]
725
726
727 * In the Datacake workspace, on the left navigation, click **Devices**.
728 * On the Devices page, click **+Add Device**.
729
730 [[image:datacake-2.png||height="820" width="1313"]]
731
732
733 * On the **Add Device** window, click **LoRaWAN** option.
734 * Click on the **Next** button.
735
736 [[image:datacake-3.png||height="823" width="1318"]]
737
738
739 * On the **Add LoRaWAN Device** window, **STEP 1**, click on **New Product from template** option.
740 * Under **Device Template**, search **lds02**. Then click on **Dragino LDS02 Door Sensor** option.
741 * Click on the **Next** button.
742
743 [[image:datacake-4.png||height="827" width="1324"]]
744
745
746 * On the **Add LoRaWAN Device** window, **STEP 2**, under **Network Server**, click on **The Things Stack V3** option.
747 * Click on the **Next** button.
748
749 [[image:datacake-5.png||height="831" width="1330"]]
750
751
752 * On the **Add LoRaWAN Device** window, **STEP 3**, under **Add Devices**, click **Manual** tab.
753 * In the **DEVEUI** textbox, enter your LDS02's 8 bytes **DevEUI**.
754 * In the **NAME** textbox, enter a suitable name to identify your LDS02.
755 * Click on the **Next** button.
756
757 [[image:datacake-6.png||height="830" width="1329"]]
758
759
760 * On the **Add LoRaWAN Device** window, **STEP 4**, select **Individual device plans** tab.
761 * Click **Free** option.
762 * Click on the **Add 1 Device** button.
763
764 [[image:datacake-7.png||height="831" width="1330"]]
765
766
767 * The device is now added to the Datacake workspace and is ready to receive uplinks from the LDS02 via The Things Stack.
768 * In the **DEVICE** column, click **lds02**.
769
770 [[image:datacake-8.png||height="824" width="1319"]]
771
772
773 You can see the **pre-built dashboard** from our template, displaying the LDS02's sensor data on various **widgets**.
774
775 [[image:datacake-9.png||height="826" width="1322"]]
776
777
778 == 4.6 Alarm Based on Timeout ==
779
780
781 (((
782 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:
783 )))
784
785 (((
786 (% style="color:blue" %)**Using AT Commands**(%%)**:**
787 )))
788
789 (((
790
791
792 * **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.
793 * **AT+TTRIG=0,0 ~-~-> **Default value, disables the timeout alarm.
794 )))
795
796 (((
797 (% style="color:blue" %)**Using Downlink Commands**(%%)**:**
798 )))
799
800 (((
801 **Command:** 0xA9 aa bb cc
802
803 * **A9:** Command Type Code
804 * **aa:** Status to be monitored
805 * **bb cc:** Timeout
806
807 If the user sends **0xA9 01 00 1E**, this is equivalent to **AT+TTRIG=1,30**.
808
809 Or
810
811 **0xA9 00 00 00**, this is equivalent to **AT+TTRIG=0,0**, which disables the timeout alarm.
812 )))
813
814
815 == 4.7 EDC Mode(Since firmware v1.8.2) ==
816
817
818 Feature: Set EDC mode, when the cumulative number of opening/closing reaches the set count value, LDS02 will send the packet.
819
820 (% style="color:blue" %)**AT Command: AT+EDC**
821
822 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
823 |=(% style="width: 138px; 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**
824 |(% style="width:126px" %)AT+EDC?|(% style="width:196px" %)Show current Settings|(% style="width:176px" %)(((
825 0,0 (default)
826 OK
827 )))
828 |(% colspan="1" rowspan="2" style="width:126px" %)(((
829
830
831
832
833 AT+EDC=aa,bb
834 )))|(% style="width:196px" %)aa: Set the open/close cumulative packet sending mode|(% style="width:176px" %)(((
835 0: Set the close cumulative packet sending mode
836 1: Set the open cumulative packet sending mode
837 )))
838 |(% style="width:196px" %)bb: Set the cumulative count and send packets when the cumulative count is reached|(% style="width:176px" %)
839
840 (% style="color:blue" %)**Downlink Command: 0X02**
841
842 Format: Command Code (0x02) followed by 4 bytes.
843
844 Example:
845
846 * Downlink paylaod: 02 01 00 00 0A  ~/~/ AT+EDC=1,10  The LDS02 will send a packet for every 10 increases in the open_count.
847 * Downlink paylaod: 02 00 00 00 14  ~/~/ AT+EDC=0,20  The LDS02 will send a packet for every 20 increases in the close_count.
848
849 (% style="color:red" %)**Note: To use the EDC mode, you need to set [[AT+DISALARM=1(downlink payload: A701)>>||anchor="H7.3CanIdisableuplinksforeacheventtosavebatterylife3F
850 "]], so that LDS02 will send packets only when the TDC time and cumulative count reach the set value.**
851
852
853 == 4.8 Set count value(Since firmware v1.8.2) ==
854
855
856 Feature: Set the initial count value.
857
858 (% style="color:blue" %)**AT Command: AT+SETCNT**
859
860 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:500px" %)
861 |=(% style="width: 157px; background-color: rgb(79, 129, 189); color: white;" %)**Command Example**|=(% style="width: 243px; background-color: rgb(79, 129, 189); color: white;" %)**Function**|=(% style="width: 100px; background-color: rgb(79, 129, 189); color: white;" %)**Response**
862 |(% style="width:154px" %)AT+SETCNT=100|(% style="width:241px" %)Initialize the count value to 100.|(% style="width:100px" %)(((
863 OK
864 )))
865
866 (% style="color:blue" %)**Downlink Command: 0XAA**
867
868 (% style="color:#037691" %)**For normal mode: 0xAA xx xx xx**
869
870 0xAA is the function code, and the next 3 bytes are the count value to be initialized.
871
872 * Example: Downlink Payload: AA 00 00 00 **~-~-->**  AT+SETCNT=0  Set the open door count to 0.
873
874 (% style="color:#037691" %)**For EDC mode: 0xAA aa xx xx xx**
875
876 0xAA is the function code. aa sets how the EDC mode is accumulated (0x01: open; 0x00: close). and the next 3 bytes are the count values to be initialized.
877
878 * Example 1: Downlink Payload: AA 01 00 00 0A  **~-~-->**  AT+SETCNT=10  Set the door open count to 10.
879 * Example 2: Downlink Payload: AA 00 00 00 14  **~-~-->**  AT+SETCNT=20  Set the door close count to 10.
880
881 = 5. Battery & How to replace =
882
883 == 5.1 Battery Type and replace ==
884
885
886 (((
887 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.
888
889 (% style="color:red" %)**Note:**
890
891 1. The LDS02 doesn't have any screws; you can use a nail to open it from the middle.
892 1. Make sure the direction is correct when installing the AAA batteries.
893 )))
894
895 (((
896 (% style="color:red" %)**Important Note: **(%%)Ensure you use new AAA LR03 batteries, and that the battery surfaces are not damaged.
897 )))
898
899 (((
900
901 )))
902
903 (((
904 Example of AAA LR03 battery:
905 )))
906
907 [[image:1654675278044-307.png]]
908
909
910 == 5.2 Power Consumption Analysis ==
911
912
913 (((
914 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:
915 )))
916
917
918 = 6. Use AT Commands =
919
920 == 6.1 Access AT Commands ==
921
922
923 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.
924
925 [[image:image-20221226104705-1.png||height="572" width="872"]]
926
927
928 (((
929 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:
930 )))
931
932 (((
933 The AT command access password is (% style="color:red" %)**123456**.
934 )))
935
936 [[image:1654675618022-630.png]]
937
938
939 Each AT command needs to have an **ENTER** key pressed at the end before sending.
940
941 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.
942
943 More details can be found in the [[AT Command Manual>>http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LDS01/]].
944
945
946 = 7. FAQ =
947
948 == 7.1 How to upgrade the image? ==
949
950
951 **~1. Connect the DAPLINK to the LDS02 as below:**
952
953
954
955 **3.3V<~-~-~-~-->VDD**
956
957 **CLK<~-~-~-~-~-~->CLK**
958
959 **DIO<~-~-~-~-~-~->DIO (SWD)**
960
961 **GND<~-~-~-~-~-~->GND**
962
963 [[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"]]
964
965 [[image:image-20230726175624-1.jpeg||height="565" width="753"]]
966
967
968 **2. Install PSoC Programmer 3.27.1**
969
970 Download Link: [[PSoCProgrammer3.27.1>>url:https://www.dragino.com/downloads/index.php?dir=tools/]]
971
972 Then, use PSoC Programmer to upgrade the firmware (**must use this version: PSoC Programmer 3.27.1**).
973
974 [[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"]]
975
976
977 **3. Download Sensor Firmware**
978
979 Downlink [[Firmware Location(same as LDS01)>>url:https://www.dropbox.com/sh/9j35mnsxnz0y3ye/AACj5gHGOURGEHCpj-E861Mua?dl=0]] to prepare the update.
980
981
982 **4. Upgrade Firmware**
983
984 * Open PSoC Programmer, then select the default configuration.
985
986 [[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"]]
987
988 * Click the file icon to select the software to be burned.
989
990 [[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"]]
991
992 [[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"]]
993
994 * 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.
995
996 [[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"]]
997
998 [[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"]]
999
1000
1001 **It is very important to press the reset button after the upgrade. This sets the device to work in Low Power mode.**
1002
1003 **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.**
1004
1005
1006 == 7.2 How to change the LoRa Frequency Bands/Region? ==
1007
1008
1009 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.
1010
1011
1012 == 7.3 Can I disable uplinks for each event to save battery life? ==
1013
1014
1015 Yes, you can use one of the methods below:
1016
1017
1018 (% style="color:blue" %)**Via AT Command**:
1019
1020 (% style="color:red" %)**AT+DISALARM=1**(%%) : The end node will only send packets during the TDC time.
1021
1022 (% 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.
1023
1024
1025 (% style="color:blue" %)**Via LoRaWAN downlink Command**:
1026
1027 (% style="color:red" %)**0xA701**(%%) : Equivalent to AT+DISALARM=1
1028
1029 (% style="color:red" %)**0xA700**(%%) : Equivalent to AT+DISALARM=0
1030
1031
1032 == 7.4 How can I change the Subband for LDS02? ==
1033
1034
1035 **Before v1.6 firmware:**
1036 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:
1037
1038 1. Press the reset button.
1039 1. Send the password **123456**.
1040 1. Send the command: **AT+CFREQBANDMASK=0006** (use 0001 for Subband 1, 0002 for Subband 2, etc.).
1041 1. Press the reset button to restart and switch to the new subband.
1042
1043 Example output:
1044
1045 (% class="mark small" %)[3369]DRAGINO LWL01 Device
1046 [3370]Frequency Band: US915 v1.5
1047 [3373]OTAA
1048 [3374]DevEui= 7896785455246354
1049 [3377]class type A
1050 [3379]freq mode intra
1051 [3381]**scan chn mask 0x0002   ~-~-> use subband 2**
1052
1053 (% class="mark small" %)LM502:~~# [10793]txDone
1054 123456       ~-~-> ENTER PASSWORD
1055 Correct Password
1056
1057 (% class="mark small" %)[105115]rxTimeOut
1058 **AT+CFREQBANDMASK=0020 ~-~-> Change to Subband6**
1059 OK
1060
1061 (% class="mark small" %)[3371]DRAGINO LWL01 Device
1062 [3373]Frequency Band: US915 v1.5
1063 [3376]OTAA
1064 [3377]DevEui= 7896785455246354
1065 [3380]class type A
1066 [3382]freq mode intra
1067 [3384]**scan chn mask 0x0001  ~-~-> reboot and works on Subband1 now**
1068
1069 [[image:image-20230103143821-1.png]]
1070
1071
1072 **Since firmware v1.6:**
1073
1074 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.
1075
1076
1077 == 7.5 My sensor worked for Helium AU915 before, but now it doesn't work. Why? ==
1078
1079
1080 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.
1081
1082
1083 == 7.6 Why do I see different working temperatures for the device? ==
1084
1085
1086 The working temperature range of the device depends on the battery the user chooses.
1087
1088 * A standard AAA battery can support a working range of -10°C to 50°C.
1089 * 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]]
1090
1091 == 7.7 The device keeps rejoining the network and is not working properly ==
1092
1093
1094 **Cause of the problem:**
1095
1096 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.
1097
1098 **Solution:**
1099
1100 1. Manually restart the device, then downlink 21 03 (only needs to be set once to be effective).
1101 1. Manually restart the device, then set AT+RPL=3 (only needs to be set once to be effective).
1102 1. Update the firmware to version v1.8 or above.
1103
1104 = 8. Ordering Information =
1105
1106
1107 **Part Number: (% style="color:blue" %)LDS02-XXX(%%)**
1108
1109 (% style="color:blue" %)**XXX:**(%%) The default frequency band
1110
1111 * (% style="color:red" %)**EU433**(%%): frequency  bands EU433
1112 * (% style="color:red" %)**EU868**(%%): frequency  bands EU868
1113 * (% style="color:red" %)**KR920**(%%): frequency  bands KR920
1114 * (% style="color:red" %)**CN470**(%%): frequency bands CN470
1115 * (% style="color:red" %)**AS923**(%%): frequency  bands AS923
1116 * (% style="color:red" %)**AU915**(%%): frequency bands AU915
1117 * (% style="color:red" %)**US915**(%%): frequency bands  US915
1118 * (% style="color:red" %)**IN865**(%%):  frequency bands  IN865
1119 * (% style="color:red" %)**CN779**(%%): frequency bands CN779
1120
1121 = 9. Packaging Information =
1122
1123
1124 (((
1125 **Package Includes**:
1126 )))
1127
1128 * (((
1129 LDS02 x 1
1130 )))
1131
1132 (((
1133 **Dimension and weight**:
1134 )))
1135
1136 * (((
1137 Device Size: 69.2 x 29.2 x 14.8 mm
1138
1139
1140 )))
1141
1142 = 10. Support =
1143
1144
1145 * 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.
1146 * 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]].