Skip to Content
Last modified by Mengting Qiu on 2025/07/03 18:55
From version 180.1
edited by Xiaoling
on 2024/08/07 15:10
Change comment: There is no comment for this version
To version 153.1
edited by Mengting Qiu
on 2024/04/17 18:07
Change comment: Uploaded new attachment "image-20240417180737-3.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
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  
... ... @@ -164,8 +164,6 @@
164 164  
165 165  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
166 166  
167 -
168 -
169 169  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
170 170  
171 171  
... ... @@ -207,8 +207,6 @@
207 207  
208 208  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
209 209  
210 -
211 -
212 212  ==== 3.3.3.2 Uplink Examples ====
213 213  
214 214  
... ... @@ -270,7 +270,6 @@
270 270  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
271 271  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
272 272  
273 -
274 274  == 3.4 [[Datacake>>https://datacake.co/]] ==
275 275  
276 276  
... ... @@ -285,13 +285,10 @@
285 285  
286 286  * (% style="color:blue" %)**S31B-NB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
287 287  
288 -
289 -
290 290  === 3.4.1 For device Already has template ===
291 291  
292 292  ==== 3.4.1.1 Create Device ====
293 293  
294 -
295 295  (% style="color:blue" %)**Add Device**(%%) in DataCake.
296 296  
297 297  [[image:image-20230808162301-1.png||height="453" width="952"]]
... ... @@ -362,11 +362,8 @@
362 362  
363 363  **Step6: Please add the decoder at the payload decoder of the device configuration.**
364 364  
365 -**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]]
356 +**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]]
366 366  
367 -**Due to version update, please use the following decoder for the new version firmware:**
368 -[[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]]
369 -
370 370  [[image:image-20240129172056-7.png||height="457" width="816"]]
371 371  
372 372  [[image:image-20240129173116-9.png||height="499" width="814"]]
... ... @@ -457,8 +457,6 @@
457 457  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
458 458  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
459 459  
460 -
461 -
462 462  == 3.6 ThingsBoard.Cloud (via MQTT) ==
463 463  
464 464  === 3.6.1 Configure ThingsBoard ===
... ... @@ -550,88 +550,11 @@
550 550  [[image:image-20230802112413-43.png||height="407" width="825"]]
551 551  
552 552  
553 -== 3.7 ThingsBoard.Cloud (via COAP) ==
539 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
554 554  
555 -=== 3.7.1 Configure ThingsBoard ===
541 +=== 3.7.1 Create device & Get Credentials ===
556 556  
557 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
558 558  
559 -
560 -(% style="color:blue" %)**Uplink Converter**
561 -
562 -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.
563 -
564 -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.
565 -
566 -[[image:image-20240729141300-1.png||height="552" width="1115"]]
567 -
568 -
569 -(% style="color:blue" %)**Downlink Converter**
570 -
571 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
572 -
573 -[[image:image-20240729142505-3.png||height="507" width="1023"]]
574 -
575 -
576 -==== 3.7.1.2 COAP Integration Setup ====
577 -
578 -
579 -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" %);
580 -
581 -[[image:image-20240729144058-4.png||height="506" width="1021"]]
582 -
583 -
584 -The next steps is to add the recently created uplink converters;
585 -
586 -[[image:image-20240729150142-5.png||height="507" width="1023"]]
587 -
588 -
589 -==== 3.7.1.3 Add COAP Integration ====
590 -
591 -
592 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
593 -
594 -
595 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
596 -
597 -==== 3.7.2.1 Instruction Description ====
598 -
599 -
600 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
601 -* AT+SERVADDR=COAP Server Address,5683
602 -
603 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
604 -
605 -[[image:image-20240729172305-12.png||height="361" width="624"]]
606 -
607 -Note:The port for the COAP protocol has been fixed to 5683
608 -
609 -
610 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
611 -
612 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
613 -
614 -e.g.
615 -
616 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
617 -
618 -[[image:image-20240729172415-13.png||height="401" width="694"]]
619 -
620 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
621 -
622 -e.g.
623 -
624 -* AT+URL1=11, "i";  
625 -* AT+URL2=11,"/faaaa241f-af4a-b780-4468-c671bb574858"
626 -
627 -[[image:image-20240729172500-14.png||height="403" width="700"]]
628 -
629 -
630 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
631 -
632 -=== 3.8.1 Create device & Get Credentials ===
633 -
634 -
635 635  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.
636 636  
637 637  [[image:image-20230802112413-44.png]]
... ... @@ -680,11 +680,9 @@
680 680  
681 681  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
682 682  
592 +=== 3.7.2 Simulate with MQTT.fx ===
683 683  
684 684  
685 -=== 3.8.2 Simulate with MQTT.fx ===
686 -
687 -
688 688  [[image:image-20230802112413-52.png]]
689 689  
690 690  
... ... @@ -698,7 +698,7 @@
698 698  [[image:image-20230808105329-3.png]]
699 699  
700 700  
701 -=== 3.8.3 tago data ===
608 +=== 3.7.3 tago data ===
702 702  
703 703  
704 704  [[image:image-20230802112413-50.png||height="242" width="1037"]]
... ... @@ -706,7 +706,7 @@
706 706  [[image:image-20230802112413-51.png||height="184" width="696"]]
707 707  
708 708  
709 -== 3.9 TCP Connection ==
616 +== 3.8 TCP Connection ==
710 710  
711 711  
712 712  (% style="color:blue" %)**AT command:**
... ... @@ -727,62 +727,11 @@
727 727  [[image:image-20230807233631-2.png]]
728 728  
729 729  
730 -== 3.10 AWS Connection ==
637 += 4. FAQ =
731 731  
639 +== 4.1 What is the usage of Multi Sampling and One Uplink? ==
732 732  
733 -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]]
734 734  
735 -
736 -= 4. MQTT/UDP/TCP downlink =
737 -
738 -== 4.1 MQTT (via MQTT.fx) ==
739 -
740 -
741 -Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
742 -
743 -**1.** Configure node MQTT connection (via MQTT.fx):
744 -
745 -(% style="color:blue" %)**AT command:**
746 -
747 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)~/~/ hex format or json format
748 -
749 -* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
750 -
751 -* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
752 -
753 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
754 -
755 -* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
756 -
757 -* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 ** (%%) ~/~/ to set MQTT server address and port
758 -
759 -(% 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.**
760 -
761 -[[image:image-20240417180145-2.png||height="434" width="587"]][[image:image-20240417180737-3.png||height="431" width="584"]]
762 -
763 -
764 -**2. **When the node uplink packets, we can observe the data in MQTT.fx.
765 -
766 -[[image:image-20240418144337-1.png||height="709" width="802"]]
767 -
768 -**3. **The downlink command can be successfully sent only when the downlink port is open.
769 -
770 - The downlink port is opened for about 3 seconds after uplink packets are sent.
771 -
772 - 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.
773 -
774 -[[image:image-20240418150435-3.png||height="582" width="659"]]
775 -
776 -[[image:image-20240418150932-4.png||height="492" width="1061"]]
777 -
778 -(% 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.**
779 -
780 -
781 -= 5. FAQ =
782 -
783 -== 5.1 What is the usage of Multi Sampling and One Uplink? ==
784 -
785 -
786 786  The NB series has the feature for Multi Sampling and one uplink. See one of them
787 787  
788 788  [[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]]
... ... @@ -797,7 +797,7 @@
797 797  1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
798 798  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.
799 799  
800 -== 5.2 Why the uplink JSON format is not standard? ==
656 +== 4.2 Why the uplink JSON format is not standard? ==
801 801  
802 802  
803 803  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.
... ... @@ -807,9 +807,9 @@
807 807  [[image:image-20240229233154-1.png]]
808 808  
809 809  
810 -= 6. Trouble Shooting: =
666 += 5. Trouble Shooting: =
811 811  
812 -== 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. ==
813 813  
814 814  
815 815  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.
... ... @@ -836,7 +836,7 @@
836 836  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.
837 837  
838 838  
839 -== 6.2 Issue: "NBIOT did not respond" ==
695 +== 5.2 Issue: "NBIOT did not respond" ==
840 840  
841 841  
842 842  (% class="box errormessage" %)
... ... @@ -864,7 +864,7 @@
864 864  [[image:image-20240208001740-1.png]]
865 865  
866 866  
867 -== 6.3 Issue: "Failed to readI MSI number" ==
723 +== 5.3 Issue: "Failed to readI MSI number" ==
868 868  
869 869  
870 870  (% class="box errormessage" %)
... ... @@ -878,77 +878,9 @@
878 878  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"]].
879 879  
880 880  
881 -== (% 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? ==
882 882  
883 883  
884 884  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.
885 885  
886 886  [[image:image-20240226111928-1.png]]
887 -
888 -
889 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
890 -
891 -(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
892 -=== UDP: ===
893 -
894 -(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
895 -Its downlink command is the same as the AT command, but brackets are required.
896 -Example:
897 -
898 -{AT+TDC=300}
899 -
900 -
901 -(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
902 -=== MQTT: ===
903 -
904 -Json：
905 -
906 -The Json format in MQTT mode needs to be configured with all commands.
907 -If you have configurations that need to be changed, please change them in the template below.
908 -Template:
909 -
910 -{
911 -"AT+SERVADDR":"119.91.62.30,1882",
912 -"AT+CLIENT":"JwcXKjQBNhQ2JykDDAA5Ahs",
913 -"AT+UNAME":"usenamedragino",
914 -"AT+PWD":"passworddragino",
915 -"AT+PUBTOPIC":"123",
916 -"AT+SUBTOPIC":"321",
917 -"AT+TDC":"7200",
918 -"AT+INTMOD":"0",
919 -"AT+APN":"NULL",
920 -"AT+5VT":"0",
921 -"AT+PRO":"3,5",
922 -"AT+TR":"900",
923 -"AT+NOUD":"0",
924 -"AT+CSQTIME":"5",
925 -"AT+DNSTIMER":"0",
926 -"AT+TLSMOD":"0,0",
927 -"AT+MQOS":"0",
928 -"AT+TEMPALARM1":"0",
929 -"AT+TEMPALARM2":"10",
930 -"AT+TEMPALARM3":"0"
931 -}
932 -
933 -Hex：
934 -
935 -MQTT's hex format. Since many commands need to support strings, only a few commands are supported.
936 -
937 -The supported commands are consistent with LoRaWAN's hex commands.
938 -Please refer to the following link to obtain the hex format:
939 -
940 -[[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/]]
941 -
942 -
943 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.6 How to obtain device logs?(%%) ==
944 -
945 -
946 -* **AT Command: AT** **+GETLOG**
947 -
948 -This command can be used to query upstream logs of data packets.
949 -
950 -[[image:image-20240701114700-1.png]]
951 -
952 -
953 -
954 -
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