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

Version 70.4 by Xiaoling on 2022/11/18 10:41

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

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

Applications

Navigation