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

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

From 129.1 to 129.2

From version 1.1

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

Change comment: There is no comment for this version

To version 129.1

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Author

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

Content

@@ -1,391 +1,530 @@
--~(% class="wikigeneratedid" id="HTableofContents:" %)
--~*~*Table of Contents:~*~*
++
--~{~{toc/}}
++(% class="wikigeneratedid" id="HTableofContents:" %)
++**Table of Contents:**
++{{toc/}}
++= 1. The use of this guideline =
--~= 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.
--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. Attach Network =
++== 2.1 General Configure to attach network ==
--~= 2. Attach Network =
++To attache end nodes to NB-IoT or LTE-M Network, You need to:
--~== 2.1 General Configure to 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
++[[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"]]
--~[~[image~:image-20230808205045-1.png||height="293" width="438"]]
++After doing above, the end nodes should be able to attach to NB-IoT network .
--After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
++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
--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-NB2:  B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B28/B66/B71/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]]~*~*
++~-~-(% style="color:blue" %)** CAT-M1:  B1/B2/B3/B4/B5/B8/B12/B13/B18/B19/B20/B25/B26/B27/B28/B66/B85 **(%%).
--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" %)
++Make sure you use a the NB-IoT or LTE-M SIM card.
--~== 2.2 Speed Up Network Attach time ==
++(% 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]]**
++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" %)
--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.
++== 2.2 Speed Up Network Attach time ==
--~(% 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~*~*
++**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" %)~*~*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
++**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.
--After connection is successful, user can use ~(% style="color:#037691" %)~*~*AT+QENG=0 ~*~*~(%%) to check which band is actually in used.
++Attache to 1NCE card for Australia use:
++* AT+COPS=1,2,"50501",8
++* AT+QCFG="band",0,0x8000000,0x8000000,1
--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/]]~*~*
++After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
++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 =
--~== 3.1 General UDP Connection ==
++See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
++=== **1.Configure Frequency Band** ===
--The NB-IoT Sensor can send packet to server use UDP protocol.
++AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
++<GSM_bandval>:
--~=== 3.1.1 Simulate UDP Connection by PC tool ===
++0    No change
++0x1    EGSM900
++0x2    DCS1800
++0x4    GSM850
++0x8    PCS1900
++0xF    All of the supported bands above
++<eMTC_bandval>:
--We can use PC tool to simulate UDP connection to make sure server works ok.
++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
--~[~[image~:image-20230802112413-1.png||height="468" width="1024"]]
++<NB-IoT_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
++0x8000000   LTE B28
++0x40000000     LTE B31
++0x20000000000000000    LTE B66
--~=== 3.1.2 Configure NB-IoT Sensor ===
++0x400000000000000000  LTE B71
++0x800000000000000000  LTE B72
++0x1000000000000000000  LTE B73
++0x1000000000000000000000   LTE B85
--~==== 3.1.2.1 AT Commands ====
++For example, setting the LTE-M network frequency band to 3.
++AT+QCFG="band",0xF,0x4,0,1
--~(% style="color:blue" %)~*~*AT Commands:~*~*
++When searching for all bands, the value of this command is set to:
--~* ~(% style="color:#037691" %)~*~*AT+PRO=2,0~*~*  ~(%%)       ~~/~~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
++AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
--~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,5601~*~*  ~(%%)    ~~/~~/  Set UDP server address and port
--~[~[image~:image-20230802112413-2.png]]
++=== **2.Configure search network sequence** ===
++AT+QCFG="nwscanseq",<scanseq>,1
--~==== 3.1.2.2 Uplink Example ====
++<scanseq>:
++00  Automatic (eMTC → NB-IoT → GSM)
++01  GSM
++02  eMTC
++03  NB-IoT
--~[~[image~:image-20230802112413-3.png]]
++AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
++=== **3.Configure Network Category to be Searched for under LTE RAT** ===
--~== 3.2 General MQTT Connection ==
++AT+QCFG="iotopmode",mode,1
++0 eMTC
++1 NB-IoT
++2 eMTC and NB-IoT
--The NB-IoT Sensor can send packet to server use MQTT protocol.
++=== **4.AT command to set frequency band and network category** ===
--Below are the commands.
++AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f    ~/~/<eMTC_bandval>,<NB-IoT_bandval>
--~(% style="color:blue" %)~*~*AT Commands:~*~*
++AT+IOTMOD=0    ~/~/ 0 eMTC  1 NB-IoT   2 eMTC and NB-IoT
--~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0~*~*   ~(%%)   ~~/~~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
++**Example :**
--~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,1883~*~*  ~(%%)      ~~/~~/  Set MQTT server address and port
++Taking the use of 1nce cards in **the United States** as an example.
--~* ~(% style="color:#037691" %)~*~*AT+CLIENT=CLIENT~*~*     ~(%%)                            ~~/~~/  Set up the CLIENT of MQTT
++AT+APN=iot.1nce.net  ~/~/set APN
--~* ~(% style="color:#037691" %)~*~*AT+UNAME=UNAME~*~*        ~(%%)                      ~~/~~/  Set the username of MQTT
++AT+QBAND=0x100180A,0  ~/~/ eMTC ：Set frequency band B2,B4,B12,B13,B25      NB-IoT：No change
--~* ~(% style="color:#037691" %)~*~*AT+PWD=PWD~*~*             ~(%%)                           ~~/~~/  Set the password of MQTT
++AT+IOTMOD=0    ~/~/ Set  eMTC Network
--~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=NSE01_PUB~*~*  ~(%%)                  ~~/~~/  Set the sending topic of MQTT
++**Setting the above commands in the United States will greatly reduce the network search time of the NB module.**
--~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=NSE01_SUB~*~*  ~(%%)                  ~~/~~/  Set the subscription topic of MQTT
--~[~[image~:image-20230802112413-4.png]]
++= 3. Configure to connect to different servers =
--~[~[image~:image-20230802112413-5.png||height="530" width="987"]]
++== 3.1 General UDP Connection ==
--~(% 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.~*~*
++The NB-IoT Sensor can send packet to server use UDP protocol.
--~== 3.3 ~[~[ThingSpeak>>url:https:~/~/thingspeak.com/]] (via MQTT) ==
++=== 3.1.1 Simulate UDP Connection by PC tool ===
--~=== 3.3.1 Get MQTT Credentials ===
++We can use PC tool to simulate UDP connection to make sure server works ok.
--~[~[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: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-20230802112413-1.png?width=1024&height=468&rev=1.1||alt="image-20230802112413-1.png"]]
--~[~[image~:image-20230802112413-6.png||height="336" width="925"]]
--~[~[image~:image-20230802112413-7.png]]
++=== 3.1.2 Configure NB-IoT Sensor ===
++==== 3.1.2.1 AT Commands ====
--~=== 3.3.2 Simulate with MQTT.fx ===
--~==== 3.3.2.1 Establish MQTT Connection ====
++(% style="color:blue" %)**AT Commands:**
++* (% style="color:#037691" %)**AT+PRO=2,0**  (%%)       ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
--After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
++* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1999**  (%%)    ~/~/  Set UDP server address and port
--~[~[image~:image-20230802112413-8.png]]
++[[image:image-20240819102802-1.png]]
--~* ~(% style="color:#037691" %)~*~*Broker Address:~*~*~(%%) mqtt3.thingspeak.com
--~* ~(% style="color:#037691" %)~*~*Broker Port:~*~*~(%%) 1883
++==== 3.1.2.2 Uplink Example ====
--~* ~(% style="color:#037691" %)~*~*Client ID:~*~*~(%%) <Your ThingSpeak MQTT ClientID>
--~* ~(% style="color:#037691" %)~*~*User Name:~*~*~(%%) <Your ThingSpeak MQTT User Name>
++[[image:image-20240819105418-8.png||height="611" width="1287"]]
--~* ~(% style="color:#037691" %)~*~*Password:~*~*~(%%) <Your ThingSpeak MQTT Password>
--~==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
++== 3.2 General COAP Connection ==
--~[~[image~:image-20230802112413-9.png]]
++The NB-IoT Sensor can send packet to server use COAP protocol.
--~[~[image~:image-20230802112413-10.png]]
++Below are the commands.
++(% style="color:blue" %)**AT Commands:**
--~(% style="color:blue" %)~*~*In MQTT.fx, we can publish below info:~*~*
++* (% style="color:#037691" %)**AT+PRO=1,0**   (%%)   ~/~/  Set to use COAP protocol to uplink, Payload Type select Hex payload.
--~* ~(% style="color:#037691" %)~*~*Topic:~*~*~(%%) channels/YOUR_CHANNEL_ID/publish
++* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%)      ~/~/  Set COAP server address and port
--~* ~(% style="color:#037691" %)~*~*Payload:~*~*~(%%) field1=63&field2=67&status=MQTTPUBLISH
++* (% 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
--Where 63 and 67 are the value to be published to field1 & field2.
++[[image:image-20240819103212-2.png]]
--~(% style="color:blue" %)~*~*Result: ~*~*
++=== 3.2.1 Uplink Example ===
--~[~[image~:image-20230802112413-11.png||height="539" width="901"]]
++[[image:image-20240819103909-4.png||height="453" width="955"]]
--~=== 3.3.3 Configure NB-IoT Sensor for connection ===
--~==== 3.3.3.1 AT Commands: ====
++== 3.2 General MQTT Connection ==
--In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
++The NB-IoT Sensor can send packet to server use MQTT protocol.
--~* ~(% style="color:blue" %)~*~*AT+PRO=3,1~*~* ~(%%)    ~~/~~/ Set to use ThingSpeak Server and Related Payload
++Below are the commands.
--~* ~(% style="color:blue" %)~*~*AT+CLIENT=<Your ThingSpeak MQTT ClientID>~*~*
++(% style="color:blue" %)**AT Commands:**
--~* ~(% style="color:blue" %)~*~*AT+UNAME=<Your ThingSpeak MQTT User Name>~*~*
++* (% style="color:#037691" %)**AT+PRO=3,0**   (%%)   ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
--~* ~(% style="color:blue" %)~*~*AT+PWD=<Your ThingSpeak MQTT Password>~*~*
++* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%)      ~/~/  Set MQTT server address and port
--~* ~(% style="color:blue" %)~*~*AT+PUBTOPIC=<YOUR_CHANNEL_ID>~*~*
++* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%)                            ~/~/  Set up the CLIENT of MQTT
--~* ~(% style="color:blue" %)~*~*AT+SUBTOPIC=<YOUR_CHANNEL_ID>~*~*
++* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%)                      ~/~/  Set the username of MQTT
--~==== 3.3.3.2 Uplink Examples ====
++* (% style="color:#037691" %)**AT+PWD=PWD**             (%%)                           ~/~/  Set the password of MQTT
++* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%)                  ~/~/  Set the sending topic of MQTT
--~[~[image~:image-20230816201942-1.png]]
++* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%)                  ~/~/  Set the subscription topic of MQTT
--For SE01-NB
++[[image:image-20240819105003-7.png||height="613" width="458"]]
--For DDS20-NB
--For DDS45-NB
++[[image:image-20240819104942-6.png||height="702" width="974"]]
--For DDS75-NB
++(% 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.**
--For NMDS120-NB
--For SPH01-NB
++== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
--For NLM01-NB
++=== 3.3.1 Get MQTT Credentials ===
--For NMDS200-NB
--For CPN01-NB
++[[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.
--For DS03A-NB
++[[image:image-20240819173602-1.png||height="401" width="743"]]
--For SN50V3-NB
++[[image:image-20240819173706-3.png||height="595" width="597"]]
--~==== 3.3.3.3 Map fields to sensor value ====
++=== 3.3.2 Simulate with MQTT.fx ===
++==== 3.3.2.1 Establish MQTT Connection ====
--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.
++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-12.png||height="504" width="1011"]]
++[[image:image-20240819173826-4.png||height="534" width="734"]]
--~[~[image~:image-20230802112413-13.png||height="331" width="978"]]
++* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
++* (% style="color:#037691" %)**Broker Port:**(%%) 1883
--Below is the NB-IoT Product Table show the mapping.
++* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
--~(% 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" %)
++* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
--~== 3.4 ~[~[Datacake>>https:~/~/datacake.co/]] ==
++* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
--~(% class="wikigeneratedid" %)
--Dragino NB-IoT sensors has its template in ~*~*~[~[Datacake>>https:~/~/datacake.co/]]~*~* Platform. There are two version for NB Sensor,
++==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
--~(% 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.
++[[image:image-20240819174033-5.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.
++[[image:image-20240819174209-6.png]]
--~=== 3.4.1 For device Already has template ===
++(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
--~==== 3.4.1.1 Create Device ====
++* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
--~(% style="color:blue" %)~*~*Add Device~*~*~(%%) in DataCake.
++* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
--~[~[image~:image-20230808162301-1.png||height="453" width="952"]]
++Where 63 and 67 are the value to be published to field1 & field2.
++(% style="color:blue" %)**Result: **
--~[~[image~:image-20230808162342-2.png||height="541" width="952"]]
++[[image:image-20240819174314-7.png||height="469" width="785"]]
--~(% style="color:blue" %)~*~*Choose the correct model~*~*~(%%) from template.
++=== 3.3.3 Configure NB-IoT Sensor for connection ===
--~[~[image~:image-20230808162421-3.png]]
++==== 3.3.3.1 AT Commands: ====
--~(% 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.
++In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
--~[~[image~:image-20230808163612-7.png||height="549" width="952"]]
++* (% style="color:blue" %)**AT+PRO=3,1** (%%)    ~/~/ Set to use ThingSpeak Server and Related Payload
--~[~[image~:image-20230808163035-5.png]]
++* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
--~[~[image~:image-20230808163049-6.png||height="544" width="926"]]
++* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
++* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
--~=== 3.4.2 For Device already registered in DataCake before shipped ===
++* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
--~==== 3.4.2.1 Scan QR Code to get the device info ====
++* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
--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"]]
++==== 3.3.3.2 Uplink Examples ====
--~[~[image~:image-20230808170548-9.png]]
++[[image:image-20240819174540-8.png]]
--~==== 3.4.2.2 Claim Device to User Account ====
++For SE01-NB
++For DDS20-NB
++For DDS45-NB
++
++For DDS75-NB
++
++For NMDS120-NB
++
++For SPH01-NB
++
++For NLM01-NB
++
++For NMDS200-NB
++
++For CPN01-NB
++
++For DS03A-NB
++
++For SN50V3-NB
++
++
++==== 3.3.3.3 Map fields to sensor value ====
++
++
++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-20240819174610-9.png]]
++
++[[image:image-20240819174618-10.png]]
++
++Below is the NB-IoT Product Table show the mapping.
++
++(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1353.82px" %)
++|(% 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:139px" %)Field4|(% style="background-color:#4f81bd; color:white; width:141px" %)Field5|(% style="background-color:#4f81bd; color:white; width:142px" %)Field6|(% style="background-color:#4f81bd; color:white; width:151px" %)Field7|(% style="background-color:#4f81bd; color:white; width:137px" %)Field8|(% style="background-color:#4f81bd; color:white; width:69px" %)Field9|(% style="background-color:#4f81bd; color:white; width:65px" %)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:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:139px" %)dielectric_constant|(% style="width:141px" %)Battery|(% style="width:142px" %)RSSI|(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% 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:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% colspan="1" rowspan="1" style="width:65px" %)
++|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% 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:139px" %)calc flag|(% style="width:141px" %)Battery|(% style="width:142px" %)RSSI|(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
++|(% 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:139px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:141px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:142px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:137px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:69px" %)Battery|(% colspan="1" rowspan="1" style="width:65px" %)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:139px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:142px" %)adc0|(% colspan="1" rowspan="1" style="width:151px" %)Temperature |(% colspan="1" rowspan="1" style="width:137px" %)Humidity|(% colspan="1" rowspan="1" style="width:69px" %) |(% colspan="1" rowspan="1" style="width:65px" %)
++|(% 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:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" style="width:142px" %)adc0|(% colspan="1" style="width:151px" %)distance|(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
++|(% 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:139px" %)adc0|(% colspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" style="width:142px" %)adc1|(% colspan="1" style="width:151px" %)Temperature|(% colspan="1" style="width:137px" %)Humidity|(% colspan="1" style="width:69px" %)adc4|(% colspan="1" style="width:65px" %)
++|(% 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:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:142px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)DS18B20 Temp2|(% colspan="1" style="width:137px" %)DS18B20 Temp3|(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
++|(% 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:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:142px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)Weight|(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
++|(% 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:139px" %)count|(% colspan="1" style="width:141px" %) |(% colspan="1" style="width:142px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
++
++== 3.4 [[Datacake>>https://datacake.co/]] ==
++
++(% 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-CB. there are two versions: **S31B-CB-1D and S31B-CB-GE.**
++
++* (% style="color:blue" %)**S31B-CB-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-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 ====
++
++
++(% style="color:blue" %)**Add Device**(%%) in DataCake.
++
++[[image:image-20240820110003-1.png]]
++
++[[image:image-20240820110017-2.png]]
++
++(% style="color:blue" %)**Choose the correct model**(%%) from template.
++
++[[image:image-20240820110031-3.png]]
++
++(% 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-20240820110048-4.png]]
++
++[[image:image-20240820110103-5.png]]
++
++[[image:image-20240820110114-6.png]]
++
++
++=== 3.4.2 For Device already registered in DataCake before shipped ===
++
++==== 3.4.2.1 Scan QR Code to get the device info ====
++
++
++Users can use their phones or computers to scan QR codes to obtain device data information.
++
++[[image:image-20240820110129-7.png]]
++
++[[image:image-20240820110218-9.png]]
++
++
++==== 3.4.2.2 Claim Device to User Account ====
++
  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) ===
++=== 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-20240820110235-10.png]][[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-20240820110247-11.png]]
--~*~*Step3: Choose to create a new device~*~*
++**Step3: Choose to create a new device**
--~[~[image~:image-20240129170539-3.png||height="459" width="646"]]
++[[image:image-20240820111016-12.png]]
--~*~*Step4: Fill in the device ID of your NB device~*~*
++**Step4: Fill in the device ID of your NB device**
--~[~[image~:image-20240202111546-1.png||height="378" width="651"]]
++[[image:image-20240820111101-13.png]]
--~*~*Step5: Please select your device plan according to your needs and complete the creation of the device~*~*
++**Step5: Please select your device plan according to your needs and complete the creation of the device**
--~[~[image~:image-20240129171236-6.png||height="450" width="648"]]
++[[image:image-20240820111113-14.png]]
--~*~*Step6: Please add the decoder at the payload decoder of the device configuration.~*~*
++**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]]
++**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]]
--~[~[image~:image-20240129172056-7.png||height="457" width="816"]]
++[[image:image-20240820111236-15.png]]
--~[~[image~:image-20240129173116-9.png||height="499" width="814"]]
++[[image:image-20240820111248-16.png]]
--~*~*Step7: Add the output of the decoder as a field~*~*
++**Step7: Add the output of the decoder as a field**
--~[~[image~:image-20240129173541-10.png||height="592" width="968"]]
++[[image:image-20240820111259-17.png]]
--~*~*Step8: Customize the dashboard and use fields as parameters of the dashboard~*~*
++**Step8: Customize the dashboard and use fields as parameters of the dashboard**
--~[~[image~:image-20240129174518-11.png||height="147" width="1042"]]
++[[image:image-20240820111312-18.png]]
--~[~[image~:image-20240129174657-12.png||height="538" width="916"]]
++[[image:image-20240820111322-19.png]]
--~[~[image~:image-20240129174840-13.png||height="536" width="750"]]
++[[image:image-20240820111333-20.png]]
--~=== 3.4.4 For device have not configured to connect to DataCake ===
++=== 3.4.4 For device have not configured to connect to DataCake ===
--~(% class="lead" %)
++(% 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 Node-Red (via MQTT) ==
--~=== 3.5.1 Configure ~[~[Node-Red>>http:~/~/wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
++=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
  Take S31-NB UDP protocol as an example.
@@ -394,411 +394,407 @@
  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-20240820111353-21.png]]
--~[~[image~:image-20230809173127-4.png]]
--
--
  Please select the NB95S31B template.
--~[~[image~:image-20230809173310-5.png||height="558" width="926"]]
++[[image:image-20240820111405-22.png]]
--~[~[image~:image-20230809173438-6.png]]
++[[image:image-20240820111418-23.png]]
--~[~[image~:image-20230809173800-7.png]]
++[[image:image-20240820111427-24.png]]
--
  Successfully imported template.
--~[~[image~:image-20230809173835-8.png||height="515" width="860"]]
++[[image:image-20240820111438-25.png]]
--
  Users can set UDP port.
--~[~[image~:image-20230809174053-9.png]]
++[[image:image-20240820111448-26.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-20240820111504-27.png]]
--~[~[image~:image-20230810084048-2.png||height="535" width="1052"]]
++[[image:image-20240820111515-28.png]]
--~=== 3.5.3 Configure NB-IoT Sensors ===
++=== 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”~*~*
++* (% 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 ThingsBoard.Cloud (via MQTT) ==
--~=== 3.6.1 Configure ThingsBoard ===
--~==== 3.6.1.1 Create Device ====
++== 3.6 ThingsBoard.Cloud (via MQTT) ==
++=== 3.6.1 Configure ThingsBoard ===
--Create a New Device in ~[~[ThingsBoard>>url:https:~/~/thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
++==== 3.6.1.1 Create Device ====
--~[~[image~:image-20230802112413-32.png||height="583" width="1066"]]
++Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
--~==== 3.6.1.2 Create Uplink & Downlink Converter ====
++[[image:image-20240820112210-29.png]]
--~(% style="color:blue" %)~*~*Uplink Converter~*~*
++==== 3.6.1.2 Create Uplink & Downlink Converter ====
--The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
--To create an uplink converter go to the ~(% style="color:blue" %)~*~*Integrations center~*~*~(%%) -> ~(% style="color:blue" %)~*~*Data converters~*~*~(%%) page and click ~(% style="color:blue" %)~*~*“plus”~*~* ~(%%)button. Name it ~(% style="color:blue" %)~*~*“MQTT Uplink Converter”~*~*~(%%) and select type ~(% style="color:blue" %)"~*~*Uplink"~*~*~(%%). Use debug mode for now.
++(% style="color:blue" %)**Uplink Converter**
--~[~[image~:image-20230802112413-33.png||height="597" width="1061"]]
++The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
++To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“MQTT Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
--~(% style="color:blue" %)~*~*Downlink Converter~*~*
++[[image:image-20240820112222-30.png]]
--The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
++(% style="color:blue" %)**Downlink Converter**
--~[~[image~:image-20230802112413-34.png||height="598" width="1063"]]
++The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
--~(% style="color:red" %)~*~*Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.~*~*
++[[image:image-20240820112236-31.png]]
++(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
--~==== 3.6.1.3 MQTT Integration Setup ====
++==== 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"]]
++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-20240820112247-32.png]]
--~* The next steps is to add the recently created uplink and downlink converters;
++* The next steps is to add the recently created uplink and downlink converters;
--~[~[image~:image-20230802112413-36.png||height="598" width="1062"]]
++[[image:image-20240820112302-33.png]]
--~[~[image~:image-20230802112413-37.png||height="598" width="1064"]]
++[[image:image-20240820112316-34.png]]
++(% style="color:blue" %)**Add a topic filter:**
--~(% 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-20240820112330-35.png]]
--~=== 3.6.2 Simulate with MQTT.fx ===
++=== 3.6.2 Simulate with MQTT.fx ===
++[[image:image-20240820112340-36.png]]
--~[~[image~:image-20230802112413-39.png]]
++[[image:image-20240820112351-37.png]]
--~[~[image~:image-20230802112413-40.png||height="525" width="980"]]
++=== 3.6.3 Configure NB-IoT Sensor ===
--~=== 3.6.3 Configure NB-IoT Sensor ===
++(% style="color:blue" %)**AT Commands**
--~(% style="color:blue" %)~*~*AT Commands~*~*
++* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)**  **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
--~* ~(% 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>**
--~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=<device name>~*~*
++* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
--~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=<device name>~*~*
++* (% style="color:#037691" %)**AT+CLIENT=<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+UNAME=<device name> or User Defined~*~*
++* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
--~* ~(% style="color:#037691" %)~*~*AT+PWD=<device name> or User Defined~*~*
++Test Uplink by click the button for 1 second
--Test Uplink by click the button for 1 second
++[[image:image-20240820112404-38.png]]
--~[~[image~:image-20230802112413-41.png||height="496" width="828"]]
++[[image:image-20240820112416-39.png]]
--~[~[image~:image-20230802112413-42.png]]
++[[image:image-20240820112426-40.png]]
--~[~[image~:image-20230802112413-43.png||height="407" width="825"]]
++== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
--~== 3.7 ~[~[Tago.io>>url:https:~/~/admin.tago.io/]] (via MQTT) ==
++=== 3.7.1 Create device & Get Credentials ===
--~=== 3.7.1 Create device & Get Credentials ===
++We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
--We use MQTT Connection to send data to ~[~[Tago.io>>url:https:~/~/admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
++[[image:image-20240820112516-41.png]]
--~[~[image~:image-20230802112413-44.png]]
++[[image:image-20240820112526-42.png]]
--~[~[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.
++[[image:image-20240820112539-43.png]]
--Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
++The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
--~[~[image~:image-20230802112413-46.png]]
++(% style="color:blue" %)**On the Connection Profile window, set the following information:**
++* (% style="color:#037691" %)**Profile Name: “Any name”**
--The device needs to enable the TLS mode and set the ~(% style="color:blue" %)~*~*AT+TLSMOD=1,0~*~*~(%%) command.
++* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
--~(% style="color:blue" %)~*~*On the Connection Profile window, set the following information:~*~*
++* (% style="color:#037691" %)**Broker Port: 8883**
--~* ~(% style="color:#037691" %)~*~*Profile Name: “Any name”~*~*
++* (% style="color:#037691" %)**Client ID: “Any value”**
--~* ~(% style="color:#037691" %)~*~*Broker Address: mqtt.tago.io~*~*
++(% style="color:blue" %)**On the section User credentials, set the following information:**
--~* ~(% style="color:#037691" %)~*~*Broker Port: 8883~*~*
++* (% style="color:#037691" %)**User Name: “Any value”** (%%)      **~/~/ Tago validates your user by the token only**
--~* ~(% style="color:#037691" %)~*~*Client ID: “Any value”~*~*
++* (% style="color:#037691" %)**Password: “Your device token”**
--~(% style="color:blue" %)~*~*On the section User credentials, set the following information:~*~*
++* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
--~* ~(% style="color:#037691" %)~*~*User Name: “Any value”~*~* ~(%%)      ~*~*~~/~~/ Tago validates your user by the token only~*~*
++* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
--~* ~(% style="color:#037691" %)~*~*Password: “Your device token”~*~*
++(% style="color:blue" %)**AT command:**
--~* ~(% style="color:#037691" %)~*~*PUBTOPIC: “Any value”~*~*
++* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%)   **~/~/ hex format or json format**
--~* ~(% style="color:#037691" %)~*~*SUBTOPIC: “Any value”~*~*
++* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
--~(% style="color:blue" %)~*~*AT command:~*~*
++* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
--~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0 or 3,5 ~*~* ~(%%)   ~*~*~~/~~/ hex format or json format~*~*
++* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
--~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=<device name>or User Defined~*~*
++* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
--~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=<device name>or User Defined~*~*
++* (% style="color:#037691" %)**AT+PWD=“Your device token”**
--~* ~(% 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.7.2 Simulate with MQTT.fx ===
--~=== 3.7.2 Simulate with MQTT.fx ===
++[[image:image-20240820112552-44.png]]
--~[~[image~:image-20230802112413-52.png]]
++[[image:image-20240820112604-45.png]]
++Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
--~[~[image~:image-20230808105300-2.png||height="553" width="1026"]]
++[[image:image-20240820112615-46.png]]
++[[image:image-20240820112626-47.png]]
--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||height="556" width="1031"]]
++=== 3.7.3 tago data ===
--~[~[image~:image-20230808105329-3.png]]
++[[image:image-20240820112637-48.png]]
--~=== 3.7.3 tago data ===
++[[image:image-20240820112647-49.png]]
--~[~[image~:image-20230802112413-50.png||height="242" width="1037"]]
++== 3.8 TCP Connection ==
--~[~[image~:image-20230802112413-51.png||height="184" width="696"]]
++(% style="color:blue" %)**AT command:**
--~== 3.8 TCP Connection ==
++* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
++* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
--~(% style="color:blue" %)~*~*AT command:~*~*
++* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 **  (%%) ~/~/ to set TCP server address and port
--~* ~(% style="color:#037691" %)~*~*AT+PRO=4,0   ~*~* ~(%%) ~~/~~/ Set to use TCP protocol to uplink(HEX format)
++(% style="color:blue" %)**Sensor Console Output when Uplink:**
--~* ~(% style="color:#037691" %)~*~*AT+PRO=4,1   ~*~* ~(%%) ~~/~~/ Set to use TCP protocol to uplink(JSON format)
++[[image:image-20240820112704-50.png]]
--~* ~(% style="color:#037691" %)~*~*AT+SERVADDR=120.24.4.116,5600 ~*~*  ~(%%) ~~/~~/ to set TCP server address and port
++(% style="color:blue" %)**See result in TCP Server:**
--~(% style="color:blue" %)~*~*Sensor Console Output when Uplink:~*~*
++[[image:image-20240820112716-51.png]]
--~[~[image~:image-20230807233631-1.png]]
++== 3.9 AWS Connection ==
--~(% style="color:blue" %)~*~*See result in TCP Server:~*~*
--~[~[image~:image-20230807233631-2.png]]
++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]]
--~== 3.9 AWS Connection ==
++= 4. COAP/UDP/MQTT/TCP downlink =
++== 4.1 MQTT (via MQTT.fx) ==
--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]]
++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):
--~= 4. MQTT/UDP/TCP downlink =
++(% style="color:blue" %)**AT command:**
--~== 4.1 MQTT (via MQTT.fx) ==
++* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 **  (%%)~/~/ hex format or json format
--Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx~/~/.~/~/
++* (% style="color:#037691" %)**AT+SUBTOPIC=User Defined**
--~*~*1.~*~* Configure node MQTT connection (via MQTT.fx):
++* (% style="color:#037691" %)**AT+PUBTOPIC=User Defined**
--~(% style="color:blue" %)~*~*AT command:~*~*
++* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
--~* ~(% style="color:#037691" %)~*~*AT+PRO=3,0 or 3,5 ~*~*  ~(%%)~~/~~/ hex format or json format
++* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
--~* ~(% style="color:#037691" %)~*~*AT+SUBTOPIC=User Defined~*~*
++* (% style="color:#037691" %)**AT+SERVADDR=8.217.91.207,1883 **  (%%) ~/~/ to set MQTT server address and port
--~* ~(% style="color:#037691" %)~*~*AT+PUBTOPIC=User Defined~*~*
++(% 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.**
--~* ~(% style="color:#037691" %)~*~*AT+UNAME=<device name> or User Defined~*~*
++[[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
--~* ~(% 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
++**2. **When the node uplink packets, we can observe the data in MQTT.fx.
--~(% 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-20240820112813-54.png]]
--~[~[image~:image-20240417180145-2.png||height="434" width="587"]]~[~[image:image-20240417180737-3.png||height="431" width="584"]]
++**3. **The downlink command can be successfully sent only when the downlink port is open.
--~*~*2. ~*~*When the node uplink packets, we can observe the data in MQTT.fx.
++    The downlink port is opened for about 3 seconds after uplink packets are sent.
--~[~[image~:image-20240418144337-1.png||height="709" width="802"]]
++    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.
--~*~*3. ~*~*The downlink command can be successfully sent only when the downlink port is open.
++[[image:image-20240820112824-55.png]]
--    The downlink port is opened for about 3 seconds after uplink packets are sent.
++[[image:image-20240820112835-56.png]]
--    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.
++(% 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.**
--~[~[image~:image-20240418150435-3.png||height="582" width="659"]]
--~[~[image~:image-20240418150932-4.png||height="492" width="1061"]]
++== 4.2 UDP (via Thingseye) ==
--~(% 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.~*~*
++(% style="color:red" %)**Note:**(%%) The UDP service on the ThingsEye platform needs to be built by the user. (Description Link:[[UDP service building instructions>>http://www.ithingsboard.com/docs/user-guide/integrations/udp/]])
++After the node is successfully connected to the platform, you need to select the corresponding node (you can refer to the node's IMEI to find it)
++[[image:image-20240820141843-2.png||height="546" width="821"]]
--~= 5. FAQ =
++After clicking Show Node Details Page, (% style="color:blue" %)**Select Properties ~-~-- select Shared Properties ~-~-- click Add Properties**
--~== 5.1 What is the usage of Multi Sampling and One Uplink? ==
++[[image:image-20240820143316-3.png||height="555" width="1170"]]
++After clicking Add Shared Attribute, set the key to (% style="color:red" %)**value**(%%), and write the command that needs to be downlinked in the Downlink Command Input box
--The NB series has the feature for Multi Sampling and one uplink. See one of them
++(% style="color:red" %)**(Note: Downlinks can only be downlinked in string format, otherwise the node will not recognize the downlink command.)**
--~[~[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]]
++[[image:image-20240820143820-4.png||height="554" width="1168"]]
--User can use this feature for below purpose:
++After the command is successfully added, the platform will send the command down on the node's next uplink.
--~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.
++[[image:image-20240820144913-6.png||height="585" width="1232"]]
--~== 5.2 Why the uplink JSON format is not standard? ==
++[[image:image-20240820145133-7.png||height="582" width="1227"]]
++Upon successful issuance, the platform automatically eliminates the attributes from the queue and waits for the next addition of new attributes
--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.
++[[image:image-20240820145309-8.png]]
--The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
--~[~[image~:image-20240229233154-1.png]]
++= 5. GPS positioning function =
++=== 1. Turn on GPS function ===
--~= 6. Trouble Shooting: =
++(% class="wikigeneratedid" %)
++AT+GPS=1 or 0  ~/~/GPS function on or off
--~== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
++=== 2.Extend the time to turn on GNSS ===
--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.
++AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
--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]]
++=== 3.Get or set GPS positioning interval in units of hour ===
++AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
--If fail to attach network, it will shows signal 99. as below:
--~[~[image~:image-20240207002129-2.png]]
++= 5. FAQ =
++== 5.1 What is the usage of Multi Sampling and One Uplink? ==
--~(% 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.
++The NB series has the feature for Multi Sampling and one uplink. See one of them
--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.
++[[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:
--~== 6.2 Issue: "NBIOT did not respond" ==
++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.
--~(% 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:
++== 5.2 Why the uplink JSON format is not standard? ==
--1) Open Enclosure
--2) Power off device by pull out the power on Jumper
++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.
--3) Power on device by connect back the power jumper.
++The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
--4) push reset button.
++[[image:image-20240820112848-57.png]]
--~[~[image~:image-20240208001740-1.png]]
++= 6. Trouble Shooting: =
--~== 6.3 Issue: "Failed to readI MSI number" ==
++== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
--~(% class="box errormessage" %)
--~(~(~(
--[18170]Failed to read IMSI:1umber.
--[20109]Failed to read IMSI numoer.
--[22048]Failed to read IMSI number.
--[29842lRestart the module...
--~)~)~)
++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.
--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"]].
++If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
++[[image:image-20240820112859-58.png]]
--~== ~(% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.4 Why sometime the AT Command is slow in reponse?~(%%) ==
++If fail to attach network, it will shows signal 99. as below:
++[[image:image-20240820112908-59.png]]
++(% 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.
++
++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.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.
--~[~[image~:image-20240226111928-1.png]]
++[[image:image-20240820113015-60.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="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: ===
++(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
++=== UDP: ===
--~(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
++(% data-sider-select-id="14a4790e-7faa-4508-a4dd-7605a53f1cb3" %)
  Its downlink command is the same as the AT command, but brackets are required.
  Example:
@@ -805,8 +805,8 @@
  {AT+TDC=300}
--~(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
--~=== MQTT: ===
++(% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
++=== MQTT: ===
  Json：
@@ -844,6 +844,138 @@
  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/]]
++
++== 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.
++
++[[image:image-20240827150705-6.png||height="489" width="687"]]
++
++If the domain name is correct, but the domain name cannot be resolved, the user can turn off the domain name resolution function(AT+GDNS=1) and use the domain name communication directly.
++
++* Set the DNS
++
++(% style="color:blue" %)**AT Command: AT+GDNS**
++
++**AT+GDNS=0**    ~/~/ Default. Automatically resolves the domain name and uses the resolved IP to communicate.
++
++**AT+GDNS=1    **~/~/ Disabling Domain name resolution. Use the domain name directly to communicate.
++
++(% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
++
++Example:
++
++[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
++
++
++== 6.5 GPS debugging ==
++
++
++Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
++
++[[image:image-20240903104250-9.png||height="275" width="614"]]
++
++
++[[image:image-20240903104431-10.png||height="291" width="621"]]
++
++
++=== 6.5.1 GPS commands ===
++
++
++The following are three related AT commands that introduce GPS functions.
++
++* **Turn on/off GPS**
++
++(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
++
++**Ex1:  **AT+GPS=0    ~/~/ Turn off GPS
++
++**Ex2:  **AT+GPS=1    ~/~/ Turn on GPS
++
++(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
++
++Format: Command Code (0x11) followed by 1 byte.
++
++Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
++
++* **Set GNSS open time**
++
++Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
++
++(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
++
++Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
++
++(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
++
++Format: Command Code (0x10) followed by 2 bytes.
++
++Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
++
++* **Set GPS positioning interval**
++
++Feature: Set GPS positioning interval (unit: hour).
++
++When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
++
++(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
++
++Example: AT+GTDC=24    ~/~/ Set the GPS positioning interval to 24h.
++
++(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
++
++Format: Command Code (0x12) followed by 3 bytes.
++
++Example: 24 hours:  24(D)=0x18(H)
++
++Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
++
++
++=== 6.5.2 GPS workflow ===
++
++
++The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
++
++~1. When activate the node, the node will turn on the GNSS, if the GPS signal is good, the node will print and upload the position information with the first data packet immediately.
++
++    If the signal is not good, it may take the whole (% style="color:#037691" %)**GNSST**(%%) time but still can not search the latitude and longitude information, at this time the node uploads the latitude and longitude all to 0.
++
++    So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
++
++2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
++
++   The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
++
++   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.
++
++
++=== 6.5.3 GPS debugging methods ===
++
++
++In summary, we can deduce the methods of debugging GPS:
++
++* **Check whether the GPS function is enabled.**
++
++[[image:image-20240903102327-5.png||height="271" width="529"]]
++
++* **Check whether the GPS antenna is loose**.
++
++If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
++
++[[image:image-20240903094214-1.png||height="340" width="461"]]
++
++* **Use the AT+GNSST command to extend the positioning time.**
++
++The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
++
++If the location fails, users can extend the location time.
++
++[[image:image-20240903102641-8.png||height="303" width="600"]]
++
++
++
++

image-20240602220856-1.png

Author

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

Size

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

Content

image-20240819102802-1.png

Author

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

Size

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

Content

image-20240819103212-2.png

Author

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

Size

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

Content

image-20240819103826-3.png

Author

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

Size

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

Content

image-20240819103909-4.png

Author

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

Size

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

Content

image-20240819104904-5.png

Author

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

Size

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

Content

image-20240819104942-6.png

Author

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

Size

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

Content

image-20240819105003-7.png

Author

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

Size

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

Content

image-20240819105418-8.png

Author

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

Size

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

Content

image-20240819112109-1.png

Author

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

Size

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

Content

image-20240819173602-1.png

Author

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

Size

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

Content

image-20240819173659-2.png

Author

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

Size

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

Content

image-20240819173706-3.png

Author

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

Size

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

Content

image-20240819173826-4.png

Author

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

Size

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

Content

image-20240819174033-5.png

Author

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

Size

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

Content

image-20240819174209-6.png

Author

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

Size

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

Content

image-20240819174314-7.png

Author

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

Size

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

Content

image-20240819174540-8.png

Author

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

Size

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

Content

image-20240819174610-9.png

Author

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

Size

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

Content

image-20240819174618-10.png

Author

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

Size

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

Content

image-20240820110003-1.png

Author

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

Size

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

Content

image-20240820110017-2.png

Author

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

Size

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

Content

image-20240820110031-3.png

Author

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

Size

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

Content

image-20240820110048-4.png

Author

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

Size

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

Content

image-20240820110103-5.png

Author

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

Size

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

Content

image-20240820110114-6.png

Author

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

Size

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

Content

image-20240820110129-7.png

Author

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

Size

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

Content

image-20240820110142-8.png

Author

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

Size

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

Content

image-20240820110218-9.png

Author

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

Size

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

Content

image-20240820110235-10.png

Author

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

Size

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

Content

image-20240820110247-11.png

Author

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

Size

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

Content

image-20240820111016-12.png

Author

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

Size

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

Content

image-20240820111101-13.png

Author

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

Size

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

Content

image-20240820111113-14.png

Author

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

Size

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

Content

image-20240820111236-15.png

Author

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

Size

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

Content

image-20240820111248-16.png

Author

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

Size

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

Content

image-20240820111259-17.png

Author

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

Size

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

Content

image-20240820111312-18.png

Author

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

Size

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

Content

image-20240820111322-19.png

Author

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

Size

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

Content

image-20240820111333-20.png

Author

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

Size

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

Content

image-20240820111353-21.png

Author

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

Size

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

Content

image-20240820111405-22.png

Author

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

Size

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

Content

image-20240820111418-23.png

Author

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

Size

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

Content

image-20240820111427-24.png

Author

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

Size

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

Content

image-20240820111438-25.png

Author

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

Size

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

Content

image-20240820111448-26.png

Author

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

Size

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

Content

image-20240820111504-27.png

Author

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

Size

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

Content

image-20240820111515-28.png

Author

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

Size

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

Content

image-20240820112210-29.png

Author

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

Size

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

Content

image-20240820112222-30.png

Author

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

Size

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

Content

image-20240820112236-31.png

Author

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

Size

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

Content

image-20240820112247-32.png

Author

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

Size

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

Content

image-20240820112302-33.png

Author

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

Size

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

Content

image-20240820112316-34.png

Author

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

Size

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

Content

image-20240820112330-35.png

Author

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

Size

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

Content

image-20240820112340-36.png

Author

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

Size

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

Content

image-20240820112351-37.png

Author

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

Size

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

Content

image-20240820112404-38.png

Author

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

Size

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

Content

image-20240820112416-39.png

Author

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

Size

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

Content

image-20240820112426-40.png

Author

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

Size

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

Content

image-20240820112516-41.png

Author

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

Size

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

Content

image-20240820112526-42.png

Author

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

Size

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

Content

image-20240820112539-43.png

Author

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

Size

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

Content

image-20240820112552-44.png

Author

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

Size

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

Content

image-20240820112604-45.png

Author

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

Size

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

Content

image-20240820112615-46.png

Author

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

Size

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

Content

image-20240820112626-47.png

Author

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

Size

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

Content

image-20240820112637-48.png

Author

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

Size

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

Content

image-20240820112647-49.png

Author

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

Size

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

Content

image-20240820112704-50.png

Author

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

Size

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

Content

image-20240820112716-51.png

Author

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

Size

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

Content

image-20240820112732-52.png

Author

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

Size

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

Content

image-20240820112758-53.png

Author

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

Size

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

Content

image-20240820112813-54.png

Author

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

Size

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

Content

image-20240820112824-55.png

Author

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

Size

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

Content

image-20240820112835-56.png

Author

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

Size

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

Content

image-20240820112848-57.png

Author

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

Size

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

Content

image-20240820112859-58.png

Author

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

Size

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

Content

image-20240820112908-59.png

Author

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

Size

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

Content

image-20240820113015-60.png

Author

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

Size

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

Content

image-20240820140935-1.png

Author

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

Size

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

Content

image-20240820141136-2.png

Author

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

Size

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

Content

image-20240820141746-1.png

Author

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

Size

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

Content

image-20240820141843-2.png

Author

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

Size

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

Content

image-20240820143316-3.png

Author

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

Size

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

Content

image-20240820143820-4.png

Author

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

Size

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

Content

image-20240820144823-5.png

Author

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

Size

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

Content

image-20240820144913-6.png

Author

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

Size

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

Content

image-20240820145133-7.png

Author

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

Size

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

Content

image-20240820145309-8.png

Author

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

Size

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

Content

image-20240827145055-4.png

Author

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

Size

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

Content

image-20240827150121-5.png

Author

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

Size

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

Content

image-20240827150705-6.png

Author

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

Size

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

Content

image-20240903094214-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+4.5 MB

Content

image-20240903094457-2.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+2.6 MB

Content

image-20240903100736-3.png

Author

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

Size

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

Content

image-20240903100832-4.png

Author

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

Size

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

Content

image-20240903102327-5.png

Author

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

Size

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

Content

image-20240903102542-6.png

Author

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

Size

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

Content

image-20240903102621-7.png

Author

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

Size

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

Content

image-20240903102641-8.png

Author

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

Size

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

Content

image-20240903104250-9.png

Author

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

Size

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

Content

image-20240903104431-10.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation