Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 149.1
edited by Edwin Chen
on 2024/03/28 07:57
Change comment: There is no comment for this version
To version 173.2
edited by kai
on 2024/07/29 16:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.kai
Content
... ... @@ -25,7 +25,7 @@
25 25  1. Power Off End Node ( See below for the power off/on position)
26 26  1. Insert the SIM card to Sensor. ( See below for direction)
27 27  1. Power On End Node
28 -1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
28 +1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net
29 29  
30 30  [[image:image-20240208102804-1.png||height="286" width="696"]]
31 31  
... ... @@ -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, US Virgin Islands
44 -)))|(% style="width:135px" %)
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
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,6 +62,7 @@
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.
65 65  
66 66  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/]]**
67 67  
... ... @@ -536,11 +536,67 @@
536 536  [[image:image-20230802112413-43.png||height="407" width="825"]]
537 537  
538 538  
539 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
540 540  
541 -=== 3.7.1 Create device & Get Credentials ===
541 +== 3.7 ThingsBoard.Cloud (via COAP) ==
542 542  
543 +=== 3.7.1 Configure ThingsBoard ===
543 543  
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+SERVADDR=COAP Server Address,5683
587 +
588 +Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
589 +
590 +Note:The port for the COAP protocol has been fixed to 5683
591 +
592 +AT+URL1=11,character length,""
593 +
594 +If the module used is BC660K, only one URL directive needs to be configured, e.g. AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
595 +
596 +== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
597 +
598 +=== 3.8.1 Create device & Get Credentials ===
599 +
600 +
544 544  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.
545 545  
546 546  [[image:image-20230802112413-44.png]]
... ... @@ -589,7 +589,7 @@
589 589  
590 590  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
591 591  
592 -=== 3.7.2 Simulate with MQTT.fx ===
649 +=== 3.8.2 Simulate with MQTT.fx ===
593 593  
594 594  
595 595  [[image:image-20230802112413-52.png]]
... ... @@ -605,7 +605,7 @@
605 605  [[image:image-20230808105329-3.png]]
606 606  
607 607  
608 -=== 3.7.3 tago data ===
665 +=== 3.8.3 tago data ===
609 609  
610 610  
611 611  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -613,7 +613,7 @@
613 613  [[image:image-20230802112413-51.png||height="184" width="696"]]
614 614  
615 615  
616 -== 3.8 TCP Connection ==
673 +== 3.9 TCP Connection ==
617 617  
618 618  
619 619  (% style="color:blue" %)**AT command:**
... ... @@ -634,11 +634,68 @@
634 634  [[image:image-20230807233631-2.png]]
635 635  
636 636  
637 -= 4. FAQ =
694 +== 3.10 AWS Connection ==
638 638  
639 -== 4.1 What is the usage of Multi Sampling and One Uplink? ==
640 640  
697 +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]]
641 641  
699 +
700 +
701 +
702 += 4. MQTT/UDP/TCP downlink =
703 +
704 +== 4.1 MQTT (via MQTT.fx) ==
705 +
706 +Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
707 +
708 +**1.** Configure node MQTT connection (via MQTT.fx):
709 +
710 +(% style="color:blue" %)**AT command:**
711 +
712 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
713 +
714 +* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
715 +
716 +* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
717 +
718 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
719 +
720 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
721 +
722 +* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
723 +
724 +(% 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.**
725 +
726 +[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
727 +
728 +
729 +**2. **When the node uplink packets, we can observe the data in MQTT.fx.
730 +
731 +[[image:image-20240418144337-1.png||height="709" width="802"]]
732 +
733 +**3. **The downlink command can be successfully sent only when the downlink port is open.
734 +
735 + The downlink port is opened for about 3 seconds after uplink packets are sent.
736 +
737 + 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.
738 +
739 +[[image:image-20240418150435-3.png||height="582" width="659"]]
740 +
741 +[[image:image-20240418150932-4.png||height="492" width="1061"]]
742 +
743 +(% 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.**
744 +
745 +
746 +
747 +
748 +
749 +
750 +
751 += 5. FAQ =
752 +
753 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
754 +
755 +
642 642  The NB series has the feature for Multi Sampling and one uplink. See one of them
643 643  
644 644  [[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]]
... ... @@ -653,10 +653,9 @@
653 653  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
654 654  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.
655 655  
770 +== 5.2 Why the uplink JSON format is not standard? ==
656 656  
657 -== 4.2 Why the uplink JSON format is not standard? ==
658 658  
659 -
660 660  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.
661 661  
662 662  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
... ... @@ -664,9 +664,9 @@
664 664  [[image:image-20240229233154-1.png]]
665 665  
666 666  
667 -= 5. Trouble Shooting: =
780 += 6. Trouble Shooting: =
668 668  
669 -== 5.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
782 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
670 670  
671 671  
672 672  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.
... ... @@ -693,7 +693,7 @@
693 693  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.
694 694  
695 695  
696 -== 5.2 Issue: "NBIOT did not respond" ==
809 +== 6.2 Issue: "NBIOT did not respond" ==
697 697  
698 698  
699 699  (% class="box errormessage" %)
... ... @@ -721,7 +721,7 @@
721 721  [[image:image-20240208001740-1.png]]
722 722  
723 723  
724 -== 5.3 Issue: "Failed to readI MSI number" ==
837 +== 6.3 Issue: "Failed to readI MSI number" ==
725 725  
726 726  
727 727  (% class="box errormessage" %)
... ... @@ -735,9 +735,76 @@
735 735  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"]].
736 736  
737 737  
738 -== 5.4 Why sometime the AT Command is slow in reponse? ==
851 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
739 739  
740 740  
741 741  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.
742 742  
743 743  [[image:image-20240226111928-1.png]]
857 +
858 +
859 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
860 +
861 +(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
862 +=== UDP: ===
863 +
864 +(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
865 +Its downlink command is the same as the AT command, but brackets are required.
866 +Example:
867 +
868 +{AT+TDC=300}
869 +
870 +
871 +(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
872 +=== MQTT: ===
873 +
874 +Json：
875 +
876 +The Json format in MQTT mode needs to be configured with all commands.
877 +If you have configurations that need to be changed, please change them in the template below.
878 +Template:
879 +
880 +{
881 +"AT+SERVADDR":"119.91.62.30,1882",
882 +"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
883 +"AT+UNAME":"usenamedragino",
884 +"AT+PWD":"passworddragino",
885 +"AT+PUBTOPIC":"123",
886 +"AT+SUBTOPIC":"321",
887 +"AT+TDC":"7200",
888 +"AT+INTMOD":"0",
889 +"AT+APN":"NULL",
890 +"AT+5VT":"0",
891 +"AT+PRO":"3,5",
892 +"AT+TR":"900",
893 +"AT+NOUD":"0",
894 +"AT+CSQTIME":"5",
895 +"AT+DNSTIMER":"0",
896 +"AT+TLSMOD":"0,0",
897 +"AT+MQOS":"0",
898 +"AT+TEMPALARM1":"0",
899 +"AT+TEMPALARM2":"10",
900 +"AT+TEMPALARM3":"0"
901 +}
902 +
903 +Hex：
904 +
905 +MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
906 +
907 +The supported commands are consistent with LoRaWAN's hex commands.
908 +Please refer to the following link to obtain the hex format:
909 +
910 +[[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/]]
911 +
912 +
913 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs？(%%) ==
914 +
915 +* **AT Command: AT** **+GETLOG**
916 +
917 +This command can be used to query upstream logs of data packets.
918 +
919 +[[image:image-20240701114700-1.png]]
920 +
921 +
922 +
923 +
image-20240417173549-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +70.3 KB
Content
image-20240417180145-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +104.1 KB
Content
image-20240417180737-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.7 KB
Content
image-20240418144337-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +95.1 KB
Content
image-20240418144714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.3 KB
Content
image-20240418150435-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +44.1 KB
Content
image-20240418150932-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +103.4 KB
Content
image-20240701114700-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +291.5 KB
Content
image-20240729141300-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +176.9 KB
Content
image-20240729142505-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +202.0 KB
Content
image-20240729144058-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +140.7 KB
Content
image-20240729150142-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +128.0 KB
Content
image-20240729160802-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +162.8 KB
Content
image-20240729161543-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.kai
Size
... ... @@ -1,0 +1,1 @@
1 +166.8 KB
Content