Skip to Content

Changes for page wiki_test

Last modified by Mengting Qiu on 2024/09/05 17:35
From version 118.2
edited by Mengting Qiu
on 2023/11/14 09:52
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,12 +295,16 @@
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. 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"]]
... ... @@ -308,20 +308,19 @@
308 308  
309 309  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  
311 -
312 312  [[image:image-20231114094432-3.png]]
313 313  
314 314  
315 315  
318 +**The HEX format payload for the double-channel mode is as follows:**
316 316  
320 +(% style="color:#4472c4" %)**f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125**
317 317  
318 318  [[image:image-20231114091229-1.png||height="180" width="1584"]]
319 319  
320 320  
321 -
322 322  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
323 323  
324 -
325 325  [[image:image-20231114094838-5.png]]
326 326  
327 327  
... ... @@ -384,9 +384,11 @@
384 384  
385 385  (% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=signal value**
386 386  
387 -[[image:image-20230921104741-1.png||height="565" width="826"]]
389 +[[image:image-20231114165017-6.png]]
388 388  
391 +[[image:image-20231114174523-8.png||height="682" width="1041"]]
389 389  
393 +
390 390  == 2.3  ​Uplink Payload ==
391 391  
392 392  === 2.3.1  Sensor Configuration, FPORT~=4 ===
... ... @@ -631,7 +631,7 @@
631 631  |=(% colspan="5" style="background-color:#4F81BD;color:white;width:515px" %)**Real-Time Open/Close Status, FPORT=3**
632 632  |(% style="width:60px" %)**Size(bytes)**|(% style="width:80px" %)**1**|(% style="width:120px" %)**3**|(% style="width:150px" %)**3**|(% style="width:90px" %)**4**
633 633  |(% style="width:95px" %)**Value**|(% style="width:97px" %)(((
634 -Status & [[Alarm>>||anchor="H2.9A0AlarmBaseonTimeout"]]
638 +Status & [[Alarm>>||anchor="2.9AlarmBaseonTimeout"]]
635 635  )))|(% style="width:95px" %)Total open door events|(% style="width:119px" %)(((
636 636  The last door open duration (unit: sec)
637 637  )))|(% style="width:108px" %)Unix TimeStamp
... ... @@ -750,6 +750,7 @@
750 750  * (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge
751 751  
752 752  * (% style="color:#037691" %)**AT+INTMOD=3  **(%%) ~/~/ Trigger by rising edge
757 +(% style="display:none" %) (%%)
753 753  
754 754  == 2.7 Set Transmit Interval Time ==
755 755  
... ... @@ -791,10 +791,8 @@
791 791  )))
792 792  * (((
793 793  Example 2: Downlink Payload: 0100003C  ~/~/ Set Transmit Interval (TDC) = 60 seconds
794 -
795 -
796 -
797 797  )))
800 +(% style="display:none" %) (%%)
798 798  
799 799  == 2.8 Enable / Disable Alarm ==
800 800  
... ... @@ -955,7 +955,7 @@
955 955  Example:  0B aa  => AT+COUNTMOD = second byte
956 956  
957 957  
958 -== 2.12  Number of channel of door sensors ==
961 +== 2.12 Number of channel of door sensors ==
959 959  
960 960  
961 961  Feature: Set the number of door sensor channels.
... ... @@ -984,7 +984,7 @@
984 984  Example:  0D aa => AT+TTRCHANNEL = second byte
985 985  
986 986  
987 -== 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 ==
988 988  
989 989  
990 990  (% style="color:blue" %)**AT Command:**
... ... @@ -1000,7 +1000,7 @@
1000 1000  The sensor will clear the open door times and the duration of the last open door.
1001 1001  
1002 1002  
1003 -== 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 ==
1004 1004  
1005 1005  
1006 1006  (% style="color:blue" %)**AT Command:**
... ... @@ -1042,6 +1042,7 @@
1042 1042  * AT Command via Bluetooth Connection (**Recommended**): [[BLE Configure Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
1043 1043  
1044 1044  * 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" %) (%%)
1045 1045  
1046 1046  == 3.2 AT Commands Set ==
1047 1047  
... ... @@ -1147,6 +1147,7 @@
1147 1147  * (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
1148 1148  
1149 1149  * 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" %) (%%)
1150 1150  
1151 1151  = 6. FAQ =
1152 1152  
... ... @@ -1190,6 +1190,7 @@
1190 1190  * Package Size / pcs : 14.0 x 8x 5 cm
1191 1191  
1192 1192  * Weight / pcs : 180g
1198 +(% style="display:none" %) (%%)
1193 1193  
1194 1194  = 9. Support =
1195 1195  
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