Skip to Content

Changes for page wiki_test

Last modified by Mengting Qiu on 2024/09/05 17:35
From version 124.4
edited by Xiaoling
on 2023/11/15 10:28
Change comment: There is no comment for this version
To version 118.3
edited by Mengting Qiu
on 2023/11/14 09:53
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
... ... @@ -38,7 +38,6 @@
38 38  
39 39  [[image:image-20231011093807-6.png||height="278" width="879"]]
40 40  
41 -(% style="display:none" %) (%%)
42 42  
43 43  == 1.2 ​Features ==
44 44  
... ... @@ -300,11 +300,8 @@
300 300  === 2.2.2 HEX format Payload(Type~=0) ===
301 301  
302 302  
303 -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. As below:
304 304  
305 -
306 -**The HEX format payload for the single-channel mode is as follows:**
307 -
308 308  (% style="color:#4472c4" %)**f86620705255985712640d9c180101000000000000006551f424010000000000006551f36500000000000105655195e0ed97040b0001076551925c0000001d000107655187dcd797043700010c655182b80000004f00010565517f34e397041f51eadc655179760000001351e758654f4125**
309 309  
310 310  [[image:image-20231114091247-2.png||height="186" width="1363"]]
... ... @@ -312,19 +312,20 @@
312 312  
313 313  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
314 314  
311 +
315 315  [[image:image-20231114094432-3.png]]
316 316  
317 317  
318 318  
319 -**The HEX format payload for the double-channel mode is as follows:**
320 320  
321 -(% style="color:#4472c4" %)**f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125**
322 322  
323 323  [[image:image-20231114091229-1.png||height="180" width="1584"]]
324 324  
325 325  
321 +
326 326  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
327 327  
324 +
328 328  [[image:image-20231114094838-5.png]]
329 329  
330 330  
... ... @@ -387,11 +387,9 @@
387 387  
388 388  (% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=signal value**
389 389  
390 -[[image:image-20231114165017-6.png]]
387 +[[image:image-20230921104741-1.png||height="565" width="826"]]
391 391  
392 -[[image:image-20231114174523-8.png||height="682" width="1041"]]
393 393  
394 -
395 395  == 2.3  ​Uplink Payload ==
396 396  
397 397  === 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