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

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

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

Applications