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