Changes for page General Manual for -CB , -CS models
Last modified by Mengting Qiu on 2025/03/08 11:35
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Xiaoling - 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 Options238 +* (% 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,6 +309,7 @@ 309 309 310 310 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 311 311 312 + 312 312 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 313 313 314 314 ... ... @@ -348,6 +348,7 @@ 348 348 349 349 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 350 350 352 + 351 351 ==== 3.3.3.2 Uplink Examples ==== 352 352 353 353 ... ... @@ -419,6 +419,7 @@ 419 419 420 420 * (% 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. 421 421 424 + 422 422 === 3.4.1 For device Already has template === 423 423 424 424 ==== 3.4.1.1 Create Device ==== ... ... @@ -578,6 +578,7 @@ 578 578 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 579 579 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 580 580 584 + 581 581 == 3.6 ThingsBoard.Cloud (via MQTT) == 582 582 583 583 === 3.6.1 Configure ThingsBoard === ... ... @@ -665,83 +665,11 @@ 665 665 [[image:image-20240820112426-40.png]] 666 666 667 667 672 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == 668 668 669 -== 3.7 ThingsBoard.Cloud(viaCOAP)==674 +=== 3.7.1 Create device & Get Credentials === 670 670 671 -=== 3.7.1 Configure ThingsBoard === 672 672 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:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729141300-1.png?width=1115&height=552&rev=1.1||alt="image-20240729141300-1.png" height="579" width="1168"]] 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:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729142505-3.png?width=1023&height=507&rev=1.1||alt="image-20240729142505-3.png" height="579" width="1168"]] 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:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729144058-4.png?width=1021&height=506&rev=1.1||alt="image-20240729144058-4.png" height="583" width="1176"]] 698 - 699 - 700 -The next steps is to add the recently created uplink converters; 701 - 702 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729150142-5.png?width=1023&height=507&rev=1.1||alt="image-20240729150142-5.png" height="591" width="1193"]] 703 - 704 - 705 -==== 3.7.1.3 Add COAP Integration ==== 706 - 707 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729161543-9.png?width=1009&height=500&rev=1.1||alt="image-20240729161543-9.png" height="590" width="1191"]] 708 - 709 - 710 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) === 711 - 712 -==== 3.7.2.1 Instruction Description ==== 713 - 714 - 715 -* AT+PRO=1,0(HEX format uplink) &AT+PRO=1,5(JSON format uplink) 716 -* AT+SERVADDR=COAP Server Address,5683 717 - 718 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created) 719 - 720 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172305-12.png?width=624&height=361&rev=1.1||alt="image-20240729172305-12.png" height="417" width="721"]] 721 - 722 -Note:The port for the COAP protocol has been fixed to 5683 723 - 724 - 725 -* AT+URL1=11,"i" 726 -* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform" 727 -* 728 - 729 --CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands, 730 - 731 -e.g. 732 - 733 -* AT+URL1=11, "i" 734 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858" 735 - 736 - 737 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20240729172500-14.png?width=700&height=403&rev=1.1||alt="image-20240729172500-14.png" height="413" width="718"]] 738 - 739 - 740 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == 741 - 742 -=== 3.8.1 Create device & Get Credentials === 743 - 744 - 745 745 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. 746 746 747 747 [[image:image-20240820112516-41.png]] ... ... @@ -788,9 +788,10 @@ 788 788 789 789 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 790 790 791 -=== 3.8.2 Simulate with MQTT.fx === 792 792 724 +=== 3.7.2 Simulate with MQTT.fx === 793 793 726 + 794 794 [[image:image-20240820112552-44.png]] 795 795 796 796 [[image:image-20240820112604-45.png]] ... ... @@ -802,7 +802,7 @@ 802 802 [[image:image-20240820112626-47.png]] 803 803 804 804 805 -=== 3. 8.3 tago data ===738 +=== 3.7.3 tago data === 806 806 807 807 808 808 [[image:image-20240820112637-48.png]] ... ... @@ -810,7 +810,7 @@ 810 810 [[image:image-20240820112647-49.png]] 811 811 812 812 813 -== 3. 9TCP Connection ==746 +== 3.8 TCP Connection == 814 814 815 815 816 816 (% style="color:blue" %)**AT command:** ... ... @@ -830,7 +830,7 @@ 830 830 [[image:image-20240820112716-51.png]] 831 831 832 832 833 -== 3. 10AWS Connection ==766 +== 3.9 AWS Connection == 834 834 835 835 836 836 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]] ... ... @@ -952,6 +952,7 @@ 952 952 1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 953 953 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. 954 954 888 + 955 955 == 6.2 Why the uplink JSON format is not standard? == 956 956 957 957