Last modified by Mengting Qiu on 2024/05/09 15:39
Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20230913101620-1.png||height="552" width="790"]]
3
4
5
6
7
8
9
10
11 **Table of Contents:**
12
13 {{toc/}}
14
15
16
17
18
19
20 = 1. Introduction =
21
22 == 1.1 What is MDS120-NB NB-IoT Microwave Radar distance Sensor ==
23
24
25 The Dragino MDS120-NB is a (% style="color:blue" %)** NB-IoT Microwave Radar distance Sensor**(%%) for Internet of Things solution. It uses use Microwave Radar to (% style="color:blue" %)**detect the distance between sensor and different objects**(%%). Different from ultrosonic or Lidar measurement. Microwave Radar is (% style="color:blue" %)**more reliable for condensation / dusty environment**(%%). It can sense correct distance even there is water or think dust on top of the sensor.
26
27 The MDS120-NB 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.
28
29 MDS120-NB supports different uplink methods including (% style="color:blue" %)**MQTT, MQTTs, UDP & TCP**(%%) for different application requirement, and support uplinks to various IoT Servers.
30
31 MDS120-NB (% style="color:blue" %)**supports BLE configure **(%%)and(% style="color:blue" %)** OTA update**(%%) which make user easy to use.
32
33 MDS120-NB is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long-term use up to several years.
34
35 MDS120-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.
36
37 [[image:image-20230913102350-2.png||height="318" width="899"]]
38
39
40 == 1.2 ​Features ==
41
42
43 * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD
44 * Ultra-low power consumption
45 * 60Ghz Microwave Radar for distance detection
46 * Measure Range: 15 ~~ 1200cm
47 * Accuracy: ±(2cm+SX0.3%). S: Measure Value
48 * Resolution: 1cm
49 * Measurement Angle: 25 degrees horizontal and 23 degrees vertical
50 * Multiply Sampling and one uplink
51 * Support Bluetooth v5.1 remote configure and update firmware
52 * Uplink on periodically
53 * Downlink to change configure
54 * 8500mAh Battery for long term use
55 * Nano SIM card slot for NB-IoT SIM
56
57 == 1.3 Specification ==
58
59
60 (% style="color:blue" %)**Common DC Characteristics:**
61
62 * Supply Voltage: 2.5v ~~ 3.6v
63 * Operating Temperature: -40 ~~ 85°C
64
65 (% style="color:blue" %)**Radar probe Spec:**
66
67 * Measuring Method: FMCW
68 * Frequency: 60 GHz
69 * Measure Range : 15 ~~ 1200cm
70 * Accuracy: ±(2cm+SX0.3%). S: Measure Value
71 * Resolution: 1cm
72 * Measurement Angle : 25 degrees horizontal and 23 degrees vertical
73
74 (% style="color:blue" %)**NB-IoT Spec:**
75
76 (% style="color:#037691" %)**NB-IoT Module: BC660K-GL**
77
78 (% style="color:#037691" %)**Support Bands:**
79
80 * B1 @H-FDD: 2100MHz
81 * B2 @H-FDD: 1900MHz
82 * B3 @H-FDD: 1800MHz
83 * B4 @H-FDD: 2100MHz
84 * B5 @H-FDD: 860MHz
85 * B8 @H-FDD: 900MHz
86 * B12 @H-FDD: 720MHz
87 * B13 @H-FDD: 740MHz
88 * B17 @H-FDD: 730MHz
89 * B18 @H-FDD: 870MHz
90 * B19 @H-FDD: 870MHz
91 * B20 @H-FDD: 790MHz
92 * B25 @H-FDD: 1900MHz
93 * B28 @H-FDD: 750MHz
94 * B66 @H-FDD: 2000MHz
95 * B70 @H-FDD: 2000MHz
96 * B85 @H-FDD: 700MHz
97
98 (% style="color:blue" %)**Battery:**
99
100 * Li/SOCI2 un-chargeable battery
101 * Capacity: 8500mAh
102 * Self Discharge: <1% / Year @ 25°C
103 * Max continuously current: 130mA
104 * Max boost current: 2A, 1 second
105
106 (% style="color:blue" %)**Power Consumption:**
107
108 * STOP Mode: 10uA @ 3.3v
109 * Max transmit power: 350mA@3.3v
110
111 == 1.4 Applications ==
112
113
114 * Horizontal distance measurement
115 * Liquid level measurement
116 * Parking management system
117 * Object proximity and presence detection
118 * Intelligent trash can management system
119 * Robot obstacle avoidance
120 * Automatic control
121 * Sewer
122 * Bottom water level monitoring
123
124 == 1.5 Sleep mode and working mode ==
125
126
127 (% style="color:blue" %)**Deep Sleep Mode: **(%%)Sensor doesn't have any NB-IoT activate. This mode is used for storage and shipping to save battery life.
128
129 (% style="color:blue" %)**Working Mode:** (%%)In this mode, Sensor will work as NB-IoT Sensor to Join NB-IoT network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.
130
131
132 == 1.6 Button & LEDs ==
133
134
135 [[image:Main.User Manual for LoRaWAN End Nodes.D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual.WebHome@1675071855856-879.png]]
136
137
138 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
139 |=(% style="width: 167px;background-color:#4F81BD;color:white" %)**Behavior on ACT**|=(% style="width: 117px;background-color:#4F81BD;color:white" %)**Function**|=(% style="width:225px;background-color:#4F81BD;color:white" %)**Action**
140 |(% style="width:167px" %)Pressing ACT between 1s < time < 3s|(% style="width:117px" %)Send an uplink|(% style="width:225px" %)(((
141 If sensor has already attached to NB-IoT network, sensor will send an uplink packet, (% style="color:blue" %)**blue led** (%%)will blink once.
142 Meanwhile, BLE module will be active and user can connect via BLE to configure device.
143 )))
144 |(% style="width:167px" %)Pressing ACT for more than 3s|(% style="width:117px" %)Active Device|(% style="width:225px" %)(((
145 (% style="color:green" %)**Green led**(%%) will fast blink 5 times, device will enter (% style="color:#037691" %)**OTA mode**(%%) for 3 seconds. And then start to attach NB-IoT network.
146 (% style="color:green" %)**Green led**(%%) will solidly turn on for 5 seconds after joined in network.
147 Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device attach NB-IoT network or not.
148 )))
149 |(% style="width:167px" %)Fast press ACT 5 times.|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode.
150
151 (% style="color:red" %)**Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.**
152
153
154 == 1.7 BLE connection ==
155
156
157 MDS120-NB support BLE remote configure and firmware update.
158
159
160 BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case:
161
162 * Press button to send an uplink
163 * Press button to active device.
164 * Device Power on or reset.
165
166 If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
167
168
169 == 1.8 Pin Definitions , Switch & SIM Direction ==
170
171
172 [[image:image-20230819104805-5.png]]
173
174
175 === 1.8.1 Jumper JP2 ===
176
177
178 Power on Device when put this jumper.
179
180
181 === 1.8.2 BOOT MODE / SW1 ===
182
183
184 **1)** (% style="color:blue" %)**ISP**(%%): upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
185
186 **2)** (% style="color:blue" %)**Flash**(%%): work mode, device starts to work and send out console output for further debug
187
188
189 === 1.8.3 Reset Button ===
190
191
192 Press to reboot the device.
193
194 (% style="display:none" %)
195
196
197 === 1.8.4 SIM Card Direction ===
198
199
200 See this link. [[How to insert SIM Card>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]].
201
202
203 == 1.9 Mechanical ==
204
205 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143884058-338.png?rev=1.1||alt="1675143884058-338.png"]]
206
207 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143899218-599.png?rev=1.1||alt="1675143899218-599.png"]]
208
209 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/D20-LBD22-LBD23-LB_LoRaWAN_Temperature_Sensor_User_Manual/WebHome/1675143909447-639.png?rev=1.1||alt="1675143909447-639.png"]]
210
211
212 = 2. Use MDS120-NB to communicate with IoT Server =
213
214 == 2.1 Send data to IoT server via NB-IoT network ==
215
216
217 The MDS120-NB is equipped with a NB-IoT module, the pre-loaded firmware in MDS120-NB will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by MDS120-NB.
218
219
220 Below shows the network structure:
221
222 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/MDS120-NB_NB-IoT_Microwave_Radar_Distance_Sensor_User_Manual/WebHome/image-20230913102350-2.png?width=899&height=318&rev=1.1||alt="image-20230913102350-2.png"]]
223
224
225 There are two version: (% style="color:blue" %)**-GE**(%%) and (% style="color:blue" %)**-1D**(%%) version of MDS120-NB.
226
227
228 (% style="color:blue" %)**GE Version**(%%): This version doesn't include SIM card or point to any IoT server. User needs to use AT Commands to configure below two steps to set MDS120-NB send data to IoT server.
229
230 * Install NB-IoT SIM card and configure APN. See instruction of [[Attach Network>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.AttachNetwork]].
231
232 * Set up sensor to point to IoT Server. See instruction of [[Configure to Connect Different Servers>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.Configuretoconnecttodifferentservers]]. 
233
234 Below shows result of different server as a glance.
235
236 (% border="1" cellspacing="4" style="width:515px" %)
237 |(% style="background-color:#4f81bd; color:white; width:100px" %)**Servers**|(% style="background-color:#4f81bd; color:white; width:300px" %)**Dash Board**|(% style="background-color:#4f81bd; color:white; width:115px" %)**Comments**
238 |(% style="width:127px" %)[[Node-Red>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.5A0Node-RedA028viaA0MQTT29]]|(% style="width:385px" %)(((
239 (% style="text-align:center" %)
240 [[image:image-20230819113244-8.png||height="183" width="367"]]
241 )))|(% style="width:170px" %)
242 |(% style="width:127px" %)[[DataCake>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]]|(% style="width:385px" %)(((
243 (% style="text-align:center" %)
244 [[image:image-20230819113244-9.png||height="119" width="367"]]
245 )))|(% style="width:170px" %)
246 |(% style="width:127px" %)[[Tago.IO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.7A0Tago.ioA028viaA0MQTT29]]|(% style="width:385px" %) |(% style="width:170px" %)
247 |(% style="width:127px" %)[[General UDP>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.1GeneralA0UDPA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %)
248 |(% style="width:127px" %)[[General MQTT>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.2GeneralA0MQTTA0Connection]]|(% style="width:385px" %)Raw Payload. Need Developer to design Dash Board|(% style="width:170px" %)
249 |(% style="width:127px" %)[[ThingSpeak>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.3A0ThingSpeakA028viaA0MQTT29]]|(% style="width:385px" %)(((
250 (% style="text-align:center" %)
251 [[image:image-20230819113244-10.png||height="104" width="367"]]
252 )))|(% style="width:170px" %)
253 |(% style="width:127px" %)[[ThingsBoard>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.6A0ThingsBoard.CloudA028viaA0MQTT29]]|(% style="width:385px" %)(((
254 (% style="text-align:center" %)
255 [[image:image-20230819113244-11.png||height="141" width="367"]]
256 )))|(% style="width:170px" %)
257
258 (% style="color:blue" %)**1D Version**(%%): This version has 1NCE SIM card pre-installed and configure to send value to DataCake. User Just need to select the sensor type in DataCake and Activate MDS120-NB and user will be able to see data in DataCake. See here for [[DataCake Config Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H3.4Datacake]].
259
260
261 == 2.2 ​Payload Types ==
262
263
264 To meet different server requirement, MDS120-NB supports different payload type.
265
266 **Includes:**
267
268 * [[General JSON format payload>>||anchor="H2.2.1GeneralJsonFormat28Type3D529"]]. (Type=5)
269
270 * [[HEX format Payload>>||anchor="H2.2.2HEXformatPayload28Type3D029"]]. (Type=0)
271
272 * [[ThingSpeak Format>>||anchor="H2.2.4ThingSpeakPayload28Type3D129"]]. (Type=1)
273
274 * [[ThingsBoard Format>>||anchor="H2.2.3ThingsBoardPayload28Type3D329"]]. (Type=3)
275
276 User can specify the payload type when choose the connection protocol. Example:
277
278 (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Use UDP Connection & hex Payload
279
280 (% style="color:#037691" %)**AT+PRO=2,5**   (%%) ~/~/ Use UDP Connection & Json Payload
281
282 (% style="color:#037691" %)**AT+PRO=3,5 ** (%%) ~/~/ Use MQTT Connection & Json Payload
283
284
285 === 2.2.1 General Json Format(Type~=5) ===
286
287
288 This is the General Json Format. As below:
289
290 (% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"MDS120-NB","distance":326,"battery":3.54,"signal":25,"1":{16383,2023/09/22 03:13:30},"2":{257,2023/09/22 02:42:56},"3":{40,2023/09/22 02:08:57},"4":{491,2023/09/22 01:21:42},"5":{501,2023/09/22 01:05:01},"6":{500,2023/09/22 00:50:01},"7":{748,2023/09/21 08:36:55},"8":{911,2023/09/21 07:44:35}}**
291
292
293 [[image:image-20230922111626-3.png||height="600" width="886"]]
294
295
296 (% style="color:red" %)**Notice, from above payload:**
297
298 * Temperature , Humidity , Battery & Signal are the value at uplink time.
299
300 * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+NOUD=8 ** (%%)Command. Each entry includes (from left to right): Temperature, Humidity, Sampling time.
301
302 === 2.2.2 HEX format Payload(Type~=0) ===
303
304
305 This is the HEX Format. As below:
306
307 (% style="color:#4472c4" %)**f8662070583784430d640dd21501000dc8650d02ff0101650cff300028650cf73901eb650cec2601f5650ce83d01f4650ce4b902ec650c00a7038f650bf46302be650beba7**
308
309 [[image:image-20230922100418-1.png||height="181" width="965"]]
310
311
312 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
313
314 [[image:image-20230922110013-2.png||height="546" width="884"]]
315
316
317
318 (% style="color:blue" %)**Version:**
319
320 These bytes include the hardware and software version.
321
322 (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x0d for MDS120-NB
323
324 (% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0
325
326
327 (% style="color:blue" %)**BAT (Battery Info):**
328
329 Ex1: 0x0DD2 = 3538mV
330
331
332 (% style="color:blue" %)**Signal Strength:**
333
334 NB-IoT Network signal Strength.
335
336 **Ex1: 0x15 = 21**
337
338 **0**  -113dBm or less
339
340 **1**  -111dBm
341
342 **2...30** -109dBm... -53dBm
343
344 **31**   -51dBm or greater
345
346 **99**    Not known or not detectable
347
348
349 (% style="color:blue" %)**Distance:**
350
351 Ex1: 0xdc8 = 3528 mm
352
353
354 (% style="color:blue" %)**TimeStamp:   **
355
356 Unit TimeStamp Example: 650d02ff(H) = 1695351551(D)
357
358 Put the decimal value into this link([[https:~~/~~/www.epochconverter.com)>>https://www.epochconverter.com]]) to get the time.
359
360
361 === 2.2.3 ThingsBoard Payload(Type~=3) ===
362
363
364 Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.
365
366 (% style="color:#4472c4" %)**{"IMEI": "866207058378443","Model": "MDS120-NB","distance": 326,"battery": 3.53,"signal": 23}**
367
368
369 [[image:image-20230922112019-4.png||height="463" width="877"]]
370
371
372 === 2.2.4 ThingSpeak Payload(Type~=1) ===
373
374
375 This payload meets ThingSpeak platform requirement. It includes only four fields. Form 1~~3 are:
376
377 Temperature, Humidity, Battery & Signal. This payload type only valid for ThingsSpeak Platform
378
379 As below:
380
381 (% style="color:#4472c4" %)**field1=Distance value&field2=Battery value&field3=Signal value**
382
383 [[image:image-20230922114723-5.png||height="573" width="827"]]
384
385
386 == 2.3  ​Uplink Payload ==
387
388
389 (((
390 MDS120-NB will uplink payload via NB-IoT with below payload format:   
391 )))
392
393 (((
394 Uplink payload includes in total 21 bytes.
395 )))
396
397 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %)
398 |=(% style="width: 60px; background-color:#4F81BD;color:white" %)Size(bytes)|=(% style="width: 50px; background-color:#4F81BD;color:white" %)8|=(% style="width: 30px; background-color:#4F81BD;color:white" %)2|=(% style="width: 30px;background-color:#4F81BD;color:white" %)2|=(% style="width: 60px;background-color:#4F81BD;color:white" %)1|=(% style="background-color: #4F81BD; color: white; width: 30px;" %)1|=(% style="background-color: #4F81BD; color: white; width: 90px" %)1|=(% style="background-color:#4F81BD;color:white;width:100px" %)2|=(% style="background-color:#4F81BD;color:white;width:60px" %)4
399 |(% style="width:95px" %)Value|(% style="width:61px" %)f+IMEI|(% style="width:61px" %)Ver|(% style="width:61px" %)[[BAT>>||anchor="H2.3.1A0BatteryInfo"]]|(% style="width:61px" %)(((
400 Signal Strength
401 )))|(% style="width:49px" %)Mod|(% style="width:79px" %)[[Digital Interrupt >>||anchor="H2.3.2A0Interrupt"]]|(% style="width:61px" %)[[Distance>>||anchor="H2.3.3A0Distance"]](unit: mm)|(% style="width:61px" %)Timestamp
402
403 If the cache upload mechanism is turned on, you will receive the payload shown in the figure below.
404
405 (% border="1" cellspacing="5" style="background-color:#f2f2f2; width:512px" %)
406 |(% style="width:115px" %)**Frame header**|(% style="width:118px" %)**Frame data(1)**|(% style="width:116px" %)**Frame data(2)**|(% style="width:39px" %)**F…**|(% style="width:117px" %)**Frame data(X)**
407
408 === 2.3.1  Battery Info ===
409
410
411 Check the battery voltage for MDS120-NB.
412
413 Ex1: 0x0B45 = 2885mV
414
415 Ex2: 0x0B49 = 2889mV
416
417
418 === 2.3.2  Interrupt ===
419
420
421 This data field shows if this packet is generated by interrupt or not.
422
423 **Example:**
424
425 0x00: Normal uplink packet.
426
427 0x01: Interrupt Uplink Packet.
428
429
430 === 2.3.3  Distance ===
431
432
433 (((
434 Distance between sensor probe to the first object. (unit: mm)
435 )))
436
437 (((
438 For example, if the data you get from the register is** __0x0D 0xC6__**, the distance between the sensor and the measured object is(% style="color:blue" %)** 0DC6(H) = 3526 (D) = 3526 mm.**
439 )))
440
441
442 (((
443 (% style="color:red" %)**Notice: The distance has a special value :**
444 )))
445
446 (((
447 (% style="color:blue" %)**0x3FFF**(%%): Reading Invalid (exceed the valid range of the probe) or Probe not detected.
448 )))
449
450
451 == 2.4 Test Uplink and Change Update Interval ==
452
453
454 By default, Sensor will send uplinks (% style="color:blue" %)**every 2 hours**(%%) & AT+NOUD=8
455
456 User can use below commands to change the (% style="color:blue" %)**uplink interval**.
457
458 (% style="color:#037691" %)**AT+TDC=600 ** (%%) ~/~/ Set Update Interval to 600s
459
460 User can also push the button for more than 1 seconds to activate an uplink.
461
462
463 == 2.5 Multi-Samplings and One uplink ==
464
465 (% style="color:red" %)Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer [[Clock Logging Feature>>||anchor="H2.7Clocklogging28Sincefirmwareversionv1.2.129"]]
466 (%%)
467 To save battery life, MDS120-NB will sample temperature & humidity data every 15 minutes and send one uplink every 2 hours. So each uplink it will include 8 stored data + 1 real-time data. They are defined by:
468
469 * (% style="color:#037691" %)**AT+TR=900**   (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds (15 minutes, the minimum can be set to 180 seconds)
470
471 * (% style="color:#037691" %)**AT+NOUD=8**     (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
472
473 The diagram below explains the relationship between TR, NOUD, and TDC more clearly:
474
475 [[image:1692424376354-959.png]]
476
477
478 == 2.6 Trggier an uplink by external interrupt ==
479
480
481 MDS120-NB has an external trigger interrupt function. Users can use the PB15 pin to trigger the upload of data packets.
482
483 (% style="color:blue" %)**AT command:**
484
485 * (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode
486
487 * (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt
488
489 * (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge
490
491 * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge
492
493 * (% style="color:#037691" %)**AT+INTMOD=3  **(%%) ~/~/ Trigger by rising edge
494
495 == 2.7 Clock logging (Since firmware version v1.2.1) ==
496
497
498 Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature.
499
500 We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data.
501
502 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CLOCKLOG=a,b,c,d(%%)**
503
504 (% style="color:#037691" %)**a: **(%%)**0:** Disable Clock logging.  ** 1: **Enable Clock Logging
505
506 (% style="color:#037691" %)**b:**(%%)** **Specify First sampling start second: range **(0 ~~ 3599, 65535)   ** ~/~/ (% style="color:red" %)**Note:**(%%)** **If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.
507
508 (% style="color:#037691" %)**c:**(%%)** **Specify the sampling interval: range **(0 ~~ 255 minutes)**
509
510 (% style="color:#037691" %)**d:**(%%)** **How many entries should be uplink on every TDC **(max 32)**
511
512 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SPH01-NB_NB-IoT_Soil_pH_Sensor_User_Manual/WebHome/image-20240315141254-1.png?rev=1.1||alt="image-20240315141254-1.png"]]
513
514 **Example:**
515
516 **AT+CLOCKLOG=1,65535,1,5**
517
518 After the node sends the first packet, data is recorded to the memory at intervals of 1 minute. For each TDC uplink, the uplink load will include: battery information + the last 5 memory records (payload + timestamp).
519
520 (% class="wikigeneratedid" %)
521 [[image:image-20240315172914-1.png||height="603" width="1191"]]
522
523 (% class="wikigeneratedid" %)
524 (% style="color:red" %)**Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.**
525
526
527 == 2.8 Example Query saved historical records ==
528
529
530 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+CDP(%%)**
531
532 This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes.
533
534 (% class="wikigeneratedid" %)
535 [[image:image-20240315173001-2.png||height="627" width="806"]]
536
537
538 == 2.9 Uplink log query ==
539
540 * (% style="color:blue" %)**AT command:**(%%)** (% style="color:#037691" %)AT+GETLOG(%%)**
541
542 This command can be used to query upstream logs of data packets.
543
544 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20240407191922-2.png?width=903&height=631&rev=1.1||alt="image-20240407191922-2.png"]]
545
546
547
548
549 = 3. Configure MDS120-NB =
550
551 == 3.1 Configure Methods ==
552
553
554 MDS120-NB supports below configure method:
555
556 * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
557
558 * AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]].
559
560 == 3.2 AT Commands Set ==
561
562
563 AT+<CMD>?        : Help on <CMD>
564
565 AT+<CMD>         : Run <CMD>
566
567 AT+<CMD>=<value> : Set the value
568
569 AT+<CMD>=?       : Get the value
570
571
572 (% style="color:blue" %)**General Commands**      
573
574 AT                    : Attention       
575
576 AT?  : Short Help     
577
578 ATZ  : MCU Reset    
579
580 AT+TDC  : Application Data Transmission Interval
581
582 AT+CFG  : Print all configurations
583
584 AT+CFGMOD           : Working mode selection
585
586 AT+DEUI  : Get or set the Device ID
587
588 AT+INTMOD            : Set the trigger interrupt mode
589
590 AT+5VT           : Set extend the time of 5V power  
591
592 AT+PRO          : Choose agreement
593
594 AT+RXDL  : Extend the sending and receiving time
595
596 AT+DNSCFG  : Get or Set DNS Server
597
598 AT+GETSENSORVALUE   : Returns the current sensor measurement
599
600 AT+NOUD  : Get or Set the number of data to be uploaded
601
602 AT+CDP     : Read or Clear cached data
603
604 AT+SHTEMP:  Get or Set alarm of temp
605
606 AT+SHHUM:  Get or Set alarm of moisture
607
608 AT+SERVADDR :  Server Address
609
610
611 (% style="color:blue" %)**UDP Management**
612
613 AT+CFM  :  Upload confirmation mode (only valid for UDP)
614
615
616 (% style="color:blue" %)**MQTT Management**
617
618 AT+CLIENT               : Get or Set MQTT client
619
620 AT+UNAME              : Get or Set MQTT Username
621
622 AT+PWD                  : Get or Set MQTT password
623
624 AT+PUBTOPIC  : Get or Set MQTT publish topic
625
626 AT+SUBTOPIC  : Get or Set MQTT subscription topic
627
628
629 (% style="color:blue" %)**Information**          
630
631 AT+FDR  : Factory Data Reset
632
633 AT+PWORD  : Serial Access Password
634
635 AT+LDATA  : Get the last upload data
636
637 AT+CDP  : Read or Clear cached data
638
639
640 = 4. Battery & Power Consumption =
641
642
643 MDS120-NB use ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
644
645 [[**Battery Info & Power Consumption Analyze**>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
646
647
648 = 5. Firmware update =
649
650
651 User can change device firmware to::
652
653 * Update with new features.
654
655 * Fix bugs.
656
657 Firmware and changelog can be downloaded from : **[[Firmware download link>>https://www.dropbox.com/sh/bhllnli22hb3hko/AAAKVTr3-dyDMm3RclNjgVFEa?dl=0]]**
658
659 Methods to Update Firmware:
660
661 * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
662
663 * Update through UART TTL interface : **[[Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
664
665 = 6. FAQ =
666
667 == 6.1 How can I access t BC660K-GL AT Commands? ==
668
669
670 User can access to BC660K-GL directly and send AT Commands.
671
672 [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]]
673
674
675 = 7. Order Info =
676
677
678 Part Number: (% style="color:blue" %)**MDS120-NB-XX**
679
680 (% style="color:red" %)**XX**(%%):
681
682 * (% style="color:#037691" %)**GE**(%%): General version ( Exclude SIM card)
683
684 * (% style="color:#037691" %)**1D**(%%): with 1NCE* 10 years 500MB SIM card and Pre-configure to DataCake server
685
686 (% style="color:#037691" %)**1NCE SIM Card NB-IoT network coverage**(%%): Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
687
688
689 = 8. ​Packing Info =
690
691
692 (% style="color:#037691" %)**Package Includes**:
693
694 * MDS120-NB NB-IoT Microwave Radar distance sensor x 1
695
696 * External antenna x 1
697
698 (% style="color:#037691" %)**Dimension and weight**:
699
700 * Device Size: 13.0 x 5 x 4.5 cm
701
702 * Device Weight: 150g
703
704 * Package Size / pcs : 14.0 x 8x 5 cm
705
706 * Weight / pcs : 180g
707
708 = 9. Support =
709
710
711 * 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.
712
713 * 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.cc>>mailto:Support@dragino.cc]].
714
715 (% style="display:none" %) (%%)

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0