Changes for page General Manual for -CB , -CS models

Last modified by Mengting Qiu on 2025/03/08 11:35

From version < 129.3 >

edited by Xiaoling
on 2024/09/14 10:54

To version < 136.1 >

edited by Bei Jinggeng
on 2025/01/13 10:38

Change comment: Uploaded new attachment "image-20250113103816-1.png", version {1}

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- image-20250113103816-1.png

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.Xiaoling
++XWiki.Bei

Content

@@ -1,11 +1,12 @@
--
++**Table of Contents:**
++{{toc/}}
--(% class="wikigeneratedid" id="HTableofContents:" %)
--**Table of Contents:**
--{{toc/}}
++
++
++
  = 1. The use of this guideline =
@@ -53,8 +53,12 @@
  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:406px" %)China Mainland, HongKong|(% style="width:351px" %) |(% style="width:120px" %)
  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:406px" %)China Mainland|(% style="width:351px" %) |(% style="width:120px" %)
++(% class="wikigeneratedid" %)
++cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
++
  == 2.2 Speed Up Network Attach time ==
++
  **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**.
  **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.
@@ -61,7 +61,7 @@
  Attache to 1NCE card for Australia use:
--* AT+COPS=1,2,"50501",8
++* AT+COPS=1,2,"50501",8
  * AT+QCFG="band",0,0x8000000,0x8000000,1
  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
@@ -73,7 +73,7 @@
  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/]]**
--=== **1.Configure Frequency Band** ===
++=== **1. Configure Frequency Band** ===
  AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
@@ -143,7 +143,7 @@
  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
--=== **2.Configure search network sequence** ===
++=== **2. Configure search network sequence** ===
  AT+QCFG="nwscanseq",<scanseq>,1
@@ -156,8 +156,9 @@
  AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
--=== **3.Configure Network Category to be Searched for under LTE RAT** ===
++=== **3. Configure Network Category to be Searched for under LTE RAT** ===
++
  AT+QCFG="iotopmode",mode,1
 eMTC
@@ -164,8 +164,9 @@
 NB-IoT
 eMTC and NB-IoT
--=== **4.AT command to set frequency band and network category** ===
++=== **4. AT command to set frequency band and network category** ===
++
  AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f    ~/~/<eMTC_bandval>,<NB-IoT_bandval>
  AT+IOTMOD=0    ~/~/ 0 eMTC  1 NB-IoT   2 eMTC and NB-IoT
@@ -187,6 +187,7 @@
  == 3.1 General UDP Connection ==
++
  The NB-IoT Sensor can send packet to server use UDP protocol.
@@ -231,7 +231,7 @@
  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%)      ~/~/  Set COAP server address and port
--* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%)                            ~/~/  Configure CoAP Message Options
++* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%)                            ~/~/  Configure CoAP Message Options
  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%)    ~/~/  Configure CoAP Message Options
  [[image:image-20240819103212-2.png]]
@@ -305,7 +305,6 @@
  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
--
  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
@@ -345,7 +345,6 @@
  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
--
  ==== 3.3.3.2 Uplink Examples ====
@@ -417,7 +417,6 @@
  * (% 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.
--
  === 3.4.1 For device Already has template ===
  ==== 3.4.1.1 Create Device ====
@@ -577,7 +577,6 @@
  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
--
  == 3.6 ThingsBoard.Cloud (via MQTT) ==
  === 3.6.1 Configure ThingsBoard ===
@@ -665,11 +665,82 @@
  [[image:image-20240820112426-40.png]]
--== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
--=== 3.7.1 Create device & Get Credentials ===
++== 3.7 ThingsBoard.Cloud (via COAP) ==
++=== 3.7.1 Configure ThingsBoard ===
++==== 3.7.1.1 Create Uplink & Downlink Converter ====
++
++
++(% style="color:blue" %)**Uplink Converter**
++
++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.
++
++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.
++
++[[image:https://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-20240729141300-1.png?width=1115&height=552&rev=1.1||alt="image-20240729141300-1.png" height="579" width="1168"]]
++
++
++(% style="color:blue" %)**Downlink Converter**
++
++The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
++
++[[image:https://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-20240729142505-3.png?width=1023&height=507&rev=1.1||alt="image-20240729142505-3.png" height="579" width="1168"]]
++
++
++==== 3.7.1.2 COAP Integration Setup ====
++
++
++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" %);
++
++[[image:https://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-20240729144058-4.png?width=1021&height=506&rev=1.1||alt="image-20240729144058-4.png" height="583" width="1176"]]
++
++
++The next steps is to add the recently created uplink converters;
++
++[[image:https://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-20240729150142-5.png?width=1023&height=507&rev=1.1||alt="image-20240729150142-5.png" height="591" width="1193"]]
++
++
++==== 3.7.1.3 Add COAP Integration ====
++
++[[image:https://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-20240729161543-9.png?width=1009&height=500&rev=1.1||alt="image-20240729161543-9.png" height="590" width="1191"]]
++
++
++=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
++
++==== 3.7.2.1 Instruction Description ====
++
++
++* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
++* AT+SERVADDR=COAP Server Address,5683
++
++Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
++
++[[image:https://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-20240729172305-12.png?width=624&height=361&rev=1.1||alt="image-20240729172305-12.png" height="417" width="721"]]
++
++Note:The port for the COAP protocol has been fixed to 5683
++
++
++* AT+URL1=11,"i"
++* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
++*
++
++-CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
++
++e.g.
++
++* AT+URL1=11, "i"
++* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
++
++[[image:https://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-20240729172500-14.png?width=700&height=403&rev=1.1||alt="image-20240729172500-14.png" height="413" width="718"]]
++
++
++== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
++
++=== 3.8.1 Create device & Get Credentials ===
++
++
  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.
  [[image:image-20240820112516-41.png]]
@@ -716,10 +716,9 @@
  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
++=== 3.8.2 Simulate with MQTT.fx ===
--=== 3.7.2 Simulate with MQTT.fx ===
--
  [[image:image-20240820112552-44.png]]
  [[image:image-20240820112604-45.png]]
@@ -731,7 +731,7 @@
  [[image:image-20240820112626-47.png]]
--=== 3.7.3 tago data ===
++=== 3.8.3 tago data ===
  [[image:image-20240820112637-48.png]]
@@ -739,7 +739,7 @@
  [[image:image-20240820112647-49.png]]
--== 3.8 TCP Connection ==
++== 3.9 TCP Connection ==
  (% style="color:blue" %)**AT command:**
@@ -746,7 +746,7 @@
  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
--* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
++* (% style="color:#037691" %)**AT+PRO=4,5   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 **  (%%) ~/~/ to set TCP server address and port
@@ -759,7 +759,7 @@
  [[image:image-20240820112716-51.png]]
--== 3.9 AWS Connection ==
++== 3.10 AWS Connection ==
  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]]
@@ -881,7 +881,6 @@
 *. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
 *. 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.
--
  == 6.2 Why the uplink JSON format is not standard? ==
@@ -1002,7 +1002,7 @@
  Example:
--[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
++[[image:image-20240827150121-5.png||height="473" width="676"]][[image:image-20240827145055-4.png||height="474" width="665"]]
  == 7.5 GPS debugging ==

image-20250113103816-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Bei

Size

...	...	@@ -1,0 +1,1 @@
	1	+13.6 KB

Content

Changes for page General Manual for -CB , -CS models

Summary

Details

Applications

Navigation