Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 70.23 >
edited by Xiaoling
on 2022/11/21 10:58
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
Title
... ... @@ -1,1 +1,1 @@
1 -NDS03A - Outdoor NB-IoT Open/Close Door Sensor User Manual
1 +NMDS200 - NB-IoT Microwave Radar Distance Sensor User Manual
Content
... ... @@ -1,59 +1,35 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20221117105556-1.png]]
2 +[[image:LMDS200_10.jpg]]
3 3  
4 4  
5 -
6 -
7 -
8 -
9 -
10 10  **Table of Contents：**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
16 16  
17 -
18 18  = 1.  Introduction =
19 19  
20 -== 1.1 ​ What is NDS03A NB-IoT Open/Close Door Sensor ==
13 +== 1.1 ​ What is NMDS200 NB-IoT Microwave Radar Distance Sensor ==
21 21  
22 22  
23 23  (((
24 -The Dragino NDS03A is an (% style="color:blue" %)**Open/Close NB-IoT Door Sensor**(%%). It detects door (% style="color:blue" %)**open/close status**(%%) and (% style="color:blue" %)**uplinks**(%%) to IoT server via NB-IoT network. NDS03A can connect two door sensors. user can see the door status, open duration, open counts in the IoT Server.
25 -)))
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.
26 26  
27 -(((
28 -The NDS03A will send periodically data (% style="color:blue" %)**every 4 hours** (%%)as well as for each door open/close action. It also counts the door open times and calculates the last door open duration. Users can also disable the uplink for each open/close event, instead, NDS03A can count each open event and uplink periodically.
29 -)))
30 30  
31 -(((
32 -NDS03A has a (% style="color:blue" %)**Datalog feature**(%%), it will record the open/close event and the user can retrieve the history from NB-IoT.
33 -)))
20 +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.
34 34  
35 -(((
36 -NDS03A has the(% style="color:blue" %)**open alarm feature**(%%), user can set this feature so the device will send an alarm if the door has been open for a certain time.
37 -)))
22 +NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
38 38  
39 -(((
40 -NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
41 -)))
24 +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.
42 42  
43 -(((
44 44  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.
45 -)))
46 46  
47 -(((
48 -NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
49 -)))
28 +NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
50 50  
51 -(((
52 -NDS03A 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 -)))
30 +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)
54 54  
55 -(((
56 -To use NDS03A, user needs to check if there is NB-IoT coverage in the field and with the Nb-IoT bands that NDS03A supports. If local operator support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from the operator and install into NDS03A to get NB-IoT network connection.
32 +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.
57 57  )))
58 58  
59 59  
... ... @@ -62,10 +62,9 @@
62 62  
63 63  
64 64  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
65 -* Open/Close detect
66 -* Open/Close statistics
41 +* Short uplink interval for Distance Alarm
67 67  * Monitor Battery Level
68 -* connect two door sensors
43 +* Microwave Radar for distance detection
69 69  * Datalog feature
70 70  * Uplink periodically
71 71  * Downlink to change configure
... ... @@ -77,30 +77,42 @@
77 77  * 8500mAh Battery for long-term use
78 78  
79 79  
80 -== 1.3  Storage & Operation ==
55 +== 1.3 Radar probe specification ==
81 81  
82 82  
83 -Temperature -40°C to +85°C
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°
84 84  
85 85  
86 -== 1.4  Mechanical ==
87 87  
69 +== 1.4  Storage Temperature ==
88 88  
89 -[[image:image-20221117114937-4.png]]
90 90  
72 + -40°C to +85°C
91 91  
92 -[[image:image-20221117114949-5.png]]
93 93  
94 94  
95 -[[image:image-20221117115010-6.png]]
96 96  
97 97  
98 -
99 99  == 1.5 ​ Applications ==
100 100  
101 101  
102 -[[image:image-20221117114842-3.png]]
103 103  
82 +* Horizontal distance measurement
83 +* Liquid level measurement
84 +* Parking management system
85 +* Object proximity and presence detection
86 +* Intelligent trash can management system
87 +* Robot obstacle avoidance
88 +* Automatic control
89 +* Sewer
90 +* Bottom water level monitoring
104 104  
105 105  
106 106  == 1.6  Specification ==
... ... @@ -109,97 +109,61 @@
109 109  (% style="color:blue" %)**Common DC Characteristics:**
110 110  
111 111  * Supply Voltage: 2.1v ~~ 3.6v
112 -* Operating Temperature: -40 ~~ 85°C
99 +* Operating Temperature: 0 ~~ 70°C
113 113  
114 114  (% style="color:blue" %)**NB-IoT Spec:**
115 115  
116 -* - B1 @H-FDD: 2100MHz
117 -* - B3 @H-FDD: 1800MHz
118 -* - B8 @H-FDD: 900MHz
119 -* - B5 @H-FDD: 850MHz
120 -* - B20 @H-FDD: 800MHz
121 -* - B28 @H-FDD: 700MHz
103 +* B1 @H-FDD: 2100MHz
104 +* B3 @H-FDD: 1800MHz
105 +* B8 @H-FDD: 900MHz
106 +* B5 @H-FDD: 850MHz
107 +* B20 @H-FDD: 800MHz
108 +* B28 @H-FDD: 700MHz
122 122  
123 123  
124 -== 1.7  Pin Definitions and Switch ==
111 +== 1.7  Installation ==
125 125  
126 126  
127 -[[image:image-20221021110429-4.png]]
114 +Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
128 128  
129 129  
130 -=== 1.7.1  Pin Definition ===
117 +[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
131 131  
132 132  
133 -The device is pre-configured to connect to a door sensor. The other pins are not used. If user wants to know more about other pins, please refer to the user manual of LSN50v2 at:  [[https:~~/~~/www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0>>https://www.dropbox.com/sh/djkxs7mr17y94mi/AABVlWbM9uzK9OA3mXyAT10Za?dl=0]]
134 134  
121 +== 1.8  Pin Definitions and Switch ==
135 135  
136 -=== 1.7.2  Jumper JP2(Power ON/OFF) ===
137 137  
124 +[[image:1670404362039-351.png]]
138 138  
139 -Power on Device when putting this jumper.
140 140  
127 += 2.  Use NMDS200 to communicate with IoT Server =
141 141  
142 -=== 1.7.3  BOOT MODE / SW1 ===
143 -
144 -
145 -1)  ISP:  upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. The firmware won't run.
146 -
147 -2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
148 -
149 -
150 -=== 1.7.4  Reset Button ===
151 -
152 -
153 -Press to reboot the device.
154 -
155 -
156 -=== 1.7.5  LED ===
157 -
158 -
159 -The LED will blink when :
160 -
161 -1.  Boot the device in flash mode
162 -
163 -2.  Send an uplink packet
164 -
165 -
166 -== 1.8  Magnet Distance ==
167 -
168 -
169 -(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
170 -
171 -(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
172 -
173 -
174 -= 2.  Use NDS03A to communicate with IoT Server =
175 -
176 176  == 2.1  How it works ==
177 177  
178 178  
179 -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.
180 180  
181 -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:
182 182  
183 183  [[image:image-20221021110615-5.png]]
184 184  
185 185  
186 -== 2.2 ​ Configure NDS03A ==
139 +== 2.2 ​ Configure NMDS200 ==
187 187  
188 -=== 2.2.1 Test Requirement ===
189 189  
142 +To use NMDS200 in your city, make sure to meet below requirements:
190 190  
191 -To use NDS03A in your city, make sure to meet below requirements:
192 -
193 193  * Your local operator has already distributed an NB-IoT Network.
194 -* The local NB-IoT network used the band that NDS03A supports.
145 +* The local NB-IoT network used the band that NMDS200 supports.
195 195  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
196 196  
197 -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.
198 198  
199 -[[image:image-20221117142300-1.png]]
150 +[[image:image-20221207173300-4.png]]
200 200  
201 201  
202 -=== 2.2.2 Insert NB-IoT SIM card ===
153 +=== 2.2.1 Insert NB-IoT SIM card ===
203 203  
204 204  
205 205  Insert the NB-IoT Card get from your provider.
... ... @@ -209,10 +209,10 @@
209 209  [[image:image-20221021110745-6.png]] ​
210 210  
211 211  
212 -=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
163 +=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
213 213  
214 214  
215 -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.
216 216  
217 217  (% style="color:blue" %)**Connection:**
218 218  
... ... @@ -235,11 +235,11 @@
235 235  
236 236  * Flow Control: (% style="color:red" %)**None**
237 237  
238 -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**(%%).
239 239  
240 240  ​[[image:image-20221021110817-7.png]]
241 241  
242 -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.
243 243  
244 244  
245 245  (% 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]]
... ... @@ -246,7 +246,7 @@
246 246  
247 247  
248 248  
249 -=== 2.2.4 Use CoAP protocol to uplink data ===
200 +=== 2.2.3 Use CoAP protocol to uplink data ===
250 250  
251 251  
252 252  (% 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/]]
... ... @@ -265,12 +265,12 @@
265 265  [[image:image-20221021110948-8.png]]
266 266  
267 267  
268 -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.
269 269  
270 -[[image:image-20221118103547-9.png||height="605" width="837"]] ​
221 +[[image:1670405841875-916.png]] ​
271 271  
272 272  
273 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
224 +=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
274 274  
275 275  
276 276  (% style="color:blue" %)**AT Commands:**
... ... @@ -288,7 +288,7 @@
288 288  
289 289  ​
290 290  
291 -=== 2.2.6 Use MQTT protocol to uplink data ===
242 +=== 2.2.5 Use MQTT protocol to uplink data ===
292 292  
293 293  
294 294  (% style="color:blue" %)**AT Commands:**
... ... @@ -310,7 +310,7 @@
310 310  ​ [[image:image-20221118103445-7.png]]
311 311  
312 312  
313 -[[image:image-20221118103453-8.png||height="608" width="841"]]
264 +[[image:1670405928926-116.png]]
314 314  
315 315  ​
316 316  
... ... @@ -317,7 +317,7 @@
317 317  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.
318 318  
319 319  
320 -=== 2.2.7 Use TCP protocol to uplink data ===
271 +=== 2.2.6 Use TCP protocol to uplink data ===
321 321  
322 322  
323 323  (% style="color:blue" %)**AT Commands:**
... ... @@ -326,18 +326,19 @@
326 326  
327 327  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
328 328  
329 -​ [[image:image-20221021111125-14.png]]
280 +​ [[image:1670406036256-101.png||height="676" width="713"]]
330 330  
282 +
331 331  [[image:image-20221021111131-15.png]]
332 332  
333 333  ​
334 334  
335 -=== 2.2.8 Change Update Interval ===
287 +=== 2.2.7 Change Update Interval ===
336 336  
337 337  
338 338  User can use below command to change the (% style="color:blue" %)**uplink interval**.
339 339  
340 -* (% 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)
341 341  
342 342  (% style="color:red" %)**NOTE:**
343 343  
... ... @@ -347,70 +347,52 @@
347 347  == 2.3  Uplink Payload ==
348 348  
349 349  
350 -The uplink payload includes 26 bytes in total by default.
302 +The uplink payload includes 23 bytes in total by default.
351 351  
352 352  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.
353 353  
354 -(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
355 355  
356 356  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
357 -|=(% 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**
358 -|=(% 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
359 359  
360 360  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
361 -|(% 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" %)(((
362 362  **1-32 group**
363 363  )))
364 -|(% 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" %)...
365 365  
366 -(% 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.
367 367  
319 +[[image:1670406261143-723.png]]
368 368  
369 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
370 -|=(% 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**
371 -|=(% 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)
372 372  
373 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
374 -|(% 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**
375 -|(% 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
376 376  
377 -(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
378 -|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
379 -**1-32 group**
380 -)))
381 -|(% 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__(%%)**
382 382  
383 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
384 -
385 -[[image:image-20221117145932-2.png]]
386 -
387 -
388 -The payload is ASCII string, representative same HEX:
389 -
390 -**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__(%%)**
391 -
392 392  **where:**
393 393  
394 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
328 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
395 395  
396 396  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
397 397  
398 -* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
332 +* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
399 399  
400 -* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
334 +* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
401 401  
402 402  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
403 403  
404 -* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
338 +* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
405 405  
406 -* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
340 +* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
407 407  
408 -* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
342 +* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
409 409  
410 -* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
344 +* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
411 411  
412 -* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
413 413  
347 +
414 414  == 2.4  Payload Explanation and Sensor Interface ==
415 415  
416 416  === 2.4.1  Device ID ===
... ... @@ -851,7 +851,6 @@
851 851  
852 852  * NDS03A Open/Close Door Sensor x 1
853 853  
854 -
855 855  = 9.  Support =
856 856  
857 857  
1670404362039-351.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
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
LMDS200_10.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20221207170748-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.1 KB
Content
image-20221207170748-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.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-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0