Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 178.1
edited by kai
on 2024/07/29 18:02
Change comment: There is no comment for this version
To version 157.1
edited by Mengting Qiu
on 2024/04/18 14:47
Change comment: Uploaded new attachment "image-20240418144714-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kai
1 +XWiki.ting
Content
... ... @@ -40,8 +40,8 @@
40 40  |(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
41 41  **[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
42 42  
43 -Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
44 -)))|(% style="width:135px" %)UK: Band20
43 +Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
44 +)))|(% style="width:135px" %)
45 45  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
46 46  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
47 47  
... ... @@ -62,7 +62,6 @@
62 62  
63 63  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
64 64  
65 -By default, device will search network for 5 minutes. User can set the time to 10 minutes by (% style="color:#037691" %)**AT+CSQTIME=10 **(%%)so it can search longer.
66 66  
67 67  See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
68 68  
... ... @@ -537,87 +537,11 @@
537 537  [[image:image-20230802112413-43.png||height="407" width="825"]]
538 538  
539 539  
539 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
540 540  
541 -== 3.7 ThingsBoard.Cloud (via COAP) ==
541 +=== 3.7.1 Create device & Get Credentials ===
542 542  
543 -=== 3.7.1 Configure ThingsBoard ===
544 544  
545 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
546 -
547 -
548 -(% style="color:blue" %)**Uplink Converter**
549 -
550 -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.
551 -
552 -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.
553 -
554 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
555 -
556 -
557 -(% style="color:blue" %)**Downlink Converter**
558 -
559 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
560 -
561 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
562 -
563 -
564 -==== 3.7.1.2 COAP Integration Setup ====
565 -
566 -
567 -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" %);
568 -
569 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
570 -
571 -
572 -The next steps is to add the recently created uplink converters;
573 -
574 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
575 -
576 -
577 -==== 3.7.1.3 Add COAP Integration ====
578 -
579 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
580 -
581 -
582 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
583 -
584 -==== 3.7.2.1 Instruction Description ====
585 -
586 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
587 -* AT+SERVADDR=COAP Server Address,5683
588 -
589 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
590 -
591 -[[image:image-20240729172305-12.png||height="361" width="624"]]
592 -
593 -Note:The port for the COAP protocol has been fixed to 5683
594 -
595 -
596 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
597 -
598 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
599 -
600 -e.g.
601 -
602 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
603 -
604 -[[image:image-20240729172415-13.png||height="401" width="694"]]
605 -
606 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
607 -
608 -e.g.
609 -
610 -* AT+URL1=11, "i"; 
611 -* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
612 -
613 -[[image:image-20240729172500-14.png||height="403" width="700"]]
614 -
615 -
616 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
617 -
618 -=== 3.8.1 Create device & Get Credentials ===
619 -
620 -
621 621  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.
622 622  
623 623  [[image:image-20230802112413-44.png]]
... ... @@ -666,7 +666,7 @@
666 666  
667 667  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
668 668  
669 -=== 3.8.2 Simulate with MQTT.fx ===
592 +=== 3.7.2 Simulate with MQTT.fx ===
670 670  
671 671  
672 672  [[image:image-20230802112413-52.png]]
... ... @@ -682,7 +682,7 @@
682 682  [[image:image-20230808105329-3.png]]
683 683  
684 684  
685 -=== 3.8.3 tago data ===
608 +=== 3.7.3 tago data ===
686 686  
687 687  
688 688  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -690,7 +690,7 @@
690 690  [[image:image-20230802112413-51.png||height="184" width="696"]]
691 691  
692 692  
693 -== 3.9 TCP Connection ==
616 +== 3.8 TCP Connection ==
694 694  
695 695  
696 696  (% style="color:blue" %)**AT command:**
... ... @@ -711,14 +711,8 @@
711 711  [[image:image-20230807233631-2.png]]
712 712  
713 713  
714 -== 3.10 AWS Connection ==
715 715  
716 716  
717 -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]]
718 -
719 -
720 -
721 -
722 722  = 4. MQTT/UDP/TCP downlink =
723 723  
724 724  == 4.1 MQTT (via MQTT.fx) ==
... ... @@ -725,11 +725,11 @@
725 725  
726 726  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
727 727  
728 -**1.** Configure node MQTT connection (via MQTT.fx):
645 +**1.** **Configure node MQTT connection (via MQTT.fx):**
729 729  
730 730  (% style="color:blue" %)**AT command:**
731 731  
732 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
649 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
733 733  
734 734  * (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
735 735  
... ... @@ -739,35 +739,19 @@
739 739  
740 740  * (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
741 741  
742 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
659 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) **~/~/ to set MQTT server address and port**
743 743  
744 744  (% 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.**
745 745  
746 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
663 +[[image:image-20240417180145-2.png||height="545" width="737"]]
747 747  
665 +[[image:image-20240417180737-3.png||height="544" width="738"]]
748 748  
749 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
750 750  
751 -[[image:image-20240418144337-1.png||height="709" width="802"]]
752 752  
753 -**3. **The downlink command can be successfully sent only when the downlink port is open.
754 754  
755 - The downlink port is opened for about 3 seconds after uplink packets are sent.
756 756  
757 - 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.
758 758  
759 -[[image:image-20240418150435-3.png||height="582" width="659"]]
760 -
761 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
762 -
763 -(% 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.**
764 -
765 -
766 -
767 -
768 -
769 -
770 -
771 771  = 5. FAQ =
772 772  
773 773  == 5.1 What is the usage of Multi Sampling and One Uplink? ==
... ... @@ -868,76 +868,9 @@
868 868  Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: [[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
869 869  
870 870  
871 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
772 +== 6.4 Why sometime the AT Command is slow in reponse? ==
872 872  
873 873  
874 874  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.
875 875  
876 876  [[image:image-20240226111928-1.png]]
877 -
878 -
879 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
880 -
881 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
882 -=== UDP: ===
883 -
884 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
885 -Its downlink command is the same as the AT command, but brackets are required.
886 -Example:
887 -
888 -{AT+TDC=300}
889 -
890 -
891 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
892 -=== MQTT: ===
893 -
894 -Json：
895 -
896 -The Json format in MQTT mode needs to be configured with all commands.
897 -If you have configurations that need to be changed, please change them in the template below.
898 -Template:
899 -
900 -{
901 -"AT+SERVADDR":"119.91.62.30,1882",
902 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
903 -"AT+UNAME":"usenamedragino",
904 -"AT+PWD":"passworddragino",
905 -"AT+PUBTOPIC":"123",
906 -"AT+SUBTOPIC":"321",
907 -"AT+TDC":"7200",
908 -"AT+INTMOD":"0",
909 -"AT+APN":"NULL",
910 -"AT+5VT":"0",
911 -"AT+PRO":"3,5",
912 -"AT+TR":"900",
913 -"AT+NOUD":"0",
914 -"AT+CSQTIME":"5",
915 -"AT+DNSTIMER":"0",
916 -"AT+TLSMOD":"0,0",
917 -"AT+MQOS":"0",
918 -"AT+TEMPALARM1":"0",
919 -"AT+TEMPALARM2":"10",
920 -"AT+TEMPALARM3":"0"
921 -}
922 -
923 -Hex：
924 -
925 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
926 -
927 -The supported commands are consistent with LoRaWAN's hex commands.
928 -Please refer to the following link to obtain the hex format:
929 -
930 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
931 -
932 -
933 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
934 -
935 -* **AT Command: AT** **+GETLOG**
936 -
937 -This command can be used to query upstream logs of data packets.
938 -
939 -[[image:image-20240701114700-1.png]]
940 -
941 -
942 -
943 -
image-20240418150435-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -103.4 KB
Content
image-20240701114700-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -166.8 KB
Content
image-20240729172234-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -57.8 KB
Content
image-20240729172305-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -49.3 KB
Content
image-20240729172415-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -54.3 KB
Content
image-20240729172500-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -48.6 KB
Content