Changes for page General Manual for -CB , -CS models
Last modified by Mengting Qiu on 2025/03/08 11:35
Change comment:
Uploaded new attachment "image-20240820113015-60.png", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -614,13 +614,13 @@ 614 614 615 615 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. 616 616 617 -[[image:image-202 40820112516-41.png]]617 +[[image:image-20230802112413-44.png]] 618 618 619 -[[image:image-202 40820112526-42.png]]619 +[[image:image-20230802112413-45.png]] 620 620 621 621 Go to the Device section and create a device. Then, go to the section tokens and copy your device-token. 622 622 623 -[[image:image-202 40820112539-43.png]]623 +[[image:image-20230802112413-46.png]] 624 624 625 625 The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command. 626 626 ... ... @@ -660,21 +660,21 @@ 660 660 661 661 === 3.7.2 Simulate with MQTT.fx === 662 662 663 -[[image:image-202 40820112552-44.png]]663 +[[image:image-20230802112413-52.png]] 664 664 665 -[[image:image-202 40820112604-45.png]]665 +[[image:image-20230808105300-2.png||height="553" width="1026"]] 666 666 667 667 Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**. 668 668 669 -[[image:image-202 40820112615-46.png]]669 +[[image:image-20230808105217-1.png||height="556" width="1031"]] 670 670 671 -[[image:image-202 40820112626-47.png]]671 +[[image:image-20230808105329-3.png]] 672 672 673 673 === 3.7.3 tago data === 674 674 675 -[[image:image-202 40820112637-48.png]]675 +[[image:image-20230802112413-50.png||height="242" width="1037"]] 676 676 677 -[[image:image-202 40820112647-49.png]]677 +[[image:image-20230802112413-51.png||height="184" width="696"]] 678 678 679 679 == 3.8 TCP Connection == 680 680 ... ... @@ -688,11 +688,11 @@ 688 688 689 689 (% style="color:blue" %)**Sensor Console Output when Uplink:** 690 690 691 -[[image:image-202 40820112704-50.png]]691 +[[image:image-20230807233631-1.png]] 692 692 693 693 (% style="color:blue" %)**See result in TCP Server:** 694 694 695 -[[image:image-202 40820112716-51.png]]695 +[[image:image-20230807233631-2.png]] 696 696 697 697 == 3.9 AWS Connection == 698 698 ... ... @@ -722,11 +722,11 @@ 722 722 723 723 (% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.** 724 724 725 -[[image:image-202408 20112732-52.png]][[image:image-20240820112758-53.png]]725 +[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584">> width="584"]] 726 726 727 727 **2. **When the node uplink packets, we can observe the data in MQTT.fx. 728 728 729 -[[image:image-20240 820112813-54.png]]729 +[[image:image-20240418144337-1.png||height="709" width="802"]] 730 730 731 731 **3. **The downlink command can be successfully sent only when the downlink port is open. 732 732 ... ... @@ -734,9 +734,9 @@ 734 734 735 735 Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command. 736 736 737 -[[image:image-20240 820112824-55.png]]737 +[[image:image-20240418150435-3.png||height="582" width="659"]] 738 738 739 -[[image:image-20240 820112835-56.png]]739 +[[image:image-20240418150932-4.png||height="492" width="1061"]] 740 740 741 741 (% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.** 742 742 ... ... @@ -782,7 +782,7 @@ 782 782 783 783 The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog. 784 784 785 -[[image:image-20240 820112848-57.png]]785 +[[image:image-20240229233154-1.png]] 786 786 787 787 = 6. Trouble Shooting: = 788 788 ... ... @@ -792,11 +792,11 @@ 792 792 793 793 If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31) 794 794 795 -[[image:image-20240 820112859-58.png]]795 +[[image:image-20240207002003-1.png]] 796 796 797 797 If fail to attach network, it will shows signal 99. as below: 798 798 799 -[[image:image-20240 820112908-59.png]]799 +[[image:image-20240207002129-2.png]] 800 800 801 801 (% class="lead" %) 802 802 When see this issue, below are the checklist: ... ... @@ -810,13 +810,13 @@ 810 810 If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check. 811 811 812 812 813 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6. 2Why sometime the AT Command is slow in reponse?(%%) ==813 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) == 814 814 815 815 When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response. 816 816 817 -[[image:image-20240 820113015-60.png]]817 +[[image:image-20240226111928-1.png]] 818 818 819 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6. 3What is the Downlink Command by the NB device?(%%) ==819 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) == 820 820 821 821 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 822 822 === UDP: ===