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

Version 81.2 by Xiaoling on 2022/12/07 18:05

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

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

Applications