Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Last modified by Mengting Qiu on 2025/07/03 18:55

From 99.2 to 99.3 From 106.1 to 107.1

From version 99.3

edited by Xiaoling
on 2023/08/11 11:48

Change comment: There is no comment for this version

To version 106.1

edited by Saxer Lin
on 2023/11/25 17:22

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -4,6 +4,10 @@
  {{toc/}}
++
++
++
++
  = 1. The use of this guideline =
@@ -12,7 +12,9 @@
  = 2. Attach Network =
++== 2.1 General Configure to attach network ==
++
  To attache NB-IoT sensors to NB-IoT Network, You need to:
 . Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
@@ -36,7 +36,21 @@
  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
++== 2.2 Speed Up Network Attach time ==
++
++BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail. User can lock the band to specify band for its operator to make this faster.
++
++(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
++
++(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
++
++(% style="color:#037691" %)**AT+QBAND=2,8,20**  (%%)  ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
++
++
++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/]]**
++
++
  = 3. Configure to connect to different servers =
  == 3.1 General UDP Connection ==
@@ -50,7 +50,7 @@
  We can use PC tool to simulate UDP connection to make sure server works ok.
--[[image:image-20230802112413-1.png]]
++[[image:image-20230802112413-1.png||height="468" width="1024"]]
  === 3.1.2 Configure NB-IoT Sensor ===
@@ -100,7 +100,7 @@
  [[image:image-20230802112413-4.png]]
--[[image:image-20230802112413-5.png]]
++[[image:image-20230802112413-5.png||height="530" width="987"]]
  (% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink  period to a suitable interval.**
@@ -112,7 +112,7 @@
  [[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.
--[[image:image-20230802112413-6.png]]
++[[image:image-20230802112413-6.png||height="336" width="925"]]
  [[image:image-20230802112413-7.png]]
@@ -137,7 +137,6 @@
  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
--
  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
@@ -157,7 +157,7 @@
  (% style="color:blue" %)**Result: **
--[[image:image-20230802112413-11.png]]
++[[image:image-20230802112413-11.png||height="539" width="901"]]
  === 3.3.3 Configure NB-IoT Sensor for connection ===
@@ -180,11 +180,10 @@
  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
--
  ==== 3.3.3.2 Uplink Examples ====
--For S31-NB
++[[image:image-20230816201942-1.png]]
  For SE01-NB
@@ -215,9 +215,9 @@
  When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
--[[image:image-20230802112413-12.png]]
++[[image:image-20230802112413-12.png||height="504" width="1011"]]
--[[image:image-20230802112413-13.png]]
++[[image:image-20230802112413-13.png||height="331" width="978"]]
  Below is the NB-IoT Product Table show the mapping.
@@ -243,28 +243,44 @@
  |(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
++== 3.4 [[Datacake>>https://datacake.co/]] ==
--== 3.4 Datacake ==
++(% class="wikigeneratedid" %)
++Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
++
++
++(% class="wikigeneratedid" %)
++As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
++
++* (% style="color:blue" %)**S31B-NB-1D**(%%): This version have pre-configure DataCake connection. User just need to Power on this device, it will auto connect send data to DataCake Server.
++
++* (% style="color:blue" %)**S31B-NB-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 Create device ===
--[[image:image-20230808162301-1.png]]
++(% style="color:blue" %)**Add Device**(%%) in DataCake.
++[[image:image-20230808162301-1.png||height="453" width="952"]]
--[[image:image-20230808162342-2.png]]
++[[image:image-20230808162342-2.png||height="541" width="952"]]
++
++(% style="color:blue" %)**Choose the correct model**(%%) from template.
++
  [[image:image-20230808162421-3.png]]
--The device ID needs to be filled in with IMEI, and a prefix of** 'f' **needs to be added.
++(% style="color:blue" %)**Fill Device ID**(%%). The device ID needs to be filled in with IMEI, and a prefix of(% style="color:blue" %)** 'f' **(%%)needs to be added.
--[[image:image-20230808163612-7.png]]
++[[image:image-20230808163612-7.png||height="549" width="952"]]
  [[image:image-20230808163035-5.png]]
--[[image:image-20230808163049-6.png]]
++[[image:image-20230808163049-6.png||height="544" width="926"]]
  === 3.4.2 Scan QR code to obtain data ===
@@ -272,7 +272,7 @@
  Users can use their phones or computers to scan QR codes to obtain device data information.
--[[image:image-20230808170051-8.png]]
++[[image:image-20230808170051-8.png||height="255" width="259"]]
  [[image:image-20230808170548-9.png]]
@@ -308,7 +308,7 @@
  Please select the NB95S31B template.
--[[image:image-20230809173310-5.png]]
++[[image:image-20230809173310-5.png||height="558" width="926"]]
  [[image:image-20230809173438-6.png]]
@@ -317,7 +317,7 @@
  Successfully imported template.
--[[image:image-20230809173835-8.png]]
++[[image:image-20230809173835-8.png||height="515" width="860"]]
  Users can set UDP port.
@@ -332,17 +332,20 @@
  [[image:image-20230810083934-1.png]]
--[[image:image-20230810084048-2.png]]
++[[image:image-20230810084048-2.png||height="535" width="1052"]]
++
  === 3.5.3 Configure NB-IoT Sensors ===
--* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)**    **~/~/  Set to UDP Server and  Payload
++* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)   **~/~/ hex format or json format**
++* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
++* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
++* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
++* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
++* (% style="color:#037691" %)**AT+PWD=“Your device token”**
--* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)**                        **~/~/  Set Server IP and  port
--
--
  == 3.6 ThingsBoard.Cloud (via MQTT) ==
  === 3.6.1 Configure ThingsBoard ===
@@ -352,7 +352,7 @@
  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
--[[image:image-20230802112413-32.png]]
++[[image:image-20230802112413-32.png||height="583" width="1066"]]
  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
@@ -364,7 +364,7 @@
  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" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
--[[image:image-20230802112413-33.png||height="732" width="1302"]]
++[[image:image-20230802112413-33.png||height="597" width="1061"]]
  (% style="color:blue" %)**Downlink Converter**
@@ -371,7 +371,7 @@
  The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
--[[image:image-20230802112413-34.png||height="734" width="1305"]]
++[[image:image-20230802112413-34.png||height="598" width="1063"]]
  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
@@ -381,14 +381,14 @@
  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" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
--[[image:image-20230802112413-35.png||height="738" width="1312"]]
++[[image:image-20230802112413-35.png||height="597" width="1062"]]
  * The next steps is to add the recently created uplink and downlink converters;
--[[image:image-20230802112413-36.png||height="736" width="1308"]]
++[[image:image-20230802112413-36.png||height="598" width="1062"]]
--[[image:image-20230802112413-37.png||height="735" width="1307"]]
++[[image:image-20230802112413-37.png||height="598" width="1064"]]
  (% style="color:blue" %)**Add a topic filter:**
@@ -397,7 +397,7 @@
  You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
--[[image:image-20230802112413-38.png||height="731" width="1300"]]
++[[image:image-20230802112413-38.png||height="598" width="1064"]]
  === 3.6.2 Simulate with MQTT.fx ===
@@ -405,7 +405,7 @@
  [[image:image-20230802112413-39.png]]
--[[image:image-20230802112413-40.png]]
++[[image:image-20230802112413-40.png||height="525" width="980"]]
  === 3.6.3 Configure NB-IoT Sensor ===
@@ -427,11 +427,11 @@
  Test Uplink by click the button for 1 second
--[[image:image-20230802112413-41.png]]
++[[image:image-20230802112413-41.png||height="496" width="828"]]
  [[image:image-20230802112413-42.png]]
--[[image:image-20230802112413-43.png]]
++[[image:image-20230802112413-43.png||height="407" width="825"]]
  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
@@ -488,7 +488,6 @@
  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
--
  === 3.7.2 Simulate with MQTT.fx ===
@@ -495,12 +495,12 @@
  [[image:image-20230802112413-52.png]]
--[[image:image-20230808105300-2.png]]
++[[image:image-20230808105300-2.png||height="553" width="1026"]]
  Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
--[[image:image-20230808105217-1.png]]
++[[image:image-20230808105217-1.png||height="556" width="1031"]]
  [[image:image-20230808105329-3.png]]
@@ -508,7 +508,7 @@
  === 3.7.3 tago data ===
--[[image:image-20230802112413-50.png]]
++[[image:image-20230802112413-50.png||height="242" width="1037"]]
  [[image:image-20230802112413-51.png||height="184" width="696"]]
@@ -524,6 +524,7 @@
  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 **  (%%) ~/~/ to set TCP server address and port
++
  (% style="color:blue" %)**Sensor Console Output when Uplink:**
  [[image:image-20230807233631-1.png]]

image-20230816201942-1.png

Author

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

Size

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

Content

Changes for page General Configure/Commands to Connect to IoT server for -NB & -NS NB-IoT models

Summary

Details

Applications

Navigation