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

Version 90.9 by Xiaoling on 2023/04/24 10:09

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

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

Applications