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

Version 84.1 by Xiaoling on 2022/12/08 11:52

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

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

Applications

Navigation