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

Version 83.8 by Xiaoling on 2022/12/08 11:29

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

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

Applications