Skip to Content

Changes for page wiki_test

Last modified by Mengting Qiu on 2024/09/05 17:35
From version 117.1
edited by Mengting Qiu
on 2023/11/14 09:48
Change comment: Uploaded new attachment "image-20231114094816-4.png", version {1}
To version 124.1
edited by Mengting Qiu
on 2023/11/14 17:45
Change comment: Uploaded new attachment "image-20231114174523-8.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -299,20 +299,32 @@
299 299  === 2.2.2 HEX format Payload(Type~=0) ===
300 300  
301 301  
302 -This is the HEX Format. As below:
302 +This is the HEX Format. HEX format Payload Single-channel and double-channel payload have different byte lengths.w
303 303  
304 +
305 +**The HEX format payload for the single-channel mode is as follows:**
306 +
304 304  (% style="color:#4472c4" %)**f86620705255985712640d9c180101000000000000006551f424010000000000006551f36500000000000105655195e0ed97040b0001076551925c0000001d000107655187dcd797043700010c655182b80000004f00010565517f34e397041f51eadc655179760000001351e758654f4125**
305 305  
306 306  [[image:image-20231114091247-2.png||height="186" width="1363"]]
307 307  
308 308  
309 -[[image:image-20231114091229-1.png||height="180" width="1584"]]
312 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
310 310  
314 +[[image:image-20231114094432-3.png]]
311 311  
312 312  
317 +
318 +**The HEX format payload for the double-channel mode is as follows:**
319 +
320 +(% style="color:#4472c4" %)**f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125**
321 +
322 +[[image:image-20231114091229-1.png||height="180" width="1584"]]
323 +
324 +
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  
315 -[[image:image-20231113180254-2.png]]
327 +[[image:image-20231114094838-5.png]]
316 316  
317 317  
318 318  (% style="color:blue" %)**Version:**
... ... @@ -374,9 +374,11 @@
374 374  
375 375  (% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=signal value**
376 376  
377 -[[image:image-20230921104741-1.png||height="565" width="826"]]
389 +[[image:image-20231114165017-6.png]]
378 378  
391 +[[image:image-20231114165035-7.png||height="674" width="1036"]]
379 379  
393 +
380 380  == 2.3  ​Uplink Payload ==
381 381  
382 382  === 2.3.1  Sensor Configuration, FPORT~=4 ===
image-20231114094838-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +78.0 KB
Content
image-20231114165017-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +64.0 KB
Content
image-20231114165035-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.7 KB
Content
image-20231114174523-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +51.6 KB
Content