Skip to Content

Changes for page wiki_test

Last modified by Mengting Qiu on 2024/09/05 17:35
From version 124.7
edited by Xiaoling
on 2023/11/15 10:30
Change comment: There is no comment for this version
To version 119.2
edited by Mengting Qiu
on 2023/11/14 10:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -54,7 +54,6 @@
54 54  * Downlink to change configure
55 55  * 8500mAh Battery for long term use
56 56  * Nano SIM card slot for NB-IoT SIM
57 -(% style="display:none" %) (%%)
58 58  
59 59  == 1.3 Specification ==
60 60  
... ... @@ -100,8 +100,11 @@
100 100  
101 101  * STOP Mode: 10uA @ 3.3v
102 102  * Max transmit power: 350mA@3.3v
102 +
103 +(% class="wikigeneratedid" id="H1.4Ratedenvironmentalconditions" %)
103 103  (% style="display:none" %) (%%)
104 104  
106 +
105 105  == 1.4 Applications ==
106 106  
107 107  
... ... @@ -203,7 +203,6 @@
203 203  
204 204  * Wood Door: 10mm ~~ 30mm
205 205  * Iron Door: 30 ~~ 45mm
206 -(% style="display:none" %) (%%)
207 207  
208 208  = 2. Use DS03A-NB to communicate with IoT Server =
209 209  
... ... @@ -298,7 +298,7 @@
298 298  === 2.2.2 HEX format Payload(Type~=0) ===
299 299  
300 300  
301 -This is the HEX Format. HEX format Payload Single-channel and double-channel payload have different byte lengths.w
302 +This is the HEX Format. HEX format Payload Single-channel and double-channel payload have different byte lengths.
302 302  
303 303  
304 304  **The HEX format payload for the single-channel mode is as follows:**
... ... @@ -310,19 +310,22 @@
310 310  
311 311  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
312 312  
314 +
313 313  [[image:image-20231114094432-3.png]]
314 314  
315 315  
316 -
317 317  **The HEX format payload for the double-channel mode is as follows:**
318 318  
319 -(% style="color:#4472c4" %)**f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125**
320 +f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125
320 320  
322 +
321 321  [[image:image-20231114091229-1.png||height="180" width="1584"]]
322 322  
323 323  
326 +
324 324  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
325 325  
329 +
326 326  [[image:image-20231114094838-5.png]]
327 327  
328 328  
... ... @@ -385,11 +385,9 @@
385 385  
386 386  (% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=signal value**
387 387  
388 -[[image:image-20231114165017-6.png]]
392 +[[image:image-20230921104741-1.png||height="565" width="826"]]
389 389  
390 -[[image:image-20231114174523-8.png||height="682" width="1041"]]
391 391  
392 -
393 393  == 2.3  ​Uplink Payload ==
394 394  
395 395  === 2.3.1  Sensor Configuration, FPORT~=4 ===
image-20231114165017-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -64.0 KB
Content
image-20231114165035-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.7 KB
Content
image-20231114174523-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -51.6 KB
Content