Changes for page General Manual for -CB , -CS models
Last modified by Mengting Qiu on 2025/03/08 11:35
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.kai - Content
-
... ... @@ -8,6 +8,7 @@ 8 8 9 9 = 1. The use of this guideline = 10 10 11 + 11 11 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. 12 12 13 13 ... ... @@ -15,6 +15,7 @@ 15 15 16 16 == 2.1 General Configure to attach network == 17 17 19 + 18 18 To attache end nodes to NB-IoT or LTE-M Network, You need to: 19 19 20 20 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) ... ... @@ -26,7 +26,7 @@ 26 26 [[image:image-20240602220856-1.png]] 27 27 28 28 29 - 放一张如何插卡图片。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"]] 30 30 31 31 32 32 After doing above, the end nodes should be able to attach to NB-IoT network . ... ... @@ -53,6 +53,7 @@ 53 53 54 54 == 2.2 Speed Up Network Attach time == 55 55 58 + 56 56 **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**. 57 57 58 58 **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. ... ... @@ -71,7 +71,7 @@ 71 71 72 72 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/]]** 73 73 74 -=== **1.Configure Frequency Band** === 77 +=== **1. Configure Frequency Band** === 75 75 76 76 AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]] 77 77 ... ... @@ -141,7 +141,7 @@ 141 141 AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1 142 142 143 143 144 -=== **2.Configure search network sequence** === 147 +=== **2. Configure search network sequence** === 145 145 146 146 AT+QCFG="nwscanseq",<scanseq>,1 147 147 ... ... @@ -154,8 +154,9 @@ 154 154 155 155 AT+QCFG="nwscanseq",02,1 ~/~/Priority search for eMTC 156 156 157 -=== **3.Configure Network Category to be Searched for under LTE RAT** === 158 158 161 +=== **3. Configure Network Category to be Searched for under LTE RAT** === 162 + 159 159 AT+QCFG="iotopmode",mode,1 160 160 161 161 0 eMTC ... ... @@ -162,8 +162,9 @@ 162 162 1 NB-IoT 163 163 2 eMTC and NB-IoT 164 164 165 -=== **4.AT command to set frequency band and network category** === 166 166 170 +=== **4. AT command to set frequency band and network category** === 171 + 167 167 AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f ~/~/<eMTC_bandval>,<NB-IoT_bandval> 168 168 169 169 AT+IOTMOD=0 ~/~/ 0 eMTC 1 NB-IoT 2 eMTC and NB-IoT ... ... @@ -185,6 +185,7 @@ 185 185 186 186 == 3.1 General UDP Connection == 187 187 193 + 188 188 The NB-IoT Sensor can send packet to server use UDP protocol. 189 189 190 190 ... ... @@ -229,7 +229,7 @@ 229 229 230 230 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port 231 231 232 -* (% style="color:#037691" %)**AT+URI1=11," I"** (%%) ~/~/ Configure CoAP Message Options238 +* (% style="color:#037691" %)**AT+URI1=11,"i"** (%%) ~/~/ Configure CoAP Message Options 233 233 * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"** (%%) ~/~/ Configure CoAP Message Options 234 234 235 235 [[image:image-20240819103212-2.png]] ... ... @@ -303,7 +303,6 @@ 303 303 304 304 * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password> 305 305 306 - 307 307 ==== 3.3.2.2 Publish Data to ThingSpeak Channel ==== 308 308 309 309 ... ... @@ -343,7 +343,6 @@ 343 343 344 344 * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>** 345 345 346 - 347 347 ==== 3.3.3.2 Uplink Examples ==== 348 348 349 349 ... ... @@ -415,7 +415,6 @@ 415 415 416 416 * (% 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. 417 417 418 - 419 419 === 3.4.1 For device Already has template === 420 420 421 421 ==== 3.4.1.1 Create Device ==== ... ... @@ -575,7 +575,6 @@ 575 575 * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined** 576 576 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 577 577 578 - 579 579 == 3.6 ThingsBoard.Cloud (via MQTT) == 580 580 581 581 === 3.6.1 Configure ThingsBoard === ... ... @@ -714,7 +714,6 @@ 714 714 715 715 * (% style="color:#037691" %)**AT+PWD=“Your device token”** 716 716 717 - 718 718 === 3.7.2 Simulate with MQTT.fx === 719 719 720 720 ... ... @@ -879,7 +879,6 @@ 879 879 1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours. 880 880 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. 881 881 882 - 883 883 == 6.2 Why the uplink JSON format is not standard? == 884 884 885 885