Wiki source code of NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual

Version 73.1 by Xiaoling on 2022/12/07 17:07

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

Wiki source code of NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual

Applications

Navigation