Wiki source code of LDS02 - LoRaWAN Door Sensor User Manual

Last modified by kai on 2025/02/26 15:43

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

Wiki source code of LDS02 - LoRaWAN Door Sensor User Manual

Applications

Navigation