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

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

From version < 10.1 >

edited by David Huang
on 2024/06/07 16:21

To version 1.1 >

edited by Edwin Chen
on 2024/06/02 21:46

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -1,466 +1,393 @@
--
++~(% class="wikigeneratedid" id="HTableofContents:" %)
++~*~*Table of Contents:~*~*
++~{~{toc/}}
--(% class="wikigeneratedid" id="HTableofContents:" %)
--**Table of Contents:**
--{{toc/}}
--= 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.
++~= 1. The use of this guideline =
--= 2. Attach Network =
++This configure instruction is for Dragino NB-IoT models with -NB or -NS suffix, for example DDS75-NB. These models use the same NB-IoT Module ~*~*~[~[BC660K-GL>>https:~/~/www.quectel.com/product/lpwa-bc660k-gl-nb2]]~*~* 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.
--== 2.1 General Configure to attach network ==
--To attache end nodes to NB-IoT or LTE-M Network, You need to:
++~= 2. Attach Network =
--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)
--1. Power Off End Node ( See below for the power off/on position)
--1. Insert the SIM card to Sensor. ( See below for direction)
--1. Power On End Node
--1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net
++~== 2.1 General Configure to attach network ==
--[[image:image-20240602220856-1.png]]
++To attache NB-IoT sensors to NB-IoT Network, You need to:
--放一张如何插卡图片。
++~1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
++~1. Power Off End Node ( See below for the power off/on position)
++~1. Insert the SIM card to Sensor. ( See below for direction)
++~1. Power On End Node
++~1. ~[~[Configure APN>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>), example AT+APN=iot.1nce.net
++~[~[image~:image-20240208102804-1.png||height="286" width="696"]]
--After doing above, the end nodes should be able to attach to NB-IoT network .
++~[~[image~:image-20230808205045-1.png||height="293" width="438"]]
--The -CB and -CS models support (% style="color:blue" %)**LTE Cat NB2 and LTE-M (CAT-M1)**(%%), with below frequency band: multiple frequency bands of
++After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
--~-~-(% style="color:blue" %)** CAT-NB2:  B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/B85 **(%%).
++The -NB and -NS models support ~(% style="color:blue" %)~*~*LTE Cat NB2~*~*~(%%), with below frequency band: multiple frequency bands of ~(% style="color:blue" %)~*~*B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85~*~*~(%%) . Make sure you use a the NB-IoT SIM card.
--~-~-(% style="color:blue" %)** CAT-M1:  B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).
++~(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:117px" %)~*~*SIM Provider~*~*|~(% style="background-color:#4f81bd; color:white; width:151px" %)~*~*AT+APN=~*~*|~(% style="background-color:#4f81bd; color:white; width:474px" %)~*~*NB-IoT Coverage~*~*|~(% style="background-color:#4f81bd; color:white; width:135px" %)~*~*Comments~*~*
++~|~(% style="width:117px" %)~*~*~[~[1NCE>>https:~/~/1nce.com]]~*~*|~(% style="width:151px" %)iot.1nce.net|~(% style="width:474px" %)~(~(~(
++~*~*~[~[Coverage Reference Link>>https:~/~/1nce.com/en-ap/1nce-connect]]~*~*
--Make sure you use a the NB-IoT or LTE-M SIM card.
++Austria, Belgium, Bulgaria, Croatia, Czech Republic, Denmark, Finland, Germany, Great Britain, Greece, Hungary, Ireland, Italy, Latvia, Malta, Netherlands, Norway, Puerto Rico, Russia, Slovak , Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, UK, US Virgin Islands
++~)~)~)|~(% style="width:135px" %)UK: Band20
++~|~(% style="width:117px" %)China Mobile|~(% style="width:151px" %)No need configure|~(% style="width:474px" %)China Mainland, HongKong|~(% style="width:135px" %)
++~|~(% style="width:117px" %)China Telecom|~(% style="width:151px" %)ctnb|~(% style="width:474px" %)China Mainland|~(% style="width:135px" %)
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1134px" %)
--|(% style="background-color:#4f81bd; color:white; width:117px" %)**SIM Provider**|(% style="background-color:#4f81bd; color:white; width:151px" %)**AT+APN=**|(% style="background-color:#4f81bd; color:white; width:406px" %)**NB-IoT Coverage**|(% style="background-color:#4f81bd; color:white; width:351px" %)**LTE-M Coverage**|(% style="background-color:#4f81bd; color:white; width:120px" %)**Comments**
--|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:406px" %)(((
--**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
++~== 2.2 Speed Up Network Attach time ==
--Austria, Belgium, Bulgaria, China, Croatia, Czech Republic, Denmark, Estonia, Finland, Germany, Great Britain, Greece, Hungary, Ireland,Italy, Latvia, Malta, Netherlands, Norway, Portugal, Puerto Rico, Russia, Slovak,Republic, Slovenia, Spain, Sweden, Switzerland, Taiwan, USA, US Virgin Islands
--)))|(% style="width:351px" %)(((
--Argentina, Austria, Australia, Belgium, Canada, Denmark,Estonia, Finland, France, Germany, Great Britain, Hungary, Ireland, Japan,Jersey, Korea, Repiblic of, Latvia, Luxembourg, Mexico, Netherlands, New Zealand, Norway, Poland, Puerto Rico, Romania, Spain, Sweden, Switzerland,Taiwan, USA, US Virgin Islands.
--)))|(% style="width:120px" %)UK: Band20
--|(% 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" %)
--== 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 and show ~*~*Signal Strenght:99~*~*. User can lock the band to specify band for its operator to make this faster.
--**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**.
++~(% 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" %)~*~*Europe General~*~*~(%%) ~*~*AT+QBAND=2,8,20 ~*~* ~~/~~/ Set to use 2 frequency bands. Band 8 and Band 20
++~(% style="color:#037691" %)~*~*Global General~*~*~(%%) : ~*~*AT+QBAND=10,8,20,28,2,4,12,13,66,85,5~*~*
--**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.
++~(% style="color:#037691" %)~*~*Verizon~*~*~(%%)~*~* ~*~*      AT+QBAND=1,13
++~(% style="color:#037691" %)~*~*AT&T~*~*~(%%)           AT+QBAND=3,12,4,2
++~(% style="color:#037691" %)~*~*Telstra~*~*~(%%)        AT+QBAND=1,28
++~(% style="color:#037691" %)~*~*Softband~*~*~(%%)     AT+QBAND=2,3,8
--Attache to 1NCE card for Australia use:
++After connection is successful, user can use ~(% style="color:#037691" %)~*~*AT+QENG=0 ~*~*~(%%) to check which band is actually in used.
--* 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.
++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/]]~*~*
--AT+QENG="servingcell"
--+QENG: "servingcell","NOCONN","eMTC","FD
--D",505,01,90D2C0B,258,9410,28,5,5,901A,-112,-17,-80,10,27
++~= 3. Configure to connect to different servers =
--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.1 General UDP Connection ==
--**1.Configure Frequency Band**
--AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
++The NB-IoT Sensor can send packet to server use UDP protocol.
--<GSM_bandval>:
--0    No change
--0x1    EGSM900
--0x2    DCS1800
--0x4    GSM850
--0x8    PCS1900
--0xF    All of the supported bands above
++~=== 3.1.1 Simulate UDP Connection by PC tool ===
--<eMTC_bandval>:
--0              No change
--0x1          LTE B1
--0x2          LTE B2
--0x4          LTE B3
--0x8          LTE B4
--0x10        LTE B5
--0x80        LTE B8
--0x800      LTE B12
--0x1000     LTE B13
--0x20000     LTE B18
--0x40000    LTE B19
--0x80000    LTE B20
--0x1000000   LTE B25
--0x2000000   LTE B26
--0x4000000   LTE B27
--0x8000000   LTE B28
--0x40000000     LTE B31
--0x20000000000000000    LTE B66
--0x800000000000000000  LTE B72
--0x1000000000000000000  LTE B73
--0x1000000000000000000000   LTE B85
++We can use PC tool to simulate UDP connection to make sure server works ok.
--<NB-IoT_bandval>:
++~[~[image~:image-20230802112413-1.png||height="468" width="1024"]]
--0              No change
--0x1          LTE B1
--0x2          LTE B2
--0x4          LTE B3
--0x8          LTE B4
--0x10        LTE B5
--0x80        LTE B8
--0x800      LTE B12
--0x1000     LTE B13
--0x20000     LTE B18
--0x40000    LTE B19
--0x80000    LTE B20
--0x1000000   LTE B25
--0x8000000   LTE B28
--0x40000000     LTE B31
--0x20000000000000000    LTE B66
--0x400000000000000000  LTE B71
--0x800000000000000000  LTE B72
--0x1000000000000000000  LTE B73
--0x1000000000000000000000   LTE B85
++~=== 3.1.2 Configure NB-IoT Sensor ===
--For example, setting the LTE-M network frequency band to 3.
++~==== 3.1.2.1 AT Commands ====
--AT+QCFG="band",0xF,0x4,0,1
--When searching for all bands, the value of this command is set to:
++~(% style="color:blue" %)~*~*AT Commands:~*~*
--AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
++~* ~(% style="color:#037691" %)~*~*AT+PRO=2,0~*~*  ~(%%)       ~~/~~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
++~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,5601~*~*  ~(%%)    ~~/~~/  Set UDP server address and port
--**2.Configure search network sequence**
++~[~[image~:image-20230802112413-2.png]]
--AT+QCFG="nwscanseq",<scanseq>,1
--<scanseq>:
++~==== 3.1.2.2 Uplink Example ====
--00  Automatic (eMTC → NB-IoT → GSM)
--01  GSM
--02  eMTC
--03  NB-IoT
--AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
++~[~[image~:image-20230802112413-3.png]]
--**3.Configure Network Category to be Searched for under LTE RAT**
--AT+QCFG="iotopmode",mode,1
++~== 3.2 General MQTT Connection ==
--0 eMTC
--1 NB-IoT
--2 eMTC and NB-IoT
++The NB-IoT Sensor can send packet to server use MQTT protocol.
--= 3. Configure to connect to different servers =
++Below are the commands.
--== 3.1 General UDP Connection ==
++~(% style="color:blue" %)~*~*AT Commands:~*~*
--The NB-IoT Sensor can send packet to server use UDP protocol.
++~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0~*~*   ~(%%)   ~~/~~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
--=== 3.1.1 Simulate UDP Connection by PC tool ===
++~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,1883~*~*  ~(%%)      ~~/~~/  Set MQTT server address and port
--We can use PC tool to simulate UDP connection to make sure server works ok.
++~* ~(% style="color:#037691" %)~*~*AT+CLIENT=CLIENT~*~*     ~(%%)                            ~~/~~/  Set up the CLIENT of MQTT
--[[image:image-20230802112413-1.png||height="468" width="1024"]]
++~* ~(% style="color:#037691" %)~*~*AT+UNAME=UNAME~*~*        ~(%%)                      ~~/~~/  Set the username of MQTT
--=== 3.1.2 Configure NB-IoT Sensor ===
++~* ~(% style="color:#037691" %)~*~*AT+PWD=PWD~*~*             ~(%%)                           ~~/~~/  Set the password of MQTT
--==== 3.1.2.1 AT Commands ====
++~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=NSE01_PUB~*~*  ~(%%)                  ~~/~~/  Set the sending topic of MQTT
--(% style="color:blue" %)**AT Commands:**
++~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=NSE01_SUB~*~*  ~(%%)                  ~~/~~/  Set the subscription topic of MQTT
--* (% style="color:#037691" %)**AT+PRO=2,0**  (%%)       ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
++~[~[image~:image-20230802112413-4.png]]
--* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%)    ~/~/  Set UDP server address and port
++~[~[image~:image-20230802112413-5.png||height="530" width="987"]]
--[[image:image-20230802112413-2.png]]
++~(% 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.~*~*
--==== 3.1.2.2 Uplink Example ====
--[[image:image-20230802112413-3.png]]
++~== 3.3 ~[~[ThingSpeak>>url:https:~/~/thingspeak.com/]] (via MQTT) ==
--== 3.2 General COAP Connection ==
++~=== 3.3.1 Get MQTT Credentials ===
--The NB-IoT Sensor can send packet to server use COAP protocol.
--Below are the commands.
++~[~[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.
--(% style="color:blue" %)**AT Commands:**
++~[~[image~:image-20230802112413-6.png||height="336" width="925"]]
--* (% style="color:#037691" %)**AT+PRO=1,0**   (%%)   ~/~/  Set to use COAP protocol to uplink, Payload Type select Hex payload.
++~[~[image~:image-20230802112413-7.png]]
--* (% 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+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%)    ~/~/  Configure CoAP Message Options
++~=== 3.3.2 Simulate with MQTT.fx ===
--=== 3.2.1 Uplink Example ===
++~==== 3.3.2.1 Establish MQTT Connection ====
++After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
--== 3.2 General MQTT Connection ==
++~[~[image~:image-20230802112413-8.png]]
--The NB-IoT Sensor can send packet to server use MQTT protocol.
++~* ~(% style="color:#037691" %)~*~*Broker Address:~*~*~(%%) mqtt3.thingspeak.com
--Below are the commands.
++~* ~(% style="color:#037691" %)~*~*Broker Port:~*~*~(%%) 1883
--(% style="color:blue" %)**AT Commands:**
++~* ~(% style="color:#037691" %)~*~*Client ID:~*~*~(%%) <Your ThingSpeak MQTT ClientID>
--* (% style="color:#037691" %)**AT+PRO=3,0**   (%%)   ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
++~* ~(% style="color:#037691" %)~*~*User Name:~*~*~(%%) <Your ThingSpeak MQTT User Name>
--* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%)      ~/~/  Set MQTT server address and port
++~* ~(% style="color:#037691" %)~*~*Password:~*~*~(%%) <Your ThingSpeak MQTT Password>
--* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%)                            ~/~/  Set up the CLIENT of MQTT
++~==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
--* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%)                      ~/~/  Set the username of MQTT
--* (% style="color:#037691" %)**AT+PWD=PWD**             (%%)                           ~/~/  Set the password of MQTT
++~[~[image~:image-20230802112413-9.png]]
--* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%)                  ~/~/  Set the sending topic of MQTT
++~[~[image~:image-20230802112413-10.png]]
--* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%)                  ~/~/  Set the subscription topic of MQTT
--[[image:image-20230802112413-4.png]]
++~(% style="color:blue" %)~*~*In MQTT.fx, we can publish below info:~*~*
--[[image:image-20230802112413-5.png||height="530" width="987"]]
++~* ~(% style="color:#037691" %)~*~*Topic:~*~*~(%%) channels/YOUR_CHANNEL_ID/publish
--(% 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.**
++~* ~(% style="color:#037691" %)~*~*Payload:~*~*~(%%) field1=63&field2=67&status=MQTTPUBLISH
--== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
++Where 63 and 67 are the value to be published to field1 & field2.
--=== 3.3.1 Get MQTT Credentials ===
--[[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.
++~(% style="color:blue" %)~*~*Result: ~*~*
--[[image:image-20230802112413-6.png||height="336" width="925"]]
++~[~[image~:image-20230802112413-11.png||height="539" width="901"]]
--[[image:image-20230802112413-7.png]]
--=== 3.3.2 Simulate with MQTT.fx ===
++~=== 3.3.3 Configure NB-IoT Sensor for connection ===
--==== 3.3.2.1 Establish MQTT Connection ====
++~==== 3.3.3.1 AT Commands: ====
--After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
--[[image:image-20230802112413-8.png]]
++In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
--* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
++~* ~(% style="color:blue" %)~*~*AT+PRO=3,1~*~* ~(%%)    ~~/~~/ Set to use ThingSpeak Server and Related Payload
--* (% style="color:#037691" %)**Broker Port:**(%%) 1883
++~* ~(% style="color:blue" %)~*~*AT+CLIENT=<Your ThingSpeak MQTT ClientID>~*~*
--* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
++~* ~(% style="color:blue" %)~*~*AT+UNAME=<Your ThingSpeak MQTT User Name>~*~*
--* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
++~* ~(% style="color:blue" %)~*~*AT+PWD=<Your ThingSpeak MQTT Password>~*~*
--* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
++~* ~(% style="color:blue" %)~*~*AT+PUBTOPIC=<YOUR_CHANNEL_ID>~*~*
--==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
++~* ~(% style="color:blue" %)~*~*AT+SUBTOPIC=<YOUR_CHANNEL_ID>~*~*
--[[image:image-20230802112413-9.png]]
++~==== 3.3.3.2 Uplink Examples ====
--[[image:image-20230802112413-10.png]]
--(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
++~[~[image~:image-20230816201942-1.png]]
--* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
++For SE01-NB
--* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
++For DDS20-NB
--Where 63 and 67 are the value to be published to field1 & field2.
++For DDS45-NB
--(% style="color:blue" %)**Result: **
++For DDS75-NB
--[[image:image-20230802112413-11.png||height="539" width="901"]]
++For NMDS120-NB
--=== 3.3.3 Configure NB-IoT Sensor for connection ===
++For SPH01-NB
--==== 3.3.3.1 AT Commands: ====
++For NLM01-NB
--In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
++For NMDS200-NB
--* (% style="color:blue" %)**AT+PRO=3,1** (%%)    ~/~/ Set to use ThingSpeak Server and Related Payload
++For CPN01-NB
--* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
++For DS03A-NB
--* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
++For SN50V3-NB
--* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
--* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
++~==== 3.3.3.3 Map fields to sensor value ====
--* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
--==== 3.3.3.2 Uplink Examples ====
++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-20230816201942-1.png]]
--For SE01-NB
++~[~[image~:image-20230802112413-12.png||height="504" width="1011"]]
--For DDS20-NB
++~[~[image~:image-20230802112413-13.png||height="331" width="978"]]
--For DDS45-NB
--For DDS75-NB
++Below is the NB-IoT Product Table show the mapping.
--For NMDS120-NB
++~(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
++~|~(% style="background-color:#4f81bd; width:143px" %) |~(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|~(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|~(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|~(% style="background-color:#4f81bd; color:white; width:154px" %)Field4|~(% style="background-color:#4f81bd; color:white; width:153px" %)Field5|~(% style="background-color:#4f81bd; color:white; width:151px" %)Field6|~(% style="background-color:#4f81bd; color:white; width:160px" %)Field7|~(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|~(% style="background-color:#4f81bd; color:white; width:67px" %)Field9|~(% style="background-color:#4f81bd; color:white; width:69px" %)Field10
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|~(% style="width:103px" %)Temperature |~(% style="width:102px" %)Humidity|~(% style="width:157px" %)Battery|~(% style="width:154px" %)RSSI|~(% style="width:153px" %) |~(% style="width:151px" %) |~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|~(% style="width:103px" %)Temperature |~(% style="width:102px" %)Humidity|~(% style="width:157px" %)conduct|~(% style="width:154px" %)dielectric_constant|~(% style="width:153px" %)Battery|~(% style="width:151px" %)RSSI|~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|~(% style="width:103px" %)distance|~(% style="width:102px" %)Battery|~(% style="width:157px" %)RSSI|~(% style="width:154px" %) |~(% style="width:153px" %) |~(% style="width:151px" %) |~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|~(% style="width:103px" %)distance|~(% style="width:102px" %)Battery|~(% style="width:157px" %)RSSI|~(% style="width:154px" %) |~(% style="width:153px" %) |~(% style="width:151px" %) |~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|~(% style="width:103px" %)distance|~(% style="width:102px" %)Battery|~(% style="width:157px" %)RSSI|~(% style="width:154px" %) |~(% style="width:153px" %) |~(% style="width:151px" %) |~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|~(% style="width:103px" %)distance|~(% style="width:102px" %)Battery|~(% style="width:157px" %)RSSI|~(% style="width:154px" %) |~(% style="width:153px" %) |~(% style="width:151px" %) |~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|~(% style="width:103px" %)ph|~(% style="width:102px" %)Temperature|~(% style="width:157px" %)Battery|~(% style="width:154px" %)RSSI|~(% style="width:153px" %) |~(% style="width:151px" %) |~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% colspan="1" rowspan="1" style="width:69px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|~(% style="width:103px" %)Humidity|~(% style="width:102px" %)Temperature|~(% style="width:157px" %)Battery|~(% style="width:154px" %)RSSI|~(% style="width:153px" %) |~(% style="width:151px" %) |~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|~(% style="width:103px" %)distance1|~(% style="width:102px" %)distance2|~(% style="width:157px" %)Battery|~(% style="width:154px" %)RSSI|~(% style="width:153px" %) |~(% style="width:151px" %) |~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|~(% style="width:103px" %)alarm|~(% style="width:102px" %)count|~(% style="width:157px" %)door open duration|~(% style="width:154px" %)calc flag|~(% style="width:153px" %)Battery|~(% style="width:151px" %)RSSI|~(% style="width:160px" %) |~(% style="width:152px" %) |~(% style="width:67px" %) |~(% style="width:69px" %)
++~|~(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|~(% colspan="1" rowspan="1" style="width:103px" %)level|~(% colspan="1" rowspan="1" style="width:102px" %)alarm|~(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|~(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time|~(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status|~(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status|~(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num|~(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|~(% colspan="1" rowspan="1" style="width:67px" %)Battery|~(% colspan="1" rowspan="1" style="width:69px" %)RSSI
++~|~(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|~(% colspan="1" rowspan="1" style="width:103px" %)mod|~(% colspan="1" rowspan="1" style="width:102px" %)Battery|~(% colspan="1" rowspan="1" style="width:157px" %)RSSI|~(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp|~(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4|~(% colspan="1" rowspan="1" style="width:151px" %)adc0|~(% colspan="1" rowspan="1" style="width:160px" %)Temperature |~(% colspan="1" rowspan="1" style="width:152px" %)Humidity|~(% colspan="1" rowspan="1" style="width:67px" %) |~(% colspan="1" rowspan="1" style="width:69px" %)
++~|~(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|~(% colspan="1" style="width:103px" %)mod|~(% colspan="1" style="width:102px" %)Battery|~(% colspan="1" style="width:157px" %)RSSI|~(% colspan="1" style="width:154px" %)DS18B20 Temp|~(% colspan="1" style="width:153px" %)exit_state/input PA4|~(% colspan="1" style="width:151px" %)adc0|~(% colspan="1" style="width:160px" %)distance|~(% colspan="1" style="width:152px" %) |~(% colspan="1" style="width:67px" %) |~(% colspan="1" style="width:69px" %)
++~|~(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|~(% colspan="1" style="width:103px" %)mod|~(% colspan="1" style="width:102px" %)Battery|~(% colspan="1" style="width:157px" %)RSSI|~(% colspan="1" style="width:154px" %)adc0|~(% colspan="1" style="width:153px" %)exit_state/input PA4|~(% colspan="1" style="width:151px" %)adc1|~(% colspan="1" style="width:160px" %)Temperature|~(% colspan="1" style="width:152px" %)Humidity|~(% colspan="1" style="width:67px" %)adc4|~(% colspan="1" style="width:69px" %)
++~|~(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|~(% colspan="1" style="width:103px" %)mod|~(% colspan="1" style="width:102px" %)Battery|~(% colspan="1" style="width:157px" %)RSSI|~(% colspan="1" style="width:154px" %)DS18B20 Temp|~(% colspan="1" style="width:153px" %)adc0|~(% colspan="1" style="width:151px" %)exit_state/input PA4|~(% colspan="1" style="width:160px" %)DS18B20 Temp2|~(% colspan="1" style="width:152px" %)DS18B20 Temp3|~(% colspan="1" style="width:67px" %) |~(% colspan="1" style="width:69px" %)
++~|~(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|~(% colspan="1" style="width:103px" %)mod|~(% colspan="1" style="width:102px" %)Battery|~(% colspan="1" style="width:157px" %)RSSI|~(% colspan="1" style="width:154px" %)DS18B20 Temp|~(% colspan="1" style="width:153px" %)adc0|~(% colspan="1" style="width:151px" %)exit_state/input PA4|~(% colspan="1" style="width:160px" %)Weight|~(% colspan="1" style="width:152px" %) |~(% colspan="1" style="width:67px" %) |~(% colspan="1" style="width:69px" %)
++~|~(% 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" %)
--For SPH01-NB
++~== 3.4 ~[~[Datacake>>https:~/~/datacake.co/]] ==
--For NLM01-NB
--For NMDS200-NB
++~(% class="wikigeneratedid" %)
++Dragino NB-IoT sensors has its template in ~*~*~[~[Datacake>>https:~/~/datacake.co/]]~*~* Platform. There are two version for NB Sensor,
--For CPN01-NB
--For DS03A-NB
++~(% class="wikigeneratedid" %)
++As example for S31B-NB. there are two versions: ~*~*S31B-NB-1D and S31B-NB-GE.~*~*
--For SN50V3-NB
++~* ~(% 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.
--==== 3.3.3.3 Map fields to sensor value ====
++~* ~(% 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.
--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.
++~=== 3.4.1 For device Already has template ===
--[[image:image-20230802112413-12.png||height="504" width="1011"]]
++~==== 3.4.1.1 Create Device ====
--[[image:image-20230802112413-13.png||height="331" width="978"]]
++~(% style="color:blue" %)~*~*Add Device~*~*~(%%) in DataCake.
--Below is the NB-IoT Product Table show the mapping.
++~[~[image~:image-20230808162301-1.png||height="453" width="952"]]
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
--|(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:154px" %)Field4|(% style="background-color:#4f81bd; color:white; width:153px" %)Field5|(% style="background-color:#4f81bd; color:white; width:151px" %)Field6|(% style="background-color:#4f81bd; color:white; width:160px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:67px" %)Field9|(% style="background-color:#4f81bd; color:white; width:69px" %)Field10
--|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:154px" %)dielectric_constant|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
--|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:154px" %)calc flag|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
--|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:67px" %)Battery|(% colspan="1" rowspan="1" style="width:69px" %)RSSI
--|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:151px" %)adc0|(% colspan="1" rowspan="1" style="width:160px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc0|(% colspan="1" style="width:160px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)adc0|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc1|(% colspan="1" style="width:160px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:67px" %)adc4|(% colspan="1" style="width:69px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
--|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
--|(% 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/]] ==
++~[~[image~:image-20230808162342-2.png||height="541" width="952"]]
--(% 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" %)~*~*Choose the correct model~*~*~(%%) from template.
--* (% 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.
++~[~[image~:image-20230808162421-3.png]]
--* (% 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 For device Already has template ===
++~(% 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.
--==== 3.4.1.1 Create Device ====
++~[~[image~:image-20230808163612-7.png||height="549" width="952"]]
--(% style="color:blue" %)**Add Device**(%%) in DataCake.
++~[~[image~:image-20230808163035-5.png]]
--[[image:image-20230808162301-1.png||height="453" width="952"]]
++~[~[image~:image-20230808163049-6.png||height="544" width="926"]]
--[[image:image-20230808162342-2.png||height="541" width="952"]]
--(% style="color:blue" %)**Choose the correct model**(%%) from template.
++~=== 3.4.2 For Device already registered in DataCake before shipped ===
--[[image:image-20230808162421-3.png]]
++~==== 3.4.2.1 Scan QR Code to get the device info ====
--(% 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||height="549" width="952"]]
++Users can use their phones or computers to scan QR codes to obtain device data information.
--[[image:image-20230808163035-5.png]]
++~[~[image~:image-20230808170051-8.png||height="255" width="259"]]
--[[image:image-20230808163049-6.png||height="544" width="926"]]
++~[~[image~:image-20230808170548-9.png]]
--=== 3.4.2 For Device already registered in DataCake before shipped ===
--==== 3.4.2.1 Scan QR Code to get the device info ====
++~==== 3.4.2.2 Claim Device to User Account ====
--Users can use their phones or computers to scan QR codes to obtain device data information.
--[[image:image-20230808170051-8.png||height="255" width="259"]]
++By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
--[[image:image-20230808170548-9.png]]
--==== 3.4.2.2 Claim Device to User Account ====
++~=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
--By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
--=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
++~*~*Step1: Add a device~*~*
--**Step1: Add a device**
++~[~[image~:image-20240129170024-1.png||height="330" width="900"]]
--[[image:image-20240129170024-1.png||height="330" width="900"]]
--**Step2: Choose your device type,please select dragino NB-IOT device**
++~*~*Step2: Choose your device type,please select dragino NB-IOT device~*~*
--[[image:image-20240129170216-2.png||height="534" width="643"]]
++~[~[image~:image-20240129170216-2.png||height="534" width="643"]]
--**Step3: Choose to create a new device**
--[[image:image-20240129170539-3.png||height="459" width="646"]]
++~*~*Step3: Choose to create a new device~*~*
--**Step4: Fill in the device ID of your NB device**
++~[~[image~:image-20240129170539-3.png||height="459" width="646"]]
--[[image:image-20240202111546-1.png||height="378" width="651"]]
--**Step5: Please select your device plan according to your needs and complete the creation of the device**
++~*~*Step4: Fill in the device ID of your NB device~*~*
--[[image:image-20240129171236-6.png||height="450" width="648"]]
++~[~[image~:image-20240202111546-1.png||height="378" width="651"]]
--**Step6: Please add the decoder at the payload decoder of the device configuration.**
--**Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
++~*~*Step5: Please select your device plan according to your needs and complete the creation of the device~*~*
--[[image:image-20240129172056-7.png||height="457" width="816"]]
++~[~[image~:image-20240129171236-6.png||height="450" width="648"]]
--[[image:image-20240129173116-9.png||height="499" width="814"]]
--**Step7: Add the output of the decoder as a field**
++~*~*Step6: Please add the decoder at the payload decoder of the device configuration.~*~*
--[[image:image-20240129173541-10.png||height="592" width="968"]]
++~*~*Decoder location:~*~*~[~[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https:~/~/github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
--**Step8: Customize the dashboard and use fields as parameters of the dashboard**
++~[~[image~:image-20240129172056-7.png||height="457" width="816"]]
--[[image:image-20240129174518-11.png||height="147" width="1042"]]
++~[~[image~:image-20240129173116-9.png||height="499" width="814"]]
--[[image:image-20240129174657-12.png||height="538" width="916"]]
--[[image:image-20240129174840-13.png||height="536" width="750"]]
++~*~*Step7: Add the output of the decoder as a field~*~*
--=== 3.4.4 For device have not configured to connect to DataCake ===
++~[~[image~:image-20240129173541-10.png||height="592" width="968"]]
--(% class="lead" %)
++
++~*~*Step8: Customize the dashboard and use fields as parameters of the dashboard~*~*
++
++~[~[image~:image-20240129174518-11.png||height="147" width="1042"]]
++
++~[~[image~:image-20240129174657-12.png||height="538" width="916"]]
++
++~[~[image~:image-20240129174840-13.png||height="536" width="750"]]
++
++
++~=== 3.4.4 For device have not configured to connect to DataCake ===
++
++
++~(% class="lead" %)
  Use AT command for connecting to DataCake
--(% style="color:blue" %)**AT+PRO=2,0**
++~(% style="color:blue" %)~*~*AT+PRO=2,0~*~*
--(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
++~(% style="color:blue" %)~*~*AT+SERVADDR=67.207.76.90,4445~*~*
--== 3.5 Node-Red (via MQTT) ==
--=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
++~== 3.5 Node-Red (via MQTT) ==
++~=== 3.5.1 Configure ~[~[Node-Red>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
++
++
  Take S31-NB UDP protocol as an example.
  Dragino provides input flow examples for the sensors.
@@ -467,348 +467,420 @@
  User can download the required JSON file through Dragino Node-RED input flow template.
--Download sample JSON file link: [[https:~~/~~/www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0>>url:https://www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0]]
++Download sample JSON file link: ~[~[https:~~~~/~~~~/www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0>>url:https:~/~/www.dropbox.com/sh/mduw85jcuwsua22/AAAvwPhg9z6dLjJhmZjqBf_ma?dl=0]]
  We can directly import the template.
  The templates for S31-NB and NB95S31B are the same.
--[[image:image-20230809173127-4.png]]
++~[~[image~:image-20230809173127-4.png]]
++
++
  Please select the NB95S31B template.
--[[image:image-20230809173310-5.png||height="558" width="926"]]
++~[~[image~:image-20230809173310-5.png||height="558" width="926"]]
--[[image:image-20230809173438-6.png]]
++~[~[image~:image-20230809173438-6.png]]
--[[image:image-20230809173800-7.png]]
++~[~[image~:image-20230809173800-7.png]]
++
  Successfully imported template.
--[[image:image-20230809173835-8.png||height="515" width="860"]]
++~[~[image~:image-20230809173835-8.png||height="515" width="860"]]
++
  Users can set UDP port.
--[[image:image-20230809174053-9.png]]
++~[~[image~:image-20230809174053-9.png]]
--=== 3.5.2 Simulate Connection ===
++~=== 3.5.2 Simulate Connection ===
++
++
  We have completed the configuration of UDP. We can try sending packets to node red.
--[[image:image-20230810083934-1.png]]
++~[~[image~:image-20230810083934-1.png]]
--[[image:image-20230810084048-2.png||height="535" width="1052"]]
++~[~[image~:image-20230810084048-2.png||height="535" width="1052"]]
--=== 3.5.3 Configure NB-IoT Sensors ===
--* (% 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”**
++~=== 3.5.3 Configure NB-IoT Sensors ===
--== 3.6 ThingsBoard.Cloud (via MQTT) ==
--=== 3.6.1 Configure ThingsBoard ===
++~* ~(% 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”~*~*
--==== 3.6.1.1 Create Device ====
++~== 3.6 ThingsBoard.Cloud (via MQTT) ==
--Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
++~=== 3.6.1 Configure ThingsBoard ===
--[[image:image-20230802112413-32.png||height="583" width="1066"]]
++~==== 3.6.1.1 Create Device ====
--==== 3.6.1.2 Create Uplink & Downlink Converter ====
--(% style="color:blue" %)**Uplink Converter**
++Create a New Device in ~[~[ThingsBoard>>url:https:~/~/thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
--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.
++~[~[image~:image-20230802112413-32.png||height="583" width="1066"]]
--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="597" width="1061"]]
++~==== 3.6.1.2 Create Uplink & Downlink Converter ====
--(% style="color:blue" %)**Downlink Converter**
--The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
++~(% style="color:blue" %)~*~*Uplink Converter~*~*
--[[image:image-20230802112413-34.png||height="598" width="1063"]]
++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.
--(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
++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.
--==== 3.6.1.3 MQTT Integration Setup ====
++~[~[image~:image-20230802112413-33.png||height="597" width="1061"]]
--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="597" width="1062"]]
++~(% style="color:blue" %)~*~*Downlink Converter~*~*
--* The next steps is to add the recently created uplink and downlink converters;
++The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
--[[image:image-20230802112413-36.png||height="598" width="1062"]]
++~[~[image~:image-20230802112413-34.png||height="598" width="1063"]]
--[[image:image-20230802112413-37.png||height="598" width="1064"]]
++~(% style="color:red" %)~*~*Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.~*~*
--(% style="color:blue" %)**Add a topic filter:**
++~==== 3.6.1.3 MQTT 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" %)~*~*“MQTT Integration”~*~*~(%%), select type ~(% style="color:blue" %)~*~*MQTT~*~*;
++
++~[~[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="598" width="1062"]]
++
++~[~[image~:image-20230802112413-37.png||height="598" width="1064"]]
++
++
++~(% style="color:blue" %)~*~*Add a topic filter:~*~*
++
  Consistent with the theme of the node setting.
--You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
++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="598" width="1064"]]
++~[~[image~:image-20230802112413-38.png||height="598" width="1064"]]
--=== 3.6.2 Simulate with MQTT.fx ===
--[[image:image-20230802112413-39.png]]
++~=== 3.6.2 Simulate with MQTT.fx ===
--[[image:image-20230802112413-40.png||height="525" width="980"]]
--=== 3.6.3 Configure NB-IoT Sensor ===
++~[~[image~:image-20230802112413-39.png]]
--(% style="color:blue" %)**AT Commands**
++~[~[image~:image-20230802112413-40.png||height="525" width="980"]]
--* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)**  **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
--* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
++~=== 3.6.3 Configure NB-IoT Sensor ===
--* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
--* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
++~(% style="color:blue" %)~*~*AT Commands~*~*
--* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
++~* ~(% style="color:#037691" %)~*~*AT+PRO=3,3  ~*~*~(%%)~*~*  ~*~*~~/~~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
--* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
++~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=<device name>~*~*
--Test Uplink by click the button for 1 second
++~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=<device name>~*~*
--[[image:image-20230802112413-41.png||height="496" width="828"]]
++~* ~(% style="color:#037691" %)~*~*AT+CLIENT=<device name> or User Defined~*~*
--[[image:image-20230802112413-42.png]]
++~* ~(% style="color:#037691" %)~*~*AT+UNAME=<device name> or User Defined~*~*
--[[image:image-20230802112413-43.png||height="407" width="825"]]
++~* ~(% style="color:#037691" %)~*~*AT+PWD=<device name> or User Defined~*~*
--== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
++Test Uplink by click the button for 1 second
--=== 3.7.1 Create device & Get Credentials ===
++~[~[image~:image-20230802112413-41.png||height="496" width="828"]]
--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-20230802112413-42.png]]
--[[image:image-20230802112413-44.png]]
++~[~[image~:image-20230802112413-43.png||height="407" width="825"]]
--[[image:image-20230802112413-45.png]]
--Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
++~== 3.7 ~[~[Tago.io>>url:https:~/~/admin.tago.io/]] (via MQTT) ==
--[[image:image-20230802112413-46.png]]
++~=== 3.7.1 Create device & Get Credentials ===
--The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
--(% style="color:blue" %)**On the Connection Profile window, set the following information:**
++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.
--* (% style="color:#037691" %)**Profile Name: “Any name”**
++~[~[image~:image-20230802112413-44.png]]
--* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
++~[~[image~:image-20230802112413-45.png]]
--* (% style="color:#037691" %)**Broker Port: 8883**
--* (% style="color:#037691" %)**Client ID: “Any value”**
++Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
--(% style="color:blue" %)**On the section User credentials, set the following information:**
++~[~[image~:image-20230802112413-46.png]]
--* (% style="color:#037691" %)**User Name: “Any value”** (%%)      **~/~/ Tago validates your user by the token only**
--* (% style="color:#037691" %)**Password: “Your device token”**
++The device needs to enable the TLS mode and set the ~(% style="color:blue" %)~*~*AT+TLSMOD=1,0~*~*~(%%) command.
--* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
++~(% style="color:blue" %)~*~*On the Connection Profile window, set the following information:~*~*
--* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
++~* ~(% style="color:#037691" %)~*~*Profile Name: “Any name”~*~*
--(% style="color:blue" %)**AT command:**
++~* ~(% style="color:#037691" %)~*~*Broker Address: mqtt.tago.io~*~*
--* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)   **~/~/ hex format or json format**
++~* ~(% style="color:#037691" %)~*~*Broker Port: 8883~*~*
--* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
++~* ~(% style="color:#037691" %)~*~*Client ID: “Any value”~*~*
--* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
++~(% style="color:blue" %)~*~*On the section User credentials, set the following information:~*~*
--* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
++~* ~(% style="color:#037691" %)~*~*User Name: “Any value”~*~* ~(%%)      ~*~*~~/~~/ Tago validates your user by the token only~*~*
--* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
++~* ~(% style="color:#037691" %)~*~*Password: “Your device token”~*~*
--* (% style="color:#037691" %)**AT+PWD=“Your device token”**
++~* ~(% style="color:#037691" %)~*~*PUBTOPIC: “Any value”~*~*
--=== 3.7.2 Simulate with MQTT.fx ===
++~* ~(% style="color:#037691" %)~*~*SUBTOPIC: “Any value”~*~*
--[[image:image-20230802112413-52.png]]
++~(% style="color:blue" %)~*~*AT command:~*~*
--[[image:image-20230808105300-2.png||height="553" width="1026"]]
++~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0 or 3,5 ~*~* ~(%%)   ~*~*~~/~~/ hex format or json format~*~*
--Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
++~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=<device name>or User Defined~*~*
--[[image:image-20230808105217-1.png||height="556" width="1031"]]
++~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=<device name>or User Defined~*~*
--[[image:image-20230808105329-3.png]]
++~* ~(% style="color:#037691" %)~*~*AT+CLIENT=<device name> or User Defined~*~*
--=== 3.7.3 tago data ===
++~* ~(% style="color:#037691" %)~*~*AT+UNAME=<device name> or User Defined~*~*
--[[image:image-20230802112413-50.png||height="242" width="1037"]]
++~* ~(% style="color:#037691" %)~*~*AT+PWD=“Your device token”~*~*
--[[image:image-20230802112413-51.png||height="184" width="696"]]
++~=== 3.7.2 Simulate with MQTT.fx ===
--== 3.8 TCP Connection ==
--(% style="color:blue" %)**AT command:**
++~[~[image~:image-20230802112413-52.png]]
--* (% 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)
++~[~[image~:image-20230808105300-2.png||height="553" width="1026"]]
--* (% 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:**
++Users can run the ~(% style="color:blue" %)~*~*AT+PRO=3,5~*~*~(%%) command, and the payload will be converted to ~*~*JSON format~*~*.
--[[image:image-20230807233631-1.png]]
++~[~[image~:image-20230808105217-1.png||height="556" width="1031"]]
--(% style="color:blue" %)**See result in TCP Server:**
++~[~[image~:image-20230808105329-3.png]]
--[[image:image-20230807233631-2.png]]
--== 3.9 AWS Connection ==
++~=== 3.7.3 tago data ===
--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]]
--= 4. MQTT/UDP/TCP downlink =
++~[~[image~:image-20230802112413-50.png||height="242" width="1037"]]
--== 4.1 MQTT (via MQTT.fx) ==
++~[~[image~:image-20230802112413-51.png||height="184" width="696"]]
--Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
--**1.** Configure node MQTT connection (via MQTT.fx):
++~== 3.8 TCP Connection ==
--(% style="color:blue" %)**AT command:**
--* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 **  (%%)~/~/ hex format or json format
++~(% style="color:blue" %)~*~*AT command:~*~*
--* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
++~* ~(% style="color:#037691" %)~*~*AT+PRO=4,0   ~*~* ~(%%) ~~/~~/ Set to use TCP protocol to uplink(HEX format)
--* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
++~* ~(% style="color:#037691" %)~*~*AT+PRO=4,1   ~*~* ~(%%) ~~/~~/ Set to use TCP protocol to uplink(JSON format)
--* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
++~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,5600 ~*~*  ~(%%) ~~/~~/ to set TCP server address and port
--* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
++~(% style="color:blue" %)~*~*Sensor Console Output when Uplink:~*~*
--* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 **  (%%) ~/~/ to set MQTT server address and port
++~[~[image~:image-20230807233631-1.png]]
--(% style="color:red" %)**Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.**
--[[image:image-20240417180145-2.png||height="434" width="587"]][[ width="584">> width="584"]]
++~(% style="color:blue" %)~*~*See result in TCP Server:~*~*
--**2. **When the node uplink packets, we can observe the data in MQTT.fx.
++~[~[image~:image-20230807233631-2.png]]
--[[image:image-20240418144337-1.png||height="709" width="802"]]
--**3. **The downlink command can be successfully sent only when the downlink port is open.
++~== 3.9 AWS Connection ==
--    The downlink port is opened for about 3 seconds after uplink packets are sent.
--    Therefore, when we see the node uplink packets in the **Subscribe** window, we need to immediately switch to the **publish** window to publish the **hex format** command.
++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]]
--[[image:image-20240418150435-3.png||height="582" width="659"]]
--[[image:image-20240418150932-4.png||height="492" width="1061"]]
--(% style="color:red" %)**Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.**
++~= 4. MQTT/UDP/TCP downlink =
--= 5. GPS positioning function =
++~== 4.1 MQTT (via MQTT.fx) ==
--(% class="wikigeneratedid" id="H5.1WhatistheusageofMultiSamplingandOneUplink3F" %)
--~1. Turn on GPS function
++Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx~/~/.~/~/
--(% class="wikigeneratedid" %)
--AT+GPS=1 or 0  ~/~/GPS function on or off
++~*~*1.~*~* Configure node MQTT connection (via MQTT.fx):
++~(% style="color:blue" %)~*~*AT command:~*~*
--2.Extend the time to turn on GNSS
++~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0 or 3,5 ~*~*  ~(%%)~~/~~/ hex format or json format
--AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
++~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=User Defined~*~*
++~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=User Defined~*~*
--3.Get or set GPS positioning interval in units of hour
++~* ~(% style="color:#037691" %)~*~*AT+UNAME=<device name> or User Defined~*~*
--AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
++~* ~(% style="color:#037691" %)~*~*AT+PWD=<device name> or User Defined~*~*
++~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=8.217.91.207,1883 ~*~*  ~(%%) ~~/~~/ to set MQTT server address and port
--= 5. FAQ =
++~(% style="color:red" %)~*~*Note: To uplink and downlink via MQTT.fx, we need set the publish topic and subscribe topic different, for example: AT+SUBTOPIC=SE01_SUB & AT+PUBTOPIC=SE01_PUB.~*~*
--== 5.1 What is the usage of Multi Sampling and One Uplink? ==
++~[~[image~:image-20240417180145-2.png||height="434" width="587"]]~[~[image:image-20240417180737-3.png||height="431" width="584"]]
++
++~*~*2. ~*~*When the node uplink packets, we can observe the data in MQTT.fx.
++
++~[~[image~:image-20240418144337-1.png||height="709" width="802"]]
++
++~*~*3. ~*~*The downlink command can be successfully sent only when the downlink port is open.
++
++    The downlink port is opened for about 3 seconds after uplink packets are sent.
++
++    Therefore, when we see the node uplink packets in the ~*~*Subscribe~*~* window, we need to immediately switch to the ~*~*publish~*~* window to publish the ~*~*hex format~*~* command.
++
++~[~[image~:image-20240418150435-3.png||height="582" width="659"]]
++
++~[~[image~:image-20240418150932-4.png||height="492" width="1061"]]
++
++~(% style="color:red" %)~*~*Note: Users can edit the hex command in advance. When the node uplink, directly click the publish button several times to increase the success rate of command configuration.~*~*
++
++
++
++
++~= 5. FAQ =
++
++~== 5.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]]
++~[~[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]]
  User can use this feature for below purpose:
--1. **Reduce power consumption**. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.
--1. Give more sampling data points.
--1. Increase reliable in transmission. For example. If user set
--1*. **AT+TR=1800**        ~/~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
--1*. **AT+NOUD=24**    ~/~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
--1*. **AT+TDC=7200**  ~/~/ Uplink every 2 hours.
--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.
++~1. ~*~*Reduce power consumption~*~*. The NB-IoT transmit power is much more higher than the sensor sampling power. To save battery life, we can sampling often and send in one uplink.
++~1. Give more sampling data points.
++~1. Increase reliable in transmission. For example. If user set
++~1*. ~*~*AT+TR=1800~*~*        ~~/~~/ The unit is seconds, and the default is to record data once every 1800 seconds (30 minutes, the minimum can be set to 180 seconds)
++~1*. ~*~*AT+NOUD=24~*~*    ~~/~~/  The device uploads 24 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
++~1*. ~*~*AT+TDC=7200~*~*  ~~/~~/ Uplink every 2 hours.
++~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.
--== 5.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.
--[[image:image-20240229233154-1.png]]
++~[~[image~:image-20240229233154-1.png]]
--= 6. Trouble Shooting: =
--== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
++~= 6. Trouble Shooting: =
++~== 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.
--If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
++If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~~~31)
--[[image:image-20240207002003-1.png]]
++~[~[image~:image-20240207002003-1.png]]
++
  If fail to attach network, it will shows signal 99. as below:
--[[image:image-20240207002129-2.png]]
++~[~[image~:image-20240207002129-2.png]]
--(% class="lead" %)
++
++~(% class="lead" %)
  When see this issue, below are the checklist:
--* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
--* Do you configure the correct APN? [[Check here for APN settings>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
--* Do you lock the frequency band? This is the most case we see. [[Explain and Instruction>>http://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
--* Check if the device is attached to Carrier network but reject. (need to check with operator).
--* Check if the antenna is connected firmly.
++~* Does your SIM card support NB-IoT network? If SIM card doesn't not specify support NB-IoT clearly, normally it doesn't support. You need to confirm with your operator.
++~* Do you configure the correct APN? ~[~[Check here for APN settings>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.1GeneralConfiguretoattachnetwork]].
++~* Do you lock the frequency band? This is the most case we see. ~[~[Explain and Instruction>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H2.2SpeedUpNetworkAttachtime]].
++~* Check if the device is attached to Carrier network but reject. (need to check with operator).
++~* Check if the antenna is connected firmly.
--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.
++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" %)6.4 Why sometime the AT Command is slow in reponse?(%%) ==
++~== 6.2 Issue: "NBIOT did not respond" ==
++
++~(% class="box errormessage" %)
++~(~(~(
++11:24:22.397 [44596]NBIOT did not respond.
++11:24:24.315 [46530]NBIOT did not respond.
++11:24:26.256 [48464]NBIOT did not respond.
++11:24:28.196 [50398]NBIOT did not respond.
++11:24:30.115 [52332]NBIOT did not respond.
++11:24:32.127 [54266]NBIOT did not respond.
++11:24:32.127 [54299]Restart the module...
++11:24:39.181 [61332]No response when shutting down
++~)~)~)
++
++This issue might due to initiate issue for NB-IoT module. In this case, please try:
++
++1) Open Enclosure
++
++2) Power off device by pull out the power on Jumper
++
++3) Power on device by connect back the power jumper.
++
++4) push reset button.
++
++~[~[image~:image-20240208001740-1.png]]
++
++
++~== 6.3 Issue: "Failed to readI MSI number" ==
++
++
++~(% class="box errormessage" %)
++~(~(~(
++[18170]Failed to read IMSI:1umber.
++[20109]Failed to read IMSI numoer.
++[22048]Failed to read IMSI number.
++[29842lRestart the module...
++~)~)~)
++
++Make sure that the SIM card is insert in correct direction and device is power off/on during insert. Here is reference link: ~[~[Insert SIM Card>>||anchor="H2.1GeneralConfiguretoattachnetwork"]].
++
++
++~== ~(% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 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.
--[[image:image-20240226111928-1.png]]
++~[~[image~:image-20240226111928-1.png]]
--== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?(%%) ==
--(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
--=== UDP: ===
++~== ~(% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.5 What is the Downlink Command by the NB device?~(%%) ==
--(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
++~(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
++~=== UDP: ===
++
++~(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
  Its downlink command is the same as the AT command, but brackets are required.
  Example:
  {AT+TDC=300}
--(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
--=== MQTT: ===
++~(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
++~=== MQTT: ===
++
  Json：
  The Json format in MQTT mode needs to be configured with all commands.
@@ -845,7 +845,6 @@
  The supported commands are consistent with LoRaWAN's hex commands.
  Please refer to the following link to obtain the hex format:
--[[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/]]
++~[~[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/]]
--

image-20240602220856-1.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation