Changes for page General Manual for -CB , -CS models
Last modified by Mengting Qiu on 2025/03/08 11:35
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Xiaoling - Content
-
... ... @@ -8,7 +8,6 @@ 8 8 9 9 = 1. The use of this guideline = 10 10 11 - 12 12 This configure instruction is for Dragino NB-IoT models with -CB or -CS suffix, for example DDS75-CB. These models use the same NB-IoT Module **[[BG95-M2>>https://www.dropbox.com/sh/3ilyaswz4odgaru/AADR86cAgL9UGlmLuEH-UZgla?st=x1ry6v5j&dl=0]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers. 13 13 14 14 ... ... @@ -16,7 +16,6 @@ 16 16 17 17 == 2.1 General Configure to attach network == 18 18 19 - 20 20 To attache end nodes to NB-IoT or LTE-M Network, You need to: 21 21 22 22 1. Get a NB-IoT or LTE-M SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone) ... ... @@ -28,7 +28,7 @@ 28 28 [[image:image-20240602220856-1.png]] 29 29 30 30 31 - [[image:http://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20230808205045-1.png?width=438&height=293&rev=1.1||alt="image-20230808205045-1.png"]]29 +放一张如何插卡图片。 32 32 33 33 34 34 After doing above, the end nodes should be able to attach to NB-IoT network . ... ... @@ -55,7 +55,6 @@ 55 55 56 56 == 2.2 Speed Up Network Attach time == 57 57 58 - 59 59 **BG95-M2** supports multi bands (% style="color:blue" %)**in NB-IoT and LTE-M. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**. 60 60 61 61 **Note:**Before using the NB module command, users need to power on the NB module. Run the AT+QSW command to turn on and off the NB module.Remember to shut down after using the NB module command, otherwise it will consume power. ... ... @@ -74,7 +74,7 @@ 74 74 75 75 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/]]** 76 76 77 -=== **1. 74 +=== **1.Configure Frequency Band** === 78 78 79 79 AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]] 80 80 ... ... @@ -144,7 +144,7 @@ 144 144 AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1 145 145 146 146 147 -=== **2. 144 +=== **2.Configure search network sequence** === 148 148 149 149 AT+QCFG="nwscanseq",<scanseq>,1 150 150 ... ... @@ -157,9 +157,8 @@ 157 157 158 158 AT+QCFG="nwscanseq",02,1 ~/~/Priority search for eMTC 159 159 157 +=== **3.Configure Network Category to be Searched for under LTE RAT** === 160 160 161 -=== **3. Configure Network Category to be Searched for under LTE RAT** === 162 - 163 163 AT+QCFG="iotopmode",mode,1 164 164 165 165 0 eMTC ... ... @@ -166,9 +166,8 @@ 166 166 1 NB-IoT 167 167 2 eMTC and NB-IoT 168 168 165 +=== **4.AT command to set frequency band and network category** === 169 169 170 -=== **4. AT command to set frequency band and network category** === 171 - 172 172 AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f ~/~/<eMTC_bandval>,<NB-IoT_bandval> 173 173 174 174 AT+IOTMOD=0 ~/~/ 0 eMTC 1 NB-IoT 2 eMTC and NB-IoT ... ... @@ -190,7 +190,6 @@ 190 190 191 191 == 3.1 General UDP Connection == 192 192 193 - 194 194 The NB-IoT Sensor can send packet to server use UDP protocol. 195 195 196 196 ... ... @@ -235,7 +235,7 @@ 235 235 236 236 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port 237 237 238 -* (% style="color:#037691" %)**AT+URI1=11," i"** (%%) ~/~/ Configure CoAP Message Options232 +* (% style="color:#037691" %)**AT+URI1=11,"I"** (%%) ~/~/ Configure CoAP Message Options 239 239 * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"** (%%) ~/~/ Configure CoAP Message Options 240 240 241 241 [[image:image-20240819103212-2.png]] ... ... @@ -309,6 +309,8 @@ 309 309 310 310 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 311 311 306 + 307 + 312 312 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 313 313 314 314 ... ... @@ -348,6 +348,8 @@ 348 348 349 349 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 350 350 347 + 348 + 351 351 ==== 3.3.3.2 Uplink Examples ==== 352 352 353 353 ... ... @@ -419,6 +419,8 @@ 419 419 420 420 * (% style="color:blue" %)**S31B-CB-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. 421 421 420 + 421 + 422 422 === 3.4.1 For device Already has template === 423 423 424 424 ==== 3.4.1.1 Create Device ==== ... ... @@ -578,6 +578,8 @@ 578 578 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 579 579 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 580 580 581 + 582 + 581 581 == 3.6 ThingsBoard.Cloud (via MQTT) == 582 582 583 583 === 3.6.1 Configure ThingsBoard === ... ... @@ -665,90 +665,11 @@ 665 665 [[image:image-20240820112426-40.png]] 666 666 667 667 670 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == 668 668 669 -== 3.7 ThingsBoard.Cloud(viaCOAP)==672 +=== 3.7.1 Create device & Get Credentials === 670 670 671 -=== 3.7.1 Configure ThingsBoard === 672 672 673 -==== 3.7.1.1 Create Uplink & Downlink Converter ==== 674 - 675 - 676 -(% style="color:blue" %)**Uplink Converter** 677 - 678 -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. 679 - 680 -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. 681 - 682 -[[image:image-20240729141300-1.png||height="552" width="1115"]] 683 - 684 - 685 -(% style="color:blue" %)**Downlink Converter** 686 - 687 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker. 688 - 689 -[[image:image-20240729142505-3.png||height="507" width="1023"]] 690 - 691 - 692 -==== 3.7.1.2 COAP Integration Setup ==== 693 - 694 - 695 -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" %); 696 - 697 -[[image:image-20240729144058-4.png||height="506" width="1021"]] 698 - 699 - 700 -The next steps is to add the recently created uplink converters; 701 - 702 -[[image:image-20240729150142-5.png||height="507" width="1023"]] 703 - 704 - 705 -==== 3.7.1.3 Add COAP Integration ==== 706 - 707 - 708 -==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ==== 709 - 710 - 711 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) === 712 - 713 -==== 3.7.2.1 Instruction Description ==== 714 - 715 - 716 -* AT+PRO=1,0(HEX format uplink) &AT+PRO=1,5(JSON format uplink) 717 -* AT+SERVADDR=COAP Server Address,5683 718 - 719 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created) 720 - 721 -[[image:image-20240729172305-12.png||height="361" width="624"]] 722 - 723 -Note:The port for the COAP protocol has been fixed to 5683 724 - 725 - 726 -* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform" 727 - 728 -If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured, 729 - 730 -e.g. 731 - 732 -* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858" 733 - 734 -[[image:image-20240729172415-13.png||height="401" width="694"]] 735 - 736 -If you are using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands, 737 - 738 -e.g. 739 - 740 -* AT+URL1=11, "i" 741 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858" 742 - 743 -[[image:image-20240729172500-14.png||height="403" width="700"]] 744 - 745 - 746 - 747 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) == 748 - 749 -=== 3.8.1 Create device & Get Credentials === 750 - 751 - 752 752 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. 753 753 754 754 [[image:image-20240820112516-41.png]] ... ... @@ -795,9 +795,11 @@ 795 795 796 796 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 797 797 798 -=== 3.8.2 Simulate with MQTT.fx === 799 799 800 800 723 +=== 3.7.2 Simulate with MQTT.fx === 724 + 725 + 801 801 [[image:image-20240820112552-44.png]] 802 802 803 803 [[image:image-20240820112604-45.png]] ... ... @@ -809,7 +809,7 @@ 809 809 [[image:image-20240820112626-47.png]] 810 810 811 811 812 -=== 3. 8.3 tago data ===737 +=== 3.7.3 tago data === 813 813 814 814 815 815 [[image:image-20240820112637-48.png]] ... ... @@ -817,7 +817,7 @@ 817 817 [[image:image-20240820112647-49.png]] 818 818 819 819 820 -== 3. 9TCP Connection ==745 +== 3.8 TCP Connection == 821 821 822 822 823 823 (% style="color:blue" %)**AT command:** ... ... @@ -837,7 +837,7 @@ 837 837 [[image:image-20240820112716-51.png]] 838 838 839 839 840 -== 3. 10AWS Connection ==765 +== 3.9 AWS Connection == 841 841 842 842 843 843 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]] ... ... @@ -921,30 +921,27 @@ 921 921 922 922 = 5. GPS positioning function = 923 923 924 -== 1. Turn on GPS function == 849 +=== 1. Turn on GPS function === 925 925 926 - 927 927 (% class="wikigeneratedid" %) 928 -AT+GPS=1 or 0 ~/~/ 852 +AT+GPS=1 or 0 ~/~/GPS function on or off 929 929 930 930 931 -== 2. 855 +=== 2.Extend the time to turn on GNSS === 932 932 857 +AT+GNSST=30 ~/~/GPS search for positioning information for 30 seconds 933 933 934 -AT+GNSST=30 ~/~/ GPS search for positioning information for 30 seconds 935 935 860 +=== 3.Get or set GPS positioning interval in units of hour === 936 936 937 -= =3.Getorset GPS positioningintervalinunits ofhour==862 +AT+GTDC=24 ~/~/The device will activate GPS positioning every 24 hours 938 938 939 939 940 - AT+GTDC=24~/~/Thedevice will activate GPS positioning every 24 hours865 += 5. FAQ = 941 941 867 +== 5.1 What is the usage of Multi Sampling and One Uplink? == 942 942 943 -= 6. FAQ = 944 944 945 -== 6.1 What is the usage of Multi Sampling and One Uplink? == 946 - 947 - 948 948 The NB series has the feature for Multi Sampling and one uplink. See one of them 949 949 950 950 [[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]] ... ... @@ -959,9 +959,11 @@ 959 959 1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 960 960 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. 961 961 962 -== 6.2 Why the uplink JSON format is not standard? == 963 963 964 964 886 +== 5.2 Why the uplink JSON format is not standard? == 887 + 888 + 965 965 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. 966 966 967 967 The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog. ... ... @@ -969,9 +969,9 @@ 969 969 [[image:image-20240820112848-57.png]] 970 970 971 971 972 -= 7. Trouble Shooting: =896 += 6. Trouble Shooting: = 973 973 974 -== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==898 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. == 975 975 976 976 977 977 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. ... ... @@ -996,7 +996,7 @@ 996 996 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. 997 997 998 998 999 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %) 7.2 Why sometime the AT Command is slow in reponse?(%%) ==923 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.2 Why sometime the AT Command is slow in reponse?(%%) == 1000 1000 1001 1001 1002 1002 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. ... ... @@ -1004,7 +1004,7 @@ 1004 1004 [[image:image-20240820113015-60.png]] 1005 1005 1006 1006 1007 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %) 7.3 What is the Downlink Command by the -CB device?(%%) ==931 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) == 1008 1008 1009 1009 (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %) 1010 1010 === UDP: === ... ... @@ -1058,7 +1058,7 @@ 1058 1058 [[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/]] 1059 1059 1060 1060 1061 -== 7.4 What if the signal is good but the domain name resolution fails? ==985 +== 6.4 What if the signal is good but the domain name resolution fails? == 1062 1062 1063 1063 1064 1064 If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name. ... ... @@ -1082,7 +1082,7 @@ 1082 1082 [[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]] 1083 1083 1084 1084 1085 -== 7.5 GPS debugging ==1009 +== 6.5 GPS debugging == 1086 1086 1087 1087 1088 1088 Indoor GPS signal is very weak, **outdoor** positioning is generally recommended. ... ... @@ -1093,7 +1093,7 @@ 1093 1093 [[image:image-20240903104431-10.png||height="291" width="621"]] 1094 1094 1095 1095 1096 -=== 7.5.1 GPS commands ===1020 +=== 6.5.1 GPS commands === 1097 1097 1098 1098 1099 1099 The following are three related AT commands that introduce GPS functions. ... ... @@ -1145,7 +1145,7 @@ 1145 1145 Downlink Payload: **12 00 00 18 **~/~/ AT+GTDC=24 1146 1146 1147 1147 1148 -=== 7.5.2 GPS workflow ===1072 +=== 6.5.2 GPS workflow === 1149 1149 1150 1150 1151 1151 The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows: ... ... @@ -1163,7 +1163,7 @@ 1163 1163 Only when the node is activated or every (% style="color:#037691" %)**GTDC**(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool. 1164 1164 1165 1165 1166 -=== 7.5.3 GPS debugging methods ===1090 +=== 6.5.3 GPS debugging methods === 1167 1167 1168 1168 1169 1169 In summary, we can deduce the methods of debugging GPS: