Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 95.2 >
edited by Mengting Qiu
on 2024/08/20 11:30
To version < 70.1 >
edited by Mengting Qiu
on 2024/08/20 11:23
>
Change comment: Uploaded new attachment "image-20240820112330-35.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -440,35 +440,35 @@
440 440  
441 441  **Step3: Choose to create a new device**
442 442  
443 -[[image:image-20240820111016-12.png]]
443 +[[image:image-20240129170539-3.png||height="459" width="646"]]
444 444  
445 445  **Step4: Fill in the device ID of your NB device**
446 446  
447 -[[image:image-20240820111101-13.png]]
447 +[[image:image-20240202111546-1.png||height="378" width="651"]]
448 448  
449 449  **Step5: Please select your device plan according to your needs and complete the creation of the device**
450 450  
451 -[[image:image-20240820111113-14.png]]
451 +[[image:image-20240129171236-6.png||height="450" width="648"]]
452 452  
453 453  **Step6: Please add the decoder at the payload decoder of the device configuration.**
454 454  
455 455  **Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
456 456  
457 -[[image:image-20240820111236-15.png]]
457 +[[image:image-20240129172056-7.png||height="457" width="816"]]
458 458  
459 -[[image:image-20240820111248-16.png]]
459 +[[image:image-20240129173116-9.png||height="499" width="814"]]
460 460  
461 461  **Step7: Add the output of the decoder as a field**
462 462  
463 -[[image:image-20240820111259-17.png]]
463 +[[image:image-20240129173541-10.png||height="592" width="968"]]
464 464  
465 465  **Step8: Customize the dashboard and use fields as parameters of the dashboard**
466 466  
467 -[[image:image-20240820111312-18.png]]
467 +[[image:image-20240129174518-11.png||height="147" width="1042"]]
468 468  
469 -[[image:image-20240820111322-19.png]]
469 +[[image:image-20240129174657-12.png||height="538" width="916"]]
470 470  
471 -[[image:image-20240820111333-20.png]]
471 +[[image:image-20240129174840-13.png||height="536" width="750"]]
472 472  
473 473  === 3.4.4 For device have not configured to connect to DataCake ===
474 474  
... ... @@ -495,31 +495,31 @@
495 495  
496 496  The templates for S31-NB and NB95S31B are the same.
497 497  
498 -[[image:image-20240820111353-21.png]]
498 +[[image:image-20230809173127-4.png]]
499 499  
500 500  Please select the NB95S31B template.
501 501  
502 -[[image:image-20240820111405-22.png]]
502 +[[image:image-20230809173310-5.png||height="558" width="926"]]
503 503  
504 -[[image:image-20240820111418-23.png]]
504 +[[image:image-20230809173438-6.png]]
505 505  
506 -[[image:image-20240820111427-24.png]]
506 +[[image:image-20230809173800-7.png]]
507 507  
508 508  Successfully imported template.
509 509  
510 -[[image:image-20240820111438-25.png]]
510 +[[image:image-20230809173835-8.png||height="515" width="860"]]
511 511  
512 512  Users can set UDP port.
513 513  
514 -[[image:image-20240820111448-26.png]]
514 +[[image:image-20230809174053-9.png]]
515 515  
516 516  === 3.5.2 Simulate Connection ===
517 517  
518 518  We have completed the configuration of UDP. We can try sending packets to node red.
519 519  
520 -[[image:image-20240820111504-27.png]]
520 +[[image:image-20230810083934-1.png]]
521 521  
522 -[[image:image-20240820111515-28.png]]
522 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
523 523  
524 524  === 3.5.3 Configure NB-IoT Sensors ===
525 525  
... ... @@ -538,7 +538,7 @@
538 538  
539 539  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
540 540  
541 -[[image:image-20240820112210-29.png]]
541 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
542 542  
543 543  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
544 544  
... ... @@ -548,13 +548,13 @@
548 548  
549 549  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" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
550 550  
551 -[[image:image-20240820112222-30.png]]
551 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
552 552  
553 553  (% style="color:blue" %)**Downlink Converter**
554 554  
555 555  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
556 556  
557 -[[image:image-20240820112236-31.png]]
557 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
558 558  
559 559  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
560 560  
... ... @@ -562,13 +562,13 @@
562 562  
563 563  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" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
564 564  
565 -[[image:image-20240820112247-32.png]]
565 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
566 566  
567 567  * The next steps is to add the recently created uplink and downlink converters;
568 568  
569 -[[image:image-20240820112302-33.png]]
569 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
570 570  
571 -[[image:image-20240820112316-34.png]]
571 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
572 572  
573 573  (% style="color:blue" %)**Add a topic filter:**
574 574  
... ... @@ -576,13 +576,13 @@
576 576  
577 577  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
578 578  
579 -[[image:image-20240820112330-35.png]]
579 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
580 580  
581 581  === 3.6.2 Simulate with MQTT.fx ===
582 582  
583 -[[image:image-20240820112340-36.png]]
583 +[[image:image-20230802112413-39.png]]
584 584  
585 -[[image:image-20240820112351-37.png]]
585 +[[image:image-20230802112413-40.png||height="525" width="980"]]
586 586  
587 587  === 3.6.3 Configure NB-IoT Sensor ===
588 588  
... ... @@ -602,11 +602,11 @@
602 602  
603 603  Test Uplink by click the button for 1 second
604 604  
605 -[[image:image-20240820112404-38.png]]
605 +[[image:image-20230802112413-41.png||height="496" width="828"]]
606 606  
607 -[[image:image-20240820112416-39.png]]
607 +[[image:image-20230802112413-42.png]]
608 608  
609 -[[image:image-20240820112426-40.png]]
609 +[[image:image-20230802112413-43.png||height="407" width="825"]]
610 610  
611 611  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
612 612  
... ... @@ -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-20240820112516-41.png]]
617 +[[image:image-20230802112413-44.png]]
618 618  
619 -[[image:image-20240820112526-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-20240820112539-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-20240820112552-44.png]]
663 +[[image:image-20230802112413-52.png]]
664 664  
665 -[[image:image-20240820112604-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-20240820112615-46.png]]
669 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
670 670  
671 -[[image:image-20240820112626-47.png]]
671 +[[image:image-20230808105329-3.png]]
672 672  
673 673  === 3.7.3 tago data ===
674 674  
675 -[[image:image-20240820112637-48.png]]
675 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
676 676  
677 -[[image:image-20240820112647-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-20240820112704-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-20240820112716-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-20240820112732-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-20240820112813-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-20240820112824-55.png]]
737 +[[image:image-20240418150435-3.png||height="582" width="659"]]
738 738  
739 -[[image:image-20240820112835-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-20240820112848-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-20240820112859-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-20240820112908-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.2 Why 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-20240820113015-60.png]]
817 +[[image:image-20240226111928-1.png]]
818 818  
819 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What 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: ===
image-20240820112340-36.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -24.7 KB
Content
image-20240820112351-37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -68.4 KB
Content
image-20240820112404-38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -40.2 KB
Content
image-20240820112416-39.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -40.9 KB
Content
image-20240820112426-40.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -101.4 KB
Content
image-20240820112516-41.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -78.6 KB
Content
image-20240820112526-42.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -128.5 KB
Content
image-20240820112539-43.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -31.2 KB
Content
image-20240820112552-44.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -28.4 KB
Content
image-20240820112604-45.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -60.9 KB
Content
image-20240820112615-46.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -60.5 KB
Content
image-20240820112626-47.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -21.1 KB
Content
image-20240820112637-48.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -53.1 KB
Content
image-20240820112647-49.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -37.8 KB
Content
image-20240820112704-50.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -21.9 KB
Content
image-20240820112716-51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -9.6 KB
Content
image-20240820112732-52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -95.3 KB
Content
image-20240820112758-53.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -34.7 KB
Content
image-20240820112813-54.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -127.7 KB
Content
image-20240820112824-55.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -24.0 KB
Content
image-20240820112835-56.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -70.6 KB
Content
image-20240820112848-57.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.5 KB
Content
image-20240820112859-58.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20240820112908-59.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20240820113015-60.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -52.0 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0