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

Version 90.14 by Xiaoling on 2023/05/26 10:16

version	line-number	content
1.5	1	(% style="text-align:center" %)
88.2	2	[[image:LMDS200_10.jpg\|\|height="572" width="572"]]
1.5	3
48.2	4
88.2	5
	6
	7
	8	(% style="display:none" %) (%%)
	9
	10
	11
	12
	13
48.2	14	Table of Contents：
	15
83.5	16	{{toc/}}
1.5	17
	18
	19
48.2	20
88.2	21
	22
	23
	24
	25
48.2	26	= 1. Introduction =
	27
71.2	28	== 1.1 What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
48.2	29
	30
52.2	31	(((
74.2	32	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.
83.9	33	)))
1.5	34
83.9	35	(((
74.2	36	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.
83.9	37	)))
1.5	38
83.9	39	(((
74.2	40	NMDS200 can (% style="color:blue" %)measure two distances(%%): the closest object and next object behind the closest one.
83.9	41	)))
53.2	42
83.9	43	(((
74.2	44	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.
83.9	45	)))
1.5	46
83.9	47	(((
70.23	48	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.
83.9	49	)))
1.5	50
83.9	51	(((
74.2	52	NMDS200 (% style="color:blue" %)supports different uplink(%%) methods including (% style="color:blue" %)TCP, MQTT, UDP, and CoAP(%%) for different application requirements.
83.9	53	)))
70.23	54
83.9	55	(((
74.2	56	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)
83.9	57	)))
53.3	58
83.9	59	(((
74.2	60	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	61	)))
	62
	63
48.2	64	== 1.2 Features ==
	65
	66
2.1	67	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
74.2	68	* Short uplink interval for Distance Alarm
2.1	69	* Monitor Battery Level
74.2	70	* Microwave Radar for distance detection
2.1	71	* Datalog feature
34.1	72	* Uplink periodically
2.1	73	* Downlink to change configure
	74	* Wall Mountable
	75	* Outdoor Use
	76	* Ultra-Low Power consumption
	77	* AT Commands to change parameters
	78	* Micro SIM card slot for NB-IoT SIM
34.1	79	* 8500mAh Battery for long-term use
1.5	80
74.2	81	== 1.3 Radar probe specification ==
70.2	82
1.5	83
74.3	84	* Measuring Method: FMCW
83.12	85	* Frequency: 24.000 ~~ 24.500 GHz
74.3	86	* Measurement output power: 6dBm
83.12	87	* Measure range: 0.5 ~~ 20m
74.3	88	* Accuracy: ±0.1m
	89	* Resolution: 0.01m
	90	* Horizontal Angel: 78°
	91	* Vertical Angel: 23°
1.5	92
74.2	93	== 1.4 Storage Temperature ==
1.5	94
	95
74.2	96	-40°C to +85°C
52.2	97
1.5	98
48.2	99	== 1.5 Applications ==
	100
	101
74.2	102	* Horizontal distance measurement
	103	* Liquid level measurement
	104	* Parking management system
	105	* Object proximity and presence detection
	106	* Intelligent trash can management system
	107	* Robot obstacle avoidance
	108	* Automatic control
	109	* Sewer
	110	* Bottom water level monitoring
1.5	111
58.2	112	== 1.6 Specification ==
1.5	113
	114
58.2	115	(% style="color:blue" %)Common DC Characteristics:
48.2	116
58.2	117	* Supply Voltage: 2.1v ~~ 3.6v
74.2	118	* Operating Temperature: 0 ~~ 70°C
58.2	119
	120	(% style="color:blue" %)NB-IoT Spec:
	121
70.24	122	* B1 @H-FDD: 2100MHz
	123	* B3 @H-FDD: 1800MHz
	124	* B8 @H-FDD: 900MHz
	125	* B5 @H-FDD: 850MHz
	126	* B20 @H-FDD: 800MHz
	127	* B28 @H-FDD: 700MHz
58.2	128
74.2	129	== 1.7 Installation ==
52.2	130
1.5	131
74.2	132	Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
1.5	133
48.2	134
83.11	135	[[image:image-20221207170748-1.png]]
48.2	136
1.5	137
83.11	138	[[image:image-20221207170748-2.png\|\|height="345" width="634"]]
38.1	139
83.11	140
74.2	141	== 1.8 Pin Definitions and Switch ==
48.2	142
	143
74.2	144	[[image:1670404362039-351.png]]
2.1	145
	146
74.3	147	= 2. Use NMDS200 to communicate with IoT Server =
48.2	148
	149	== 2.1 How it works ==
	150
	151
74.3	152	The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
48.2	153
74.3	154	The diagram below shows the working flow in the default firmware of NMDS200:
2.1	155
83.12	156	[[image:image-20221021110615-5.png\|\|height="996" width="492"]]
2.1	157
	158
76.2	159	== 2.2 Configure NMDS200 ==
2.1	160
48.2	161
76.2	162	To use NMDS200 in your city, make sure to meet below requirements:
48.2	163
40.1	164	* Your local operator has already distributed an NB-IoT Network.
76.2	165	* The local NB-IoT network used the band that NMDS200 supports.
2.1	166	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	167
76.2	168	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	169
88.2	170	[[image:image-20221209090938-1.png]]
40.1	171
2.1	172
76.2	173	=== 2.2.1 Insert NB-IoT SIM card ===
48.2	174
	175
2.1	176	Insert the NB-IoT Card get from your provider.
	177
40.1	178	User needs to take out the NB-IoT module and insert the SIM card like below:
2.1	179
31.1	180	[[image:image-20221021110745-6.png]]
2.1	181
40.1	182
79.2	183	=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
2.1	184
	185
79.2	186	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	187
48.2	188	(% style="color:blue" %)Connection:
2.1	189
48.2	190	(% style="background-color:yellow" %) USB TTL GND <~-~-~-~-> GND
2.1	191
48.2	192	(% style="background-color:yellow" %) USB TTL TXD <~-~-~-~-> UART_RXD
	193
	194	(% style="background-color:yellow" %) USB TTL RXD <~-~-~-~-> UART_TXD
	195
	196
2.1	197	In the PC, use below serial tool settings:
	198
48.2	199	* Baud: (% style="color:red" %)9600
2.1	200
48.2	201	* Data bits: (% style="color:red" %)8(%%)
	202
	203	* Stop bits: (% style="color:red" %)1
	204
	205	* Parity: (% style="color:red" %)None
	206
	207	* Flow Control: (% style="color:red" %)None
	208
79.2	209	Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)Yellow Jumper(%%).
2.1	210
31.1	211	[[image:image-20221021110817-7.png]]
2.1	212
79.2	213	NMDS200 will output system info once powered on as below, we can enter the password: 12345678 to access AT Command input.
40.1	214
	215
48.2	216	(% 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	217
42.1	218
79.2	219	=== 2.2.3 Use CoAP protocol to uplink data ===
2.1	220
	221
48.2	222	(% 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	223
2.1	224
83.2	225	(% style="color:blue" %)Use below commands in NMDS200:
48.2	226
48.3	227	* (% style="color:#037691" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
48.2	228
48.3	229	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5683 (%%) ~/~/ Set CoAP server address and port
48.2	230
48.3	231	* (% style="color:#037691" %)AT+URI=0,0,11,2,"mqtt" (%%) ~/~/ Set CoAP resource path
48.2	232
2.1	233	For parameter description, please refer to AT command set
	234
87.2	235	[[image:1670471530120-960.png\|\|height="647" width="674"]]
2.1	236
	237
79.2	238	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	239
79.2	240	[[image:1670405841875-916.png]]
2.1	241
42.1	242
79.2	243	=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
2.1	244
42.1	245
48.2	246	(% style="color:blue" %)AT Commands:
2.1	247
48.3	248	* (% style="color:#037691" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
48.2	249
48.3	250	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ Set UDP server address and port
48.2	251
48.3	252	* (% style="color:#037691" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
48.2	253
87.2	254	[[image:1670471559211-638.png]]
2.1	255
48.3	256
31.1	257	[[image:image-20221021111033-11.png\|\|height="241" width="576"]]
2.1	258
	259
	260
79.2	261	=== 2.2.5 Use MQTT protocol to uplink data ===
2.1	262
42.1	263
48.2	264	(% style="color:blue" %)AT Commands:
2.1	265
48.3	266	* (% style="color:#037691" %)AT+PRO=3 (%%) ~/~/ Set to use MQTT protocol to uplink
48.2	267
48.3	268	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/ Set MQTT server address and port
48.2	269
48.3	270	* (% style="color:#037691" %)AT+CLIENT=CLIENT (%%) ~/~/ Set up the CLIENT of MQTT
48.2	271
48.3	272	* (% style="color:#037691" %)AT+UNAME=UNAME (%%) ~/~/ Set the username of MQTT
48.2	273
48.3	274	* (% style="color:#037691" %)AT+PWD=PWD (%%) ~/~/ Set the password of MQTT
48.2	275
48.3	276	* (% style="color:#037691" %)AT+PUBTOPIC=NSE01_PUB (%%) ~/~/ Set the sending topic of MQTT
48.2	277
48.3	278	* (% style="color:#037691" %)AT+SUBTOPIC=NSE01_SUB (%%) ~/~/ Set the subscription topic of MQTT
48.2	279
88.2	280	[[image:1670471584490-640.png]]
2.1	281
48.3	282
79.2	283	[[image:1670405928926-116.png]]
2.1	284
	285
	286
42.1	287	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	288
42.1	289
79.2	290	=== 2.2.6 Use TCP protocol to uplink data ===
2.1	291
	292
48.3	293	(% style="color:blue" %)AT Commands:
2.1	294
48.3	295	* (% style="color:#037691" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
48.2	296
48.3	297	* (% style="color:#037691" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ Set TCP server address and port
48.2	298
88.4	299	[[image:1670471613823-833.png]]
2.1	300
79.2	301
31.1	302	[[image:image-20221021111131-15.png]]
2.1	303
	304
	305
79.2	306	=== 2.2.7 Change Update Interval ===
2.1	307
	308
48.2	309	User can use below command to change the (% style="color:blue" %)uplink interval.
2.1	310
79.2	311	* (% style="color:#037691" %)AT+TDC=7200 (%%) ~/~/ Set Update Interval to 7200s (4 hours)
2.1	312
48.2	313	(% style="color:red" %)NOTE:
2.1	314
59.3	315	1. By default, the device will send an uplink message every 4 hour.
42.1	316
48.3	317
48.2	318	== 2.3 Uplink Payload ==
2.1	319
48.2	320
80.2	321	The uplink payload includes 23 bytes in total by default.
2.1	322
61.3	323	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	324
	325
90.12	326	(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
	327	\|=(% scope="row" style="width: 60px;background-color:#4F81BD;color:white" %)Size(bytes)\|(% style="width:50px;background-color:#4F81BD;color:white" %)8\|(% style="width:30px;background-color:#4F81BD;color:white" %)2\|(% style="width:30px;background-color:#4F81BD;color:white" %)2\|(% style="width:75px;background-color:#4F81BD;color:white" %)1\|(% style="width:30px;background-color:#4F81BD;color:white" %)1\|(% style="width:50px;background-color:#4F81BD;color:white" %)1\|(% style="width:60px;background-color:#4F81BD;color:white" %)2\|(% style="width:60px;background-color:#4F81BD;color:white" %)2
83.7	328	\|=(% 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>>\|\|anchor="H2.4.5A0Distance"]] \|(% style="width:93px" %) [[Distance 2>>\|\|anchor="H2.4.5A0Distance"]]
2.1	329
90.13	330	(% border="1" style="background-color:#f2f2f2; width:429px" %)
	331	\|(% style="width:60px;background-color:#4F81BD;color:white" %)4\|(% style="width:60px;background-color:#4F81BD;color:white" %)2\|(% style="width:60px;background-color:#4F81BD;color:white" %)2\|(% style="width:60px;background-color:#4F81BD;color:white" %)4\|(% style="width:100px;background-color:#4F81BD;color:white" %)(((
61.3	332	1-32 group
	333	)))
83.12	334	\|(% style="width:98px" %)[[Time stamp>>\|\|anchor="H2.4.6A0Timestamp"]]\| Distance 1 \| Distance 2\|(% style="width:67px" %)Time stamp\|(% style="width:100px" %)...
48.3	335
80.2	336	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	337
80.2	338	[[image:1670406261143-723.png]]
61.3	339
	340
90.4	341	The payload is ASCII string, representative same HEX: 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	342
48.2	343	where:
2.1	344
80.2	345	* (% style="color:#037691" %)Device ID:(%%) 0x f867787050471071 = f867787050471071
2.1	346
70.2	347	* (% style="color:#037691" %)Version:(%%) 0x0064=100=1.0.0
33.1	348
80.2	349	* (% style="color:#037691" %)BAT :(%%) 0x0cc3 = 3267 mV = 3.267V
33.1	350
80.2	351	* (% style="color:#037691" %)Singal: (%%)0x09 = 9
33.1	352
70.2	353	* (% style="color:#037691" %)Mod:(%%) 0x01 = 1
33.1	354
80.2	355	* (% style="color:#037691" %)Exit flag: (%%)0x00 =0
33.1	356
80.2	357	* (% style="color:#037691" %)Distance 1: (%%)0x00ef=239
33.1	358
80.2	359	* (% style="color:#037691" %)Distance 2: (%%)0x013d =317
33.1	360
80.2	361	* (% style="color:#037691" %)Timestamp: (%%)0x6390453d =1670399293 (Unix Time)
33.1	362
48.2	363	== 2.4 Payload Explanation and Sensor Interface ==
	364
	365	=== 2.4.1 Device ID ===
	366
	367
42.1	368	By default, the Device ID is equal to the last 15 bits of IMEI.
2.1	369
48.2	370	User can use (% style="color:blue" %)AT+DEUI (%%)to set Device ID
2.1	371
	372	Example:
	373
	374	AT+DEUI=868411056754138
	375
42.1	376	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	377
42.1	378
48.2	379	=== 2.4.2 Version Info ===
	380
	381
42.1	382	Specify the software version: 0x64=100, which means firmware version 1.00.
2.1	383
90.5	384	For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
2.1	385
42.1	386
48.2	387	=== 2.4.3 Battery Info ===
	388
	389
81.2	390	Check the battery voltage for NMDS200.
2.1	391
	392	Ex1: 0x0B45 = 2885mV
	393
	394	Ex2: 0x0B49 = 2889mV
	395
42.1	396
48.2	397	=== 2.4.4 Signal Strength ===
	398
	399
2.1	400	NB-IoT Network signal Strength.
	401
83.4	402	(% style="color:blue" %)Ex1: 0x1d = 29
2.1	403
83.4	404	(% style="color:#037691" %)0 (%%) -113dBm or less
2.1	405
83.4	406	(% style="color:#037691" %)1 (%%) -111dBm
2.1	407
83.4	408	(% style="color:#037691" %)2...30 (%%) -109dBm... -53dBm
2.1	409
83.4	410	(% style="color:#037691" %)31 (%%) -51dBm or greater
2.1	411
83.4	412	(% style="color:#037691" %)99 (%%) Not known or not detectable
2.1	413
42.1	414
81.2	415	=== 2.4.5 Distance ===
48.2	416
	417
81.2	418	[[image:1670407401682-959.png]]
2.1	419
83.2	420
81.3	421	(% style="color:blue" %)Object1 Distance:
2.1	422
81.2	423	Distance between sensor probe to the first object. (unit: cm)
2.1	424
81.2	425	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	426
81.3	427	(% style="color:blue" %)0205(H) = 517 (D) = 517 cm.
42.1	428
48.2	429
81.3	430	(% style="color:blue" %)Object2 Distance:
48.2	431
81.2	432	Distance between sensor probe to the second object. (unit: cm)
2.1	433
42.1	434
81.2	435	=== 2.4.6 Timestamp ===
2.1	436
81.2	437
61.6	438	Timestamp : 0x6315537b =1662342011
48.2	439
	440
	441	== 2.5 Downlink Payload ==
	442
	443
81.3	444	By default, NMDS200 prints the downlink payload to console port.
2.1	445
90.11	446	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
	447	\|(% style="background-color:#d9e2f3; color:#0070c0" %)Downlink Control Type\|(% style="background-color:#d9e2f3; color:#0070c0" %)FPort\|(% style="background-color:#d9e2f3; color:#0070c0; width:97px" %)Type Code\|(% style="background-color:#d9e2f3; color:#0070c0; width:183px" %)Downlink payload size(bytes)
	448	\|TDC (Transmit Time Interval)\|Any\|(% style="width:97px" %)01\|(% style="width:183px" %)4
	449	\|RESET\|Any\|(% style="width:97px" %)04\|(% style="width:183px" %)2
	450	\|INTMOD\|Any\|(% style="width:97px" %)06\|(% style="width:183px" %)4
	451
2.1	452
	453	Examples:
	454
48.2	455	* (% style="color:#037691" %)Set TDC
2.1	456
	457	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
	458
	459	Payload: 01 00 00 1E TDC=30S
	460
	461	Payload: 01 00 00 3C TDC=60S
	462
48.2	463	* (% style="color:#037691" %)Reset
2.1	464
81.3	465	If payload = 0x04FF, it will reset the NMDS200
2.1	466
48.2	467	* (% style="color:#037691" %)INTMOD
2.1	468
	469	Downlink Payload: 06000003, Set AT+INTMOD=3
	470
	471
48.2	472	== 2.6 LED Indicator ==
	473
	474
81.3	475	The NMDS200 has an internal LED which is to show the status of different states.
2.1	476
45.1	477	* When the device starts normally, the LED will light up for 1 second.
83.2	478	* After NMDS200 join NB-IoT network. The LED will be ON for 3 seconds.
2.1	479	* For each uplink probe, LED will be on for 500ms.
	480
81.3	481	== 2.7 Distance alarm function ==
	482
	483
81.4	484	(% style="color:blue" %)AT Command: AT+ALARM1=min,max
2.1	485
83.4	486	(% style="color:#037691" %)Example 1:
2.1	487
89.1	488	AT+ ALARM1 =60,200 ~/~/ Alarm when distance1 lower than 60.
2.1	489
81.4	490	AT+ ALARM2 =min,max
2.1	491
	492
83.4	493	(% style="color:#037691" %)Example 2:
2.1	494
89.1	495	AT+ ALARM2 =200,1500 ~/~/ Alarm when distance2 lower than 1500.
2.1	496
	497
82.2	498	== 2.8 Set the number of data to be uploaded and the recording time ==
48.2	499
	500
	501	(% style="color:blue" %)AT Command:
	502
66.2	503	(% 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)
	504
	505	(% 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.
	506
	507
82.2	508	== 2.9 Read or Clear cached data ==
66.2	509
	510
	511	(% style="color:blue" %)AT Command:
	512
48.2	513	(% style="color:#037691" %)AT+CDP (%%) ~/~/ Read cached data
	514
	515	(% style="color:#037691" %)AT+CDP=0 (%%) ~/~/ Clear cached data
	516
82.2	517	[[image:1670408172929-569.png]]
2.1	518
	519
82.2	520	== 2.10 Firmware Change Log ==
2.1	521
48.2	522
90.3	523	Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
2.1	524
48.12	525	Upgrade Instruction: [[Upgrade Firmware>>\|\|anchor="H5.1200BHowtoUpgradeFirmware"]]
2.1	526
	527
90.6	528	== 2.11 Battery & Power Consumption ==
48.2	529
	530
90.6	531	NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
48.2	532
90.6	533	[[Battery Info & Power Consumption Analyze>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
2.1	534
90.7	535
48.2	536	= 3. Access NB-IoT Module =
	537
	538
2.1	539	Users can directly access the AT command set of the NB-IoT module.
	540
	541	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/]]
	542
70.22	543
67.2	544	[[image:image-20221118094449-6.png]]
2.1	545
	546
48.2	547	= 4. Using the AT Commands =
	548
	549	== 4.1 Access AT Commands ==
	550
	551
2.1	552	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]]
	553
	554	AT+<CMD>? : Help on <CMD>
	555
	556	AT+<CMD> : Run <CMD>
	557
	558	AT+<CMD>=<value> : Set the value
	559
	560	AT+<CMD>=? : Get the value
	561
	562
48.2	563	(% style="color:blue" %)General Commands
	564
2.1	565	AT : Attention
	566
	567	AT? : Short Help
	568
	569	ATZ : MCU Reset
	570
	571	AT+TDC : Application Data Transmission Interval
	572
	573	AT+CFG : Print all configurations
	574
	575	AT+CFGMOD : Working mode selection
	576
	577	AT+INTMOD : Set the trigger interrupt mode
	578
83.8	579	AT+5VT : Set extend the time of 5V power
2.1	580
83.8	581	AT+PRO : Choose agreement
2.1	582
83.8	583	AT+RXDL : Extend the sending and receiving time
2.1	584
83.8	585	AT+SERVADDR : Server Address
2.1	586
83.2	587	AT+TR : Get or Set record time
2.1	588
83.2	589	AT+NOUD : Get or Set the number of data to be uploaded
2.1	590
48.2	591	AT+CDP : Read or Clear cached data
2.1	592
83.8	593	AT+DEBUG: Enable or Disable debug mode
2.1	594
83.2	595	AT+ALARM1: Get or Set alarm of distance1
2.1	596
83.2	597	AT+ALARM2: Get or Set alarm of distance2
2.1	598
83.2	599	AT+GETSENSORVALUE : Returns the current sensor measurement
2.1	600
83.2	601	AT+POWERIC : Get or set the Power IC flag
2.1	602
	603
48.2	604	(% style="color:blue" %)COAP Management
	605
83.2	606	AT+URI : Resource parameters
2.1	607
	608
48.2	609	(% style="color:blue" %)UDP Management
	610
83.2	611	AT+CFM : Upload confirmation mode (only valid for UDP)
2.1	612
	613
48.2	614	(% style="color:blue" %)MQTT Management
	615
83.2	616	AT+CLIENT : Get or Set MQTT client
2.1	617
83.2	618	AT+UNAME : Get or Set MQTT Username
2.1	619
83.2	620	AT+PWD : Get or Set MQTT password
2.1	621
83.2	622	AT+PUBTOPIC : Get or Set MQTT publish topic
2.1	623
83.2	624	AT+SUBTOPIC : Get or Set MQTT subscription topic
2.1	625
	626
48.2	627	(% style="color:blue" %)Information
	628
83.2	629	AT+FDR : Factory Data Reset
2.1	630
83.2	631	AT+PWORD : Serial Access Password
2.1	632
	633
48.2	634	= 5. FAQ =
2.1	635
48.2	636	== 5.1 How to Upgrade Firmware ==
2.1	637
	638
48.2	639	User can upgrade the firmware for 1) bug fix, 2) new feature release.
2.1	640
48.2	641	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	642
83.2	643	(% style="color:red" %)Notice: (% style="color:blue" %)NMDS200 (%%)and (% style="color:blue" %)LMDS200(%%)(% style="color:blue" %) (%%)share the same mother board. They use the same connection and method to update.
2.1	644
42.1	645
48.2	646	= 6. Trouble Shooting =
2.1	647
48.2	648	== 6.1 Connection problem when uploading firmware ==
2.1	649
	650
48.2	651	(% 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	652
2.1	653
48.2	654	== 6.2 AT Command input doesn't work ==
2.1	655
	656
48.2	657	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	658
	659
90.9	660	== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
	661
	662
	663	This means sensor is trying to join the NB-IoT network but fail. Please see this link for //[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//.
	664
	665
48.2	666	= 7. Order Info =
2.1	667
	668
83.4	669	Part Number:(% style="color:blue" %) NMDS200
2.1	670
	671
48.2	672	= 8. Packing Info =
2.1	673
	674
48.2	675	(% style="color:blue" %)Package Includes:
2.1	676
83.2	677	* NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
2.1	678
48.2	679	= 9. Support =
2.1	680
	681
48.2	682	* 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	683
48.2	684	* 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	685
48.2	686

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

Applications

Navigation