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

Version 62.1 by Xiaoling on 2022/11/18 09:29

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
1.5	12
	13
	14
48.2	15
	16	= 1. Introduction =
	17
53.2	18	== 1.1 What is NDS03A NB-IoT Open/Close Door Sensor ==
48.2	19
	20
52.2	21	(((
53.3	22	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.
	23	)))
1.5	24
53.3	25	(((
	26	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.
	27	)))
1.5	28
53.3	29	(((
	30	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.
	31	)))
1.5	32
53.3	33	(((
	34	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.
	35	)))
53.2	36
53.3	37	(((
53.2	38	NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
52.2	39	)))
1.5	40
52.2	41	(((
53.3	42	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	43	)))
1.5	44
53.3	45	(((
	46	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)
	47	)))
	48
	49	(((
	50	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.
	51	)))
	52
	53
35.1	54
48.2	55	== 1.2 Features ==
	56
	57
2.1	58	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
	59	* Open/Close detect
	60	* Open/Close statistics
	61	* Monitor Battery Level
58.2	62	* connect two door sensors
2.1	63	* Datalog feature
34.1	64	* Uplink periodically
2.1	65	* Downlink to change configure
	66	* Wall Mountable
	67	* Outdoor Use
	68	* Ultra-Low Power consumption
	69	* AT Commands to change parameters
	70	* Micro SIM card slot for NB-IoT SIM
34.1	71	* 8500mAh Battery for long-term use
1.5	72
58.2	73	== 1.3 Storage & Operation ==
1.5	74
	75
58.2	76	Temperature -40°C to +85°C
1.5	77
	78
58.2	79	== 1.4 Mechanical ==
48.2	80
1.5	81
58.2	82	[[image:image-20221117114937-4.png]]
1.5	83
52.2	84
58.2	85	[[image:image-20221117114949-5.png]]
1.5	86
38.1	87
58.2	88	[[image:image-20221117115010-6.png]]
31.1	89
58.2	90
	91
48.2	92	== 1.5 Applications ==
	93
	94
58.2	95	[[image:image-20221117114842-3.png]]
1.5	96
	97
48.2	98
58.2	99	== 1.6 Specification ==
1.5	100
	101
58.2	102	(% style="color:blue" %)Common DC Characteristics:
48.2	103
58.2	104	* Supply Voltage: 2.1v ~~ 3.6v
	105	* Operating Temperature: -40 ~~ 85°C
	106
	107	(% style="color:blue" %)NB-IoT Spec:
	108
	109	* - B1 @H-FDD: 2100MHz
	110	* - B3 @H-FDD: 1800MHz
	111	* - B8 @H-FDD: 900MHz
	112	* - B5 @H-FDD: 850MHz
	113	* - B20 @H-FDD: 800MHz
	114	* - B28 @H-FDD: 700MHz
	115
48.2	116	== 1.7 Pin Definitions and Switch ==
	117
52.2	118
31.1	119	[[image:image-20221021110429-4.png]]
1.5	120
	121
48.2	122	=== 1.7.1 Pin Definition ===
	123
	124
58.4	125	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	126
38.1	127
1.5	128
48.2	129	=== 1.7.2 Jumper JP2(Power ON/OFF) ===
	130
	131
2.1	132	Power on Device when putting this jumper.
	133
	134
	135
48.2	136	=== 1.7.3 BOOT MODE / SW1 ===
2.1	137
	138
48.3	139	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	140
48.3	141	2) Flash: working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
2.1	142
	143
	144
48.2	145	=== 1.7.4 Reset Button ===
	146
	147
2.1	148	Press to reboot the device.
	149
	150
	151
48.2	152	=== 1.7.5 LED ===
2.1	153
48.2	154
38.1	155	The LED will blink when :
2.1	156
48.2	157	1. Boot the device in flash mode
2.1	158
48.2	159	2. Send an uplink packet
2.1	160
	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
	171
48.2	172	= 2. Use CPN01 to communicate with IoT Server =
	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
40.1	184
59.3	185	== 2.2 Configure NDS03A ==
2.1	186
48.2	187	=== 2.2.1 Test Requirement ===
	188
	189
59.2	190	To use NDS03A in your city, make sure to meet below requirements:
2.1	191
40.1	192	* Your local operator has already distributed an NB-IoT Network.
59.3	193	* The local NB-IoT network used the band that NDS03A supports.
2.1	194	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	195
59.2	196	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	197
59.2	198	[[image:image-20221117142300-1.png]]
40.1	199
2.1	200
	201
	202
48.2	203	=== 2.2.2 Insert NB-IoT SIM card ===
	204
	205
2.1	206	Insert the NB-IoT Card get from your provider.
	207
40.1	208	User needs to take out the NB-IoT module and insert the SIM card like below:
2.1	209
31.1	210	[[image:image-20221021110745-6.png]]
2.1	211
40.1	212
2.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
48.2	257	(% style="color:blue" %)Use below commands in CPN01:
	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
59.3	270	After configuring the server address and (% style="color:green" %)reset CPN01(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
42.1	271
31.1	272	[[image:image-20221021110956-9.png]]
2.1	273
42.1	274
2.1	275
48.2	276	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
2.1	277
42.1	278
48.2	279	(% style="color:blue" %)AT Commands:
2.1	280
48.3	281	* (% style="color:#037691" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
48.2	282
48.3	283	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ Set UDP server address and port
48.2	284
48.3	285	* (% style="color:#037691" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
48.2	286
32.1	287	[[image:image-20221021111025-10.png]]
2.1	288
48.3	289
31.1	290	[[image:image-20221021111033-11.png\|\|height="241" width="576"]]
2.1	291
	292
	293
	294
48.2	295	=== 2.2.6 Use MQTT protocol to uplink data ===
2.1	296
42.1	297
48.2	298	(% style="color:blue" %)AT Commands:
2.1	299
48.3	300	* (% style="color:#037691" %)AT+PRO=3 (%%) ~/~/ Set to use MQTT protocol to uplink
48.2	301
48.3	302	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
48.2	303
48.3	304	* (% style="color:#037691" %)AT+CLIENT=CLIENT (%%) ~/~/ Set up the CLIENT of MQTT
48.2	305
48.3	306	* (% style="color:#037691" %)AT+UNAME=UNAME (%%) ~/~/ Set the username of MQTT
48.2	307
48.3	308	* (% style="color:#037691" %)AT+PWD=PWD (%%) ~/~/ Set the password of MQTT
48.2	309
48.3	310	* (% style="color:#037691" %)AT+PUBTOPIC=NSE01_PUB (%%) ~/~/ Set the sending topic of MQTT
48.2	311
48.3	312	* (% style="color:#037691" %)AT+SUBTOPIC=NSE01_SUB (%%) ~/~/ Set the subscription topic of MQTT
48.2	313
32.1	314	[[image:image-20221021111058-12.png]]
2.1	315
48.3	316
47.1	317	[[image:image-20221021111201-16.png\|\|height="472" width="653"]]
2.1	318
	319
	320
42.1	321	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	322
42.1	323
48.3	324
48.2	325	=== 2.2.7 Use TCP protocol to uplink data ===
2.1	326
	327
48.3	328	(% style="color:blue" %)AT Commands:
2.1	329
48.3	330	* (% style="color:#037691" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
48.2	331
48.3	332	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ Set TCP server address and port
48.2	333
32.1	334	[[image:image-20221021111125-14.png]]
2.1	335
31.1	336	[[image:image-20221021111131-15.png]]
2.1	337
	338
	339
48.3	340
48.2	341	=== 2.2.8 Change Update Interval ===
2.1	342
	343
48.2	344	User can use below command to change the (% style="color:blue" %)uplink interval.
2.1	345
59.3	346	* (% style="color:#037691" %)AT+TDC=14400 (%%) ~/~/ Set Update Interval to 14400s (4 hours)
2.1	347
48.2	348	(% style="color:red" %)NOTE:
2.1	349
59.3	350	1. By default, the device will send an uplink message every 4 hour.
42.1	351
48.3	352
	353
48.2	354	== 2.3 Uplink Payload ==
2.1	355
48.2	356
61.3	357	The uplink payload includes 26 bytes in total by default.
2.1	358
61.3	359	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	360
61.3	361	(% style="color:blue" %)When AT+TTRCHANNEL=1:
2.1	362
61.3	363	(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:693px" %)
	364	\|=(% 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
	365	\|=(% 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.4.6A0Alarm"]]\|(% style="width:94px" %)door open num(pb14) \|(% style="width:93px" %)last open time(pb14)
2.1	366
52.3	367	(% border="1.5" style="background-color:#ffffcc; color:green; width:490px" %)
61.3	368	\|(% style="width:50px" %)4\|(% style="width:70px" %)1\|(% style="width:50px" %)3\|(% style="width:99px" %)3\|(% style="width:67px" %)4\|(% style="width:50px" %)(((
	369	1-32 group
	370	)))
	371	\|(% style="width:98px" %)[[Time stamp>>\|\|anchor="H2.4.10A0Timestamp"]]\|(% 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	372
61.3	373	(% style="color:blue" %)When AT+TTRCHANNEL=2:
	374
	375
	376	(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
	377	\|=(% 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
	378	\|=(% 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\|(% style="width:57px" %)[[Alarm Status>>\|\|anchor="H2.4.6A0Alarm"]]\|(% style="width:86px" %)door open num(pb14) \|(% style="width:82px" %)last open time(pb14)
	379
	380	(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:520px" %)
	381	\|(% 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
	382	\|(% style="width:59px" %)Door Status(pb15)\|(% style="width:67px" %)[[Alarm Status>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPN01-%20NB-IoT%20Outdoor%20OpenClose%20Dry%20Contact%20Sensor%C2%A0User%20Manual/#H2.4.7A0ContactStatus]](pb15)\|(% style="width:88px" %)door open num(pb15)\|(% style="width:81px" %)last open time(pb15)\|(% style="width:50px" %)Time stamp\|(% style="width:66px" %)Door Status(pb14)\|(% style="width:92px" %)door open num(pb14)
	383
	384	(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:500px" %)
	385	\|(% style="width:102px" %)3\|(% style="width:93px" %)1\|(% style="width:91px" %)3\|(% style="width:88px" %)3\|(% style="width:63px" %)4\|(% style="width:87px" %)(((
	386	1-32 group
	387	)))
	388	\|(% 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\|(% style="width:87px" %)...
	389
61.2	390	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	391
61.2	392	[[image:image-20221117145932-2.png]]
2.1	393
48.3	394
2.1	395	The payload is ASCII string, representative same HEX:
	396
61.2	397	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__(%%)
	398
48.2	399	where:
2.1	400
48.13	401	* (% style="color:#037691" %)Device ID:(%%) 0x f867787050213317 = f867787050213317
2.1	402
48.13	403	* (% style="color:#037691" %)Version:(%%) 0x0064=100=1.0.0
33.1	404
61.2	405	* (% style="color:#037691" %)BAT :(%%) 0x0ccf = 3279 mV = 3.279V
33.1	406
61.2	407	* (% style="color:#037691" %)Singal: (%%)0x19 = 25
33.1	408
48.13	409	* (% style="color:#037691" %)Mod:(%%) 0x01 = 1
33.1	410
61.2	411	* (% style="color:#037691" %)Door Status:(%%) 0x00=0
33.1	412
61.2	413	* (% style="color:#037691" %)Alarm Status: (%%)0x00 =0
33.1	414
61.2	415	* (% style="color:#037691" %)door open num: (%%)0x000016 =22
33.1	416
61.2	417	* (% style="color:#037691" %)last open time: (%%)0x000017 =23
33.1	418
61.2	419	* (% style="color:#037691" %)Timestamp:(%%) 0x637590df =1668649183 (Unix Time)
33.1	420
48.2	421	== 2.4 Payload Explanation and Sensor Interface ==
	422
	423
	424	=== 2.4.1 Device ID ===
	425
	426
42.1	427	By default, the Device ID is equal to the last 15 bits of IMEI.
2.1	428
48.2	429	User can use (% style="color:blue" %)AT+DEUI (%%)to set Device ID
2.1	430
	431	Example:
	432
	433	AT+DEUI=868411056754138
	434
42.1	435	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	436
42.1	437
48.2	438	=== 2.4.2 Version Info ===
	439
	440
42.1	441	Specify the software version: 0x64=100, which means firmware version 1.00.
2.1	442
61.5	443	For example 0x00 64 : This device is NDS03A 1 with firmware version 1.0.0.
2.1	444
42.1	445
48.2	446	=== 2.4.3 Battery Info ===
	447
	448
61.5	449	Check the battery voltage for NDS03A.
2.1	450
	451	Ex1: 0x0B45 = 2885mV
	452
	453	Ex2: 0x0B49 = 2889mV
	454
42.1	455
48.2	456	=== 2.4.4 Signal Strength ===
	457
	458
2.1	459	NB-IoT Network signal Strength.
	460
	461	Ex1: 0x1d = 29
	462
	463	0 -113dBm or less
	464
	465	1 -111dBm
	466
	467	2...30 -109dBm... -53dBm
	468
	469	31 -51dBm or greater
	470
	471	99 Not known or not detectable
	472
42.1	473
61.5	474	=== 2.4.5 Disalarm: (default: 0) ===
48.2	475
	476
61.5	477	(% 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	478
61.5	479	(% 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	480
61.5	481	(% 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	482
	483
61.6	484	=== 2.4.6 Keep Status & Keep Time ===
42.1	485
48.2	486
61.6	487	Shows the configure value of Alarm Base on Timeout Feature
48.2	488
2.1	489
61.6	490	=== 2.4.7 Timestamp ===
42.1	491
2.1	492
61.6	493	Timestamp : 0x6315537b =1662342011
48.2	494
	495
2.1	496
61.6	497	=== 2.4.8 Switch Dual Channel Mode ===
2.1	498
42.1	499
61.6	500	NDS03A can connect two door sensors. Another door sensor can be connected to PB15 pin. Both channels support alarm function.
2.1	501
48.2	502
	503	== 2.5 Downlink Payload ==
	504
	505
61.7	506	By default, NDS03A prints the downlink payload to console port.
2.1	507
31.1	508	[[image:image-20221021111414-18.png]]
2.1	509
48.2	510
2.1	511	Examples:
	512
48.2	513	* (% style="color:#037691" %)Set TDC
2.1	514
	515	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
	516
	517	Payload: 01 00 00 1E TDC=30S
	518
	519	Payload: 01 00 00 3C TDC=60S
	520
48.2	521	* (% style="color:#037691" %)Reset
2.1	522
	523	If payload = 0x04FF, it will reset the NSE01
	524
48.2	525	* (% style="color:#037691" %)INTMOD
2.1	526
	527	Downlink Payload: 06000003, Set AT+INTMOD=3
	528
	529
48.2	530
	531	== 2.6 LED Indicator ==
	532
	533
42.1	534	The CPN01 has an internal LED which is to show the status of different states.
2.1	535
45.1	536	* When the device starts normally, the LED will light up for 1 second.
2.1	537	* After CPN01 join NB-IoT network. The LED will be ON for 3 seconds.
	538	* For each uplink probe, LED will be on for 500ms.
	539
48.2	540	== 2.7 Alarm Base on Timeout ==
2.1	541
48.2	542
42.1	543	CPN01 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	544
	545
48.2	546	(% style="color:blue" %)1. Keep Status: Status to be monitor
2.1	547
	548	Keep Status = 1: Monitor Close to Open event
	549
	550	Keep Status = 0: Monitor Open to Close event
	551
	552
48.2	553	(% style="color:blue" %)2. Keep Time: Timeout to send an Alarm
2.1	554
	555	Range 0 ~~ 65535(0xFFFF) seconds.
	556
	557	If keep time = 0, Disable Alarm Base on Timeout feature.
	558
	559	If keep time > 0, device will monitor the keep status event and send an alarm when status doesn’t change after timeout.
	560
	561
48.2	562	(% style="color:blue" %)AT Command to configure:
2.1	563
48.2	564	(% 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. CPN01 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	565
48.2	566	(% style="color:#037691" %)AT+TTRIG=0,0 (%%) ~-~-> Default Value, disable timeout Alarm.
2.1	567
42.1	568
2.1	569
48.2	570	== 2.8 Set debug mode ==
	571
	572
2.1	573	Feature: Enable or Disable debug mode
	574
48.2	575	(% style="color:blue" %)AT Command: AT+DEBUG
2.1	576
31.1	577	[[image:image-20221021111629-21.png]]
2.1	578
	579
48.2	580
	581	== 2.9 Clear Flash Record ==
	582
	583
2.1	584	Feature: Clear flash storage for data log feature.
	585
48.2	586	(% style="color:blue" %)AT Command: AT+CLRDTA
2.1	587
31.1	588	[[image:image-20221021111527-19.png]]
2.1	589
	590
	591
48.2	592	== 2.10 Set trigger mode ==
	593
	594
	595	(% style="color:blue" %)AT Command: AT+TTRMOD
	596
2.1	597	Feature: Set the trigger interrupt mode.
	598
31.1	599	[[image:image-20221021111552-20.png]]
2.1	600
	601
48.2	602
	603	== 2.11 Set the calculate flag ==
	604
	605
2.1	606	Feature: Set the calculate flag
	607
48.2	608	(% style="color:blue" %)AT Command: AT+CALCFLAG
2.1	609
31.1	610	[[image:image-20221021111711-22.png]]
2.1	611
	612
48.2	613
	614	== 2.12 Set count number ==
	615
	616
2.1	617	Feature: Manually set the count number
	618
48.2	619	(% style="color:blue" %)AT Command: AT+SETCNT
2.1	620
31.1	621	[[image:image-20221021111748-24.png]]
2.1	622
	623
	624
48.2	625	== 2.13 Set the number of data to be uploaded and the recording time ==
2.1	626
	627
48.2	628	(% style="color:blue" %)AT Command:
2.1	629
48.2	630	(% 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)
2.1	631
48.2	632	(% style="color:#037691" %)AT+NOUD=8 (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
2.1	633
	634
48.2	635
	636	== 2.14 Read or Clear cached data ==
	637
	638
	639	(% style="color:blue" %)AT Command:
	640
	641	(% style="color:#037691" %)AT+CDP (%%) ~/~/ Read cached data
	642
	643	(% style="color:#037691" %)AT+CDP=0 (%%) ~/~/ Clear cached data
	644
31.1	645	[[image:image-20221021111810-25.png\|\|height="364" width="797"]]
2.1	646
	647
	648
48.2	649	== 2.15 Firmware Change Log ==
2.1	650
48.2	651
48.14	652	Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0>>https://www.dropbox.com/sh/8p5nuvo6gh7je4n/AAAMP7MMusgbXMz9Ik7Ls03Ga?dl=0]]
2.1	653
48.12	654	Upgrade Instruction: [[Upgrade Firmware>>\|\|anchor="H5.1200BHowtoUpgradeFirmware"]]
2.1	655
	656
	657
48.2	658	== 2.16 Battery Analysis ==
	659
	660
	661	=== 2.16.1 Battery Type ===
	662
	663
42.1	664	The CPN01 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	665
42.1	666	The battery is designed to last for several years depends on the actual use environment and update interval.
2.1	667
42.1	668	The battery-related documents as below:
2.1	669
	670	* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
48.2	671
2.1	672	* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
48.2	673
2.1	674	* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
	675
31.1	676	[[image:image-20221021111911-26.png]]
2.1	677
	678
48.2	679
	680	=== 2.16.2 Power consumption Analyze ===
	681
	682
2.1	683	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.
	684
	685	Instruction to use as below:
	686
48.2	687	(% 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	688
48.2	689	(% style="color:blue" %)Step 2: (%%) Open it and choose
2.1	690
	691	* Product Model
48.2	692
2.1	693	* Uplink Interval
48.2	694
2.1	695	* Working Mode
	696
	697	And the Life expectation in difference case will be shown on the right.
	698
48.2	699	[[image:1666596205057-567.png]]
2.1	700
	701
48.2	702
	703	=== 2.16.3 Battery Note ===
	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
48.2	709
	710	=== 2.16.4 Replace the battery ===
	711
	712
2.1	713	The default battery pack of CPN01 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).
	714
42.1	715
2.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
31.1	724	[[image:image-20221021112006-28.png]]
2.1	725
	726
	727
48.2	728	= 4. Using the AT Commands =
	729
	730
	731	== 4.1 Access AT Commands ==
	732
	733
2.1	734	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]]
	735
	736	AT+<CMD>? : Help on <CMD>
	737
	738	AT+<CMD> : Run <CMD>
	739
	740	AT+<CMD>=<value> : Set the value
	741
	742	AT+<CMD>=? : Get the value
	743
	744
48.2	745	(% style="color:blue" %)General Commands
	746
2.1	747	AT : Attention
	748
	749	AT? : Short Help
	750
	751	ATZ : MCU Reset
	752
	753	AT+TDC : Application Data Transmission Interval
	754
	755	AT+CFG : Print all configurations
	756
	757	AT+CFGMOD : Working mode selection
	758
	759	AT+INTMOD : Set the trigger interrupt mode
	760
	761	AT+5VT : Set extend the time of 5V power
	762
	763	AT+PRO : Choose agreement
	764
	765	AT+RXDL : Extend the sending and receiving time
	766
	767	AT+SERVADDR : Server Address
	768
48.2	769	AT+TR : Get or Set record time
2.1	770
	771	AT+NOUD : Get or Set the number of data to be uploaded
	772
48.2	773	AT+CDP : Read or Clear cached data
2.1	774
	775	AT+ DEBUG : Enable or Disable debug mode
	776
	777	AT+ TTRIG : Get or Set Alarm Base on Timeout
	778
	779	AT+ TTRMOD : Get or Set the trigger interrupt mode(0:falling,1:rising)
	780
	781	AT+ CALCFLAG : Get or Set the calculate flag
	782
	783	AT+ CLRC : Clear current door open count
	784
	785
48.2	786	(% style="color:blue" %)COAP Management
	787
2.1	788	AT+URI : Resource parameters
	789
	790
48.2	791	(% style="color:blue" %)UDP Management
	792
2.1	793	AT+CFM : Upload confirmation mode (only valid for UDP)
	794
	795
48.2	796	(% style="color:blue" %)MQTT Management
	797
2.1	798	AT+CLIENT : Get or Set MQTT client
	799
	800	AT+UNAME : Get or Set MQTT Username
	801
	802	AT+PWD : Get or Set MQTT password
	803
	804	AT+PUBTOPIC : Get or Set MQTT publish topic
	805
	806	AT+SUBTOPIC : Get or Set MQTT subscription topic
	807
	808
48.2	809	(% style="color:blue" %)Information
	810
2.1	811	AT+FDR : Factory Data Reset
	812
	813	AT+PWORD : Serial Access Password
	814
	815
	816
48.2	817	= 5. FAQ =
2.1	818
	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
48.2	827	(% style="color:red" %)Notice: (% style="color:blue" %)CPN01 (%%)and (% style="color:blue" %)CPL01(%%)(% style="color:blue" %) (%%)share the same mother board. They use the same connection and method to update.
2.1	828
42.1	829
2.1	830
48.2	831	= 6. Trouble Shooting =
2.1	832
42.1	833
48.2	834	== 6.1 Connection problem when uploading firmware ==
2.1	835
	836
48.2	837	(% 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	838
2.1	839
	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
	847
48.2	848	= 7. Order Info =
2.1	849
	850
48.2	851	Part Number: CPN01
2.1	852
	853
	854
48.2	855	= 8. Packing Info =
2.1	856
	857
48.2	858	(% style="color:blue" %)Package Includes:
2.1	859
48.2	860	* CPN01 Open/Close Sensor x 1
	861	* External antenna x 1
2.1	862
48.2	863	(% style="color:blue" %)Dimension and weight:
2.1	864
48.2	865	* Size: 195 x 125 x 55 mm
	866	* Weight: 420g
2.1	867
48.2	868	= 9. Support =
2.1	869
	870
48.2	871	* 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	872
48.2	873	* 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	874
48.2	875

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

Applications

Navigation