Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 179.1
edited by Bei Jinggeng
on 2024/08/07 11:24
Change comment: There is no comment for this version
To version 151.1
edited by Mengting Qiu
on 2024/04/17 17:35
Change comment: Uploaded new attachment "image-20240417173549-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
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  
... ... @@ -356,9 +356,6 @@
356 356  
357 357  **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]]
358 358  
359 -**Due to version update, please use the following decoder for the new version firmware**
360 -[[dragino-end-node-decoder/Datacake-Dragino_NB_New_Version at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB_New_Version]]
361 -
362 362  [[image:image-20240129172056-7.png||height="457" width="816"]]
363 363  
364 364  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -540,87 +540,11 @@
540 540  [[image:image-20230802112413-43.png||height="407" width="825"]]
541 541  
542 542  
539 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
543 543  
544 -== 3.7 ThingsBoard.Cloud (via COAP) ==
541 +=== 3.7.1 Create device & Get Credentials ===
545 545  
546 -=== 3.7.1 Configure ThingsBoard ===
547 547  
548 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
549 -
550 -
551 -(% style="color:blue" %)**Uplink Converter**
552 -
553 -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.
554 -
555 -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.
556 -
557 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
558 -
559 -
560 -(% style="color:blue" %)**Downlink Converter**
561 -
562 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
563 -
564 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
565 -
566 -
567 -==== 3.7.1.2 COAP Integration Setup ====
568 -
569 -
570 -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" %);
571 -
572 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
573 -
574 -
575 -The next steps is to add the recently created uplink converters;
576 -
577 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
578 -
579 -
580 -==== 3.7.1.3 Add COAP Integration ====
581 -
582 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
583 -
584 -
585 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
586 -
587 -==== 3.7.2.1 Instruction Description ====
588 -
589 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
590 -* AT+SERVADDR=COAP Server Address,5683
591 -
592 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
593 -
594 -[[image:image-20240729172305-12.png||height="361" width="624"]]
595 -
596 -Note:The port for the COAP protocol has been fixed to 5683
597 -
598 -
599 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
600 -
601 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
602 -
603 -e.g.
604 -
605 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
606 -
607 -[[image:image-20240729172415-13.png||height="401" width="694"]]
608 -
609 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
610 -
611 -e.g.
612 -
613 -* AT+URL1=11, "i";  
614 -* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
615 -
616 -[[image:image-20240729172500-14.png||height="403" width="700"]]
617 -
618 -
619 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
620 -
621 -=== 3.8.1 Create device & Get Credentials ===
622 -
623 -
624 624  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.
625 625  
626 626  [[image:image-20230802112413-44.png]]
... ... @@ -669,7 +669,7 @@
669 669  
670 670  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
671 671  
672 -=== 3.8.2 Simulate with MQTT.fx ===
592 +=== 3.7.2 Simulate with MQTT.fx ===
673 673  
674 674  
675 675  [[image:image-20230802112413-52.png]]
... ... @@ -685,7 +685,7 @@
685 685  [[image:image-20230808105329-3.png]]
686 686  
687 687  
688 -=== 3.8.3 tago data ===
608 +=== 3.7.3 tago data ===
689 689  
690 690  
691 691  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -693,7 +693,7 @@
693 693  [[image:image-20230802112413-51.png||height="184" width="696"]]
694 694  
695 695  
696 -== 3.9 TCP Connection ==
616 +== 3.8 TCP Connection ==
697 697  
698 698  
699 699  (% style="color:blue" %)**AT command:**
... ... @@ -714,68 +714,11 @@
714 714  [[image:image-20230807233631-2.png]]
715 715  
716 716  
717 -== 3.10 AWS Connection ==
637 += 4. FAQ =
718 718  
639 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
719 719  
720 -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]]
721 721  
722 -
723 -
724 -
725 -= 4. MQTT/UDP/TCP downlink =
726 -
727 -== 4.1 MQTT (via MQTT.fx) ==
728 -
729 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
730 -
731 -**1.** Configure node MQTT connection (via MQTT.fx):
732 -
733 -(% style="color:blue" %)**AT command:**
734 -
735 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
736 -
737 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
738 -
739 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
740 -
741 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
742 -
743 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
744 -
745 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
746 -
747 -(% 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.**
748 -
749 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
750 -
751 -
752 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
753 -
754 -[[image:image-20240418144337-1.png||height="709" width="802"]]
755 -
756 -**3. **The downlink command can be successfully sent only when the downlink port is open.
757 -
758 - The downlink port is opened for about 3 seconds after uplink packets are sent.
759 -
760 - 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.
761 -
762 -[[image:image-20240418150435-3.png||height="582" width="659"]]
763 -
764 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
765 -
766 -(% 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.**
767 -
768 -
769 -
770 -
771 -
772 -
773 -
774 -= 5. FAQ =
775 -
776 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
777 -
778 -
779 779  The NB series has the feature for Multi Sampling and one uplink. See one of them
780 780  
781 781  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
... ... @@ -790,7 +790,7 @@
790 790  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
791 791  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.
792 792  
793 -== 5.2 Why the uplink JSON format is not standard? ==
656 +== 4.2 Why the uplink JSON format is not standard? ==
794 794  
795 795  
796 796  The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
... ... @@ -800,9 +800,9 @@
800 800  [[image:image-20240229233154-1.png]]
801 801  
802 802  
803 -= 6. Trouble Shooting: =
666 += 5. Trouble Shooting: =
804 804  
805 -== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
668 +== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
806 806  
807 807  
808 808  There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.
... ... @@ -829,7 +829,7 @@
829 829  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.
830 830  
831 831  
832 -== 6.2 Issue: "NBIOT did not respond" ==
695 +== 5.2 Issue: "NBIOT did not respond" ==
833 833  
834 834  
835 835  (% class="box errormessage" %)
... ... @@ -857,7 +857,7 @@
857 857  [[image:image-20240208001740-1.png]]
858 858  
859 859  
860 -== 6.3 Issue: "Failed to readI MSI number" ==
723 +== 5.3 Issue: "Failed to readI MSI number" ==
861 861  
862 862  
863 863  (% class="box errormessage" %)
... ... @@ -871,76 +871,9 @@
871 871  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"]].
872 872  
873 873  
874 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
737 +== 5.4 Why sometime the AT Command is slow in reponse? ==
875 875  
876 876  
877 877  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.
878 878  
879 879  [[image:image-20240226111928-1.png]]
880 -
881 -
882 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
883 -
884 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
885 -=== UDP: ===
886 -
887 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
888 -Its downlink command is the same as the AT command, but brackets are required.
889 -Example:
890 -
891 -{AT+TDC=300}
892 -
893 -
894 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
895 -=== MQTT: ===
896 -
897 -Json：
898 -
899 -The Json format in MQTT mode needs to be configured with all commands.
900 -If you have configurations that need to be changed, please change them in the template below.
901 -Template:
902 -
903 -{
904 -"AT+SERVADDR":"119.91.62.30,1882",
905 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
906 -"AT+UNAME":"usenamedragino",
907 -"AT+PWD":"passworddragino",
908 -"AT+PUBTOPIC":"123",
909 -"AT+SUBTOPIC":"321",
910 -"AT+TDC":"7200",
911 -"AT+INTMOD":"0",
912 -"AT+APN":"NULL",
913 -"AT+5VT":"0",
914 -"AT+PRO":"3,5",
915 -"AT+TR":"900",
916 -"AT+NOUD":"0",
917 -"AT+CSQTIME":"5",
918 -"AT+DNSTIMER":"0",
919 -"AT+TLSMOD":"0,0",
920 -"AT+MQOS":"0",
921 -"AT+TEMPALARM1":"0",
922 -"AT+TEMPALARM2":"10",
923 -"AT+TEMPALARM3":"0"
924 -}
925 -
926 -Hex：
927 -
928 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
929 -
930 -The supported commands are consistent with LoRaWAN's hex commands.
931 -Please refer to the following link to obtain the hex format:
932 -
933 -[[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/]]
934 -
935 -
936 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
937 -
938 -* **AT Command: AT** **+GETLOG**
939 -
940 -This command can be used to query upstream logs of data packets.
941 -
942 -[[image:image-20240701114700-1.png]]
943 -
944 -
945 -
946 -
image-20240417180145-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -59.7 KB
Content
image-20240418144337-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.3 KB
Content
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