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

Version 83.4 by Xiaoling on 2022/12/08 09:47

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

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

Applications