Last modified by Kilight Cao on 2025/07/23 16:27

From version 53.2
edited by Xiaoling
on 2023/08/02 11:35
Change comment: There is no comment for this version
To version 115.1
edited by Bei Jinggeng
on 2024/01/29 17:12
Change comment: Uploaded new attachment "image-20240129171236-6.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,3 +1,13 @@
1 +(% class="wikigeneratedid" id="HTableofContents:" %)
2 +**Table of Contents:**
3 +
4 +{{toc/}}
5 +
6 +
7 +
8 +
9 +
10 +
1 1  = 1. The use of this guideline =
2 2  
3 3  
... ... @@ -4,143 +4,196 @@
4 4  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.
5 5  
6 6  
7 -= 2. Network Connection =
17 += 2. Attach Network =
8 8  
19 +== 2.1 General Configure to attach network ==
9 9  
21 +
22 +To attache NB-IoT sensors to NB-IoT Network, You need to:
23 +
24 +1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
25 +1. Insert the SIM card to Sensor
26 +1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
27 +
28 +[[image:image-20230808205045-1.png||height="293" width="438"]]
29 +
30 +After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
31 +
10 10  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.
11 11  
34 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
35 +|(% 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**
36 +|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
37 +**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
12 12  
13 -== 2.1 1NCE SIM Card. ==
39 +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, US Virgin Islands
40 +)))|(% style="width:135px" %)
41 +|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
42 +|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
14 14  
44 +== 2.2 Speed Up Network Attach time ==
15 15  
16 -(% border="1" cellspacing="4" style="width:510px;background-color:#F2F2F2" %)
17 -|(% style="background-color:#4F81BD;color:white" %)SIM Provider|(% style="background-color:#4F81BD;color:white" %)APN|(% style="background-color:#4F81BD;color:white" %)NB-IoT Coverage|(% style="background-color:#4F81BD;color:white" %)Comments
18 -|1NCE| | |
19 -|China Mobile| | |
20 20  
47 +BC660K-GL supports multi bands (% style="color:blue" %)**B1/B2/B3/B4/B5/B8/B12/B13/B14/B17/B18/B19/B20/B25/B28/B66/B70/B85. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail. User can lock the band to specify band for its operator to make this faster.
21 21  
22 -= 3. Configure to connect to different servers =
49 +(% style="color:#037691" %)**AT+QBAND?       **(%%) ~/~/ Check what is the current used frequency band
23 23  
51 +(% style="color:#037691" %)**AT+QBAND=1,4    **(%%) ~/~/ Set to use 1 frequency band. Band4
24 24  
25 -= NB-IoT 服务器对接例子 =
53 +(% style="color:#037691" %)**AT+QBAND=2,8,20 **(%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
26 26  
27 -= 1. General UDP Connection =
28 28  
56 +After connection is successful, user can use (% style="color:#037691" %)**AT+QENG=0 **(%%) to check which band is actually in used.
57 +
58 +
59 +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/]]**
60 +
61 +
62 += 3. Configure to connect to different servers =
63 +
64 +== 3.1 General UDP Connection ==
65 +
66 +
29 29  The NB-IoT Sensor can send packet to server use UDP protocol.
30 30  
31 -== 1.1 Simulate UDP Connection by PC tool ==
32 32  
70 +=== 3.1.1 Simulate UDP Connection by PC tool ===
71 +
72 +
33 33  We can use PC tool to simulate UDP connection to make sure server works ok.
34 34  
35 -[[image:image-20230802112413-1.png]]
75 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
36 36  
37 -== 1.2 Configure NB-IoT Sensor ==
38 38  
39 -=== 1.2.1 AT Commands ===
78 +=== 3.1.2 Configure NB-IoT Sensor ===
40 40  
41 -AT Commands:
80 +==== 3.1.2.1 AT Commands ====
42 42  
43 -* AT+PRO=2,0 ~/~/  Set to use UDP protocol to uplink  ,  Payload Type select Hex payload
44 -* AT+SERVADDR=120.24.4.116,5601    ~/~/  Set UDP server address and port
45 -* AT+CFM=1        ~/~/  If the server does not respond, this command is unnecessary
46 46  
83 +(% style="color:blue" %)**AT Commands:**
84 +
85 +* (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
86 +
87 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
88 +
89 +* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
90 +
47 47  [[image:image-20230802112413-2.png]]
48 48  
49 -=== 1.2.2 Uplink Example ===
50 50  
94 +==== 3.1.2.2 Uplink Example ====
51 51  
96 +
52 52  [[image:image-20230802112413-3.png]]
53 53  
54 54  
55 -= 2. General MQTT Connection =
100 +== 3.2 General MQTT Connection ==
56 56  
102 +
57 57  The NB-IoT Sensor can send packet to server use MQTT protocol.
58 58  
59 -Below are the commands
105 +Below are the commands.
60 60  
61 -AT Commands:
107 +(% style="color:blue" %)**AT Commands:**
62 62  
63 -* AT+PRO=3,0 ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
64 -* AT+SERVADDR=120.24.4.116,1883    ~/~/  Set MQTT server address and port
65 -* AT+CLIENT=CLIENT        ~/~/  Set up the CLIENT of MQTT
66 -* AT+UNAME=UNAME                      ~/~/  Set the username of MQTT
67 -* AT+PWD=PWD                          ~/~/  Set the password of MQTT
68 -* AT+PUBTOPIC=NSE01_PUB               ~/~/  Set the sending topic of MQTT
69 -* AT+SUBTOPIC=NSE01_SUB           ~/~/  Set the subscription topic of MQTT
109 +* (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
70 70  
111 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
112 +
113 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
114 +
115 +* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
116 +
117 +* (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
118 +
119 +* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
120 +
121 +* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/  Set the subscription topic of MQTT
122 +
71 71  [[image:image-20230802112413-4.png]]
72 72  
73 -[[image:image-20230802112413-5.png]]
125 +[[image:image-20230802112413-5.png||height="530" width="987"]]
74 74  
75 -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.
127 +(% 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.**
76 76  
77 77  
130 +== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
78 78  
79 -= 3. [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) =
132 +=== 3.3.1 Get MQTT Credentials ===
80 80  
81 -== 1.1 Get MQTT Credentials ==
82 82  
83 83  [[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.
84 84  
85 -[[image:image-20230802112413-6.png]]
137 +[[image:image-20230802112413-6.png||height="336" width="925"]]
86 86  
87 87  [[image:image-20230802112413-7.png]]
88 88  
89 89  
90 -== 1.2. Simulate with MQTT.fx ==
142 +=== 3.3.2 Simulate with MQTT.fx ===
91 91  
92 -=== 1.2.1 Establish MQTT Connection ===
144 +==== 3.3.2.1 Establish MQTT Connection ====
93 93  
146 +
94 94  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
95 95  
96 96  [[image:image-20230802112413-8.png]]
97 97  
98 -* Broker Address: mqtt3.thingspeak.com
99 -* Broker Port: 1883
100 -* Client ID: <Your ThingSpeak MQTT ClientID>
101 -* User Name: <Your ThingSpeak MQTT User Name>
102 -* Password: <Your ThingSpeak MQTT Password>
151 +* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
103 103  
153 +* (% style="color:#037691" %)**Broker Port:**(%%) 1883
104 104  
105 -=== 1.2.2 Publish Data to ThingSpeak Channel ===
155 +* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
106 106  
157 +* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
158 +
159 +* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
160 +
161 +==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
162 +
163 +
107 107  [[image:image-20230802112413-9.png]]
108 108  
109 109  [[image:image-20230802112413-10.png]]
110 110  
111 -In MQTT.fx, we can publish below info:
112 112  
113 -* Topic: channels/YOUR_CHANNEL_ID/publish
114 -* Payload: field1=63&field2=67&status=MQTTPUBLISH
169 +(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
115 115  
171 +* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
116 116  
173 +* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
174 +
117 117  Where 63 and 67 are the value to be published to field1 & field2.
118 118  
119 119  
120 -Result:
178 +(% style="color:blue" %)**Result: **
121 121  
122 -[[image:image-20230802112413-11.png]]
180 +[[image:image-20230802112413-11.png||height="539" width="901"]]
123 123  
124 124  
125 -== 1.3 Configure NB-IoT Sensor for connection ==
183 +=== 3.3.3 Configure NB-IoT Sensor for connection ===
126 126  
127 -=== 1.3.1 AT Commands: ===
185 +==== 3.3.3.1 AT Commands: ====
128 128  
187 +
129 129  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
130 130  
131 -* AT+PRO=3,1   ~/~/Set to use ThingSpeak Server and Related Payload
132 -* AT+CLIENT=<Your ThingSpeak MQTT ClientID>
133 -* AT+UNAME=<Your ThingSpeak MQTT User Name>
134 -* AT+PWD=<Your ThingSpeak MQTT Password>
135 -* AT+PUBTOPIC=<YOUR_CHANNEL_ID>
136 -* AT+SUBTOPIC=<YOUR_CHANNEL_ID>
190 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
137 137  
192 +* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
138 138  
194 +* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
139 139  
140 -=== 1.3.2 Uplink Examples ===
196 +* (% style="color:blue" %)**AT+PWD=<Your ThingSpeaMQTT Password>**
141 141  
142 -For S31-NB
198 +* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
143 143  
200 +* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
201 +
202 +==== 3.3.3.2 Uplink Examples ====
203 +
204 +
205 +[[image:image-20230816201942-1.png]]
206 +
144 144  For SE01-NB
145 145  
146 146  For DDS20-NB
... ... @@ -164,405 +164,347 @@
164 164  For SN50V3-NB
165 165  
166 166  
167 -=== 1.3.Map fields to sensor value ===
230 +==== 3.3.3.3 Map fields to sensor value ====
168 168  
232 +
169 169  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.
170 170  
171 171  
172 -[[image:image-20230802112413-12.png]]
236 +[[image:image-20230802112413-12.png||height="504" width="1011"]]
173 173  
174 -[[image:image-20230802112413-13.png]]
238 +[[image:image-20230802112413-13.png||height="331" width="978"]]
175 175  
176 176  
177 177  Below is the NB-IoT Product Table show the mapping.
178 178  
179 -|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)Field1|(% colspan="1" rowspan="1" %)Field2|(% colspan="1" rowspan="1" %)Field3|(% colspan="1" rowspan="1" %)Field4|(% colspan="1" rowspan="1" %)Field5|(% colspan="1" rowspan="1" %)Field6|(% colspan="1" rowspan="1" %)Field7|(% colspan="1" rowspan="1" %)Field8|(% colspan="1" rowspan="1" %)(((
180 -Field9
243 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
244 +|(% 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
245 +|(% 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" %)
246 +|(% 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" %)
247 +|(% 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" %)
248 +|(% 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" %)
249 +|(% 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" %)
250 +|(% 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" %)
251 +|(% 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" %)
252 +|(% 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" %)
253 +|(% 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" %)
254 +|(% 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" %)
255 +|(% 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
256 +|(% 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" %)
257 +|(% 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" %)
258 +|(% 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" %)
259 +|(% 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" %)
260 +|(% 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" %)
261 +|(% 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" %)
181 181  
182 -
183 -)))|(% colspan="1" rowspan="1" %)(((
184 -Field10
263 +== 3.4 [[Datacake>>https://datacake.co/]] ==
185 185  
186 -
187 -)))
188 -|(% colspan="1" rowspan="1" %)S31x-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
189 -|(% colspan="1" rowspan="1" %)SE01-NB|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)conduct|(% colspan="1" rowspan="1" %)dielectric_constant|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
190 -|(% colspan="1" rowspan="1" %)DDS20-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
191 -Battery
192 192  
193 -
194 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
195 -|(% colspan="1" rowspan="1" %)DDS45-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
196 -Battery
266 +(% class="wikigeneratedid" %)
267 +Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
197 197  
198 -
199 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
200 -|(% colspan="1" rowspan="1" %)DDS75-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
201 -Battery
202 202  
203 -
204 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
205 -|(% colspan="1" rowspan="1" %)NMDS120-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
206 -Battery
270 +(% class="wikigeneratedid" %)
271 +As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
207 207  
208 -
209 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
210 -|(% colspan="1" rowspan="1" %)SPH01-NB|(% colspan="1" rowspan="1" %)ph|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
211 -|(% colspan="1" rowspan="1" %)NLM01-NB|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
212 -|(% colspan="1" rowspan="1" %)NMDS200-NB|(% colspan="1" rowspan="1" %)distance1|(% colspan="1" rowspan="1" %)distance2|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
213 -|(% colspan="1" rowspan="1" %)CPN01-NB|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %)door open duration|(% colspan="1" rowspan="1" %)calc flag|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
214 -|(% colspan="1" rowspan="1" %)DS03A-NB|(% colspan="1" rowspan="1" %)level|(% colspan="1" rowspan="1" %)alarm|(% colspan="1" rowspan="1" %)pb14door open num|(% colspan="1" rowspan="1" %)pb14 last open time|(% colspan="1" rowspan="1" %)pb15 level status|(% colspan="1" rowspan="1" %)pb15 alarm status|(% colspan="1" rowspan="1" %)pb15 door open num|(% colspan="1" rowspan="1" %)pb15 last open time|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI
215 -|(% colspan="1" rowspan="1" %)SN50V3-NB|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
216 -|(% colspan="1" rowspan="1" %)mod1|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)DS18B20 Temp|(% colspan="1" rowspan="1" %)exit_state/input PA4|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)Temperature |(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
217 -|(% colspan="1" rowspan="1" %)mod2|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
218 -DS18B20 Temp
273 +* (% 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.
219 219  
220 -
221 -)))|(% colspan="1" rowspan="1" %)(((
222 -exit_state/input PA4
275 +* (% 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.
223 223  
224 -
225 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
226 -|(% colspan="1" rowspan="1" %)mod3|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
227 -Battery
277 +=== 3.4.1 For device Already has template ===
228 228  
229 -
230 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
231 -exit_state/input PA4
279 +==== 3.4.1.1 Create Device ====
232 232  
233 -
234 -)))|(% colspan="1" rowspan="1" %)adc1|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)adc4|(% colspan="1" rowspan="1" %)
235 -|(% colspan="1" rowspan="1" %)mod4|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
236 -Battery
281 +(% style="color:blue" %)**Add Device**(%%) in DataCake.
237 237  
238 -
239 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
240 -DS18B20 Temp
283 +[[image:image-20230808162301-1.png||height="453" width="952"]]
241 241  
242 -
243 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
244 -exit_state/input PA4
245 245  
246 -
247 -)))|(% colspan="1" rowspan="1" %)(((
248 -DS18B20 Temp2
286 +[[image:image-20230808162342-2.png||height="541" width="952"]]
249 249  
250 -
251 -)))|(% colspan="1" rowspan="1" %)(((
252 -DS18B20 Temp3
253 253  
254 -
255 -)))|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
256 -|(% colspan="1" rowspan="1" %)mod5|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
257 -Battery
289 +(% style="color:blue" %)**Choose the correct model**(%%) from template.
258 258  
259 -
260 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
261 -DS18B20 Temp
291 +[[image:image-20230808162421-3.png]]
262 262  
263 -
264 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
265 -exit_state/input PA4
266 266  
267 -
268 -)))|(% colspan="1" rowspan="1" %)Weight|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
269 -|(% colspan="1" rowspan="1" %)mod6|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
270 -Battery
294 +(% 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.
271 271  
272 -
273 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)count|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
296 +[[image:image-20230808163612-7.png||height="549" width="952"]]
274 274  
298 +[[image:image-20230808163035-5.png]]
275 275  
276 -= 4. Datacake =
300 +[[image:image-20230808163049-6.png||height="544" width="926"]]
277 277  
278 -== 1.1 Define Product ==
279 279  
280 -Firstly, we need to set the MQTT mode to datacakeand we need to run AT+PRO=3,2. This command is set to datacake. After running the command, the device automatically sets the server address, port.
303 +=== 3.4.2 For Device already registered in DataCake before shipped ===
281 281  
305 +**Scan QR Code to get the device info.**
282 282  
283 -By chosing to add the device under a "New Product" you are required to give a name for this product. Yocan name it something like "My First MQTT Product".
307 +Users can use their phones or computers to scan QR codes to obtain device data information.
284 284  
285 -[[image:image-20230802112413-14.png]]
309 +[[image:image-20230808170051-8.png||height="255" width="259"]]
286 286  
287 -== 1.2 Create Device ==
311 +[[image:image-20230808170548-9.png]]
288 288  
289 -In the second step you have to define the device which should be added to the product.
290 290  
291 -[[image:image-20230802112413-15.png]]
314 +=== 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
292 292  
293 -Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button.
294 294  
317 +=== 3.4.4 For device have not configured to connect to DataCake ===
295 295  
296 -== 1.3 Create Database Fields ==
319 +(% class="lead" %)
320 +Use AT command for connecting to DataCake
297 297  
298 -After creating the device, it is listed in the table of the fleet view. Now open the device by clicking on the entry in the list.
322 +(% style="color:blue" %)**AT+PRO=2,0**
299 299  
300 -You will then see a device view with an empty dashboard. Now, the first thing we want to do is navigate to the Device configuration. To do this, use the tab bar and click on "Configuration".
324 +(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
301 301  
302 -[[image:image-20230802112413-16.png]]
303 303  
304 -[[image:image-20230802112413-17.png]]
327 +== 3.5 Node-Red (via MQTT) ==
305 305  
306 -To create a first database fieldplease click on the "Add Field" button amarked in the screenshot above.
329 +=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
307 307  
308 -This will open another modal asking for some required input for your first field.
309 309  
310 -[[image:image-20230802112413-18.png]]
332 +Take S31-NB UDP protocol as an example.
311 311  
312 -[[image:image-20230802112413-19.png]]
334 +Dragino provides input flow examples for the sensors.
313 313  
314 -== 1.4 Set up Broker ==
336 +User can download the required JSON file through Dragino Node-RED input flow template.
315 315  
316 -The brokeis running on mqtt.datacake.co on ports 1883 and 8883. Port 1883 is unsecured and should not be used in production environments. Port 8883 uses a CA signed server certificate.
338 +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]]
317 317  
318 -You will need an access token to log into the Datacake MQTT Broker. You can use your own personal token or create a token explicitly for individual devices or groups of devices.
340 +We can directly import the template.
319 319  
320 -View your Personal Access Token
342 +The templates for S31-NB and NB95S31B are the same.
321 321  
322 -You can view your own token via the User-Settings-Menu. You can reach this menu by clicking on "Edit Profile" at the end of the list using the Workspace Selector:
323 323  
324 -[[image:image-20230802112413-20.png]]
345 +[[image:image-20230809173127-4.png]]
325 325  
326 -MQTT Client-ID
327 327  
328 -The Datacake Broker manages the client IDs internally. You do not need to worry about a client ID. If your client optionally supports the specification of a client ID, please leave this specification blank. Your client then creates a randomly generated ID.
348 +Please select the NB95S31B template.
329 329  
330 -AT+CLIENT=“Any value
350 +[[image:image-20230809173310-5.png||height="558" width="926"]]
331 331  
332 -AT+UNAME=Token
352 +[[image:image-20230809173438-6.png]]
333 333  
334 -AT+PWD=Token
354 +[[image:image-20230809173800-7.png]]
335 335  
336 -[[image:image-20230802112413-21.png]]
337 337  
357 +Successfully imported template.
338 338  
339 -== 1.6 Create your first Subscription ==
359 +[[image:image-20230809173835-8.png||height="515" width="860"]]
340 340  
341 -Subscribe
342 342  
343 -Data is published according to the following structure:
362 +Users can set UDP port.
344 344  
345 -dtck~/~//
364 +[[image:image-20230809174053-9.png]]
346 346  
347 -Subscribe to topics using this structure to receive messages via MQTT when readings (via API or MQTT) arrive in the Datacake Cloud. Messages are published whenever there is a change to a corresponding database field.
348 348  
367 +=== 3.5.2 Simulate Connection ===
349 349  
350 -[[image:image-20230802112413-22.png]]
351 351  
370 +We have completed the configuration of UDP. We can try sending packets to node red.
352 352  
353 -[[image:image-20230802112413-23.png]]
372 +[[image:image-20230810083934-1.png]]
354 354  
374 +[[image:image-20230810084048-2.png||height="535" width="1052"]]
355 355  
356 -[[image:image-20230802112413-24.png]]
357 357  
377 +=== 3.5.3 Configure NB-IoT Sensors ===
358 358  
359 -example:
360 360  
361 -AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
380 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
381 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
382 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
383 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
384 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
385 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
362 362  
363 -[[image:image-20230802112413-25.png]]
387 +== 3.6 ThingsBoard.Cloud (via MQTT) ==
364 364  
365 -== 1.7 DefinPublish Topic ==
389 +=== 3.6.1 ConfigurThingsBoard ===
366 366  
367 -Publish
391 +==== 3.6.1.1 Create Device ====
368 368  
369 -To upload data into the Datacake Cloud and into a specific device, you publish the data to the respective topic structure.
370 370  
371 -Due to thnaturof MQTT, the topic prefix differs as follows:
394 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
372 372  
373 -dtck-pub~/~//
396 +[[image:image-20230802112413-32.png||height="583" width="1066"]]
374 374  
375 -example:
376 376  
377 -AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
399 +==== 3.6.1.2 Create Uplink & Downlink Converter ====
378 378  
379 -== 1.8 upload data ==
380 380  
381 -[[image:image-20230802112413-26.png]]
402 +(% style="color:blue" %)**Uplink Converter**
382 382  
383 -[[image:image-20230802112413-27.png]]
404 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceNamand deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
384 384  
385 -[[image:image-20230802112413-28.png]]
406 +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.
386 386  
387 -= =
408 +[[image:image-20230802112413-33.png||height="597" width="1061"]]
388 388  
389 -= 5. Node-Red (via MQTT) =
390 390  
411 +(% style="color:blue" %)**Downlink Converter**
391 391  
392 -== 1.1 ConfigurNode-Red ==
413 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
393 393  
394 -[[image:image-20230802112413-29.png]]
415 +[[image:image-20230802112413-34.png||height="598" width="1063"]]
395 395  
396 -[[image:image-20230802112413-30.png]]
417 +(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
397 397  
398 -== 1.2 Simulate Connection ==
399 399  
400 -[[image:image-20230802112413-31.png]]
420 +==== 3.6.1.3 MQTT Integration Setup ====
401 401  
402 -== 1.3 Configure NB-IoT Sensors ==
403 403  
404 -* AT+PRO=3,0(hex format) or 3,5(json format)    ~/~/Set to mqtt Server and  Payload
405 -* AT+CLIENT=any value
406 -* AT+UNAME=any value
407 -* AT+PWD=any value
408 -* AT+PUBTOPIC=any value
409 -* AT+SUBTOPIC=any value
423 +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**;
410 410  
425 +[[image:image-20230802112413-35.png||height="597" width="1062"]]
411 411  
412 -= 6. ThingsBoard.Cloud (via MQTT) =
413 413  
414 -== 1.1 ConfigurThingsBoard ==
428 +* The next steps is to add the recently created uplink and downlink converters;
415 415  
416 -=== 1.1.1 Create Device ===
430 +[[image:image-20230802112413-36.png||height="598" width="1062"]]
417 417  
418 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
432 +[[image:image-20230802112413-37.png||height="598" width="1064"]]
419 419  
420 -[[image:image-20230802112413-32.png]]
421 421  
422 -=== 1.1.2 Create Uplink & Downlink Converter ===
435 +(% style="color:blue" %)**Add a topic filter:**
423 423  
424 -Uplink Converter
437 +Consistent with the theme of the node setting.
425 425  
426 -The purpose of the decoder function is tparse 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 flakey-value objects. Nested objects arnot supported.
439 +You caalso select an MQTT QoS level. We use MQTT QoS level 0 (Amost once) by default;
427 427  
428 -To create an uplink converter go to the Integrations center -> Data converters page and click “plus” button. Name it “MQTT Uplink Converter” and select type Uplink. Use debug mode for now.
441 +[[image:image-20230802112413-38.png||height="598" width="1064"]]
429 429  
430 -[[image:image-20230802112413-33.png]]
431 431  
444 +=== 3.6.2 Simulate with MQTT.fx ===
432 432  
433 -Downlink Converter
434 434  
435 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
447 +[[image:image-20230802112413-39.png]]
436 436  
437 -[[image:image-20230802112413-34.png]]
449 +[[image:image-20230802112413-40.png||height="525" width="980"]]
438 438  
439 -Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
440 440  
441 -=== 1.1.3 MQTT Integration Setup ===
452 +=== 3.6.3 Configure NB-IoT Sensor ===
442 442  
443 -Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
444 444  
445 -[[image:image-20230802112413-35.png]]
455 +(% style="color:blue" %)**AT Commands**
446 446  
447 -* Thnext steps is to add the recently created uplinand downlink converters;
457 +* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
448 448  
449 -[[image:image-20230802112413-36.png]]
459 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
450 450  
451 -[[image:image-20230802112413-37.png]]
461 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
452 452  
453 -Add a topic filter:
463 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
454 454  
465 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
455 455  
456 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
467 +* (% style="color:#037691" %)**AT+PWD=<device name> or User Defined**
457 457  
458 -You can also selecaMQTT QoS level. We use MQTT QoS level 0 (At mosonce) by default;
469 +TesUplink by click thbutton for 1 second
459 459  
460 -[[image:image-20230802112413-38.png]]
471 +[[image:image-20230802112413-41.png||height="496" width="828"]]
461 461  
462 -== 1.2 Simulate with MQTT.fx ==
473 +[[image:image-20230802112413-42.png]]
463 463  
464 -[[image:image-20230802112413-39.png]]
475 +[[image:image-20230802112413-43.png||height="407" width="825"]]
465 465  
466 -[[image:image-20230802112413-40.png]]
467 467  
468 -== 1.3 Configure NB-IoT Sensor ==
478 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
469 469  
470 -AT Commands
480 +=== 3.7.1 Create device & Get Credentials ===
471 471  
472 -AT+PRO=3,3  ~/~/ Use MQTT to connect to ThingsBoard.
473 473  
474 -AT+SUBTOPIC=device name ~-~-> 只需要 Device Nam吗?对的
483 +We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. Wneed to Create Device and Get MQTT Credentials first.
475 475  
476 -AT+PUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
485 +[[image:image-20230802112413-44.png]]
477 477  
487 +[[image:image-20230802112413-45.png]]
478 478  
479 -Users do not need to fill in the client, username, and password. But the configuration information of the device requires setting the client, username, and password, which can be entered freely. (软件自动填充为 Device Name 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)
480 480  
481 -CLIENT :“Any value
490 +Go to the Device sectioand create a device. Then, go to the section tokens and copy your device-token.
482 482  
483 -User Name:“Any value
492 +[[image:image-20230802112413-46.png]]
484 484  
485 -Password:“Any value”
486 486  
495 +The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
487 487  
488 -Test Uplink by click the button for 1 second
497 +(% style="color:blue" %)**Othe Connection Profile window, set the following information:**
489 489  
490 -[[image:image-20230802112413-41.png]]
499 +* (% style="color:#037691" %)**Profile Name: “Any name”**
491 491  
492 -[[image:image-20230802112413-42.png]]
501 +* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
493 493  
494 -[[image:image-20230802112413-43.png]]
503 +* (% style="color:#037691" %)**Broker Port: 8883**
495 495  
505 +* (% style="color:#037691" %)**Client ID: “Any value”**
496 496  
497 -= 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) =
507 +(% style="color:blue" %)**On the section User credentials, set the following information:**
498 498  
499 -== 5.1 Creatdevic& Get Credentials ==
509 +* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
500 500  
501 -We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We neeto Create Device and Get MQTT Credentials first.
511 +* (% style="color:#037691" %)**Password: “Youdevice token”**
502 502  
503 -[[image:image-20230802112413-44.png]]
513 +* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
504 504  
505 -[[image:image-20230802112413-45.png]]
515 +* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
506 506  
507 -= =
517 +(% style="color:blue" %)**AT command:**
508 508  
509 -Go to the Device section and create a device. Thengo to the sectiotokens and copy your device-token.
519 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
510 510  
511 -[[image:image-20230802112413-46.png]]
521 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
512 512  
523 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
513 513  
514 -On the Connection Profilwindow, set the following information: (这边加一个截图)
525 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
515 515  
516 -* Profile Name: “Any name”
517 -* Broker Address: mqtt.tago.io
518 -* Broker Port: 1883
519 -* Client ID: “Any value”
527 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
520 520  
529 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
521 521  
522 -On the section User credentials, set thfollowing information:(这边加一个截图)
531 +=== 3.7.2 Simulate with MQTT.fx ===
523 523  
524 -* User Name: “Any value” Tago validates your user by the token only
525 -* Password: “Your device token”
526 -* PUBTOPIC: “Any value”
527 -* SUBTOPIC: “Any value”
528 528  
534 +[[image:image-20230802112413-52.png]]
529 529  
530 -== 5.2 Simulate with MQTT.fx ==
531 531  
532 -[[image:image-20230802112413-47.png]]
537 +[[image:image-20230808105300-2.png||height="553" width="1026"]]
533 533  
534 -[[image:image-20230802112413-48.png]]
535 535  
536 -Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
540 +Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
537 537  
538 -[[image:image-20230802112413-49.png]]
542 +[[image:image-20230808105217-1.png||height="556" width="1031"]]
539 539  
540 -== 1.4. tago data ==
544 +[[image:image-20230808105329-3.png]]
541 541  
542 542  
543 -[[image:image-20230802112413-50.png]]
547 +=== 3.7.3 tago data ===
544 544  
545 -[[image:image-20230802112413-51.png]]
546 546  
547 -== 1.4. TLS mode ==
550 +[[image:image-20230802112413-50.png||height="242" width="1037"]]
548 548  
549 -Users can choose to use SSL/TLS mode.
552 +[[image:image-20230802112413-51.png||height="184" width="696"]]
550 550  
551 -On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
552 552  
553 -The device needs to enable the TLS mode and set the AT+TLSMOD=1,0 command.
555 +== 3.8 TCP Connection ==
554 554  
555 -* Profile Name: “Any name”
556 -* Broker Address: mqtt.tago.io
557 -* Broker Port: 8883
558 -* Client ID: “Any value”
559 -* User Name: “Any value” Tago validates your user by the token only
560 -* Password: “Your device token”
561 -* PUBTOPIC: “Any value”
562 -* SUBTOPIC: “Any value”
563 563  
558 +(% style="color:blue" %)**AT command:**
564 564  
565 -[[image:image-20230802112413-52.png]]
560 +* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
566 566  
562 +* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
567 567  
568 -
564 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
565 +
566 +(% style="color:blue" %)**Sensor Console Output when Uplink:**
567 +
568 +[[image:image-20230807233631-1.png]]
569 +
570 +
571 +(% style="color:blue" %)**See result in TCP Server:**
572 +
573 +[[image:image-20230807233631-2.png]]
image-20230807233631-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +21.9 KB
Content
image-20230807233631-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +9.6 KB
Content
image-20230808105217-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +68.5 KB
Content
image-20230808105300-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +70.1 KB
Content
image-20230808105329-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +21.1 KB
Content
image-20230808162301-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +76.9 KB
Content
image-20230808162342-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +63.8 KB
Content
image-20230808162421-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +59.2 KB
Content
image-20230808162727-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +54.2 KB
Content
image-20230808163035-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +71.6 KB
Content
image-20230808163049-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +61.5 KB
Content
image-20230808163612-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +53.4 KB
Content
image-20230808170051-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +21.5 KB
Content
image-20230808170548-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +54.1 KB
Content
image-20230808205045-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +373.9 KB
Content
image-20230809165928-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +74.4 KB
Content
image-20230809170225-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20230809170532-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +38.7 KB
Content
image-20230809173127-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +82.5 KB
Content
image-20230809173310-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +51.9 KB
Content
image-20230809173438-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +41.0 KB
Content
image-20230809173800-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +46.8 KB
Content
image-20230809173835-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +88.8 KB
Content
image-20230809174053-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.0 KB
Content
image-20230809180523-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +63.7 KB
Content
image-20230816201942-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +99.8 KB
Content
image-20240129170024-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +52.3 KB
Content
image-20240129170216-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +56.0 KB
Content
image-20240129170539-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +55.0 KB
Content
image-20240129171029-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +36.1 KB
Content
image-20240129171113-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +47.2 KB
Content
image-20240129171236-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +49.8 KB
Content