Skip to Content
Last modified by Mengting Qiu on 2025/06/18 15:53
From version 130.1
edited by Xiaoling
on 2024/09/14 10:55
Change comment: There is no comment for this version
To version 132.1
edited by Mengting Qiu
on 2024/10/18 15:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -235,7 +235,7 @@
235 235  
236 236  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
237 237  
238 -* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
238 +* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
239 239  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
240 240  
241 241  [[image:image-20240819103212-2.png]]
... ... @@ -309,7 +309,6 @@
309 309  
310 310  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
311 311  
312 -
313 313  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
314 314  
315 315  
... ... @@ -349,7 +349,6 @@
349 349  
350 350  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
351 351  
352 -
353 353  ==== 3.3.3.2 Uplink Examples ====
354 354  
355 355  
... ... @@ -421,7 +421,6 @@
421 421  
422 422  * (% style="color:blue" %)**S31B-CB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
423 423  
424 -
425 425  === 3.4.1 For device Already has template ===
426 426  
427 427  ==== 3.4.1.1 Create Device ====
... ... @@ -581,7 +581,6 @@
581 581  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
582 582  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
583 583  
584 -
585 585  == 3.6 ThingsBoard.Cloud (via MQTT) ==
586 586  
587 587  === 3.6.1 Configure ThingsBoard ===
... ... @@ -669,11 +669,90 @@
669 669  [[image:image-20240820112426-40.png]]
670 670  
671 671  
672 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
673 673  
674 -=== 3.7.1 Create device & Get Credentials ===
669 +== 3.7 ThingsBoard.Cloud (via COAP) ==
675 675  
671 +=== 3.7.1 Configure ThingsBoard ===
676 676  
673 +==== 3.7.1.1 Create Uplink & Downlink Converter ====
674 +
675 +
676 +(% style="color:blue" %)**Uplink Converter**
677 +
678 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
679 +
680 +To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
681 +
682 +[[image:image-20240729141300-1.png||height="552" width="1115"]]
683 +
684 +
685 +(% style="color:blue" %)**Downlink Converter**
686 +
687 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
688 +
689 +[[image:image-20240729142505-3.png||height="507" width="1023"]]
690 +
691 +
692 +==== 3.7.1.2 COAP Integration Setup ====
693 +
694 +
695 +Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“CoAP Integration”**(%%), select type **COAP    **(% style="color:blue" %);
696 +
697 +[[image:image-20240729144058-4.png||height="506" width="1021"]]
698 +
699 +
700 +The next steps is to add the recently created uplink converters;
701 +
702 +[[image:image-20240729150142-5.png||height="507" width="1023"]]
703 +
704 +
705 +==== 3.7.1.3 Add COAP Integration ====
706 +
707 +
708 +==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
709 +
710 +
711 +=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
712 +
713 +==== 3.7.2.1 Instruction Description ====
714 +
715 +
716 +* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
717 +* AT+SERVADDR=COAP Server Address,5683
718 +
719 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
720 +
721 +[[image:image-20240729172305-12.png||height="361" width="624"]]
722 +
723 +Note:The port for the COAP protocol has been fixed to 5683
724 +
725 +
726 +* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
727 +
728 +If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
729 +
730 +e.g.
731 +
732 +* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
733 +
734 +[[image:image-20240729172415-13.png||height="401" width="694"]]
735 +
736 +If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
737 +
738 +e.g.
739 +
740 +* AT+URL1=11, "i"
741 +* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
742 +
743 +[[image:image-20240729172500-14.png||height="403" width="700"]]
744 +
745 +
746 +
747 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
748 +
749 +=== 3.8.1 Create device & Get Credentials ===
750 +
751 +
677 677  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
678 678  
679 679  [[image:image-20240820112516-41.png]]
... ... @@ -720,10 +720,9 @@
720 720  
721 721  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
722 722  
798 +=== 3.8.2 Simulate with MQTT.fx ===
723 723  
724 -=== 3.7.2 Simulate with MQTT.fx ===
725 725  
726 -
727 727  [[image:image-20240820112552-44.png]]
728 728  
729 729  [[image:image-20240820112604-45.png]]
... ... @@ -735,7 +735,7 @@
735 735  [[image:image-20240820112626-47.png]]
736 736  
737 737  
738 -=== 3.7.3 tago data ===
812 +=== 3.8.3 tago data ===
739 739  
740 740  
741 741  [[image:image-20240820112637-48.png]]
... ... @@ -743,7 +743,7 @@
743 743  [[image:image-20240820112647-49.png]]
744 744  
745 745  
746 -== 3.8 TCP Connection ==
820 +== 3.9 TCP Connection ==
747 747  
748 748  
749 749  (% style="color:blue" %)**AT command:**
... ... @@ -763,7 +763,7 @@
763 763  [[image:image-20240820112716-51.png]]
764 764  
765 765  
766 -== 3.9 AWS Connection ==
840 +== 3.10 AWS Connection ==
767 767  
768 768  
769 769  Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
... ... @@ -885,7 +885,6 @@
885 885  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
886 886  1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
887 887  
888 -
889 889  == 6.2 Why the uplink JSON format is not standard? ==
890 890  
891 891