Wiki source code of NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual

Version 70.1 by Xiaoling on 2022/11/18 10:35

version	line-number	content
1.5	1	(% style="text-align:center" %)
53.2	2	[[image:image-20221117105556-1.png]]
1.5	3
48.2	4
	5
53.2	6
	7
	8
	9
48.2	10	Table of Contents：
	11
67.4	12	{{toc/}}
1.5	13
	14
	15
48.2	16
67.4	17
48.2	18	= 1. Introduction =
	19
53.2	20	== 1.1 What is NDS03A NB-IoT Open/Close Door Sensor ==
48.2	21
	22
52.2	23	(((
53.3	24	The Dragino NDS03A is an (% style="color:blue" %)Open/Close NB-IoT Door Sensor(%%). It detects door (% style="color:blue" %)open/close status(%%) and (% style="color:blue" %)uplinks(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
	25	)))
1.5	26
53.3	27	(((
	28	The NDS03A will send periodically data (% style="color:blue" %)every 4 hours (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
	29	)))
1.5	30
53.3	31	(((
	32	NDS03A has a (% style="color:blue" %)Datalog feature(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
	33	)))
1.5	34
53.3	35	(((
	36	NDS03A has the(% style="color:blue" %)open alarm feature(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
	37	)))
53.2	38
53.3	39	(((
53.2	40	NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
52.2	41	)))
1.5	42
52.2	43	(((
53.3	44	NarrowBand-Internet of Things (NB-IoT) is a (% style="color:blue" %)standards-based low power wide area (LPWA) technologyTCP, MQTT, UDP, and CoAP(%%) for different application requirements.
52.2	45	)))
1.5	46
53.3	47	(((
	48	NDS03A is powered by (% style="color:blue" %)8500mAh Li-SOCI2 battery(%%), It is designed for long-term use of up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	49	)))
	50
	51	(((
	52	To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)NB-IoT SIM card(%%) from the operator and install into NDS03A to get NB-IoT network connection.
	53	)))
	54
	55
35.1	56
48.2	57	== 1.2 Features ==
	58
	59
2.1	60	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
	61	* Open/Close detect
	62	* Open/Close statistics
	63	* Monitor Battery Level
58.2	64	* connect two door sensors
2.1	65	* Datalog feature
34.1	66	* Uplink periodically
2.1	67	* Downlink to change configure
	68	* Wall Mountable
	69	* Outdoor Use
	70	* Ultra-Low Power consumption
	71	* AT Commands to change parameters
	72	* Micro SIM card slot for NB-IoT SIM
34.1	73	* 8500mAh Battery for long-term use
1.5	74
58.2	75	== 1.3 Storage & Operation ==
1.5	76
	77
58.2	78	Temperature -40°C to +85°C
1.5	79
	80
58.2	81	== 1.4 Mechanical ==
48.2	82
1.5	83
58.2	84	[[image:image-20221117114937-4.png]]
1.5	85
52.2	86
58.2	87	[[image:image-20221117114949-5.png]]
1.5	88
38.1	89
58.2	90	[[image:image-20221117115010-6.png]]
31.1	91
58.2	92
	93
48.2	94	== 1.5 Applications ==
	95
	96
58.2	97	[[image:image-20221117114842-3.png]]
1.5	98
	99
48.2	100
58.2	101	== 1.6 Specification ==
1.5	102
	103
58.2	104	(% style="color:blue" %)Common DC Characteristics:
48.2	105
58.2	106	* Supply Voltage: 2.1v ~~ 3.6v
	107	* Operating Temperature: -40 ~~ 85°C
	108
	109	(% style="color:blue" %)NB-IoT Spec:
	110
	111	* - B1 @H-FDD: 2100MHz
	112	* - B3 @H-FDD: 1800MHz
	113	* - B8 @H-FDD: 900MHz
	114	* - B5 @H-FDD: 850MHz
	115	* - B20 @H-FDD: 800MHz
	116	* - B28 @H-FDD: 700MHz
	117
48.2	118	== 1.7 Pin Definitions and Switch ==
	119
52.2	120
31.1	121	[[image:image-20221021110429-4.png]]
1.5	122
	123
48.2	124	=== 1.7.1 Pin Definition ===
	125
	126
58.4	127	The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at: [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
1.5	128
38.1	129
1.5	130
48.2	131	=== 1.7.2 Jumper JP2(Power ON/OFF) ===
	132
	133
2.1	134	Power on Device when putting this jumper.
	135
	136
	137
48.2	138	=== 1.7.3 BOOT MODE / SW1 ===
2.1	139
	140
48.3	141	1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
2.1	142
48.3	143	2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
2.1	144
	145
	146
48.2	147	=== 1.7.4 Reset Button ===
	148
	149
2.1	150	Press to reboot the device.
	151
	152
	153
48.2	154	=== 1.7.5 LED ===
2.1	155
48.2	156
38.1	157	The LED will blink when :
2.1	158
48.2	159	1. Boot the device in flash mode
2.1	160
48.2	161	2. Send an uplink packet
2.1	162
	163
	164
58.2	165	== 1.8 Magnet Distance ==
	166
	167
58.4	168	(% style="color:blue" %)Wood Door:(%%) 10 ~~ 30mm
58.2	169
61.2	170	(% style="color:blue" %)Iron Door:(%%) 30 ~~ 45mm
58.2	171
	172
	173
67.3	174	= 2. Use NDS03A to communicate with IoT Server =
48.2	175
	176	== 2.1 How it works ==
	177
	178
59.2	179	In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
48.2	180
59.2	181	The diagram below shows the working flow in the default firmware of NDS03A:
2.1	182
31.1	183	[[image:image-20221021110615-5.png]]
2.1	184
	185
40.1	186
59.3	187	== 2.2 Configure NDS03A ==
2.1	188
48.2	189	=== 2.2.1 Test Requirement ===
	190
	191
59.2	192	To use NDS03A in your city, make sure to meet below requirements:
2.1	193
40.1	194	* Your local operator has already distributed an NB-IoT Network.
59.3	195	* The local NB-IoT network used the band that NDS03A supports.
2.1	196	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	197
59.2	198	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDS03A will use (% style="color:red" %)CoAP(120.24.4.116:5683)(%%) or raw (% style="color:red" %)UDP(120.24.4.116:5601) (%%)or (% style="color:red" %)MQTT(120.24.4.116:1883) (%%)or (% style="color:red" %)TCP(120.24.4.116:5600)protocol(%%) to send data to the test server.
2.1	199
59.2	200	[[image:image-20221117142300-1.png]]
40.1	201
2.1	202
	203
	204
48.2	205	=== 2.2.2 Insert NB-IoT SIM card ===
	206
	207
2.1	208	Insert the NB-IoT Card get from your provider.
	209
40.1	210	User needs to take out the NB-IoT module and insert the SIM card like below:
2.1	211
31.1	212	[[image:image-20221021110745-6.png]]
2.1	213
40.1	214
2.1	215
59.3	216	=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
2.1	217
	218
59.3	219	User need to configure NDS03A via serial port to set the (% style="color:red" %)Server Address / Uplink Topic(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
2.1	220
48.2	221	(% style="color:blue" %)Connection:
2.1	222
48.2	223	(% style="background-color:yellow" %) USB TTL GND <~-~-~-~-> GND
2.1	224
48.2	225	(% style="background-color:yellow" %) USB TTL TXD <~-~-~-~-> UART_RXD
	226
	227	(% style="background-color:yellow" %) USB TTL RXD <~-~-~-~-> UART_TXD
	228
	229
2.1	230	In the PC, use below serial tool settings:
	231
48.2	232	* Baud: (% style="color:red" %)9600
2.1	233
48.2	234	* Data bits: (% style="color:red" %)8(%%)
	235
	236	* Stop bits: (% style="color:red" %)1
	237
	238	* Parity: (% style="color:red" %)None
	239
	240	* Flow Control: (% style="color:red" %)None
	241
59.3	242	Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)Yellow Jumper(%%).
2.1	243
31.1	244	[[image:image-20221021110817-7.png]]
2.1	245
59.3	246	NDS03A will output system info once powered on as below, we can enter the password: 12345678 to access AT Command input.
40.1	247
	248
48.2	249	(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
2.1	250
42.1	251
2.1	252
48.2	253	=== 2.2.4 Use CoAP protocol to uplink data ===
2.1	254
	255
48.2	256	(% style="color:red" %)Note: if you don't have a CoAP server, you can refer this link to set up a CoAP server: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
42.1	257
2.1	258
67.3	259	(% style="color:blue" %)Use below commands in NDS03A:
48.2	260
48.3	261	* (% style="color:#037691" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
48.2	262
48.3	263	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5683 (%%) ~/~/ Set CoAP server address and port
48.2	264
48.3	265	* (% style="color:#037691" %)AT+URI=0,0,11,2,"mqtt" (%%) ~/~/ Set CoAP resource path
48.2	266
2.1	267	For parameter description, please refer to AT command set
	268
31.1	269	[[image:image-20221021110948-8.png]]
2.1	270
	271
67.3	272	After configuring the server address and (% style="color:green" %)reset NDS03A(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
42.1	273
31.1	274	[[image:image-20221021110956-9.png]]
2.1	275
42.1	276
2.1	277
48.2	278	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
2.1	279
42.1	280
48.2	281	(% style="color:blue" %)AT Commands:
2.1	282
48.3	283	* (% style="color:#037691" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
48.2	284
48.3	285	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ Set UDP server address and port
48.2	286
48.3	287	* (% style="color:#037691" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
48.2	288
32.1	289	[[image:image-20221021111025-10.png]]
2.1	290
48.3	291
31.1	292	[[image:image-20221021111033-11.png\|\|height="241" width="576"]]
2.1	293
	294
	295
	296
48.2	297	=== 2.2.6 Use MQTT protocol to uplink data ===
2.1	298
42.1	299
48.2	300	(% style="color:blue" %)AT Commands:
2.1	301
48.3	302	* (% style="color:#037691" %)AT+PRO=3 (%%) ~/~/ Set to use MQTT protocol to uplink
48.2	303
48.3	304	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
48.2	305
48.3	306	* (% style="color:#037691" %)AT+CLIENT=CLIENT (%%) ~/~/ Set up the CLIENT of MQTT
48.2	307
48.3	308	* (% style="color:#037691" %)AT+UNAME=UNAME (%%) ~/~/ Set the username of MQTT
48.2	309
48.3	310	* (% style="color:#037691" %)AT+PWD=PWD (%%) ~/~/ Set the password of MQTT
48.2	311
48.3	312	* (% style="color:#037691" %)AT+PUBTOPIC=NSE01_PUB (%%) ~/~/ Set the sending topic of MQTT
48.2	313
48.3	314	* (% style="color:#037691" %)AT+SUBTOPIC=NSE01_SUB (%%) ~/~/ Set the subscription topic of MQTT
48.2	315
32.1	316	[[image:image-20221021111058-12.png]]
2.1	317
48.3	318
47.1	319	[[image:image-20221021111201-16.png\|\|height="472" width="653"]]
2.1	320
	321
	322
42.1	323	MQTT protocol has a much higher power consumption compare with UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
2.1	324
42.1	325
48.3	326
48.2	327	=== 2.2.7 Use TCP protocol to uplink data ===
2.1	328
	329
48.3	330	(% style="color:blue" %)AT Commands:
2.1	331
48.3	332	* (% style="color:#037691" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
48.2	333
48.3	334	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ Set TCP server address and port
48.2	335
32.1	336	[[image:image-20221021111125-14.png]]
2.1	337
31.1	338	[[image:image-20221021111131-15.png]]
2.1	339
	340
	341
48.3	342
48.2	343	=== 2.2.8 Change Update Interval ===
2.1	344
	345
48.2	346	User can use below command to change the (% style="color:blue" %)uplink interval.
2.1	347
59.3	348	* (% style="color:#037691" %)AT+TDC=14400 (%%) ~/~/ Set Update Interval to 14400s (4 hours)
2.1	349
48.2	350	(% style="color:red" %)NOTE:
2.1	351
59.3	352	1. By default, the device will send an uplink message every 4 hour.
42.1	353
48.3	354
	355
48.2	356	== 2.3 Uplink Payload ==
2.1	357
48.2	358
61.3	359	The uplink payload includes 26 bytes in total by default.
2.1	360
61.3	361	Each time the device uploads a data package. The user can use the AT+NOUD command to upload the recorded data.Up to 32 sets of recorded data can be uploaded.
2.1	362
61.3	363	(% style="color:blue" %)When AT+TTRCHANNEL=1:
2.1	364
61.3	365	(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
	366	\|=(% scope="row" style="width: 93px;" %)Size(bytes)\|(% style="width:67px" %)8\|(% style="width:40px" %)2\|(% style="width:45px" %)2\|(% style="width:75px" %)1\|(% style="width:54px" %)1\|(% style="width:62px" %)1\|(% style="width:60px" %)1\|(% style="width:94px" %)3\|(% style="width:93px" %)3
67.5	367	\|=(% style="width: 93px;" %)Value\|(% style="width:67px" %)[[Device ID>>\|\|anchor="H2.4.1A0A0DeviceID"]]\|(% style="width:40px" %)[[Ver>>\|\|anchor="H2.4.2A0VersionInfo"]]\|(% style="width:45px" %)[[BAT>>\|\|anchor="H2.4.3A0BatteryInfo"]]\|(% style="width:75px" %)[[Signal Strength>>\|\|anchor="H2.4.4A0SignalStrength"]]\|(% style="width:54px" %)MOD\|(% style="width:62px" %)Door Status\|(% style="width:60px" %)[[Alarm Status>>\|\|anchor="H2.7A0AlarmBaseonTimeout"]]\|(% style="width:94px" %)door open num(pb14) \|(% style="width:93px" %)last open time(pb14)
2.1	368
52.3	369	(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
61.3	370	\|(% style="width:50px" %)4\|(% style="width:70px" %)1\|(% style="width:50px" %)3\|(% style="width:99px" %)3\|(% style="width:67px" %)4\|(% style="width:50px" %)(((
	371	1-32 group
	372	)))
67.6	373	\|(% style="width:98px" %)[[Time stamp>>\|\|anchor="H2.4.7A0Timestamp"]]\|(% style="width:115px" %)Door Status(pb14)\|(% style="width:92px" %)door open num(pb14)\|(% style="width:99px" %)last open time(pb14)\|(% style="width:67px" %)Time stamp\|(% style="width:74px" %)...
48.3	374
61.3	375	(% style="color:blue" %)When AT+TTRCHANNEL=2:
	376
	377
	378	(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
	379	\|=(% scope="row" style="width: 96px;" %)Size(bytes)\|(% style="width:66px" %)8\|(% style="width:40px" %)2\|(% style="width:46px" %)2\|(% style="width:70px" %)1\|(% style="width:54px" %)1\|(% style="width:55px" %)1\|(% style="width:57px" %)1\|(% style="width:86px" %)3\|(% style="width:82px" %)3
67.5	380	\|=(% style="width: 96px;" %)Value\|(% style="width:66px" %)[[Device ID>>\|\|anchor="H2.4.1A0A0DeviceID"]]\|(% style="width:40px" %)[[Ver>>\|\|anchor="H2.4.2A0VersionInfo"]]\|(% style="width:46px" %)[[BAT>>\|\|anchor="H2.4.3A0BatteryInfo"]]\|(% style="width:70px" %)[[Signal Strength>>\|\|anchor="H2.4.4A0SignalStrength"]]\|(% style="width:54px" %)MOD\|(% style="width:55px" %)Door Status(pb14)\|(% style="width:57px" %)[[Alarm Status>>\|\|anchor="H2.7A0AlarmBaseonTimeout"]](pb14)\|(% style="width:86px" %)door open num(pb14) \|(% style="width:82px" %)last open time(pb14)
61.3	381
	382	(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
	383	\|(% style="width:59px" %)1\|(% style="width:67px" %)1\|(% style="width:88px" %)3\|(% style="width:81px" %)3\|(% style="width:50px" %)4\|(% style="width:66px" %)1\|(% style="width:92px" %)3
67.6	384	\|(% style="width:59px" %)Door Status(pb15)\|(% style="width:67px" %)[[Alarm Status>>\|\|anchor="H2.7A0AlarmBaseonTimeout"]](pb15)\|(% style="width:88px" %)door open num(pb15)\|(% style="width:81px" %)last open time(pb15)\|(% style="width:50px" %)[[Time stamp>>\|\|anchor="H2.4.7A0Timestamp"]]\|(% style="width:66px" %)Door Status(pb14)\|(% style="width:92px" %)door open num(pb14)
61.3	385
	386	(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
	387	\|(% style="width:102px" %)3\|(% style="width:93px" %)1\|(% style="width:91px" %)3\|(% style="width:88px" %)3\|(% style="width:63px" %)4\|(% style="width:87px" %)(((
	388	1-32 group
	389	)))
67.6	390	\|(% style="width:102px" %)last open time (pb14)\|(% style="width:93px" %)Door Status(pb15)\|(% style="width:91px" %)door open num(pb15)\|(% style="width:88px" %)last open time(pb15)\|(% style="width:63px" %)[[Time stamp>>\|\|anchor="H2.4.7A0Timestamp"]]\|(% style="width:87px" %)......
61.3	391
61.2	392	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
2.1	393
61.2	394	[[image:image-20221117145932-2.png]]
2.1	395
48.3	396
2.1	397	The payload is ASCII string, representative same HEX:
	398
61.2	399	0x (% style="color:red" %)__f867787050213317__ (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)
	400
48.2	401	where:
2.1	402
48.13	403	* (% style="color:#037691" %)Device ID:(%%) 0x f867787050213317 = f867787050213317
2.1	404
48.13	405	* (% style="color:#037691" %)Version:(%%) 0x0064=100=1.0.0
33.1	406
61.2	407	* (% style="color:#037691" %)BAT :(%%) 0x0ccf = 3279 mV = 3.279V
33.1	408
61.2	409	* (% style="color:#037691" %)Singal: (%%)0x19 = 25
33.1	410
48.13	411	* (% style="color:#037691" %)Mod:(%%) 0x01 = 1
33.1	412
61.2	413	* (% style="color:#037691" %)Door Status:(%%) 0x00=0
33.1	414
61.2	415	* (% style="color:#037691" %)Alarm Status: (%%)0x00 =0
33.1	416
61.2	417	* (% style="color:#037691" %)door open num: (%%)0x000016 =22
33.1	418
61.2	419	* (% style="color:#037691" %)last open time: (%%)0x000017 =23
33.1	420
61.2	421	* (% style="color:#037691" %)Timestamp:(%%) 0x637590df =1668649183 (Unix Time)
33.1	422
48.2	423	== 2.4 Payload Explanation and Sensor Interface ==
	424
	425	=== 2.4.1 Device ID ===
	426
	427
42.1	428	By default, the Device ID is equal to the last 15 bits of IMEI.
2.1	429
48.2	430	User can use (% style="color:blue" %)AT+DEUI (%%)to set Device ID
2.1	431
	432	Example:
	433
	434	AT+DEUI=868411056754138
	435
42.1	436	The Device ID is stored in a non-erase area, Upgrade the firmware or run AT+FDR won't erase the Device ID.
2.1	437
42.1	438
48.2	439	=== 2.4.2 Version Info ===
	440
	441
42.1	442	Specify the software version: 0x64=100, which means firmware version 1.00.
2.1	443
61.5	444	For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
2.1	445
42.1	446
48.2	447	=== 2.4.3 Battery Info ===
	448
	449
61.5	450	Check the battery voltage for NDS03A.
2.1	451
	452	Ex1: 0x0B45 = 2885mV
	453
	454	Ex2: 0x0B49 = 2889mV
	455
42.1	456
48.2	457	=== 2.4.4 Signal Strength ===
	458
	459
2.1	460	NB-IoT Network signal Strength.
	461
	462	Ex1: 0x1d = 29
	463
	464	0 -113dBm or less
	465
	466	1 -111dBm
	467
	468	2...30 -109dBm... -53dBm
	469
	470	31 -51dBm or greater
	471
	472	99 Not known or not detectable
	473
42.1	474
61.5	475	=== 2.4.5 Disalarm: (default: 0) ===
48.2	476
	477
61.5	478	(% style="color:blue" %)If Disalarm = 1(%%), NDS03A will only send uplink at every TDC periodically. This is normally use for pulse meter application, in this application, there are many open/close event, and platform only care about the total number of pulse.
2.1	479
61.5	480	(% style="color:blue" %)If Disalarm = 0(%%), NDS03A will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time.
2.1	481
61.5	482	(% style="color:red" %)Note:(%%) When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast.
2.1	483
	484
61.6	485	=== 2.4.6 Keep Status & Keep Time ===
42.1	486
48.2	487
61.6	488	Shows the configure value of Alarm Base on Timeout Feature
48.2	489
2.1	490
61.6	491	=== 2.4.7 Timestamp ===
42.1	492
2.1	493
61.6	494	Timestamp : 0x6315537b =1662342011
48.2	495
	496
2.1	497
61.6	498	=== 2.4.8 Switch Dual Channel Mode ===
2.1	499
42.1	500
61.6	501	NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
2.1	502
48.2	503
	504	== 2.5 Downlink Payload ==
	505
	506
61.7	507	By default, NDS03A prints the downlink payload to console port.
2.1	508
31.1	509	[[image:image-20221021111414-18.png]]
2.1	510
48.2	511
2.1	512	Examples:
	513
48.2	514	* (% style="color:#037691" %)Set TDC
2.1	515
	516	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
	517
	518	Payload: 01 00 00 1E TDC=30S
	519
	520	Payload: 01 00 00 3C TDC=60S
	521
48.2	522	* (% style="color:#037691" %)Reset
2.1	523
65.2	524	If payload = 0x04FF, it will reset the NDS03A
2.1	525
48.2	526	* (% style="color:#037691" %)INTMOD
2.1	527
	528	Downlink Payload: 06000003, Set AT+INTMOD=3
	529
	530
48.2	531
	532	== 2.6 LED Indicator ==
	533
	534
65.2	535	The NDS03A has an internal LED which is to show the status of different states.
2.1	536
45.1	537	* When the device starts normally, the LED will light up for 1 second.
67.3	538	* After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
2.1	539	* For each uplink probe, LED will be on for 500ms.
	540
48.2	541	== 2.7 Alarm Base on Timeout ==
2.1	542
48.2	543
65.2	544	NDS03A can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are:
2.1	545
	546
48.2	547	(% style="color:blue" %)1. Keep Status: Status to be monitor
2.1	548
	549	Keep Status = 1: Monitor Close to Open event
	550
	551	Keep Status = 0: Monitor Open to Close event
	552
	553
48.2	554	(% style="color:blue" %)2. Keep Time: Timeout to send an Alarm
2.1	555
	556	Range 0 ~~ 65535(0xFFFF) seconds.
	557
	558	If keep time = 0, Disable Alarm Base on Timeout feature.
	559
65.2	560	If keep time > 0, device will monitor the keep status event and send an alarm when status doesn't change after timeout.
2.1	561
	562
48.2	563	(% style="color:blue" %)AT Command to configure:
2.1	564
65.2	565	(% style="color:blue" %)PB14 PIN:
	566
67.3	567	(% style="color:#037691" %)AT+TTRIG=1,30 (%%) ~-~-> When the Keep Status change from connected to disconnect, and device remains in disconnect status for more than 30 seconds. NDS03A will send an uplink packet, the [[Alarm bit>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/#H2.3.3Real-TimeOpen2FCloseStatus2CUplinkFPORT3D2]] (the second bit of 1^^st^^ byte of payload) on this uplink packet is set to 1.
2.1	568
48.2	569	(% style="color:#037691" %)AT+TTRIG=0,0 (%%) ~-~-> Default Value, disable timeout Alarm.
2.1	570
42.1	571
65.2	572	(% style="color:blue" %)PB15 PIN:
2.1	573
65.2	574	(% style="color:#037691" %)AT+TTRIG2=1,30
	575
	576	(% style="color:#037691" %)AT+TTRIG2=0,0
	577
	578
48.2	579	== 2.8 Set debug mode ==
	580
	581
2.1	582	Feature: Enable or Disable debug mode
	583
48.2	584	(% style="color:blue" %)AT Command: AT+DEBUG
2.1	585
31.1	586	[[image:image-20221021111629-21.png]]
2.1	587
	588
48.2	589
	590	== 2.9 Clear Flash Record ==
	591
	592
2.1	593	Feature: Clear flash storage for data log feature.
	594
48.2	595	(% style="color:blue" %)AT Command: AT+CLRDTA
2.1	596
31.1	597	[[image:image-20221021111527-19.png]]
2.1	598
	599
	600
65.2	601	== 2.10 Count Mod ==
48.2	602
	603
65.2	604	(% style="color:blue" %)AT Command: AT+COUNTMOD
48.2	605
65.2	606	[[image:image-20221118092935-1.png]]
2.1	607
	608
	609
65.2	610	== 2.11 Interrupt Pin Channel Mod ==
48.2	611
	612
65.2	613	(% style="color:blue" %)AT Command: AT+TTRCHANNEL
48.2	614
65.2	615	[[image:image-20221118093144-2.png]]
2.1	616
	617
	618
65.2	619	== 2.12 TTRIG1/2 timeout status alarm ==
2.1	620
48.2	621
65.2	622	It needs to be used with AT+TTRIG1 or AT+TTRIG2. When TTRIG1 or TTRIG2 times out and causes an alarm, and the status does not change subsequently, an alarm packet will be sent at the alarm interval.
48.2	623
65.2	624	(% style="color:blue" %)AT Command: AT+TTRALARM
48.2	625
65.2	626	[[image:image-20221118093512-3.png]]
2.1	627
	628
	629
65.2	630	== 2.13 Select counting mode ==
2.1	631
	632
65.2	633	(% style="color:blue" %)AT Command: AT+TTRMODx=a,b
2.1	634
65.2	635	When (% style="color:red" %)a=0(%%), the door is opened to count, and when (% style="color:red" %)a=1(%%),the closed door is counted.
2.1	636
65.2	637	When (% style="color:red" %)b=0(%%), it is the last door open duration, and when (% style="color:red" %)b=1(%%),the last door close duration.
2.1	638
65.2	639	[[image:image-20221118093658-4.png]]
2.1	640
	641
48.2	642
65.2	643
66.2	644	== 2.14 Set the number of data to be uploaded and the recording time ==
48.2	645
	646
	647	(% style="color:blue" %)AT Command:
	648
66.2	649	(% style="color:#037691" %)AT+TR=900(%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
	650
	651	(% style="color:#037691" %)AT+NOUD=8(%%) ~/~/ The device uploads 0 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	652
	653
	654	== 2.15 Read or Clear cached data ==
	655
	656
	657	(% style="color:blue" %)AT Command:
	658
48.2	659	(% style="color:#037691" %)AT+CDP (%%) ~/~/ Read cached data
	660
	661	(% style="color:#037691" %)AT+CDP=0 (%%) ~/~/ Clear cached data
	662
66.2	663	[[image:image-20221118094227-5.png]]
2.1	664
	665
	666
66.2	667	== 2.16 Firmware Change Log ==
2.1	668
48.2	669
48.14	670	Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
2.1	671
48.12	672	Upgrade Instruction: [[Upgrade Firmware>>\|\|anchor="H5.1200BHowtoUpgradeFirmware"]]
2.1	673
	674
	675
67.2	676	== 2.17 Battery Analysis ==
48.2	677
	678
67.2	679	=== 2.17.1 Battery Type ===
48.2	680
	681
67.2	682	The NDS03A battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
2.1	683
42.1	684	The battery is designed to last for several years depends on the actual use environment and update interval.
2.1	685
42.1	686	The battery-related documents as below:
2.1	687
	688	* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
48.2	689
2.1	690	* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
48.2	691
2.1	692	* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	693
31.1	694	[[image:image-20221021111911-26.png]]
2.1	695
	696
48.2	697
67.2	698	=== 2.17.2 Power consumption Analyze ===
48.2	699
	700
2.1	701	Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
	702
	703	Instruction to use as below:
	704
48.2	705	(% style="color:blue" %)Step 1: (%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
2.1	706
48.2	707	(% style="color:blue" %)Step 2: (%%) Open it and choose
2.1	708
	709	* Product Model
48.2	710
2.1	711	* Uplink Interval
48.2	712
2.1	713	* Working Mode
	714
	715	And the Life expectation in difference case will be shown on the right.
	716
48.2	717	[[image:1666596205057-567.png]]
2.1	718
	719
48.2	720
67.2	721	=== 2.17.3 Battery Note ===
48.2	722
	723
2.1	724	The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
	725
	726
48.2	727
67.2	728	=== 2.17.4 Replace the battery ===
48.2	729
	730
67.3	731	The default battery pack of NDS03A includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
2.1	732
42.1	733
2.1	734
48.2	735	= 3. Access NB-IoT Module =
	736
	737
2.1	738	Users can directly access the AT command set of the NB-IoT module.
	739
	740	The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]
	741
67.2	742	[[image:image-20221118094449-6.png]]
2.1	743
	744
	745
48.2	746	= 4. Using the AT Commands =
	747
	748
	749	== 4.1 Access AT Commands ==
	750
	751
2.1	752	See this link for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
	753
	754	AT+<CMD>? : Help on <CMD>
	755
	756	AT+<CMD> : Run <CMD>
	757
	758	AT+<CMD>=<value> : Set the value
	759
	760	AT+<CMD>=? : Get the value
	761
	762
48.2	763	(% style="color:blue" %)General Commands
	764
2.1	765	AT : Attention
	766
	767	AT? : Short Help
	768
	769	ATZ : MCU Reset
	770
	771	AT+TDC : Application Data Transmission Interval
	772
	773	AT+CFG : Print all configurations
	774
	775	AT+CFGMOD : Working mode selection
	776
	777	AT+INTMOD : Set the trigger interrupt mode
	778
	779	AT+5VT : Set extend the time of 5V power
	780
	781	AT+PRO : Choose agreement
	782
	783	AT+RXDL : Extend the sending and receiving time
	784
	785	AT+SERVADDR : Server Address
	786
48.2	787	AT+TR : Get or Set record time
2.1	788
	789	AT+NOUD : Get or Set the number of data to be uploaded
	790
48.2	791	AT+CDP : Read or Clear cached data
2.1	792
	793	AT+ DEBUG : Enable or Disable debug mode
	794
67.2	795	AT+ TTRIG1 : Get or Set PB14 PIN Alarm Base on Timeout
2.1	796
67.2	797	AT+ TTRIG2 : Get or Set PB15 PIN Alarm Base on Timeout
2.1	798
67.2	799	AT+COUNTMOD : Get or Set the count mode
2.1	800
67.2	801	AT+TTRCHANNEL : Get or Set the number of interrupt channels
2.1	802
67.2	803	AT+TTRALARM : Get or Set TTRIG1 of Alarm interval (unit: minute)
2.1	804
67.2	805	AT+DISALARM : Enable/Disable Alarm for door open/close or water leak event
	806
	807	AT+ CLRC : Clear current door open count
	808
	809
48.2	810	(% style="color:blue" %)COAP Management
	811
2.1	812	AT+URI : Resource parameters
	813
	814
48.2	815	(% style="color:blue" %)UDP Management
	816
2.1	817	AT+CFM : Upload confirmation mode (only valid for UDP)
	818
	819
48.2	820	(% style="color:blue" %)MQTT Management
	821
2.1	822	AT+CLIENT : Get or Set MQTT client
	823
	824	AT+UNAME : Get or Set MQTT Username
	825
	826	AT+PWD : Get or Set MQTT password
	827
	828	AT+PUBTOPIC : Get or Set MQTT publish topic
	829
	830	AT+SUBTOPIC : Get or Set MQTT subscription topic
	831
	832
48.2	833	(% style="color:blue" %)Information
	834
2.1	835	AT+FDR : Factory Data Reset
	836
	837	AT+PWORD : Serial Access Password
	838
	839
	840
48.2	841	= 5. FAQ =
2.1	842
	843
48.2	844	== 5.1 How to Upgrade Firmware ==
2.1	845
	846
48.2	847	User can upgrade the firmware for 1) bug fix, 2) new feature release.
2.1	848
48.2	849	Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
2.1	850
67.2	851	(% style="color:red" %)Notice: (% style="color:blue" %)NDS03A (%%)and (% style="color:blue" %)LDS03A(%%)(% style="color:blue" %) (%%)share the same mother board. They use the same connection and method to update.
2.1	852
42.1	853
2.1	854
48.2	855	= 6. Trouble Shooting =
2.1	856
42.1	857
48.2	858	== 6.1 Connection problem when uploading firmware ==
2.1	859
	860
48.2	861	(% style="color:blue" %)Please see: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
42.1	862
2.1	863
	864
48.2	865	== 6.2 AT Command input doesn't work ==
2.1	866
	867
48.2	868	In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)ENTER(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)ENTER (%%)while press the send key, user need to add ENTER in their string.
2.1	869
	870
	871
48.2	872	= 7. Order Info =
2.1	873
	874
67.2	875	Part Number: NDS03A
2.1	876
	877
	878
48.2	879	= 8. Packing Info =
2.1	880
	881
48.2	882	(% style="color:blue" %)Package Includes:
2.1	883
67.2	884	* NDS03A Open/Close Door Sensor x 1
2.1	885
48.2	886	= 9. Support =
2.1	887
	888
48.2	889	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
2.1	890
48.2	891	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
2.1	892
48.2	893

Wiki source code of NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual

Applications