Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 92.1
edited by Mengting Qiu
on 2024/04/02 17:03
To version < 83.2 >
edited by Xiaoling
on 2022/12/08 09:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -1,28 +1,13 @@
1 1  (% style="text-align:center" %)
2 -[[image:LMDS200_10.jpg||height="572" width="572"]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -(% style="display:none" %) (%%)
9 -
10 -
11 -
12 -
13 -
14 14  **Table of Contents：**
15 15  
16 -{{toc/}}
17 17  
18 18  
19 19  
20 20  
21 -
22 -
23 -
24 -
25 -
26 26  = 1.  Introduction =
27 27  
28 28  == 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
... ... @@ -30,33 +30,19 @@
30 30  
31 31  (((
32 32  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.
33 -)))
34 34  
35 -(((
36 36  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.
37 -)))
38 38  
39 -(((
40 40  NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
41 -)))
42 42  
43 -(((
44 44  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.
45 -)))
46 46  
47 -(((
48 48  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.
49 -)))
50 50  
51 -(((
52 52  NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
53 -)))
54 54  
55 -(((
56 56  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)
57 -)))
58 58  
59 -(((
60 60  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.
61 61  )))
62 62  
... ... @@ -78,20 +78,18 @@
78 78  * Micro SIM card slot for NB-IoT SIM
79 79  * 8500mAh Battery for long-term use
80 80  
81 -
82 82  == 1.3 Radar probe specification ==
83 83  
84 84  
85 85  * Measuring Method: FMCW
86 -* Frequency: 24.000 ~~ 24.500 GHz
56 +* Frequency: 24.000 24.500 GHz
87 87  * Measurement output power: 6dBm
88 -* Measure range: 0.5 ~~ 20m
58 +* Measure range: 0.5 20m
89 89  * Accuracy: ±0.1m
90 90  * Resolution: 0.01m
91 91  * Horizontal Angel: 78°
92 92  * Vertical Angel: 23°
93 93  
94 -
95 95  == 1.4  Storage Temperature ==
96 96  
97 97  
... ... @@ -111,7 +111,6 @@
111 111  * Sewer
112 112  * Bottom water level monitoring
113 113  
114 -
115 115  == 1.6  Specification ==
116 116  
117 117  
... ... @@ -129,7 +129,6 @@
129 129  * B20 @H-FDD: 800MHz
130 130  * B28 @H-FDD: 700MHz
131 131  
132 -
133 133  == 1.7  Installation ==
134 134  
135 135  
... ... @@ -136,12 +136,10 @@
136 136  Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
137 137  
138 138  
139 -[[image:image-20221207170748-1.png]]
106 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
140 140  
141 141  
142 - [[image:image-20221207170748-2.png||height="345" width="634"]]
143 143  
144 -
145 145  == 1.8  Pin Definitions and Switch ==
146 146  
147 147  
... ... @@ -157,7 +157,7 @@
157 157  
158 158  The diagram below shows the working flow in the default firmware of NMDS200:
159 159  
160 -[[image:image-20221021110615-5.png||height="996" width="492"]]
125 +[[image:image-20221021110615-5.png]]
161 161  
162 162  
163 163  == 2.2 ​ Configure NMDS200 ==
... ... @@ -171,7 +171,7 @@
171 171  
172 172  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.
173 173  
174 -[[image:image-20221209090938-1.png]]
139 +[[image:image-20221208090742-1.png]]
175 175  
176 176  
177 177  === 2.2.1 Insert NB-IoT SIM card ===
... ... @@ -220,6 +220,7 @@
220 220  (% 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]]
221 221  
222 222  
188 +
223 223  === 2.2.3 Use CoAP protocol to uplink data ===
224 224  
225 225  
... ... @@ -236,7 +236,7 @@
236 236  
237 237  For parameter description, please refer to AT command set
238 238  
239 -[[image:1670471530120-960.png||height="647" width="674"]]
205 +[[image:image-20221021110948-8.png]]
240 240  
241 241  
242 242  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.
... ... @@ -253,9 +253,11 @@
253 253  
254 254  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  Set UDP server address and port
255 255  
256 -​ [[image:1670471559211-638.png]]
222 +* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
257 257  
224 +​ [[image:image-20221021111025-10.png]]
258 258  
226 +
259 259  [[image:image-20221021111033-11.png||height="241" width="576"]]
260 260  
261 261  ​
... ... @@ -279,7 +279,7 @@
279 279  
280 280  * (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
281 281  
282 -​ [[image:1670471584490-640.png]]
250 +​ [[image:image-20221118103445-7.png]]
283 283  
284 284  
285 285  [[image:1670405928926-116.png]]
... ... @@ -298,7 +298,7 @@
298 298  
299 299  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
300 300  
301 -​ [[image:1670471613823-833.png]]
269 +​ [[image:1670406036256-101.png||height="676" width="713"]]
302 302  
303 303  
304 304  [[image:image-20221021111131-15.png]]
... ... @@ -325,15 +325,15 @@
325 325  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.
326 326  
327 327  
328 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:450px" %)
329 -|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:50px" %)**8**|(% style="background-color:#4f81bd; color:white; width:31px" %)**2**|(% style="background-color:#4f81bd; color:white; width:31px" %)**2**|(% style="background-color:#4f81bd; color:white; width:75px" %)**1**|(% style="background-color:#4f81bd; color:white; width:31px" %)**1**|(% style="background-color:#4f81bd; color:white; width:51px" %)**1**|(% style="background-color:#4f81bd; color:white; width:61px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**2**
330 -|(% style="width:93px" %)**Value**|(% style="width:67px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:40px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:45px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:54px" %)MOD|(% style="width:62px" %)Exit flag|(% style="width:94px" %) [[Distance 1>>||anchor="H2.4.5A0Distance"]] |(% style="width:93px" %) [[Distance 2>>||anchor="H2.4.5A0Distance"]]
296 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
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**
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 |(% style="width:93px" %) Distance  2
331 331  
332 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:430px" %)
333 -|(% style="background-color:#4f81bd; color:white; width:80px" %)**4**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**2**|(% style="background-color:#4f81bd; color:white; width:80px" %)**4**|(% style="background-color:#4f81bd; color:white; width:110px" %)(((
300 +(% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
301 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
334 334  **1-32 group**
335 335  )))
336 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.6A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:100px" %)...
304 +|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
337 337  
338 338  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
339 339  
... ... @@ -340,8 +340,10 @@
340 340  [[image:1670406261143-723.png]]
341 341  
342 342  
343 -The payload is ASCII string, representative same HEX: **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__(%%)**
311 +The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
344 344  
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__(%%)**
314 +
345 345  **where:**
346 346  
347 347  * (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
... ... @@ -362,7 +362,6 @@
362 362  
363 363  * (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
364 364  
365 -
366 366  == 2.4  Payload Explanation and Sensor Interface ==
367 367  
368 368  === 2.4.1  Device ID ===
... ... @@ -384,7 +384,7 @@
384 384  
385 385  Specify the software version: 0x64=100, which means firmware version 1.00.
386 386  
387 -For example 0x00 64 : This device is NMDS200 with firmware version 1.0.0.
356 +For example 0x00 64 : This device is NMDS200 1 with firmware version 1.0.0.
388 388  
389 389  
390 390  === 2.4.3  Battery Info ===
... ... @@ -402,17 +402,17 @@
402 402  
403 403  NB-IoT Network signal Strength.
404 404  
405 -(% style="color:blue" %)**Ex1: 0x1d = 29**
374 +**Ex1: 0x1d = 29**
406 406  
407 -(% style="color:#037691" %)**0** (%%) -113dBm or less
376 +**0**  -113dBm or less
408 408  
409 -(% style="color:#037691" %)**1**  (%%) -111dBm
378 +**1**  -111dBm
410 410  
411 -(% style="color:#037691" %)**2...30** (%%) -109dBm... -53dBm
380 +**2...30** -109dBm... -53dBm
412 412  
413 -(% style="color:#037691" %)**31** (%%) -51dBm or greater
382 +**31**   -51dBm or greater
414 414  
415 -(% style="color:#037691" %)**99** (%%) Not known or not detectable
384 +**99**    Not known or not detectable
416 416  
417 417  
418 418  === 2.4.5  Distance ===
... ... @@ -446,12 +446,9 @@
446 446  
447 447  By default, NMDS200 prints the downlink payload to console port.
448 448  
449 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
450 -|(% style="background-color:#4f81bd; color:white" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:97px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:183px" %)**Downlink payload size(bytes)**
451 -|TDC (Transmit Time Interval)|Any|(% style="width:97px" %)01|(% style="width:183px" %)4
452 -|RESET|Any|(% style="width:97px" %)04|(% style="width:183px" %)2
453 -|INTMOD|Any|(% style="width:97px" %)06|(% style="width:183px" %)4
418 +[[image:image-20221021111414-18.png]] ​
454 454  
420 +
455 455  **Examples:**
456 456  
457 457  * (% style="color:#037691" %)**Set TDC**
... ... @@ -481,29 +481,33 @@
481 481  * For each uplink probe, LED will be on for 500ms.
482 482  
483 483  
450 +
451 +
484 484  == 2.7  Distance alarm function ==
485 485  
486 486  
487 487  (% style="color:blue" %)**AT Command: AT+ALARM1=min,max**
488 488  
489 -(% style="color:#037691" %)**Example 1:**
457 +**(% style="color:blue" %)Example 1:**
490 490  
491 -AT+ ALARM1 =60,200  ~/~/ Alarm when distance1 lower than 60.
459 +AT+ ALARM1 =60,200  ~/~/ Alarm when moisture lower than 60.
492 492  
493 493  AT+ ALARM2 =min,max
494 494  
495 495  
496 -(% style="color:#037691" %)**Example 2:**
464 +**(% style="color:blue" %)Example 2:**
497 497  
498 -AT+ ALARM2 =200,1500  ~/~/ Alarm when distance2 lower than 1500.
466 +AT+ ALARM2 =200,1500  ~/~/ Alarm when temperature lower than 1500
499 499  
500 500  
469 +
470 +
501 501  == 2.8  Set the number of data to be uploaded and the recording time ==
502 502  
503 503  
504 504  (% style="color:blue" %)**AT Command:**
505 505  
506 -(% 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, **also the time when the alarm function sends an uplink when it detects an alarm)**
476 +(% 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)
507 507  
508 508  (% 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.
509 509  
... ... @@ -523,19 +523,65 @@
523 523  == 2.10  ​Firmware Change Log ==
524 524  
525 525  
526 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0>>https://www.dropbox.com/sh/8elvp2qi9bcv47a/AAAKp0E2nUffztF0tYhqPoE1a?dl=0]]
496 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0>>https://www.dropbox.com/sh/hacq385w6qgnonr/AAC3D79GFGF1JdZUIzNegn2Ha?dl=0]]
527 527  
528 528  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
529 529  
530 530  
531 -== 2.11 Battery & Power Consumption ==
501 +== 2.11  ​Battery Analysis ==
532 532  
503 +=== 2.11.1  ​Battery Type ===
533 533  
534 -NMDS200 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
535 535  
536 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
506 +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.
537 537  
508 +The battery is designed to last for several years depends on the actual use environment and update interval. 
538 538  
510 +The battery-related documents as below:
511 +
512 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
513 +
514 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
515 +
516 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
517 +
518 +[[image:image-20221021111911-26.png]] ​
519 +
520 +
521 +=== 2.11.2  Power consumption Analyze ===
522 +
523 +
524 +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.
525 +
526 +Instruction to use as below:
527 +
528 +(% 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/]]
529 +
530 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
531 +
532 +* Product Model
533 +
534 +* Uplink Interval
535 +
536 +* Working Mode
537 +
538 +And the Life expectation in difference case will be shown on the right.
539 +
540 +[[image:1666596205057-567.png]] ​
541 +
542 +
543 +=== 2.11.3  ​Battery Note ===
544 +
545 +
546 +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.
547 +
548 +
549 +=== 2.11.4  Replace the battery ===
550 +
551 +
552 +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).
553 +
554 +
539 539  = 3. ​ Access NB-IoT Module =
540 540  
541 541  
... ... @@ -579,13 +579,13 @@
579 579  
580 580  AT+INTMOD            : Set the trigger interrupt mode
581 581  
582 -AT+5VT  : Set extend the time of 5V power  
598 +AT+5VT  : Set extend the time of 5V power  
583 583  
584 -AT+PRO  : Choose agreement
600 +AT+PRO  : Choose agreement
585 585  
586 -AT+RXDL  : Extend the sending and receiving time
602 +AT+RXDL  : Extend the sending and receiving time
587 587  
588 -AT+SERVADDR  : Server Address
604 +AT+SERVADDR  : Server Address
589 589  
590 590  AT+TR      :  Get or Set record time
591 591  
... ... @@ -593,7 +593,7 @@
593 593  
594 594  AT+CDP     :  Read or Clear cached data
595 595  
596 -AT+DEBUG:  Enable or Disable debug mode
612 +AT+DEBUG:  Enable or Disable debug mode
597 597  
598 598  AT+ALARM1:  Get or Set alarm of distance1
599 599  
... ... @@ -609,7 +609,11 @@
609 609  AT+URI :  Resource parameters
610 610  
611 611  
628 +(% style="color:blue" %)**UDP Management**
612 612  
630 +AT+CFM :  Upload confirmation mode (only valid for UDP)
631 +
632 +
613 613  (% style="color:blue" %)**MQTT Management**
614 614  
615 615  AT+CLIENT  : Get or Set MQTT client
... ... @@ -656,16 +656,10 @@
656 656  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.
657 657  
658 658  
659 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
660 -
661 -
662 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
663 -
664 -
665 665  = 7. ​ Order Info =
666 666  
667 667  
668 -Part Number:(% style="color:blue" %)** NMDS200**
682 +Part Number:**(% style="color:blue" %) NMDS200**
669 669  
670 670  
671 671  = 8.  Packing Info =
... ... @@ -675,7 +675,6 @@
675 675  
676 676  * NMDS200 NB-IoT Microwave Radar Distance Sensor x 1
677 677  
678 -
679 679  = 9.  Support =
680 680  
681 681  
1670471530120-960.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.6 KB
Content
1670471559211-638.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -170.6 KB
Content
1670471584490-640.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.1 KB
Content
1670471613823-833.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
image-20221209090938-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -121.9 KB
Content
image-20221212171610-1.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -756.0 KB
Content

Applications

Navigation

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