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

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

From version < 132.1 >

edited by Mengting Qiu
on 2024/10/18 15:33

To version < 129.1 >

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

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

Content

@@ -8,7 +8,6 @@
  = 1. The use of this guideline =
--
  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.
@@ -16,7 +16,6 @@
  == 2.1 General Configure to attach network ==
--
  To attache end nodes to NB-IoT or LTE-M Network, You need to:
 . 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 @@
  [[image:image-20240602220856-1.png]]
--[[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"]]
++放一张如何插卡图片。
  After doing above, the end nodes should be able to attach to NB-IoT network .
@@ -55,7 +55,6 @@
  == 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.
@@ -74,7 +74,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>]]
@@ -144,7 +144,7 @@
  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
--=== **2. Configure search network sequence** ===
++=== **2.Configure search network sequence** ===
  AT+QCFG="nwscanseq",<scanseq>,1
@@ -157,9 +157,8 @@
  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
@@ -166,9 +166,8 @@
 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
@@ -190,7 +190,6 @@
  == 3.1 General UDP Connection ==
--
  The NB-IoT Sensor can send packet to server use UDP protocol.
@@ -235,7 +235,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]]
@@ -309,6 +309,8 @@
  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
++
++
  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
@@ -348,6 +348,8 @@
  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
++
++
  ==== 3.3.3.2 Uplink Examples ====
@@ -419,6 +419,8 @@
  * (% 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 ====
@@ -578,6 +578,8 @@
  * (% 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,90 +665,11 @@
  [[image:image-20240820112426-40.png]]
++== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
--== 3.7 ThingsBoard.Cloud (via COAP) ==
++=== 3.7.1 Create device & Get Credentials ===
--=== 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:image-20240729141300-1.png||height="552" width="1115"]]
--
--
--(% style="color:blue" %)**Downlink Converter**
--
--The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
--
--[[image:image-20240729142505-3.png||height="507" width="1023"]]
--
--
--==== 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:image-20240729144058-4.png||height="506" width="1021"]]
--
--
--The next steps is to add the recently created uplink converters;
--
--[[image:image-20240729150142-5.png||height="507" width="1023"]]
--
--
--==== 3.7.1.3 Add COAP Integration ====
--
--
--==== [[image:image-20240729161543-9.png||height="500" width="1009"]] ====
--
--
--=== 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:image-20240729172305-12.png||height="361" width="624"]]
--
--Note:The port for the COAP protocol has been fixed to 5683
--
--
--* AT+URL1=11,(% style="color:red" %)**character length**(%%),"Needs to be consistent with the CoAP endpoint URL in the platform"
--
--If the module used is (% style="color:red" %)**BC660K, only one **(%%)URL directive needs to be configured,
--
--e.g.
--
--* AT+URL1=11,38, "i/faaaa241f-af4a-b780-4468-c671bb574858"
--
--[[image:image-20240729172415-13.png||height="401" width="694"]]
--
--If you are 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:image-20240729172500-14.png||height="403" width="700"]]
--
--
--
--== 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]]
@@ -795,9 +795,11 @@
  * (% 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]]
@@ -809,7 +809,7 @@
  [[image:image-20240820112626-47.png]]
--=== 3.8.3 tago data ===
++=== 3.7.3 tago data ===
  [[image:image-20240820112637-48.png]]
@@ -817,7 +817,7 @@
  [[image:image-20240820112647-49.png]]
--== 3.9 TCP Connection ==
++== 3.8 TCP Connection ==
  (% style="color:blue" %)**AT command:**
@@ -837,7 +837,7 @@
  [[image:image-20240820112716-51.png]]
--== 3.10 AWS Connection ==
++== 3.9 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]]
@@ -921,30 +921,27 @@
  = 5. GPS positioning function =
--== 1. Turn on GPS function ==
++=== 1. Turn on GPS function ===
--
  (% class="wikigeneratedid" %)
--AT+GPS=1 or 0  ~/~/ GPS function on or off
++AT+GPS=1 or 0  ~/~/GPS function on or off
--== 2. Extend the time to turn on GNSS ==
++=== 2.Extend the time to turn on GNSS ===
++AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
--AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
++=== 3.Get or set GPS positioning interval in units of hour ===
--== 3. Get or set GPS positioning interval in units of hour ==
++AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
--AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
++= 5. FAQ =
++== 5.1 What is the usage of Multi Sampling and One Uplink? ==
--= 6. FAQ =
--== 6.1 What is the usage of Multi Sampling and One Uplink? ==
--
--
  The NB series has the feature for Multi Sampling and one uplink. See one of them
  [[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 @@
 *. **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? ==
++== 5.2 Why the uplink JSON format is not standard? ==
++
++
  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.
  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
@@ -969,9 +969,9 @@
  [[image:image-20240820112848-57.png]]
--= 7. Trouble Shooting: =
++= 6. Trouble Shooting: =
--== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
++== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
  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 @@
  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.
--== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
++== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.2 Why sometime the AT Command is slow in reponse?(%%) ==
  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 @@
  [[image:image-20240820113015-60.png]]
--== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
++== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
  === UDP: ===
@@ -1058,7 +1058,7 @@
  [[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/]]
--== 7.4 What if the signal is good but the domain name resolution fails? ==
++== 6.4 What if the signal is good but the domain name resolution fails? ==
  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 @@
  [[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
--== 7.5 GPS debugging ==
++== 6.5 GPS debugging ==
  Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
@@ -1093,7 +1093,7 @@
  [[image:image-20240903104431-10.png||height="291" width="621"]]
--=== 7.5.1 GPS commands ===
++=== 6.5.1 GPS commands ===
  The following are three related AT commands that introduce GPS functions.
@@ -1145,7 +1145,7 @@
  Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
--=== 7.5.2 GPS workflow ===
++=== 6.5.2 GPS workflow ===
  The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
@@ -1163,7 +1163,7 @@
     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.
--=== 7.5.3 GPS debugging methods ===
++=== 6.5.3 GPS debugging methods ===
  In summary, we can deduce the methods of debugging GPS:

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

Summary

Details

Applications

Navigation