Changes for page wiki_test
Last modified by Mengting Qiu on 2024/09/05 17:35
From version 120.1
edited by Mengting Qiu
on 2023/11/14 10:43
on 2023/11/14 10:43
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 9 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Xiaoling - Content
-
... ... @@ -44,6 +44,7 @@ 44 44 45 45 * NB-IoT Bands: B1/B2/B3/B4/B5/B8/B12/B13/B17/B18/B19/B20/B25/B28/B66/B70/B85 @H-FDD 46 46 * Ultra-low power consumption 47 +* Upload water flow volume 47 47 * Door Open/Close detect 48 48 * Door open/close statistics 49 49 * Datalog Feature ... ... @@ -137,9 +137,6 @@ 137 137 ))) 138 138 |(% style="width:167px" %)Fast press ACT 5 times.|(% style="width:117px" %)Deactivate Device|(% style="width:225px" %)(% style="color:red" %)**Red led**(%%) will solid on for 5 seconds. Means device is in Deep Sleep Mode. 139 139 140 -(% style="color:red" %)**Note: When the device is executing a program, the buttons may become invalid. It is best to press the buttons after the device has completed the program execution.** 141 - 142 - 143 143 == 1.7 BLE connection == 144 144 145 145 ... ... @@ -206,6 +206,7 @@ 206 206 * Wood Door: 10mm ~~ 30mm 207 207 * Iron Door: 30 ~~ 45mm 208 208 207 + 209 209 = 2. Use DS03A-NB to communicate with IoT Server = 210 210 211 211 == 2.1 Send data to IoT server via NB-IoT network == ... ... @@ -284,10 +284,10 @@ 284 284 285 285 This is the General Json Format. As below: 286 286 287 -(% style="color:#4472c4" %)**{"IMEI":"86620705 2559857","Model":"DS03A-NB","level status":1,"alarm status":0,"door open num":0,"last open time":0,"level status2":1,"alarm status2":0,"door open num2":0,"last open time2":0,"battery":3.48,"signal":24,"1":{1,0,0,2023/11/1309:59:01},"2":{0,0,261,2023/11/1303:20:00},"3":{237,9896971,263,2023/11/1303:05:00},"4":{0,29,263,2023/11/1302:20:12},"5":{215,9897015,268,2023/11/1301:58:16},"6":{0,79,261,2023/11/1301:43:16},"7":{227,9896991,5368540,2023/11/1301:18:46},"8":{0,19,5367640,2023/11/1108:53:57}}**286 +(% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"DS03A-NB","flow":217,"battery":3.54,"signal":24,"1":{221,2023/09/20 09:47:01},"2":{0,2023/09/20 09:15:04},"3":{0,2023/09/20 09:00:04},"4":{0,2023/09/20 08:45:03},"5":{0,2023/09/20 08:30:03},"6":{0,2023/09/20 08:15:03},"7":{0,2023/09/20 08:00:04},"8":{0,2023/09/20 07:45:04}}** 288 288 289 289 290 -[[image:image-2023 1113180055-1.png]]289 +[[image:image-20230920175015-3.png||height="613" width="890"]] 291 291 292 292 293 293 (% style="color:red" %)**Notice, from above payload:** ... ... @@ -299,34 +299,18 @@ 299 299 === 2.2.2 HEX format Payload(Type~=0) === 300 300 301 301 302 -This is the HEX Format. HEXformat Payload Single-channel and double-channelpayload have different byte lengths.w301 +This is the HEX Format. As below: 303 303 303 +(% style="color:#4472c4" %)**f8662070583784430b640dda15010003a4650abc400000650ab8180000650ab4940000650ab10f0000650aad8b0000650aaa070000650aa6840000650aa3000000650a9308** 304 304 305 - **The HEX format payload for thesingle-channel modeisas follows:**305 +[[image:image-20230920172200-1.png||height="191" width="1047"]] 306 306 307 -(% style="color:#4472c4" %)**f86620705255985712640d9c180101000000000000006551f424010000000000006551f36500000000000105655195e0ed97040b0001076551925c0000001d000107655187dcd797043700010c655182b80000004f00010565517f34e397041f51eadc655179760000001351e758654f4125** 308 308 309 -[[image:image-20231114091247-2.png||height="186" width="1363"]] 310 - 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 -[[image:image-2023 1114094432-3.png]]310 +[[image:image-20230920173352-2.png||height="636" width="919"]] 315 315 316 316 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 - 325 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 326 - 327 -[[image:image-20231114094838-5.png]] 328 - 329 - 330 330 (% style="color:blue" %)**Version:** 331 331 332 332 These bytes include the hardware and software version. ... ... @@ -375,6 +375,7 @@ 375 375 [[image:image-20230922094043-2.png||height="558" width="851"]] 376 376 377 377 361 + 378 378 === 2.2.4 ThingSpeak Payload(Type~=1) === 379 379 380 380 ... ... @@ -384,7 +384,7 @@ 384 384 385 385 As below: 386 386 387 -(% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3= signal value**371 +(% style="color:#4472c4" %)**field1=Flow value&field2=Battery value&field3=Singal value** 388 388 389 389 [[image:image-20230921104741-1.png||height="565" width="826"]] 390 390 ... ... @@ -429,6 +429,7 @@ 429 429 430 430 **If Disalarm = 0**, DS03A-NB will send uplink at every TDC periodically and send data on each open/close event. This is useful for the application user need to monitor the open/close event in real-time. 431 431 416 + 432 432 (% style="color:red" %)** Note: When Disalarm=0, a high frequently open/close event will cause lots of uplink and drain battery very fast. ** 433 433 434 434 ... ... @@ -436,9 +436,10 @@ 436 436 (% style="color:blue" %)**Keep Status1 & Keep Time1 & Keep Status2 & Keep Time2** 437 437 ))) 438 438 439 -Shows the configure value of [[Alarm Base on Timeout Feature>>||anchor="H2.9AlarmBaseonTimeout"]] 424 +Shows the configure value of [[Alarm Base on Timeout Feature>>||anchor="H2.9A0AlarmBaseonTimeout"]] 440 440 441 441 427 + 442 442 * ((( 443 443 (% style="color:blue" %)**Alarm interval(default: 0)** 444 444 ))) ... ... @@ -451,7 +451,7 @@ 451 451 452 452 DS03A-NB will send this uplink **after** Device Status once join the LoRaWAN network successfully. And DS03A-NB will send uplinks when: 453 453 454 -* Every 2 hours, this interval [[can be changed>>||anchor="H2.7SetTransmitIntervalTime"]]. 440 +* Every 2 hours, this interval [[can be changed>>||anchor="H2.7A0SetTransmitIntervalTime"]]. 455 455 * There is an Open/Close event. (This info can be disabled by AT+DISALARM=1) 456 456 457 457 **1) When (% style="color:blue" %)AT+TTRCHANNEL=1(%%), Uplink Payload totals (% style="color:blue" %)11 bytes. (Default mode)(%%)** ... ... @@ -460,7 +460,7 @@ 460 460 |=(% colspan="5" style="background-color:#4F81BD;color:white;width:515px" %)**Real-Time Open/Close Status, FPORT=2** 461 461 |(% style="width:94px" %)**Size(bytes)**|(% style="width:97px" %)**1**|(% style="width:95px" %)**3**|(% style="width:119px" %)**3**|(% style="width:107px" %)**4** 462 462 |(% style="width:95px" %)**Value**|(% style="width:97px" %)((( 463 -Status & [[Alarm>>||anchor=" 2.10TTRIG126TTRIG2timeoutstatusalarm"]]449 +Status & [[Alarm>>||anchor="H3.3.4A0TTRIG126TTRIG2timeoutstatusalarm"]] 464 464 )))|(% style="width:95px" %)Total open door events|(% style="width:119px" %)((( 465 465 The last door open duration (unit: sec) 466 466 )))|(% style="width:108px" %)Unix TimeStamp ... ... @@ -592,7 +592,7 @@ 592 592 (% style="color:#0000ff" %)**Alarm1 or Alarm2** 593 593 ))) 594 594 595 -See [[Alarm Base on Timeout>>||anchor="H2.9AlarmBaseonTimeout"]] 581 +See [[Alarm Base on Timeout>>||anchor="H2.9A0AlarmBaseonTimeout"]] 596 596 597 597 598 598 * ((( ... ... @@ -753,6 +753,7 @@ 753 753 754 754 * (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge 755 755 742 + 756 756 == 2.7 Set Transmit Interval Time == 757 757 758 758 ... ... @@ -793,9 +793,6 @@ 793 793 ))) 794 794 * ((( 795 795 Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds 796 - 797 - 798 - 799 799 ))) 800 800 801 801 == 2.8 Enable / Disable Alarm == ... ... @@ -817,7 +817,7 @@ 817 817 0xA7 00 ~/~/ Same As AT+DISALARM=0 818 818 819 819 820 -== 2.9 Alarm Base on Timeout == 804 +== 2.9 Alarm Base on Timeout == 821 821 822 822 823 823 DS03A-NB can monitor the timeout for a status change, this feature can be used to monitor some events such as door opening too long etc. Related Parameters are: ... ... @@ -870,6 +870,7 @@ 870 870 * ((( 871 871 (% style="color:#037691" %)**AT+TTRIG1=0,0** (%%) **~-~-> ** Default Value, disable timeout Alarm. 872 872 857 + 873 873 874 874 ))) 875 875 ... ... @@ -891,6 +891,7 @@ 891 891 * ((( 892 892 (% style="color:#037691" %)**AT+TTRIG2=0,0** (%%) **~-~-> ** Default Value, disable timeout Alarm. 893 893 879 + 894 894 895 895 ))) 896 896 ... ... @@ -986,11 +986,49 @@ 986 986 Example: 0D aa => AT+TTRCHANNEL = second byte 987 987 988 988 989 -== 2.13 Cleartheopen door timesandthe duration of thelast open door==975 +== 2.13 Set Time Sync Mode == 990 990 991 991 978 +Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply to this command. 979 + 980 +SYNCMOD is set to 1 by default. If user wants to set a different time from the LoRaWAN server, the user needs to set this to 0. 981 + 992 992 (% style="color:blue" %)**AT Command:** 993 993 984 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %) 985 +|=(% style="width: 155px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 288px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 57px;background-color:#4F81BD;color:white" %)**Response** 986 +|(% style="width:155px" %)((( 987 +AT+SYNCMOD=1 988 +)))|(% style="width:259px" %)((( 989 +Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq) The default is zero time zone. 990 +)))|(% style="width:44px" %)((( 991 +OK 992 +))) 993 +|(% style="width:155px" %)((( 994 +AT+SYNCMOD=1,8 995 +)))|(% style="width:259px" %)((( 996 +Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq) Set to East eight time zone. 997 +)))|(% style="width:44px" %)((( 998 +OK 999 +))) 1000 +|(% style="width:155px" %)AT+SYNCMOD=1,-12|(% style="width:259px" %)Enable Sync system time via LoRaWAN MAC Command (DeviceTimeReq) Set to West Twelve Time Zone.|(% style="width:44px" %)OK 1001 + 1002 +(% style="color:blue" %)**Downlink Command:** 1003 + 1004 +0x28 01 ~/~/ Same As AT+SYNCMOD=1 1005 + 1006 +0x28 01 08 ~/~/ Same As AT+SYNCMOD=1,8 1007 + 1008 +0x28 01 F4 ~/~/ Same As AT+SYNCMOD=1,-12 1009 + 1010 +0x28 00 ~/~/ Same As AT+SYNCMOD=0 1011 + 1012 + 1013 +== 2.14 Clear the open door times and the duration of the last open door == 1014 + 1015 + 1016 +(% style="color:blue" %)**AT Command:** 1017 + 994 994 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 995 995 |=(% style="width: 163px;background-color:#4F81BD;color:white" %)**Command Example**|=(% style="width: 290px; background-color:#4F81BD;color:white" %)**Function**|=(% style="width: 57px;background-color:#4F81BD;color:white" %)**Response** 996 996 |(% style="width:155px" %)AT+CLRC|(% style="width:259px" %)clear the open door times and the duration of the last open door.|(% style="width:44px" %)((( ... ... @@ -1002,7 +1002,7 @@ 1002 1002 The sensor will clear the open door times and the duration of the last open door. 1003 1003 1004 1004 1005 -== 2.1 4Set the count value of the number of open door ==1029 +== 2.15 Set the count value of the number of open door == 1006 1006 1007 1007 1008 1008 (% style="color:blue" %)**AT Command:** ... ... @@ -1174,6 +1174,7 @@ 1174 1174 (% style="color:#037691" %)**1NCE SIM Card NB-IoT network coverage**(%%): Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands 1175 1175 1176 1176 1201 + 1177 1177 = 8. Packing Info = 1178 1178 1179 1179
- image-20231102094508-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.6 KB - Content
- image-20231102100109-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.1 KB - Content
- image-20231113180055-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.2 KB - Content
- image-20231113180254-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -71.5 KB - Content
- image-20231114091229-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -32.8 KB - Content
- image-20231114091247-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -26.0 KB - Content
- image-20231114094432-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -73.6 KB - Content
- image-20231114094816-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.0 KB - Content
- image-20231114094838-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.0 KB - Content