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

From version 105.1
edited by Edwin Chen
on 2023/11/05 08:49
Change comment: There is no comment for this version
To version 53.2
edited by Xiaoling
on 2023/08/02 11:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,13 +11,3 @@
1 -(% class="wikigeneratedid" id="HTableofContents:" %)
2 -**Table of Contents:**
3 -
4 -{{toc/}}
5 -
6 -
7 -
8 -
9 -
10 -
11 11  = 1. The use of this guideline =
12 12  
13 13  
... ... @@ -14,196 +14,143 @@
14 14  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.
15 15  
16 16  
17 -= 2. Attach Network =
7 += 2. Network Connection =
18 18  
19 -== 2.1 General Configure to attach network ==
20 20  
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 -
32 32  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.
33 33  
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]]**
38 38  
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" %)
13 +== 2.1 1NCE SIM Card. ==
43 43  
44 44  
45 -== 2.2 Speed Up Network Attach time ==
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| | |
46 46  
47 47  
48 -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.
49 -
50 -(% style="color:#037691" %)**AT+QBAND?       ** (%%) ~/~/ Check what is the current used frequency band
51 -
52 -(% style="color:#037691" %)**AT+QBAND=1,4    ** (%%) ~/~/ Set to use 1 frequency band. Band4
53 -
54 -(% style="color:#037691" %)**AT+QBAND=2,8,20**  (%%) ~/~/ Set to use 2 frequency bands. Band 8 and Band 20
55 -
56 -
57 -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/]]**
58 -
59 -
60 60  = 3. Configure to connect to different servers =
61 61  
62 -== 3.1 General UDP Connection ==
63 63  
25 += NB-IoT 服务器对接例子 =
64 64  
27 += 1. General UDP Connection =
28 +
65 65  The NB-IoT Sensor can send packet to server use UDP protocol.
66 66  
31 +== 1.1 Simulate UDP Connection by PC tool ==
67 67  
68 -=== 3.1.1 Simulate UDP Connection by PC tool ===
69 -
70 -
71 71  We can use PC tool to simulate UDP connection to make sure server works ok.
72 72  
73 73  [[image:image-20230802112413-1.png]]
74 74  
37 +== 1.2 Configure NB-IoT Sensor ==
75 75  
76 -=== 3.1.2 Configure NB-IoT Sensor ===
39 +=== 1.2.1 AT Commands ===
77 77  
78 -==== 3.1.2.1 AT Commands ====
41 +AT Commands:
79 79  
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
80 80  
81 -(% style="color:blue" %)**AT Commands:**
82 -
83 -* (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/  Set to use UDP protocol to uplink ,Payload Type select Hex payload
84 -
85 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601**  (%%) ~/~/  Set UDP server address and port
86 -
87 -* (% style="color:#037691" %)**AT+CFM=1**    (%%) ~/~/  If the server does not respond, this command is unnecessary
88 -
89 89  [[image:image-20230802112413-2.png]]
90 90  
49 +=== 1.2.2 Uplink Example ===
91 91  
92 -==== 3.1.2.2 Uplink Example ====
93 93  
94 -
95 95  [[image:image-20230802112413-3.png]]
96 96  
97 97  
98 -== 3.2 General MQTT Connection ==
55 += 2General MQTT Connection =
99 99  
100 -
101 101  The NB-IoT Sensor can send packet to server use MQTT protocol.
102 102  
103 -Below are the commands.
59 +Below are the commands
104 104  
105 -(% style="color:blue" %)**AT Commands:**
61 +AT Commands:
106 106  
107 -* (% style="color:#037691" %)**AT+PRO=3,0**   (%%) ~/~/  Set to use MQTT protocol to uplink, Payload Type select Hex payload.
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
108 108  
109 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883**  (%%) ~/~/  Set MQTT server address and port
110 -
111 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT**     (%%) ~/~/  Set up the CLIENT of MQTT
112 -
113 -* (% style="color:#037691" %)**AT+UNAME=UNAME**        (%%) ~/~/  Set the username of MQTT
114 -
115 -* (% style="color:#037691" %)**AT+PWD=PWD**             (%%) ~/~/  Set the password of MQTT
116 -
117 -* (% style="color:#037691" %)**AT+PUBTOPIC=NSE01_PUB**  (%%) ~/~/  Set the sending topic of MQTT
118 -
119 -* (% style="color:#037691" %)**AT+SUBTOPIC=NSE01_SUB**  (%%) ~/~/  Set the subscription topic of MQTT
120 -
121 121  [[image:image-20230802112413-4.png]]
122 122  
123 -[[image:image-20230802112413-5.png||height="530" width="987"]]
73 +[[image:image-20230802112413-5.png]]
124 124  
125 -(% 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.**
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.
126 126  
127 127  
128 -== 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
129 129  
130 -=== 3.3.1 Get MQTT Credentials ===
79 += 3. [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) =
131 131  
81 +== 1.1 Get MQTT Credentials ==
132 132  
133 133  [[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.
134 134  
135 -[[image:image-20230802112413-6.png||height="336" width="925"]]
85 +[[image:image-20230802112413-6.png]]
136 136  
137 137  [[image:image-20230802112413-7.png]]
138 138  
139 139  
140 -=== 3.3.2 Simulate with MQTT.fx ===
90 +== 1.2Simulate with MQTT.fx ==
141 141  
142 -==== 3.3.2.1 Establish MQTT Connection ====
92 +=== 1.2.1 Establish MQTT Connection ===
143 143  
144 -
145 145  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
146 146  
147 147  [[image:image-20230802112413-8.png]]
148 148  
149 -* (% style="color:#037691" %)**Broker Address:**(%%) mqtt3.thingspeak.com
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>
150 150  
151 -* (% style="color:#037691" %)**Broker Port:**(%%) 1883
152 152  
153 -* (% style="color:#037691" %)**Client ID:**(%%) <Your ThingSpeak MQTT ClientID>
105 +=== 1.2.2 Publish Data to ThingSpeak Channel ===
154 154  
155 -* (% style="color:#037691" %)**User Name:**(%%) <Your ThingSpeak MQTT User Name>
156 -
157 -* (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
158 -
159 -
160 -==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
161 -
162 -
163 163  [[image:image-20230802112413-9.png]]
164 164  
165 165  [[image:image-20230802112413-10.png]]
166 166  
111 +In MQTT.fx, we can publish below info:
167 167  
168 -(% style="color:blue" %)**In MQTT.fx, we can publish below info:**
113 +* Topic: channels/YOUR_CHANNEL_ID/publish
114 +* Payload: field1=63&field2=67&status=MQTTPUBLISH
169 169  
170 -* (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
171 171  
172 -* (% style="color:#037691" %)**Payload:**(%%) field1=63&field2=67&status=MQTTPUBLISH
173 -
174 174  Where 63 and 67 are the value to be published to field1 & field2.
175 175  
176 176  
177 -(% style="color:blue" %)**Result: **
120 +Result:
178 178  
179 -[[image:image-20230802112413-11.png||height="539" width="901"]]
122 +[[image:image-20230802112413-11.png]]
180 180  
181 181  
182 -=== 3.3.3 Configure NB-IoT Sensor for connection ===
125 +== 1.3 Configure NB-IoT Sensor for connection ==
183 183  
184 -==== 3.3.3.1 AT Commands: ====
127 +=== 1.3.1 AT Commands: ===
185 185  
186 -
187 187  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
188 188  
189 -* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
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 190  
191 -* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
192 192  
193 -* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
194 194  
195 -* (% style="color:blue" %)**AT+PWD=<Your ThingSpeaMQTT Password>**
140 +=== 1.3.2 Uplink Examples ===
196 196  
197 -* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
142 +For S31-NB
198 198  
199 -* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
200 -
201 -
202 -==== 3.3.3.2 Uplink Examples ====
203 -
204 -
205 -[[image:image-20230816201942-1.png]]
206 -
207 207  For SE01-NB
208 208  
209 209  For DDS20-NB
... ... @@ -227,340 +227,405 @@
227 227  For SN50V3-NB
228 228  
229 229  
230 -==== 3.3.3.3 Map fields to sensor value ====
167 +=== 1.3.Map fields to sensor value ===
231 231  
232 -
233 233  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.
234 234  
235 235  
236 -[[image:image-20230802112413-12.png||height="504" width="1011"]]
172 +[[image:image-20230802112413-12.png]]
237 237  
238 -[[image:image-20230802112413-13.png||height="331" width="978"]]
174 +[[image:image-20230802112413-13.png]]
239 239  
240 240  
241 241  Below is the NB-IoT Product Table show the mapping.
242 242  
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" %)
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
262 262  
182 +
183 +)))|(% colspan="1" rowspan="1" %)(((
184 +Field10
263 263  
264 -== 3.4 [[Datacake>>https://datacake.co/]] ==
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
265 265  
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 266  
267 -(% class="wikigeneratedid" %)
268 -Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
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
269 269  
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 270  
271 -(% class="wikigeneratedid" %)
272 -As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
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 273  
274 -* (% 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.
220 +
221 +)))|(% colspan="1" rowspan="1" %)(((
222 +exit_state/input PA4
275 275  
276 -* (% 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.
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 277  
229 +
230 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
231 +exit_state/input PA4
278 278  
279 -=== 3.4.1 Create device ===
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
280 280  
238 +
239 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
240 +DS18B20 Temp
281 281  
282 -(% style="color:blue" %)**Add Device**(%%) in DataCake.
242 +
243 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
244 +exit_state/input PA4
283 283  
284 -[[image:image-20230808162301-1.png||height="473" width="994"]]
246 +
247 +)))|(% colspan="1" rowspan="1" %)(((
248 +DS18B20 Temp2
285 285  
250 +
251 +)))|(% colspan="1" rowspan="1" %)(((
252 +DS18B20 Temp3
286 286  
287 -[[image:image-20230808162342-2.png]]
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
288 288  
259 +
260 +)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
261 +DS18B20 Temp
289 289  
290 -(% style="color:blue" %)**Choose the correct model**(%%) from template.
263 +
264 +)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
265 +exit_state/input PA4
291 291  
292 -[[image:image-20230808162421-3.png]]
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
293 293  
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" %)
294 294  
295 -(% 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.
296 296  
297 -[[image:image-20230808163612-7.png]]
276 += 4. Datacake =
298 298  
299 -[[image:image-20230808163035-5.png]]
278 +== 1.1 Define Product ==
300 300  
301 -[[image:image-20230808163049-6.png]]
280 +Firstly, we need to set the MQTT mode to datacake, and 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.
302 302  
303 303  
304 -=== 3.4.2 Scan QR code to obtain data ===
283 +By chosing to add the device under a "New Product" you are required to give a name fothis product. You can name it something like "My First MQTT Product".
305 305  
285 +[[image:image-20230802112413-14.png]]
306 306  
307 -Users can use their phones or computers to scan QR codes to obtain device data information.
287 +== 1.2 Create Device ==
308 308  
309 -[[image:image-20230808170051-8.png||height="255" width="259"]]
289 +In the second step you have to define the device which should be added to the product.
310 310  
311 -[[image:image-20230808170548-9.png]]
291 +[[image:image-20230802112413-15.png]]
312 312  
293 +Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button.
313 313  
314 -=== 3.4.2 AT command for connecting to DataCake ===
315 315  
296 +== 1.3 Create Database Fields ==
316 316  
317 -(% style="color:blue" %)**AT+PRO=2,0**
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.
318 318  
319 -(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
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".
320 320  
302 +[[image:image-20230802112413-16.png]]
321 321  
322 -== 3.5 Node-Red (via MQTT) ==
304 +[[image:image-20230802112413-17.png]]
323 323  
324 -=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
306 +To create a first database fieldplease click on the "Add Field" button as marked in the screenshot above.
325 325  
308 +This will open another modal asking for some required input for your first field.
326 326  
327 -Take S31-NB UDP protocol as an example.
310 +[[image:image-20230802112413-18.png]]
328 328  
329 -Dragino provides input flow examples for the sensors.
312 +[[image:image-20230802112413-19.png]]
330 330  
331 -User can download the required JSON file through Dragino Node-RED input flow template.
314 +== 1.4 Set up Broker ==
332 332  
333 -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]]
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.
334 334  
335 -We can directly import the template.
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.
336 336  
337 -The templates for S31-NB and NB95S31B are the same.
320 +View your Personal Access Token
338 338  
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:
339 339  
340 -[[image:image-20230809173127-4.png]]
324 +[[image:image-20230802112413-20.png]]
341 341  
326 +MQTT Client-ID
342 342  
343 -Please select the NB95S31B template.
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.
344 344  
345 -[[image:image-20230809173310-5.png]]
330 +AT+CLIENT=“Any value
346 346  
347 -[[image:image-20230809173438-6.png]]
332 +AT+UNAME=Token
348 348  
349 -[[image:image-20230809173800-7.png]]
334 +AT+PWD=Token
350 350  
336 +[[image:image-20230802112413-21.png]]
351 351  
352 -Successfully imported template.
353 353  
354 -[[image:image-20230809173835-8.png]]
339 +== 1.6 Create your first Subscription ==
355 355  
341 +Subscribe
356 356  
357 -Users can set UDP port.
343 +Data is published accordinto the following structure:
358 358  
359 -[[image:image-20230809174053-9.png]]
345 +dtck~/~//
360 360  
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.
361 361  
362 -=== 3.5.2 Simulate Connection ===
363 363  
350 +[[image:image-20230802112413-22.png]]
364 364  
365 -We have completed the configuration of UDP. We can try sending packets to node red.
366 366  
367 -[[image:image-20230810083934-1.png]]
353 +[[image:image-20230802112413-23.png]]
368 368  
369 -[[image:image-20230810084048-2.png]]
370 370  
371 -=== 3.5.3 Configure NB-IoT Sensors ===
356 +[[image:image-20230802112413-24.png]]
372 372  
373 373  
374 -* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
359 +example:
375 375  
376 -* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
361 +AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
377 377  
363 +[[image:image-20230802112413-25.png]]
378 378  
379 -== 3.6 ThingsBoard.Cloud (via MQTT) ==
365 +== 1.7 Define Publish Topic ==
380 380  
381 -=== 3.6.1 Configure ThingsBoard ===
367 +Publish
382 382  
383 -==== 3.6.1.1 Create Device ====
369 +To upload data into the Datacake Cloud and into a specific device, you publish the data to threspective topic structure.
384 384  
371 +Due to the nature of MQTT, the topic prefix differs as follows:
385 385  
386 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
373 +dtck-pub~/~//
387 387  
388 -[[image:image-20230802112413-32.png]]
375 +example:
389 389  
377 +AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
390 390  
391 -==== 3.6.1.2 Create Uplink & Downlink Converter ====
379 +== 1.8 upload data ==
392 392  
381 +[[image:image-20230802112413-26.png]]
393 393  
394 -(% style="color:blue" %)**Uplink Converter**
383 +[[image:image-20230802112413-27.png]]
395 395  
396 -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.
385 +[[image:image-20230802112413-28.png]]
397 397  
398 -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.
387 += =
399 399  
400 -[[image:image-20230802112413-33.png||height="732" width="1302"]]
389 += 5. Node-Red (via MQTT) =
401 401  
402 402  
403 -(% style="color:blue" %)**Downlink Converter**
392 +== 1.1 Configure Node-Red ==
404 404  
405 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
394 +[[image:image-20230802112413-29.png]]
406 406  
407 -[[image:image-20230802112413-34.png||height="734" width="1305"]]
396 +[[image:image-20230802112413-30.png]]
408 408  
409 -(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
398 +== 1.2 Simulate Connection ==
410 410  
400 +[[image:image-20230802112413-31.png]]
411 411  
412 -==== 3.6.1.3 MQTT Integration Setup ====
402 +== 1.3 Configure NB-IoT Sensors ==
413 413  
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
414 414  
415 -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**;
416 416  
417 -[[image:image-20230802112413-35.png||height="738" width="1312"]]
412 += 6. ThingsBoard.Cloud (via MQTT) =
418 418  
414 +== 1.1 Configure ThingsBoard ==
419 419  
420 -* The next steps is to add the recently created uplink and downlink converters;
416 +=== 1.1.1 Create Device ===
421 421  
422 -[[image:image-20230802112413-36.png||height="736" width="1308"]]
418 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
423 423  
424 -[[image:image-20230802112413-37.png||height="735" width="1307"]]
420 +[[image:image-20230802112413-32.png]]
425 425  
422 +=== 1.1.2 Create Uplink & Downlink Converter ===
426 426  
427 -(% style="color:blue" %)**Add a topic filter:**
424 +Uplink Converter
428 428  
429 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
426 +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 telemetrare optional. Attributes and telemetry arflat key-value objects. Nested objects are not supported.
430 430  
431 -You can also select an MQTT QoS level. We use MQTT QoS level 0 (Amosonce) by default;
428 +To create an uplink converter go to the Integrations center -> Data converters pagand click “plus” button. Namit “MQTT Uplink Converter” and select type Uplink. Usdebug mode for now.
432 432  
433 -[[image:image-20230802112413-38.png||height="731" width="1300"]]
430 +[[image:image-20230802112413-33.png]]
434 434  
435 435  
436 -=== 3.6.2 Simulate with MQTT.fx ===
433 +Downlink Converter
437 437  
435 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
438 438  
439 -[[image:image-20230802112413-39.png]]
437 +[[image:image-20230802112413-34.png]]
440 440  
441 -[[image:image-20230802112413-40.png]]
439 +Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
442 442  
441 +=== 1.1.3 MQTT Integration Setup ===
443 443  
444 -=== 3.6.3 Configure NB-IoT Sensor ===
443 +Go to the Integrations center -Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
445 445  
445 +[[image:image-20230802112413-35.png]]
446 446  
447 -(% style="color:blue" %)**AT Commands**
447 +* The next steps is to add the recently created uplink and downlink converters;
448 448  
449 -* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
449 +[[image:image-20230802112413-36.png]]
450 450  
451 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
451 +[[image:image-20230802112413-37.png]]
452 452  
453 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
453 +Add a topic filter:
454 454  
455 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
456 456  
457 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
456 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
458 458  
459 -* (% style="color:#037691" %)**AT+PWD=<devicname> or User Defined**
458 +You can also select an MQTT Qolevel. We use MQTT QoS level 0 (At most once) by default;
460 460  
461 -Test Uplink by click the button for 1 second
460 +[[image:image-20230802112413-38.png]]
462 462  
463 -[[image:image-20230802112413-41.png]]
462 +== 1.2 Simulate with MQTT.fx ==
464 464  
465 -[[image:image-20230802112413-42.png]]
464 +[[image:image-20230802112413-39.png]]
466 466  
467 -[[image:image-20230802112413-43.png]]
466 +[[image:image-20230802112413-40.png]]
468 468  
468 +== 1.3 Configure NB-IoT Sensor ==
469 469  
470 -== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
470 +AT Commands
471 471  
472 -=== 3.7.1 Create device & GeCredentials ===
472 +AT+PRO=3,3  ~/~/ UsMQTT to connect to ThingsBoard.
473 473  
474 +AT+SUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
474 474  
475 -We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. Wneed to Create Device and Get MQTT Credentials first.
476 +AT+PUBTOPIC=device nam~-~-> 只需要 Device Nam吗?对的
476 476  
477 -[[image:image-20230802112413-44.png]]
478 478  
479 -[[image:image-20230802112413-45.png]]
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”
481 481  
482 -Go to the Device section and create a device. Then, go to the section tokens and copyour device-token.
483 +User Name:“Any value
483 483  
484 -[[image:image-20230802112413-46.png]]
485 +Password:“Any value
485 485  
486 486  
487 -The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
488 +Test Uplinby click the button for 1 second
488 488  
489 -(% style="color:blue" %)**On the Connection Profile window, set the following information:**
490 +[[image:image-20230802112413-41.png]]
490 490  
491 -* (% style="color:#037691" %)**Profile Name: “Any name”**
492 +[[image:image-20230802112413-42.png]]
492 492  
493 -* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
494 +[[image:image-20230802112413-43.png]]
494 494  
495 -* (% style="color:#037691" %)**Broker Port: 8883**
496 496  
497 -* (% style="color:#037691" %)**Client ID: “Any value”**
497 += 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) =
498 498  
499 -(% style="color:blue" %)**On thsection User credentials, set the following information:**
499 +== 5.1 Create device & Get Credentials ==
500 500  
501 -* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
501 +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.
502 502  
503 -* (% style="color:#037691" %)**Password: “Your device token”**
503 +[[image:image-20230802112413-44.png]]
504 504  
505 -* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
505 +[[image:image-20230802112413-45.png]]
506 506  
507 -* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
507 += =
508 508  
509 -(% style="color:blue" %)**AT command:**
509 +Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
510 510  
511 -* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
511 +[[image:image-20230802112413-46.png]]
512 512  
513 -* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
514 514  
515 -* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
514 +On the ConnectioProfilwindow, set the following information: (这边加一个截图)
516 516  
517 -* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
516 +* Profile Name: “Any name”
517 +* Broker Address: mqtt.tago.io
518 +* Broker Port: 1883
519 +* Client ID: “Any value”
518 518  
519 -* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
520 520  
521 -* (% style="color:#037691" %)**AT+PWD=“Your device token”**
522 +On the section User credentials, set the following information:(这边加一个截图)
522 522  
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”
523 523  
524 -=== 3.7.2 Simulate with MQTT.fx ===
525 525  
530 +== 5.2 Simulate with MQTT.fx ==
526 526  
527 -[[image:image-20230802112413-52.png]]
532 +[[image:image-20230802112413-47.png]]
528 528  
534 +[[image:image-20230802112413-48.png]]
529 529  
530 -[[image:image-20230808105300-2.png]]
536 +Users can run the AT+PRO=3,5 command, and the payload will be converted to JSON format.
531 531  
538 +[[image:image-20230802112413-49.png]]
532 532  
533 -Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
540 +== 1.4. tago data ==
534 534  
535 -[[image:image-20230808105217-1.png]]
536 536  
537 -[[image:image-20230808105329-3.png]]
538 -
539 -
540 -=== 3.7.3 tago data ===
541 -
542 -
543 543  [[image:image-20230802112413-50.png]]
544 544  
545 -[[image:image-20230802112413-51.png||height="184" width="696"]]
545 +[[image:image-20230802112413-51.png]]
546 546  
547 +== 1.4. TLS mode ==
547 547  
548 -== 3.8 TCP Connection ==
549 +Users can choose to use SSL/TLS mode.
549 549  
551 +On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
550 550  
551 -(% style="color:blue" %)**AT command:**
553 +The device needs to enable the TLS mode and set the AT+TLSMOD=1,0 command.
552 552  
553 -* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
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”
554 554  
555 -* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
556 556  
557 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
565 +[[image:image-20230802112413-52.png]]
558 558  
559 -(% style="color:blue" %)**Sensor Console Output when Uplink:**
560 560  
561 -[[image:image-20230807233631-1.png]]
562 -
563 -
564 -(% style="color:blue" %)**See result in TCP Server:**
565 -
566 -[[image:image-20230807233631-2.png]]
568 +
image-20230807233631-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -21.9 KB
Content
image-20230807233631-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -9.6 KB
Content
image-20230808105217-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -68.5 KB
Content
image-20230808105300-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -70.1 KB
Content
image-20230808105329-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -21.1 KB
Content
image-20230808162301-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -76.9 KB
Content
image-20230808162342-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -63.8 KB
Content
image-20230808162421-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -59.2 KB
Content
image-20230808162727-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -54.2 KB
Content
image-20230808163035-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -71.6 KB
Content
image-20230808163049-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -61.5 KB
Content
image-20230808163612-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -53.4 KB
Content
image-20230808170051-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -21.5 KB
Content
image-20230808170548-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -54.1 KB
Content
image-20230808205045-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -373.9 KB
Content
image-20230809165928-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -74.4 KB
Content
image-20230809170225-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20230809170532-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -38.7 KB
Content
image-20230809173127-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -82.5 KB
Content
image-20230809173310-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -51.9 KB
Content
image-20230809173438-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -41.0 KB
Content
image-20230809173800-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -46.8 KB
Content
image-20230809173835-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -88.8 KB
Content
image-20230809174053-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -58.0 KB
Content
image-20230809180523-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -91.9 KB
Content
image-20230810083934-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20230810084048-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -63.7 KB
Content
image-20230816201942-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -99.8 KB
Content