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 < 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 (1 modified, 0 added, 0 removed)

Details

Page properties

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 .
@@ -306,6 +306,7 @@
  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
++
  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
@@ -346,6 +346,7 @@
  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
++
  ==== 3.3.3.2 Uplink Examples ====
@@ -418,6 +418,7 @@
  * (% 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,7 @@
  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
++
  == 3.6 ThingsBoard.Cloud (via MQTT) ==
  === 3.6.1 Configure ThingsBoard ===
@@ -717,6 +717,7 @@
  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
++
  === 3.7.2 Simulate with MQTT.fx ===
@@ -843,30 +843,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]]
@@ -882,9 +882,10 @@
 *. 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.
@@ -892,9 +892,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.
@@ -919,7 +919,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.
@@ -927,7 +927,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: ===
@@ -981,7 +981,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.
@@ -1005,7 +1005,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.
@@ -1016,7 +1016,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.
@@ -1068,7 +1068,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:
@@ -1086,7 +1086,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