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

Version 74.3 by Xiaoling on 2022/12/07 17:16

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

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

Applications

Navigation