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

Last modified by Mengting Qiu on 2024/04/02 16:55

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

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

Applications

Navigation