Changes for page NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 17:03
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 6 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -52,7 +52,6 @@ 52 52 * 8500mAh Battery for long-term use 53 53 54 54 55 - 56 56 == 1.3 Radar probe specification == 57 57 58 58 ... ... @@ -67,7 +67,6 @@ 67 67 68 68 69 69 70 - 71 71 == 1.4 Storage Temperature == 72 72 73 73 ... ... @@ -92,7 +92,6 @@ 92 92 * Bottom water level monitoring 93 93 94 94 95 - 96 96 == 1.6 Specification == 97 97 98 98 ... ... @@ -111,7 +111,6 @@ 111 111 * B28 @H-FDD: 700MHz 112 112 113 113 114 - 115 115 == 1.7 Installation == 116 116 117 117 ... ... @@ -140,23 +140,21 @@ 140 140 [[image:image-20221021110615-5.png]] 141 141 142 142 143 -== 2.2 Configure NDS0 3A==139 +== 2.2 Configure NMDS200 == 144 144 145 -=== 2.2.1 Test Requirement === 146 146 142 +To use NMDS200 in your city, make sure to meet below requirements: 147 147 148 -To use NDS03A in your city, make sure to meet below requirements: 149 - 150 150 * Your local operator has already distributed an NB-IoT Network. 151 -* The local NB-IoT network used the band that NDS0 3Asupports.145 +* The local NB-IoT network used the band that NMDS200 supports. 152 152 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 153 153 154 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDS0 3Awill 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. 155 155 156 -[[image:image-20221 117142300-1.png]]150 +[[image:image-20221207173300-4.png]] 157 157 158 158 159 -=== 2.2. 2Insert NB-IoT SIM card ===153 +=== 2.2.1 Insert NB-IoT SIM card === 160 160 161 161 162 162 Insert the NB-IoT Card get from your provider. ... ... @@ -166,10 +166,10 @@ 166 166 [[image:image-20221021110745-6.png]] 167 167 168 168 169 -=== 2.2. 3Connect USB – TTL to NDS03Aand configure it ===163 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it === 170 170 171 171 172 -User need to configure NDS0 3Avia serial port to set the (% style="color:red" %)**Server Address** / **Uplink Topic**(%%) to define where and how-to uplink packets. NDS03Asupport AT Commands, user can use a USB to TTL adapter to connect to NDS03Aand 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. 173 173 174 174 (% style="color:blue" %)**Connection:** 175 175 ... ... @@ -192,11 +192,11 @@ 192 192 193 193 * Flow Control: (% style="color:red" %)**None** 194 194 195 -Make sure the switch is in FLASH position, then power on NDS0 3Aby 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**(%%). 196 196 197 197 [[image:image-20221021110817-7.png]] 198 198 199 -NDS0 3Awill 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. 200 200 201 201 202 202 (% 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]] ... ... @@ -203,7 +203,7 @@ 203 203 204 204 205 205 206 -=== 2.2. 4Use CoAP protocol to uplink data ===200 +=== 2.2.3 Use CoAP protocol to uplink data === 207 207 208 208 209 209 (% 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/]] ... ... @@ -222,12 +222,12 @@ 222 222 [[image:image-20221021110948-8.png]] 223 223 224 224 225 -After configuring the server address and (% style="color:green" %)**reset NDS0 3A**(%%)3Awill 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. 226 226 227 -[[image: image-20221118103547-9.png||height="605" width="837"]] 221 +[[image:1670405841875-916.png]] 228 228 229 229 230 -=== 2.2. 5Use UDP protocol to uplink data(Default protocol) ===224 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) === 231 231 232 232 233 233 (% style="color:blue" %)**AT Commands:** ... ... @@ -245,7 +245,7 @@ 245 245 246 246 247 247 248 -=== 2.2. 6Use MQTT protocol to uplink data ===242 +=== 2.2.5 Use MQTT protocol to uplink data === 249 249 250 250 251 251 (% style="color:blue" %)**AT Commands:** ... ... @@ -267,7 +267,7 @@ 267 267 [[image:image-20221118103445-7.png]] 268 268 269 269 270 -[[image: image-20221118103453-8.png||height="608" width="841"]]264 +[[image:1670405928926-116.png]] 271 271 272 272 273 273 ... ... @@ -274,7 +274,7 @@ 274 274 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. 275 275 276 276 277 -=== 2.2. 7Use TCP protocol to uplink data ===271 +=== 2.2.6 Use TCP protocol to uplink data === 278 278 279 279 280 280 (% style="color:blue" %)**AT Commands:** ... ... @@ -283,18 +283,19 @@ 283 283 284 284 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ Set TCP server address and port 285 285 286 - [[image: image-20221021111125-14.png]]280 + [[image:1670406036256-101.png||height="676" width="713"]] 287 287 282 + 288 288 [[image:image-20221021111131-15.png]] 289 289 290 290 291 291 292 -=== 2.2. 8Change Update Interval ===287 +=== 2.2.7 Change Update Interval === 293 293 294 294 295 295 User can use below command to change the (% style="color:blue" %)**uplink interval**. 296 296 297 -* (% style="color:#037691" %)**AT+TDC= 14400 ** (%%) ~/~/ Set Update Interval to14400s (4 hours)292 +* (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (4 hours) 298 298 299 299 (% style="color:red" %)**NOTE:** 300 300 ... ... @@ -304,70 +304,52 @@ 304 304 == 2.3 Uplink Payload == 305 305 306 306 307 -The uplink payload includes 2 6bytes in total by default.302 +The uplink payload includes 23 bytes in total by default. 308 308 309 309 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. 310 310 311 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:** 312 312 313 313 (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 314 -|=(% 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**315 -|=(% 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" %)dooropennum(pb14)|(% style="width:93px" %)lastopentime(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 316 316 317 317 (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %) 318 -|(% 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" %)((( 319 319 **1-32 group** 320 320 ))) 321 -|(% 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" %)lastopentime(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" %)... 322 322 323 - (%style="color:blue"%)**WhenAT+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. 324 324 319 +[[image:1670406261143-723.png]] 325 325 326 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 327 -|=(% 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** 328 -|=(% 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) 329 329 330 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 331 -|(% 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** 332 -|(% 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 333 333 334 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %) 335 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)((( 336 -**1-32 group** 337 -))) 338 -|(% 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__(%%)** 339 339 340 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data. 341 - 342 -[[image:image-20221117145932-2.png]] 343 - 344 - 345 -The payload is ASCII string, representative same HEX: 346 - 347 -**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__(%%)** 348 - 349 349 **where:** 350 350 351 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050 213317 = f867787050213317328 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071 352 352 353 353 * (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 354 354 355 -* (% style="color:#037691" %)**BAT :**(%%) 0x0cc f= 3279mV = 3.279V332 +* (% style="color:#037691" %)**BAT :**(%%) 0x0cc3 = 3267 mV = 3.267V 356 356 357 -* (% style="color:#037691" %)**Singal: **(%%)0x 19 =25334 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9 358 358 359 359 * (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 360 360 361 -* (% style="color:#037691" %)** Door Status:**(%%)338 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0 362 362 363 -* (% style="color:#037691" %)** Alarm Status: **(%%)0x000340 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239 364 364 365 -* (% style="color:#037691" %)** door opennum: **(%%)0x000016=22342 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317 366 366 367 -* (% style="color:#037691" %)** last open time:00017=23344 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time) 368 368 369 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time) 370 370 347 + 371 371 == 2.4 Payload Explanation and Sensor Interface == 372 372 373 373 === 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