Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 74.2 >
edited by Xiaoling
on 2022/12/07 17:12
To version < 80.2 >
edited by Xiaoling
on 2022/12/07 18:00
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -51,21 +51,21 @@
51 51  * Micro SIM card slot for NB-IoT SIM
52 52  * 8500mAh Battery for long-term use
53 53  
54 +
54 54  == 1.3 Radar probe specification ==
55 55  
56 56  
57 -Measuring Method: FMCW
58 -Frequency: 24.000 24.500 GHz
59 -Measurement output power: 6dBm
60 -Measure range: 0.5 20m
61 -Accuracy: ±0.1m
62 -Resolution: 0.01m
63 -Horizontal Angel: 78°
64 -Vertical Angel: 23°
58 +* Measuring Method: FMCW
59 +* Frequency: 24.000 24.500 GHz
60 +* Measurement output power: 6dBm
61 +* Measure range: 0.5 20m
62 +* Accuracy: ±0.1m
63 +* Resolution: 0.01m
64 +* Horizontal Angel: 78°
65 +* Vertical Angel: 23°
65 65  
66 66  
67 67  
68 -
69 69  == 1.4  Storage Temperature ==
70 70  
71 71  
... ... @@ -90,7 +90,6 @@
90 90  * Bottom water level monitoring
91 91  
92 92  
93 -
94 94  == 1.6  Specification ==
95 95  
96 96  
... ... @@ -109,7 +109,6 @@
109 109  * B28 @H-FDD: 700MHz
110 110  
111 111  
112 -
113 113  == 1.7  Installation ==
114 114  
115 115  
... ... @@ -126,35 +126,33 @@
126 126  [[image:1670404362039-351.png]]
127 127  
128 128  
129 -= 2.  Use NDS03A to communicate with IoT Server =
127 += 2.  Use NMDS200 to communicate with IoT Server =
130 130  
131 131  == 2.1  How it works ==
132 132  
133 133  
134 -In this user case, the NDS03A is installed on the door edge to detect the open/close event and send the status to the NB-IoT server. The NB-IoT network will forward this value to IoT server via the protocol defined by NDS03A.
132 +The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
135 135  
136 -The diagram below shows the working flow in the default firmware of NDS03A:
134 +The diagram below shows the working flow in the default firmware of NMDS200:
137 137  
138 138  [[image:image-20221021110615-5.png]]
139 139  
140 140  
141 -== 2.2 ​ Configure NDS03A ==
139 +== 2.2 ​ Configure NMDS200 ==
142 142  
143 -=== 2.2.1 Test Requirement ===
144 144  
142 +To use NMDS200 in your city, make sure to meet below requirements:
145 145  
146 -To use NDS03A in your city, make sure to meet below requirements:
147 -
148 148  * Your local operator has already distributed an NB-IoT Network.
149 -* The local NB-IoT network used the band that NDS03A supports.
145 +* The local NB-IoT network used the band that NMDS200 supports.
150 150  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
151 151  
152 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDS03A 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.
148 +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.
153 153  
154 -[[image:image-20221117142300-1.png]]
150 +[[image:image-20221207173300-4.png]]
155 155  
156 156  
157 -=== 2.2.2 Insert NB-IoT SIM card ===
153 +=== 2.2.1 Insert NB-IoT SIM card ===
158 158  
159 159  
160 160  Insert the NB-IoT Card get from your provider.
... ... @@ -164,10 +164,10 @@
164 164  [[image:image-20221021110745-6.png]] ​
165 165  
166 166  
167 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
163 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
168 168  
169 169  
170 -User need to configure NDS03A via serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03A support AT Commands, user can use a USB to TTL adapter to connect to NDS03A and use AT Commands to configure it, as below.
166 +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.
171 171  
172 172  (% style="color:blue" %)**Connection:**
173 173  
... ... @@ -190,11 +190,11 @@
190 190  
191 191  * Flow Control: (% style="color:red" %)**None**
192 192  
193 -Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
189 +Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
194 194  
195 195  ​[[image:image-20221021110817-7.png]]
196 196  
197 -NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
193 +NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
198 198  
199 199  
200 200  (% 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]]
... ... @@ -201,7 +201,7 @@
201 201  
202 202  
203 203  
204 -=== 2.2.4 Use CoAP protocol to uplink data ===
200 +=== 2.2.3 Use CoAP protocol to uplink data ===
205 205  
206 206  
207 207  (% 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/]]
... ... @@ -220,12 +220,12 @@
220 220  [[image:image-20221021110948-8.png]]
221 221  
222 222  
223 -After configuring the server address and (% style="color:green" %)**reset NDS03A**(%%) (via AT+ATZ ), NDS03A will start to uplink sensor values to the CoAP server.
219 +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.
224 224  
225 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
221 +[[image:1670405841875-916.png]] ​
226 226  
227 227  
228 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
224 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
229 229  
230 230  
231 231  (% style="color:blue" %)**AT Commands:**
... ... @@ -243,7 +243,7 @@
243 243  
244 244  ​
245 245  
246 -=== 2.2.6 Use MQTT protocol to uplink data ===
242 +=== 2.2.5 Use MQTT protocol to uplink data ===
247 247  
248 248  
249 249  (% style="color:blue" %)**AT Commands:**
... ... @@ -265,7 +265,7 @@
265 265  ​ [[image:image-20221118103445-7.png]]
266 266  
267 267  
268 -[[image:image-20221118103453-8.png||height="608" width="841"]]
264 +[[image:1670405928926-116.png]]
269 269  
270 270  ​
271 271  
... ... @@ -272,7 +272,7 @@
272 272  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.
273 273  
274 274  
275 -=== 2.2.7 Use TCP protocol to uplink data ===
271 +=== 2.2.6 Use TCP protocol to uplink data ===
276 276  
277 277  
278 278  (% style="color:blue" %)**AT Commands:**
... ... @@ -281,18 +281,19 @@
281 281  
282 282  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
283 283  
284 -​ [[image:image-20221021111125-14.png]]
280 +​ [[image:1670406036256-101.png||height="676" width="713"]]
285 285  
282 +
286 286  [[image:image-20221021111131-15.png]]
287 287  
288 288  ​
289 289  
290 -=== 2.2.8 Change Update Interval ===
287 +=== 2.2.7 Change Update Interval ===
291 291  
292 292  
293 293  User can use below command to change the (% style="color:blue" %)**uplink interval**.
294 294  
295 -* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
292 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
296 296  
297 297  (% style="color:red" %)**NOTE:**
298 298  
... ... @@ -302,70 +302,52 @@
302 302  == 2.3  Uplink Payload ==
303 303  
304 304  
305 -The uplink payload includes 26 bytes in total by default.
302 +The uplink payload includes 23 bytes in total by default.
306 306  
307 307  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.
308 308  
309 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
310 310  
311 311  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
312 -|=(% 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:60px" %)**1**|(% style="width:90px" %)**3**|(% style="width:100px" %)**3**
313 -|=(% 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" %)Door Status|(% style="width:60px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]]|(% style="width:94px" %)door open num(pb14) |(% style="width:93px" %)last open time(pb14)
308 +|=(% 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**
309 +|=(% 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 |(% style="width:93px" %) Distance  2
314 314  
315 315  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
316 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
312 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
317 317  **1-32 group**
318 318  )))
319 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:115px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)|(% style="width:99px" %)last open time(pb14)|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
315 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
320 320  
321 -(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
317 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
322 322  
319 +[[image:1670406261143-723.png]]
323 323  
324 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
325 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:45px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:65px" %)**1**|(% style="width:25px" %)**1**|(% style="width:60px" %)**1**|(% style="width:60px" %)**1**|(% style="width:87px" %)**3**|(% style="width:80px" %)**3**
326 -|=(% style="width: 96px;" %)**Value**|(% style="width:66px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:70px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:55px" %)Door Status(pb14)|(% style="width:57px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb14)|(% style="width:86px" %)door open num(pb14) |(% style="width:82px" %)last open time(pb14)
327 327  
328 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
329 -|(% style="width:80px" %)**1**|(% style="width:80px" %)**1**|(% style="width:88px" %)**3**|(% style="width:81px" %)**3**|(% style="width:50px" %)**4**|(% style="width:75px" %)**1**|(% style="width:75px" %)**3**
330 -|(% style="width:59px" %)Door Status(pb15)|(% style="width:67px" %)[[Alarm Status>>||anchor="H2.7A0AlarmBaseonTimeout"]](pb15)|(% style="width:88px" %)door open num(pb15)|(% style="width:81px" %)last open time(pb15)|(% style="width:50px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:66px" %)Door Status(pb14)|(% style="width:92px" %)door open num(pb14)
322 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
331 331  
332 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
333 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
334 -**1-32 group**
335 -)))
336 -|(% style="width:102px" %)last open time(pb14)|(% style="width:93px" %)Door Status(pb15)|(% style="width:91px" %)door open num(pb15)|(% style="width:100px" %)last open time(pb15)|(% style="width:63px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]|(% style="width:87px" %)......
324 +**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__(%%)**
337 337  
338 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
339 -
340 -[[image:image-20221117145932-2.png]]
341 -
342 -
343 -The payload is ASCII string, representative same HEX:
344 -
345 -**0x (% style="color:red" %)__f867787050213317__  (% style="color:blue" %)__0064__ (% style="color:green" %) __0ccf__(% style="color:#00b0f0" %) __19__(% style="color:#7030a0" %) __01__(% style="color:#0020b0" %) __00__ (% style="color:#420042" %)__00__(% style="color:#660066" %) (% style="color:#aaaa40" %)__000016__(% style="color:#663300" %) __000017__ (% style="color:#d60093" %)__637590df__(%%)**
346 -
347 347  **where:**
348 348  
349 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
328 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
350 350  
351 351  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
352 352  
353 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
332 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
354 354  
355 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
334 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
356 356  
357 357  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
358 358  
359 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
338 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
360 360  
361 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
340 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
362 362  
363 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
342 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
364 364  
365 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
344 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
366 366  
367 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
368 368  
347 +
369 369  == 2.4  Payload Explanation and Sensor Interface ==
370 370  
371 371  === 2.4.1  Device ID ===
1670405841875-916.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content

Applications

Navigation

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