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

Version 70.24 by Xiaoling on 2022/11/21 11:00

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

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

Applications

Navigation