Skip to Content

Changes for page wiki_test

Last modified by Mengting Qiu on 2024/09/05 17:35
From version 137.1
edited by Mengting Qiu
on 2024/03/16 15:10
Change comment: There is no comment for this version
To version 152.1
edited by Mengting Qiu
on 2024/06/11 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -292,16 +292,16 @@
292 292  
293 293  **The General Json format payload for the single-channel mode is as follows:**
294 294  
295 -(% style="color:#4472c4" %)**{"IMEI":"866207052559857","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/13 09:59:01},"2":{0,0,261,2023/11/13 03:20:00},"3":{237,9896971,263,2023/11/13 03:05:00},"4":{0,29,263,2023/11/13 02:20:12},"5":{215,9897015,268,2023/11/13 01:58:16},"6":{0,79,261,2023/11/13 01:43:16},"7":{227,9896991,5368540,2023/11/13 01:18:46},"8":{0,19,5367640,2023/11/11 08:53:57}}**
295 +(% style="color:#4472c4" %)**{"IMEI":"863663062798914","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.34,"signal":17,"1":[1,0,0,"2024/06/11 03:09:07"],"2":[1,0,0,"2024/06/11 02:51:00"],"3":[1,0,0,"2024/06/11 02:36:00"],"4":[8,100,100,"2024/05/30 10:19:53"],"5":[8,100,100,"2024/05/30 10:19:18"],"6":[8,100,100,"2024/05/30 10:17:53"],"7":[8,100,100,"2024/05/30 10:16:53"],"8":[8,100,100,"2024/05/30 10:16:28"]}**
296 296  
297 -[[image:image-20231115162221-7.png]]
297 +[[image:image-20240611150437-1.png||height="733" width="958"]]
298 298  
299 299  
300 300  **The General Json format payload for the double-channel mode is as follows:**
301 301  
302 -(% style="color:#4472c4" %)**{"IMEI":"866207058378443","Model":"DS03A-NB","level status":1,"alarm status":0,"door open num":2,"last open time":0,"level status2":1,"alarm status2":0,"door open num2":3,"last open time2":0,"battery":3.39,"signal":25,"1":{1,4,0,1,3,0,2023/11/15 07:54:30},"2":{1,3,0,1,6,1,2023/11/15 07:10:04},"3":{0,0,0,1,1,0,2023/11/15 06:55:04},"4":{0,0,0,1,0,0,2023/11/15 06:40:04},"5":{0,0,0,1,0,0,2023/11/15 03:50:36},"6":{0,0,0,1,4,11,2023/11/15 03:28:16},"7":{0,0,0,1,4,11,2023/11/15 03:13:16},"8":{0,0,0,1,3,11,2023/11/15 02:58:25}}**
302 +(% style="color:#4472c4" %)**{"IMEI":"863663062798914","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.34,"signal":15,"1":[1,0,0,1,0,0,"2024/06/11 05:49:07"],"2":[0,200,300,1,0,0,"2024/06/11 05:34:07"],"3":[0,200,300,1,0,0,"2024/06/11 05:19:07"],"4":[0,200,300,1,0,0,"2024/06/11 05:04:07"],"5":[0,200,300,1,0,0,"2024/06/11 04:49:07"],"6":[0,200,300,1,0,0,"2024/06/11 04:34:07"],"7":[0,200,300,1,0,0,"2024/06/11 04:19:07"],"8":[0,200,300,1,0,0,"2024/06/11 04:04:07"]}**
303 303  
304 -[[image:image-20231115161803-6.png]]
304 +[[image:image-20240611150520-2.png||height="733" width="945"]]
305 305  
306 306  
307 307  (% style="color:red" %)**Notice, from above payload:**
... ... @@ -308,7 +308,7 @@
308 308  
309 309  * level status, alarm status, door open num, last open time, level status2, alarm status2, door open sum2, last open time2, Battery & Signal are the value at uplink time.
310 310  
311 -* 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):
311 +* Json entry 1 ~~ 8 are the last 1 ~~ 8 sampling data as specify by (% style="color:#037691" %)**AT+CLOCKLOG=1,65535,15,8 ** (%%)Command. Each entry includes (from left to right):
312 312  
313 313   Single-channel mode: level status, door open num, last open time, Sampling time.
314 314  
... ... @@ -324,27 +324,27 @@
324 324  
325 325  **The HEX format payload for the single-channel mode is as follows:**
326 326  
327 -(% style="color:#4472c4" %)**f86620705255985712640d9c180101000000000000006551f424010000000000006551f36500000000000105655195e0ed97040b0001076551925c0000001d000107655187dcd797043700010c655182b80000004f00010565517f34e397041f51eadc655179760000001351e758654f4125**
327 +(% style="color:#4472c4" %)**062798914127b0d00120101000000000000006667e2e0010000000000006667e1cf010000000000006667de4b010000000000006667dac7010000000000006667d743010000000000006667d3bf010000000000006667d03b010000000000006667ccb7010000000000006667c7c7**
328 328  
329 -[[image:image-20231114091247-2.png||height="186" width="1363"]]
330 330  
330 +[[image:image-20240611151016-5.png]]
331 331  
332 332  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
333 333  
334 -[[image:image-20231114094432-3.png]]
334 +[[image:image-20240611151101-6.png||height="753" width="980"]]
335 335  
336 336  
337 337  
338 338  **The HEX format payload for the double-channel mode is as follows:**
339 339  
340 -(% style="color:#4472c4" %)**f86620705255985712640db71701010000000000000001000000000000006552d13401000000000000000000000000006551f365000000000001050000005f00005f655195e0ed97040b0001070000005c00005c6551925c0000001d00010700000033000033655187dcd797043700010c00000033000033655182b80000004f0001050000003300003365517f34e397041f51eadc00000000000000655179760000001351e75800000000000000654f4125**
340 +(% style="color:#4472c4" %)**062798914127b0cea0e01010000000000000001000000000000006667e66a01000000000000010000000000006667e55301000000000000000000c800012c6667e1cf01000000000000000000c800012c6667de4b01000000000000000000c800012c6667dac701000000000000000000c800012c6667d74301000000000000000000c800012c6667d3bf01000000000000000000c800012c6667d03b01000000000000000000c800012c6667ccb7**
341 341  
342 -[[image:image-20231114091229-1.png||height="180" width="1584"]]
343 343  
343 +[[image:image-20240611151148-7.png]]
344 344  
345 345  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
346 346  
347 -[[image:image-20231114094838-5.png]]
347 +[[image:image-20240611151206-8.png||height="741" width="961"]]
348 348  
349 349  
350 350  (% style="color:blue" %)**Version:**
... ... @@ -353,7 +353,7 @@
353 353  
354 354  (% style="color:#037691" %)**Higher byte:**(%%) Specify Sensor Model: 0x12 for DS03A-NB
355 355  
356 -(% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x64=100, means firmware version 1.0.0
356 +(% style="color:#037691" %)**Lower byte:**(%%) Specify the software version: 0x7b=123, means firmware version 1.2.3
357 357  
358 358  
359 359  (% style="color:blue" %)**BAT (Battery Info):**
... ... @@ -390,24 +390,66 @@
390 390  
391 391  Type3 payload special design for ThingsBoard, it will also configure other default server to ThingsBoard.
392 392  
393 +**The type3 format payload for the single-channel mode is as follows:**
394 +
393 393  (% style="color:#4472c4" %)**{
394 - "IMEI": "866207058378443",
396 + "topic": "2276492",
397 + "payload": {
398 + "IMEI": "863663062798914",
395 395   "Model": "DS03A-NB",
396 396   "level status": 1,
397 397   "alarm status": 0,
398 - "door open num": 6,
399 - "last open time": 1,
402 + "door open num": 0,
403 + "last open time": 0,
400 400   "level status2": 1,
401 401   "alarm status2": 0,
402 - "door open num2": 2,
406 + "door open num2": 0,
403 403   "last open time2": 0,
404 - "battery": 3.4,
405 - "signal": 24
406 - }**
408 + "battery": 3.33,
409 + "signal": 22,
410 + "1": [1, 0, 0, "2024/06/11 06:08:46"],
411 + "2": [1, 0, 0, "2024/06/11 05:49:07"],
412 + "3": [1, 0, 0, "2024/06/11 05:34:07"],
413 + "4": [1, 0, 0, "2024/06/11 05:19:07"],
414 + "5": [1, 0, 0, "2024/06/11 05:04:07"],
415 + "6": [1, 0, 0, "2024/06/11 04:49:07"],
416 + "7": [1, 0, 0, "2024/06/11 04:34:07"],
417 + "8": [1, 0, 0, "2024/06/11 04:19:07"]
418 + }
419 +}**(%%)
420 +[[image:image-20240611151445-9.png]]
407 407  
408 -[[image:image-20231115150948-1.png||height="625" width="1188"]]
422 +**The type3 format payload for the double-channel mode is as follows:**
409 409  
424 +(% style="color:#4472c4" %)**{
425 + "topic": "2276492",
426 + "payload": {
427 + "IMEI": "863663062798914",
428 + "Model": "DS03A-NB",
429 + "level status": 1,
430 + "alarm status": 0,
431 + "door open num": 0,
432 + "last open time": 0,
433 + "level status2": 1,
434 + "alarm status2": 0,
435 + "door open num2": 0,
436 + "last open time2": 0,
437 + "battery": 3.34,
438 + "signal": 20,
439 + "1": [1, 0, 0, 1, 0, 0, "2024/06/11 06:08:46"],
440 + "2": [1, 0, 0, 1, 0, 0, "2024/06/11 05:49:07"],
441 + "3": [0, 200, 300, 1, 0, 0, "2024/06/11 05:34:07"],
442 + "4": [0, 200, 300, 1, 0, 0, "2024/06/11 05:19:07"],
443 + "5": [0, 200, 300, 1, 0, 0, "2024/06/11 05:04:07"],
444 + "6": [0, 200, 300, 1, 0, 0, "2024/06/11 04:49:07"],
445 + "7": [0, 200, 300, 1, 0, 0, "2024/06/11 04:34:07"],
446 + "8": [0, 200, 300, 1, 0, 0, "2024/06/11 04:19:07"]
447 + }
448 +}**
410 410  
450 +[[image:image-20240611151543-10.png]]
451 +
452 +
411 411  === 2.2.4 ThingSpeak Payload(Type~=1) ===
412 412  
413 413  
... ... @@ -440,6 +440,8 @@
440 440  == 2.4 Multi-Samplings and One uplink ==
441 441  
442 442  
485 +(% style="color:red" %)**Notice: The AT+NOUD feature is upgraded to Clock Logging, please refer [[Clock Logging Feature>>||anchor="H2.14Clocklogging28Sincefirmwareversionv1.2.129"]].**
486 +
443 443  To save battery life, DS03A-NB will sample Water Flow data every 15 minutes and send one uplink every 2 hours. So each uplink it will include 8 stored data + 1 real-time data. They are defined by:
444 444  
445 445  * (% style="color:#037691" %)**AT+TR=900**   (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds (15 minutes, the minimum can be set to 180 seconds)
... ... @@ -747,11 +747,9 @@
747 747  0xA6 02 00 00 32  ==>  AT+SETCNT=2,50
748 748  
749 749  
750 -
751 -
752 -
753 753  == 2.14 Clock logging (Since firmware version v1.2.1) ==
754 754  
796 +
755 755  Sometimes when we deploy lots of end nodes in field. We want all sensors sample data at the same time, and upload these data together for analyze. In such case, we can use clock loging feature.
756 756  
757 757  We can use this command to set the start time of data recording and the time interval to meet the requirements of the specific collection time of data.
... ... @@ -760,7 +760,7 @@
760 760  
761 761  (% style="color:blue" %)**a:**(%%)** 0:** Disable Clock logging.  ** 1: **Enable Clock Logging
762 762  
763 -(% style="color:blue" %)**b:**(%%)** **Specify First sampling start second: range **(0 ~~ 3599, 65535)   ** ~/~/**Note: **If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.
805 +(% style="color:blue" %)**b:**(%%)** **Specify First sampling start second: range **(0 ~~ 3599, 65535)   ** ~/~/ (% style="color:red" %)**Note:**(%%)** **If parameter b is set to 65535, the log period starts after the node accesses the network and sends packets.
764 764  
765 765  (% style="color:blue" %)**c:**(%%)** **Specify the sampling interval: range **(0 ~~ 255 minutes)**
766 766  
... ... @@ -781,11 +781,20 @@
781 781  (% style="color:red" %)**Note: Users need to synchronize the server time before configuring this command. If the server time is not synchronized before this command is configured, the command takes effect only after the node is reset.**
782 782  
783 783  
826 +* (% style="color:blue" %)**Downlink Command: 0x0A**
784 784  
828 +Format: Command Code (0x0A) followed by 5 bytes.
785 785  
830 +* **Example 1**: Downlink Payload:** 0A01FFFF0F08**  ~/~/ Set SHT record time: AT+CLOCKLOG=1,65535,15,8
831 +* **Example 1**: Downlink Payload:** 0A0104B00F08**  ~/~/ Set SHT record time: AT+CLOCKLOG=1,1200,15,8
786 786  
787 -== 2.8 Example Query saved historical records ==
833 +(% style="color:red" %)**Note: When entering the downlink payload, there must be no Spaces between bytes.**
788 788  
835 +
836 +
837 +== 2.15 Example Query saved historical records ==
838 +
839 +
789 789  * (% style="color:blue" %)**AT Command: AT+CDP**
790 790  
791 791  This command can be used to search the saved history, recording up to 32 groups of data, each group of historical data contains a maximum of 100 bytes.
... ... @@ -794,11 +794,47 @@
794 794  [[image:image-20240316151014-2.png||height="632" width="825"]]
795 795  
796 796  
848 +== 2.16 Uplink log query ==
797 797  
798 798  
851 +* (% style="color:blue" %)**AT Command: AT+GETLOG**
799 799  
853 +This command can be used to query upstream logs of data packets.
800 800  
855 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-NB-NA_NB-IoT_Analog_Sensor_User_Manual/WebHome/image-20240407191922-2.png?width=903&height=631&rev=1.1||alt="image-20240407191922-2.png"]]
801 801  
857 +
858 +== 2.17 Scheduled domain name resolution ==
859 +
860 +
861 +This command is used to set up scheduled domain name resolution.
862 +
863 +(% style="color:blue" %)**AT command:**
864 +
865 +* (% style="color:#037691" %)**AT+DNSTIMER=XX   **(%%)~/~/ Unit: hour
866 +
867 +After setting this command, domain name resolution will be performed regularly.
868 +
869 +
870 +== 2.18 Set the QoS level ==
871 +
872 +This command is used to set the QoS level of **MQTT**.
873 +
874 +(% style="color:blue" %)**AT command:**
875 +
876 +* (% style="color:#037691" %)**AT+MQOS=xx**(%%)**  **~/~/ 0~~2
877 +
878 +(% style="color:blue" %)**Downlink Command: 0x07**
879 +
880 +Format: Command Code (0x07) followed by 1 byte.
881 +
882 +**Ex1:** Downlink payload: **0x0700**  ~/~/AT+MQOS=0
883 +
884 +**Ex2:** Downlink payload: **0x0701**  ~/~/AT+MQOS=1
885 +
886 +
887 +
888 +
802 802  = 3. Configure DS03A-NB =
803 803  
804 804  == 3.1 Configure Methods ==
... ... @@ -862,11 +862,6 @@
862 862  AT+SERVADDR :  Server Address
863 863  
864 864  
865 -(% style="color:blue" %)**UDP Management**
866 -
867 -AT+CFM  :  Upload confirmation mode (only valid for UDP)
868 -
869 -
870 870  (% style="color:blue" %)**MQTT Management**
871 871  
872 872  AT+CLIENT               : Get or Set MQTT client
... ... @@ -919,7 +919,7 @@
919 919  
920 920  = 6. FAQ =
921 921  
922 -== 6.1 How can I access t BC660K-GL AT Commands? ==
1004 +== 6.1 How can I access the BC660K-GL AT Commands? ==
923 923  
924 924  
925 925  User can access to BC660K-GL directly and send AT Commands.
... ... @@ -927,6 +927,13 @@
927 927  [[See BC660K-GL AT Command set>>url:https://www.dropbox.com/sh/5f6ssda5fum8rvs/AABT68l8ZzWOvZ5eg2qwOoFda?dl=0]]
928 928  
929 929  
1012 +== 6.2 How to configure the certificate? ==
1013 +
1014 +
1015 +User can can refer to this [[description>>url:http://wiki.dragino.com/xwiki/bin/view/How%20to%20configure%20the%20certificate%3F/]] to configure the certificate.
1016 +
1017 +
1018 +
930 930  = 7. Order Info =
931 931  
932 932  
image-20240611150437-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +46.6 KB
Content
image-20240611150520-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +48.8 KB
Content
image-20240611150928-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +29.8 KB
Content
image-20240611150954-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +29.8 KB
Content
image-20240611151016-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +29.8 KB
Content
image-20240611151101-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +37.2 KB
Content
image-20240611151148-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +34.1 KB
Content
image-20240611151206-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +41.4 KB
Content
image-20240611151445-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +107.4 KB
Content
image-20240611151543-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +108.3 KB
Content
image-20240611151637-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +15.6 KB
Content