Skip to Content

Changes for page wiki_test

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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -54,6 +54,7 @@
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" %) (%%)
57 57  
58 58  == 1.3 Specification ==
59 59  
... ... @@ -99,11 +99,8 @@
99 99  
100 100  * STOP Mode: 10uA @ 3.3v
101 101  * Max transmit power: 350mA@3.3v
102 -
103 -(% class="wikigeneratedid" id="H1.4Ratedenvironmentalconditions" %)
104 104  (% style="display:none" %) (%%)
105 105  
106 -
107 107  == 1.4 Applications ==
108 108  
109 109  
... ... @@ -205,6 +205,7 @@
205 205  
206 206  * Wood Door: 10mm ~~ 30mm
207 207  * Iron Door: 30 ~~ 45mm
206 +(% style="display:none" %) (%%)
208 208  
209 209  = 2. Use DS03A-NB to communicate with IoT Server =
210 210  
... ... @@ -295,11 +295,12 @@
295 295  * Distance , Battery & Signal are the value at uplink time.
296 296  
297 297  * Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+NOUD=8 ** (%%)Command. Each entry includes (from left to right): Water Flow, Sampling time.
297 +(% style="display:none" %) (%%)
298 298  
299 299  === 2.2.2 HEX format Payload(Type~=0) ===
300 300  
301 301  
302 -This is the HEX Format. HEX format Payload Single-channel and double-channel payload have different byte lengths.
302 +This is the HEX Format. HEX format Payload Single-channel and double-channel payload have different byte lengths.w
303 303  
304 304  
305 305  **The HEX format payload for the single-channel mode is as follows:**
... ... @@ -311,22 +311,19 @@
311 311  
312 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.
313 313  
314 -
315 315  [[image:image-20231114094432-3.png]]
316 316  
317 317  
317 +
318 318  **The HEX format payload for the double-channel mode is as follows:**
319 319  
320 -f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125
320 +(% style="color:#4472c4" %)**f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125**
321 321  
322 -
323 323  [[image:image-20231114091229-1.png||height="180" width="1584"]]
324 324  
325 325  
326 -
327 327  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
328 328  
329 -
330 330  [[image:image-20231114094838-5.png]]
331 331  
332 332  
... ... @@ -389,9 +389,11 @@
389 389  
390 390  (% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=signal value**
391 391  
392 -[[image:image-20230921104741-1.png||height="565" width="826"]]
389 +[[image:image-20231114165017-6.png]]
393 393  
391 +[[image:image-20231114174523-8.png||height="682" width="1041"]]
394 394  
393 +
395 395  == 2.3  ​Uplink Payload ==
396 396  
397 397  === 2.3.1  Sensor Configuration, FPORT~=4 ===
... ... @@ -636,7 +636,7 @@
636 636  |=(% colspan="5" style="background-color:#4F81BD;color:white;width:515px" %)**Real-Time Open/Close Status, FPORT=3**
637 637  |(% style="width:60px" %)**Size(bytes)**|(% style="width:80px" %)**1**|(% style="width:120px" %)**3**|(% style="width:150px" %)**3**|(% style="width:90px" %)**4**
638 638  |(% style="width:95px" %)**Value**|(% style="width:97px" %)(((
639 -Status & [[Alarm>>||anchor="H2.9A0AlarmBaseonTimeout"]]
638 +Status & [[Alarm>>||anchor="2.9AlarmBaseonTimeout"]]
640 640  )))|(% style="width:95px" %)Total open door events|(% style="width:119px" %)(((
641 641  The last door open duration (unit: sec)
642 642  )))|(% style="width:108px" %)Unix TimeStamp
... ... @@ -755,6 +755,7 @@
755 755  * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge
756 756  
757 757  * (% style="color:#037691" %)**AT+INTMOD=3  **(%%) ~/~/ Trigger by rising edge
757 +(% style="display:none" %) (%%)
758 758  
759 759  == 2.7 Set Transmit Interval Time ==
760 760  
... ... @@ -796,10 +796,8 @@
796 796  )))
797 797  * (((
798 798  Example 2: Downlink Payload: 0100003C  ~/~/ Set Transmit Interval (TDC) = 60 seconds
799 -
800 -
801 -
802 802  )))
800 +(% style="display:none" %) (%%)
803 803  
804 804  == 2.8 Enable / Disable Alarm ==
805 805  
... ... @@ -960,7 +960,7 @@
960 960  Example:  0B aa  => AT+COUNTMOD = second byte
961 961  
962 962  
963 -== 2.12  Number of channel of door sensors ==
961 +== 2.12 Number of channel of door sensors ==
964 964  
965 965  
966 966  Feature: Set the number of door sensor channels.
... ... @@ -989,7 +989,7 @@
989 989  Example:  0D aa => AT+TTRCHANNEL = second byte
990 990  
991 991  
992 -== 2.13  Clear the open door times and the duration of the last open door ==
990 +== 2.13 Clear the open door times and the duration of the last open door ==
993 993  
994 994  
995 995  (% style="color:blue" %)**AT Command:**
... ... @@ -1005,7 +1005,7 @@
1005 1005  The sensor will clear the open door times and the duration of the last open door.
1006 1006  
1007 1007  
1008 -== 2.14  Set the count value of the number of open door ==
1006 +== 2.14 Set the count value of the number of open door ==
1009 1009  
1010 1010  
1011 1011  (% style="color:blue" %)**AT Command:**
... ... @@ -1047,6 +1047,7 @@
1047 1047  * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
1048 1048  
1049 1049  * AT Command via UART Connection : See [[UART Connection>>http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H2.3UARTConnectionforSN50v3basemotherboard]].
1048 +(% style="display:none" %) (%%)
1050 1050  
1051 1051  == 3.2 AT Commands Set ==
1052 1052  
... ... @@ -1152,6 +1152,7 @@
1152 1152  * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
1153 1153  
1154 1154  * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]**.
1154 +(% style="display:none" %) (%%)
1155 1155  
1156 1156  = 6. FAQ =
1157 1157  
... ... @@ -1195,6 +1195,7 @@
1195 1195  * Package Size / pcs : 14.0 x 8x 5 cm
1196 1196  
1197 1197  * Weight / pcs : 180g
1198 +(% style="display:none" %) (%%)
1198 1198  
1199 1199  = 9. Support =
1200 1200  
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