Last modified by Mengting Qiu on 2024/04/02 17:03
<
From version < 80.2 >
edited by Xiaoling
on 2022/12/07 18:00
To version < 74.1 >
edited by Xiaoling
on 2022/12/07 17:12
>
Change comment: Uploaded new attachment "1670404362039-351.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -14,22 +14,39 @@
14 14  
15 15  
16 16  (((
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.
17 +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.
18 +)))
18 18  
20 +(((
21 +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.
22 +)))
19 19  
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.
24 +(((
25 +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.
26 +)))
21 21  
22 -NMDS200 can (% style="color:blue" %)**measure two distances**(%%): the closest object and next object behind the closest one.
28 +(((
29 +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.
30 +)))
23 23  
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.
32 +(((
33 +NDS03A is designed for outdoor use. It has a weatherproof enclosure and industrial level battery to work in low to high temperatures.
34 +)))
25 25  
36 +(((
26 26  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.
38 +)))
27 27  
28 -NMDS200 (% style="color:blue" %)**supports different uplink**(%%) methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
40 +(((
41 +NDS03A supports different uplink methods including (% style="color:blue" %)**TCP, MQTT, UDP, and CoAP**(%%) for different application requirements.
42 +)))
29 29  
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)
44 +(((
45 +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)
46 +)))
31 31  
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.
48 +(((
49 +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.
33 33  )))
34 34  
35 35  
... ... @@ -38,9 +38,10 @@
38 38  
39 39  
40 40  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 -* Short uplink interval for Distance Alarm
58 +* Open/Close detect
59 +* Open/Close statistics
42 42  * Monitor Battery Level
43 -* Microwave Radar for distance detection
61 +* connect two door sensors
44 44  * Datalog feature
45 45  * Uplink periodically
46 46  * Downlink to change configure
... ... @@ -52,42 +52,30 @@
52 52  * 8500mAh Battery for long-term use
53 53  
54 54  
55 -== 1.3 Radar probe specification ==
73 +== 1.3  Storage & Operation ==
56 56  
57 57  
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°
76 +Temperature -40°C to +85°C
66 66  
67 67  
79 +== 1.4  Mechanical ==
68 68  
69 -== 1.4  Storage Temperature ==
70 70  
82 +[[image:image-20221117114937-4.png]]
71 71  
72 - -40°C to +85°C
73 73  
85 +[[image:image-20221117114949-5.png]]
74 74  
75 75  
88 +[[image:image-20221117115010-6.png]]
76 76  
77 77  
91 +
78 78  == 1.5 ​ Applications ==
79 79  
80 80  
95 +[[image:image-20221117114842-3.png]]
81 81  
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
91 91  
92 92  
93 93  == 1.6  Specification ==
... ... @@ -96,7 +96,7 @@
96 96  (% style="color:blue" %)**Common DC Characteristics:**
97 97  
98 98  * Supply Voltage: 2.1v ~~ 3.6v
99 -* Operating Temperature: 0 ~~ 70°C
105 +* Operating Temperature: -40 ~~ 85°C
100 100  
101 101  (% style="color:blue" %)**NB-IoT Spec:**
102 102  
... ... @@ -108,49 +108,85 @@
108 108  * B28 @H-FDD: 700MHz
109 109  
110 110  
111 -== 1.7  Installation ==
117 +== 1.7  Pin Definitions and Switch ==
112 112  
113 113  
114 -Sensor measure direction and angle is as below. When install the sensor, please make sure the sensor direct to object.
120 +[[image:image-20221021110429-4.png]]
115 115  
116 116  
117 -[[image:image-20221207170748-1.png]] [[image:image-20221207170748-2.png||height="366" width="672"]]
123 +=== 1.7.1  Pin Definition ===
118 118  
119 119  
126 +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]]
120 120  
121 -== 1.8  Pin Definitions and Switch ==
122 122  
129 +=== 1.7.2  Jumper JP2(Power ON/OFF) ===
123 123  
124 -[[image:1670404362039-351.png]]
125 125  
132 +Power on Device when putting this jumper.
126 126  
127 -= 2.  Use NMDS200 to communicate with IoT Server =
128 128  
135 +=== 1.7.3  BOOT MODE / SW1 ===
136 +
137 +
138 +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.
139 +
140 +2)  Flash:  working mode, the device starts to work for NB-IoT connection and sends out console output for further debugging.
141 +
142 +
143 +=== 1.7.4  Reset Button ===
144 +
145 +
146 +Press to reboot the device.
147 +
148 +
149 +=== 1.7.5  LED ===
150 +
151 +
152 +The LED will blink when :
153 +
154 +1.  Boot the device in flash mode
155 +
156 +2.  Send an uplink packet
157 +
158 +
159 +== 1.8  Magnet Distance ==
160 +
161 +
162 +(% style="color:blue" %)**Wood Door:**(%%) 10 ~~ 30mm
163 +
164 +(% style="color:blue" %)**Iron Door:**(%%)**    **30 ~~ 45mm
165 +
166 +
167 += 2.  Use NDS03A to communicate with IoT Server =
168 +
129 129  == 2.1  How it works ==
130 130  
131 131  
132 -The NB-IoT network will forward this value to IoT server via the protocol defined by NMDS200.
172 +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.
133 133  
134 -The diagram below shows the working flow in the default firmware of NMDS200:
174 +The diagram below shows the working flow in the default firmware of NDS03A:
135 135  
136 136  [[image:image-20221021110615-5.png]]
137 137  
138 138  
139 -== 2.2 ​ Configure NMDS200 ==
179 +== 2.2 ​ Configure NDS03A ==
140 140  
181 +=== 2.2.1 Test Requirement ===
141 141  
142 -To use NMDS200 in your city, make sure to meet below requirements:
143 143  
184 +To use NDS03A in your city, make sure to meet below requirements:
185 +
144 144  * Your local operator has already distributed an NB-IoT Network.
145 -* The local NB-IoT network used the band that NMDS200 supports.
187 +* The local NB-IoT network used the band that NDS03A supports.
146 146  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
147 147  
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.
190 +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.
149 149  
150 -[[image:image-20221207173300-4.png]]
192 +[[image:image-20221117142300-1.png]]
151 151  
152 152  
153 -=== 2.2.1 Insert NB-IoT SIM card ===
195 +=== 2.2.2 Insert NB-IoT SIM card ===
154 154  
155 155  
156 156  Insert the NB-IoT Card get from your provider.
... ... @@ -160,10 +160,10 @@
160 160  [[image:image-20221021110745-6.png]] ​
161 161  
162 162  
163 -=== 2.2.2 Connect USB – TTL to NMDS200 and configure it ===
205 +=== 2.2.3 Connect USB – TTL to NDS03A and configure it ===
164 164  
165 165  
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.
208 +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.
167 167  
168 168  (% style="color:blue" %)**Connection:**
169 169  
... ... @@ -186,11 +186,11 @@
186 186  
187 187  * Flow Control: (% style="color:red" %)**None**
188 188  
189 -Make sure the switch is in FLASH position, then power on NMDS200 by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
231 +Make sure the switch is in FLASH position, then power on NDS03A by connecting the (% style="color:orange" %)**Yellow Jumper**(%%).
190 190  
191 191  ​[[image:image-20221021110817-7.png]]
192 192  
193 -NMDS200 will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
235 +NDS03A will output system info once powered on as below, we can enter the **password: 12345678** to access AT Command input.
194 194  
195 195  
196 196  (% 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]]
... ... @@ -197,7 +197,7 @@
197 197  
198 198  
199 199  
200 -=== 2.2.3 Use CoAP protocol to uplink data ===
242 +=== 2.2.4 Use CoAP protocol to uplink data ===
201 201  
202 202  
203 203  (% 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/]]
... ... @@ -216,12 +216,12 @@
216 216  [[image:image-20221021110948-8.png]]
217 217  
218 218  
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.
261 +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.
220 220  
221 -[[image:1670405841875-916.png]] ​
263 +[[image:image-20221118103547-9.png||height="605" width="837"]] ​
222 222  
223 223  
224 -=== 2.2.4 Use UDP protocol to uplink data(Default protocol) ===
266 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
225 225  
226 226  
227 227  (% style="color:blue" %)**AT Commands:**
... ... @@ -239,7 +239,7 @@
239 239  
240 240  ​
241 241  
242 -=== 2.2.5 Use MQTT protocol to uplink data ===
284 +=== 2.2.6 Use MQTT protocol to uplink data ===
243 243  
244 244  
245 245  (% style="color:blue" %)**AT Commands:**
... ... @@ -261,7 +261,7 @@
261 261  ​ [[image:image-20221118103445-7.png]]
262 262  
263 263  
264 -[[image:1670405928926-116.png]]
306 +[[image:image-20221118103453-8.png||height="608" width="841"]]
265 265  
266 266  ​
267 267  
... ... @@ -268,7 +268,7 @@
268 268  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.
269 269  
270 270  
271 -=== 2.2.6 Use TCP protocol to uplink data ===
313 +=== 2.2.7 Use TCP protocol to uplink data ===
272 272  
273 273  
274 274  (% style="color:blue" %)**AT Commands:**
... ... @@ -277,19 +277,18 @@
277 277  
278 278  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  Set TCP server address and port
279 279  
280 -​ [[image:1670406036256-101.png||height="676" width="713"]]
322 +​ [[image:image-20221021111125-14.png]]
281 281  
282 -
283 283  [[image:image-20221021111131-15.png]]
284 284  
285 285  ​
286 286  
287 -=== 2.2.7 Change Update Interval ===
328 +=== 2.2.8 Change Update Interval ===
288 288  
289 289  
290 290  User can use below command to change the (% style="color:blue" %)**uplink interval**.
291 291  
292 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (4 hours)
333 +* (% style="color:#037691" %)**AT+TDC=14400      ** (%%) ~/~/ Set Update Interval to 14400s (4 hours)
293 293  
294 294  (% style="color:red" %)**NOTE:**
295 295  
... ... @@ -299,50 +299,69 @@
299 299  == 2.3  Uplink Payload ==
300 300  
301 301  
302 -The uplink payload includes 23 bytes in total by default.
343 +The uplink payload includes 26 bytes in total by default.
303 303  
304 304  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.
305 305  
347 +(% style="color:blue" %)**When AT+TTRCHANNEL=1:**
306 306  
307 307  (% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
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
350 +|=(% 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**
351 +|=(% 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)
310 310  
311 311  (% border="1.5" style="background-color:#ffffcc; color:green; width:450px" %)
312 -|(% style="width:50px" %)**4**|(% style="width:90px" %)**2**|(% style="width:90px" %)**2**|(% style="width:60px" %)**4**|(% style="width:50px" %)(((
354 +|(% style="width:50px" %)**4**|(% style="width:90px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:60px" %)4|(% style="width:50px" %)(((
313 313  **1-32 group**
314 314  )))
315 -|(% style="width:98px" %)[[Time stamp>>||anchor="H2.4.7A0Timestamp"]]| Distance 1 | Distance  2|(% style="width:67px" %)Time stamp|(% style="width:74px" %)...
357 +|(% 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" %)...
316 316  
317 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NMDS200 uplink data.
359 +(% style="color:blue" %)**When AT+TTRCHANNEL=2:**
318 318  
319 -[[image:1670406261143-723.png]]
320 320  
362 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
363 +|=(% 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**
364 +|=(% 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)
321 321  
322 -The payload is ASCII string, representative same HEX: f867787050471071  0064  0cc3  09  01  00 00ef  013d  6390453d
366 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
367 +|(% 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**
368 +|(% 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)
323 323  
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__(%%)**
370 +(% border="1" cellspacing="5" style="background-color:#ffffcc; color:green; width:510px" %)
371 +|(% style="width:100px" %)**3**|(% style="width:80px" %)**1**|(% style="width:90px" %)**3**|(% style="width:90px" %)**3**|(% style="width:70px" %)**4**|(% style="width:80px" %)(((
372 +**1-32 group**
373 +)))
374 +|(% 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" %)......
325 325  
376 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDS03A uplink data.
377 +
378 +[[image:image-20221117145932-2.png]]
379 +
380 +
381 +The payload is ASCII string, representative same HEX:
382 +
383 +**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__(%%)**
384 +
326 326  **where:**
327 327  
328 -* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050471071 = f867787050471071
387 +* (% style="color:#037691" %)**Device ID:**(%%) 0x f867787050213317 = f867787050213317
329 329  
330 330  * (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
331 331  
332 -* (% style="color:#037691" %)**BAT :**(%%)  0x0cc3 = 3267 mV = 3.267V
391 +* (% style="color:#037691" %)**BAT :**(%%)  0x0ccf = 3279 mV = 3.279V
333 333  
334 -* (% style="color:#037691" %)**Singal: **(%%)0x09 = 9
393 +* (% style="color:#037691" %)**Singal: **(%%)0x19 = 25
335 335  
336 336  * (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
337 337  
338 -* (% style="color:#037691" %)**Exit flag: **(%%)0x00 =0
397 +* (% style="color:#037691" %)**Door Status:**(%%)  0x00=0
339 339  
340 -* (% style="color:#037691" %)**Distance 1: **(%%)0x00ef=239
399 +* (% style="color:#037691" %)**Alarm Status: **(%%)0x00 =0
341 341  
342 -* (% style="color:#037691" %)**Distance 2: **(%%)0x013d =317
401 +* (% style="color:#037691" %)**door open num: **(%%)0x000016 =22
343 343  
344 -* (% style="color:#037691" %)**Timestamp: **(%%)0x6390453d =1670399293 (Unix Time)
403 +* (% style="color:#037691" %)**last open time:   **(%%)0x000017 =23
345 345  
405 +* (% style="color:#037691" %)**Timestamp:**(%%) 0x637590df =1668649183 (Unix Time)
346 346  
347 347  
348 348  == 2.4  Payload Explanation and Sensor Interface ==
... ... @@ -461,6 +461,7 @@
461 461  * After NDS03A join NB-IoT network. The LED will be ON for 3 seconds.
462 462  * For each uplink probe, LED will be on for 500ms.
463 463  
524 +
464 464  == 2.7  Alarm Base on Timeout ==
465 465  
466 466  
... ... @@ -785,6 +785,7 @@
785 785  
786 786  * NDS03A Open/Close Door Sensor x 1
787 787  
849 +
788 788  = 9.  Support =
789 789  
790 790  
1670405841875-916.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
1670405928926-116.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
1670406036256-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -181.0 KB
Content
1670406261143-723.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.9 KB
Content
image-20221207173200-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -76.7 KB
Content
image-20221207173300-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content

Applications

Navigation

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