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

From version 53.10
edited by Xiaoling
on 2023/08/02 12:04
Change comment: There is no comment for this version
To version 103.1
edited by Edwin Chen
on 2023/10/02 18:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,4 +1,4 @@
1 -(% class="wikigeneratedid" %)
1 +(% class="wikigeneratedid" id="HTableofContents:" %)
2 2  **Table of Contents:**
3 3  
4 4  {{toc/}}
... ... @@ -5,6 +5,9 @@
5 5  
6 6  
7 7  
8 +
9 +
10 +
8 8  = 1. The use of this guideline =
9 9  
10 10  
... ... @@ -11,20 +11,38 @@
11 11  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.
12 12  
13 13  
14 -= 2. Network Connection =
17 += 2. Attach Network =
15 15  
19 +== 2.1 General Configure to attach network ==
16 16  
21 +To attache NB-IoT sensors to NB-IoT Network, You need to:
22 +
23 +1. Get a NB-IoT SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
24 +1. Insert the SIM card to Sensor
25 +1. [[Configure APN>>http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20configure%20APN%20in%20the%20node/]] in the sensor (AT+APN=<APN>)
26 +
27 +[[image:image-20230808205045-1.png||height="293" width="438"]]
28 +
29 +After doing above, the NB-IoT Sensors should be able to attach to NB-IoT network .
30 +
17 17  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.
18 18  
19 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
20 -|(% 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**
21 -|1NCE| | |
22 -|China Mobile| | |
33 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:878px" %)
34 +|(% 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**
35 +|(% style="width:117px" %)**[[1NCE>>https://1nce.com]]**|(% style="width:151px" %)iot.1nce.net|(% style="width:474px" %)(((
36 +**[[Coverage Reference Link>>https://1nce.com/en-ap/1nce-connect]]**
23 23  
24 -== 2.1 1NCE SIM Card. ==
38 +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
39 +)))|(% style="width:135px" %)
40 +|(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:474px" %)China Mainland, HongKong|(% style="width:135px" %)
41 +|(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:474px" %)China Mainland|(% style="width:135px" %)
25 25  
43 +== 2.2 Speed Up Network Attach time ==
26 26  
45 +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.
27 27  
47 +
48 +
28 28  = 3. Configure to connect to different servers =
29 29  
30 30  == 3.1 General UDP Connection ==
... ... @@ -88,7 +88,7 @@
88 88  
89 89  [[image:image-20230802112413-4.png]]
90 90  
91 -[[image:image-20230802112413-5.png]]
112 +[[image:image-20230802112413-5.png||height="530" width="987"]]
92 92  
93 93  (% 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.**
94 94  
... ... @@ -100,14 +100,14 @@
100 100  
101 101  [[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.
102 102  
103 -[[image:image-20230802112413-6.png]]
124 +[[image:image-20230802112413-6.png||height="336" width="925"]]
104 104  
105 105  [[image:image-20230802112413-7.png]]
106 106  
107 107  
108 -== 3.3.2 Simulate with MQTT.fx ==
129 +=== 3.3.2 Simulate with MQTT.fx ===
109 109  
110 -=== 3.3.2.1 Establish MQTT Connection ===
131 +==== 3.3.2.1 Establish MQTT Connection ====
111 111  
112 112  
113 113  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
... ... @@ -125,13 +125,14 @@
125 125  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
126 126  
127 127  
149 +==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
128 128  
129 -=== 3.3.2.2 Publish Data to ThingSpeak Channel ===
130 130  
131 131  [[image:image-20230802112413-9.png]]
132 132  
133 133  [[image:image-20230802112413-10.png]]
134 134  
156 +
135 135  (% style="color:blue" %)**In MQTT.fx, we can publish below info:**
136 136  
137 137  * (% style="color:#037691" %)**Topic:**(%%) channels/YOUR_CHANNEL_ID/publish
... ... @@ -143,35 +143,33 @@
143 143  
144 144  (% style="color:blue" %)**Result: **
145 145  
146 -[[image:image-20230802112413-11.png]]
168 +[[image:image-20230802112413-11.png||height="539" width="901"]]
147 147  
148 148  
149 -== 3.3 Configure NB-IoT Sensor for connection ==
171 +=== 3.3.3 Configure NB-IoT Sensor for connection ===
150 150  
151 -=== 3.3.1 AT Commands: ===
173 +==== 3.3.3.1 AT Commands: ====
152 152  
153 153  
154 154  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
155 155  
156 -* **AT+PRO=3,1**   ~/~/ Set to use ThingSpeak Server and Related Payload
178 +* (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
157 157  
158 -* **AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
180 +* (% style="color:blue" %)**AT+CLIENT=<Your ThingSpeak MQTT ClientID>**
159 159  
160 -* **AT+UNAME=<Your ThingSpeak MQTT User Name>**
182 +* (% style="color:blue" %)**AT+UNAME=<Your ThingSpeak MQTT User Name>**
161 161  
162 -* **AT+PWD=<Your ThingSpeak MQTT Password>**
184 +* (% style="color:blue" %)**AT+PWD=<Your ThingSpeak MQTT Password>**
163 163  
164 -* **AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
186 +* (% style="color:blue" %)**AT+PUBTOPIC=<YOUR_CHANNEL_ID>**
165 165  
166 -* **AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
188 +* (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
167 167  
168 168  
191 +==== 3.3.3.2 Uplink Examples ====
169 169  
170 -=== 3.3.2 Uplink Examples ===
193 +[[image:image-20230816201942-1.png]]
171 171  
172 -
173 -For S31-NB
174 -
175 175  For SE01-NB
176 176  
177 177  For DDS20-NB
... ... @@ -195,401 +195,340 @@
195 195  For SN50V3-NB
196 196  
197 197  
198 -=== 3.3.3 Map fields to sensor value ===
218 +==== 3.3.3.3 Map fields to sensor value ====
199 199  
200 200  
201 201  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.
202 202  
203 203  
204 -[[image:image-20230802112413-12.png]]
224 +[[image:image-20230802112413-12.png||height="504" width="1011"]]
205 205  
206 -[[image:image-20230802112413-13.png]]
226 +[[image:image-20230802112413-13.png||height="331" width="978"]]
207 207  
208 208  
209 209  Below is the NB-IoT Product Table show the mapping.
210 210  
211 -|(% 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" %)(((
212 -Field9
231 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
232 +|(% 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
233 +|(% 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" %)
234 +|(% 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" %)
235 +|(% 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" %)
236 +|(% 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" %)
237 +|(% 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" %)
238 +|(% 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" %)
239 +|(% 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" %)
240 +|(% 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" %)
241 +|(% 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" %)
242 +|(% 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" %)
243 +|(% 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
244 +|(% 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" %)
245 +|(% 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" %)
246 +|(% 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" %)
247 +|(% 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" %)
248 +|(% 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" %)
249 +|(% 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" %)
213 213  
214 -
215 -)))|(% colspan="1" rowspan="1" %)(((
216 -Field10
217 217  
218 -
219 -)))
220 -|(% 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" %)
221 -|(% 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" %)
222 -|(% colspan="1" rowspan="1" %)DDS20-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
223 -Battery
252 +== 3.4 [[Datacake>>https://datacake.co/]] ==
224 224  
225 -
226 -)))|(% 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" %)
227 -|(% colspan="1" rowspan="1" %)DDS45-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
228 -Battery
229 229  
230 -
231 -)))|(% 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" %)
232 -|(% colspan="1" rowspan="1" %)DDS75-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
233 -Battery
255 +(% class="wikigeneratedid" %)
256 +Dragino NB-IoT sensors has its template in **[[Datacake>>https://datacake.co/]]** Platform. There are two version for NB Sensor,
234 234  
235 -
236 -)))|(% 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" %)
237 -|(% colspan="1" rowspan="1" %)NMDS120-NB|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %)(((
238 -Battery
239 239  
240 -
241 -)))|(% 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" %)
242 -|(% 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" %)
243 -|(% 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" %)
244 -|(% 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" %)
245 -|(% 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" %)
246 -|(% 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
247 -|(% 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" %)
248 -|(% 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" %)
249 -|(% colspan="1" rowspan="1" %)mod2|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)Battery|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
250 -DS18B20 Temp
259 +(% class="wikigeneratedid" %)
260 +As example for S31B-NB. there are two versions: **S31B-NB-1D and S31B-NB-GE.**
251 251  
252 -
253 -)))|(% colspan="1" rowspan="1" %)(((
254 -exit_state/input PA4
262 +* (% 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.
255 255  
256 -
257 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)distance|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
258 -|(% colspan="1" rowspan="1" %)mod3|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
259 -Battery
264 +* (% 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.
260 260  
261 -
262 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
263 -exit_state/input PA4
264 264  
265 -
266 -)))|(% colspan="1" rowspan="1" %)adc1|(% colspan="1" rowspan="1" %)Temperature|(% colspan="1" rowspan="1" %)Humidity|(% colspan="1" rowspan="1" %)adc4|(% colspan="1" rowspan="1" %)
267 -|(% colspan="1" rowspan="1" %)mod4|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
268 -Battery
267 +=== 3.4.1 Create device ===
269 269  
270 -
271 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
272 -DS18B20 Temp
273 273  
274 -
275 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
276 -exit_state/input PA4
270 +(% style="color:blue" %)**Add Device**(%%) in DataCake.
277 277  
278 -
279 -)))|(% colspan="1" rowspan="1" %)(((
280 -DS18B20 Temp2
272 +[[image:image-20230808162301-1.png||height="473" width="994"]]
281 281  
282 -
283 -)))|(% colspan="1" rowspan="1" %)(((
284 -DS18B20 Temp3
285 285  
286 -
287 -)))|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
288 -|(% colspan="1" rowspan="1" %)mod5|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
289 -Battery
275 +[[image:image-20230808162342-2.png]]
290 290  
291 -
292 -)))|(% colspan="1" rowspan="1" %)RSSI|(% colspan="1" rowspan="1" %)(((
293 -DS18B20 Temp
294 294  
295 -
296 -)))|(% colspan="1" rowspan="1" %)adc0|(% colspan="1" rowspan="1" %)(((
297 -exit_state/input PA4
278 +(% style="color:blue" %)**Choose the correct model**(%%) from template.
298 298  
299 -
300 -)))|(% colspan="1" rowspan="1" %)Weight|(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %) |(% colspan="1" rowspan="1" %)
301 -|(% colspan="1" rowspan="1" %)mod6|(% colspan="1" rowspan="1" %)mod|(% colspan="1" rowspan="1" %)(((
302 -Battery
280 +[[image:image-20230808162421-3.png]]
303 303  
304 -
305 -)))|(% 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" %)
306 306  
307 -= 4. Datacake =
283 +(% 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.
308 308  
309 -== 1.1 Define Product ==
285 +[[image:image-20230808163612-7.png]]
310 310  
311 -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.
287 +[[image:image-20230808163035-5.png]]
312 312  
289 +[[image:image-20230808163049-6.png]]
313 313  
314 -By chosing to add the device under a "New Product" you are required to give a name for this product. You can name it something like "My First MQTT Product".
315 315  
316 -[[image:image-20230802112413-14.png]]
292 +=== 3.4.2 Scan QR code to obtain data ===
317 317  
318 -== 1.2 Create Device ==
319 319  
320 -In the seconstep you have to define the device which should be added to the product.
295 +Users can use their phones or computers to scan QR codes to obtain device data information.
321 321  
322 -[[image:image-20230802112413-15.png]]
297 +[[image:image-20230808170051-8.png||height="255" width="259"]]
323 323  
324 -Enter a name here (such as "My First MQTT Device") and complete the creation of the device by clicking on the "Next" button.
299 +[[image:image-20230808170548-9.png]]
325 325  
326 326  
327 -== 1.3 CreatDatabase Fields ==
302 +=== 3.4.2 AT command for connecting to DataCake ===
328 328  
329 -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.
330 330  
331 -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".
305 +(% style="color:blue" %)**AT+PRO=2,0**
332 332  
333 -[[image:image-20230802112413-16.png]]
307 +(% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
334 334  
335 -[[image:image-20230802112413-17.png]]
336 336  
337 -To create a first database field, please click on the "Add Field" button as marked in the screenshot above.
310 +== 3.5 Node-Red (via MQTT) ==
338 338  
339 -This will open another modal asking fosome required input for your first field.
312 +=== 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
340 340  
341 -[[image:image-20230802112413-18.png]]
342 342  
343 -[[image:image-20230802112413-19.png]]
315 +Take S31-NB UDP protocol as an example.
344 344  
345 -== 1.4 Set up Broker ==
317 +Dragino provides input flow examples for the sensors.
346 346  
347 -The broker is running on mqtt.datacake.co on ports 1883 and 8883. Port 1883 is unsecured and should not be used in production environments. Port 8883 usea CA signed server certificate.
319 +User can download the required JSON file through Dragino Node-RED input flow template.
348 348  
349 -Yowill 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.
321 +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]]
350 350  
351 -Vieyour Personal Access Token
323 +We can directly import the template.
352 352  
353 -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:
325 +The templates for S31-NB and NB95S31B are the same.
354 354  
355 -[[image:image-20230802112413-20.png]]
356 356  
357 -MQTT Client-ID
328 +[[image:image-20230809173127-4.png]]
358 358  
359 -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.
360 360  
361 -AT+CLIENT=“Any value
331 +Please select the NB95S31B template.
362 362  
363 -AT+UNAME=Token
333 +[[image:image-20230809173310-5.png]]
364 364  
365 -AT+PWD=Token
335 +[[image:image-20230809173438-6.png]]
366 366  
367 -[[image:image-20230802112413-21.png]]
337 +[[image:image-20230809173800-7.png]]
368 368  
369 369  
370 -== 1.6 Create your first Subscription ==
340 +Successfully imported template.
371 371  
372 -Subscribe
342 +[[image:image-20230809173835-8.png]]
373 373  
374 -Data is published according to the following structure:
375 375  
376 -dtck~/~//
345 +Users can set UDP port.
377 377  
378 -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.
347 +[[image:image-20230809174053-9.png]]
379 379  
380 380  
381 -[[image:image-20230802112413-22.png]]
350 +=== 3.5.2 Simulate Connection ===
382 382  
383 383  
384 -[[image:image-20230802112413-23.png]]
353 +We have completed the configuration of UDP. We can try sending packets to node red.
385 385  
355 +[[image:image-20230810083934-1.png]]
386 386  
387 -[[image:image-20230802112413-24.png]]
357 +[[image:image-20230810084048-2.png]]
388 388  
359 +=== 3.5.3 Configure NB-IoT Sensors ===
389 389  
390 -example:
391 391  
392 -AT+PUBTOPIC=dtck-pub/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
362 +* (% style="color:blue" %)**AT+PRO=2,0(hex format) or 2,1(json format)  **(%%)** **~/~/  Set to UDP Server and  Payload
393 393  
394 -[[image:image-20230802112413-25.png]]
364 +* (% style="color:blue" %)**AT+SERVADDR=xx.xx.xx.xx,port   **(%%)** **~/~/  Set Server IP and  port
395 395  
396 -== 1.7 Define Publish Topic ==
397 397  
398 -Publish
367 +== 3.6 ThingsBoard.Cloud (via MQTT) ==
399 399  
400 -To upload data into the Datacake Cloud and into a specific device, you publish thdata to the respective topic structure.
369 +=== 3.6.1 ConfigurThingsBoard ===
401 401  
402 -Due to the naturof MQTT, the topic prefix differs as follows:
371 +==== 3.6.1.1 Create Device ====
403 403  
404 -dtck-pub~/~//
405 405  
406 -example:
374 +Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
407 407  
408 -AT+SUBTOPIC=dtck/nbmattest/936c0db6-e9a5-4353-9fdb-3f63c8bfce7e/Temperature
376 +[[image:image-20230802112413-32.png]]
409 409  
410 -== 1.8 upload data ==
411 411  
412 -[[image:image-20230802112413-26.png]]
379 +==== 3.6.1.2 Create Uplink & Downlink Converter ====
413 413  
414 -[[image:image-20230802112413-27.png]]
415 415  
416 -[[image:image-20230802112413-28.png]]
382 +(% style="color:blue" %)**Uplink Converter**
417 417  
418 -= =
384 +The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
419 419  
420 -= 5. Node-Red (via MQTT) =
386 +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.
421 421  
388 +[[image:image-20230802112413-33.png||height="732" width="1302"]]
422 422  
423 -== 1.1 Configure Node-Red ==
424 424  
425 -[[image:image-20230802112413-29.png]]
391 +(% style="color:blue" %)**Downlink Converter**
426 426  
427 -[[image:image-20230802112413-30.png]]
393 +The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
428 428  
429 -== 1.2 Simulate Connection ==
395 +[[image:image-20230802112413-34.png||height="734" width="1305"]]
430 430  
431 -[[image:image-20230802112413-31.png]]
397 +(% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
432 432  
433 -== 1.3 Configure NB-IoT Sensors ==
434 434  
435 -* AT+PRO=3,0(hex format) or 3,5(json format)    ~/~/Set to mqtt Server and  Payload
436 -* AT+CLIENT=any value
437 -* AT+UNAME=any value
438 -* AT+PWD=any value
439 -* AT+PUBTOPIC=any value
440 -* AT+SUBTOPIC=any value
400 +==== 3.6.1.3 MQTT Integration Setup ====
441 441  
442 -= 6. ThingsBoard.Cloud (via MQTT) =
443 443  
444 -== 1.1 Configure ThingsBoard ==
403 +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**;
445 445  
446 -=== 1.1.1 Create Device ===
405 +[[image:image-20230802112413-35.png||height="738" width="1312"]]
447 447  
448 -Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]].
449 449  
450 -[[image:image-20230802112413-32.png]]
408 +* The next steps is to add the recently created uplink and downlink converters;
451 451  
452 -=== 1.1.2 Create Uplink & Downlink Converter ===
410 +[[image:image-20230802112413-36.png||height="736" width="1308"]]
453 453  
454 -Uplink Converter
412 +[[image:image-20230802112413-37.png||height="735" width="1307"]]
455 455  
456 -The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
457 457  
458 -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.
415 +(% style="color:blue" %)**Add a topic filter:**
459 459  
460 -[[image:image-20230802112413-33.png]]
417 +tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature  **固定的? 对的。**
461 461  
419 +You can also select an MQTT QoS level. We use MQTT QoS level 0 (At most once) by default;
462 462  
463 -Downlink Converter
421 +[[image:image-20230802112413-38.png||height="731" width="1300"]]
464 464  
465 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external MQTT broke
466 466  
467 -[[image:image-20230802112413-34.png]]
424 +=== 3.6.2 Simulate with MQTT.fx ===
468 468  
469 -Note:Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.
470 470  
471 -=== 1.1.3 MQTT Integration Setup ===
427 +[[image:image-20230802112413-39.png]]
472 472  
473 -Go to the Integrations center -> Integrations page and click “plus” icon to add a new integration. Name it “MQTT Integration”, select type MQTT;
429 +[[image:image-20230802112413-40.png]]
474 474  
475 -[[image:image-20230802112413-35.png]]
476 476  
477 -* The next steps is to add the recently created uplink and downlink converters;
432 +=== 3.6.3 Configure NB-IoT Sensor ===
478 478  
479 -[[image:image-20230802112413-36.png]]
480 480  
481 -[[image:image-20230802112413-37.png]]
435 +(% style="color:blue" %)**AT Commands**
482 482  
483 -Add a topifilter:
437 +* (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
484 484  
439 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>**
485 485  
486 -tb/mqtt-integration-tutorial/sensors~/~/temperature ~-~-> Temperature 固定的? 对的。
441 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>**
487 487  
488 -You can also select an MQTT Qolevel. We use MQTT QoS level 0 (At most once) by default;
443 +* (% style="color:#037691" %)**AT+CLIENT=<devicname> or User Defined**
489 489  
490 -[[image:image-20230802112413-38.png]]
445 +* (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
491 491  
492 -== 1.2 Simulatwith MQTT.fx ==
447 +* (% style="color:#037691" %)**AT+PWD=<devicname> or User Defined**
493 493  
494 -[[image:image-20230802112413-39.png]]
449 +Test Uplink by click the button for 1 second
495 495  
496 -[[image:image-20230802112413-40.png]]
451 +[[image:image-20230802112413-41.png]]
497 497  
498 -== 1.3 Configure NB-IoT Sensor ==
453 +[[image:image-20230802112413-42.png]]
499 499  
500 -AT Commands
455 +[[image:image-20230802112413-43.png]]
501 501  
502 -AT+PRO=3,3  ~/~/ Use MQTT to connect to ThingsBoard.
503 503  
504 -AT+SUBTOPIC=device name ~-~-> 只需要 Device Name 吗?对的
458 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
505 505  
506 -AT+PUBTOPIC=device nam~-~-> 只需要 Device Nam吗?对的
460 +=== 3.7.1 Creatdevice & Get Credentials ===
507 507  
508 508  
509 -Userdo noneed to fill in the client, username, anpassword. But the configuration information of thdevice requires setting the client, username, and password, which can be entered freely. (软件自动填充为 Device Name 吧).这边不用提示了,客户不需要输入。(大部分客户还是会自己去设置这个的,提高安全性)
463 +We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. Wneed to CreatDevice and Get MQTT Credentials first.
510 510  
511 -CLIENT :“Any value
465 +[[image:image-20230802112413-44.png]]
512 512  
513 -User Name:“Any value
467 +[[image:image-20230802112413-45.png]]
514 514  
515 -Password:“Any value”
516 516  
470 +Go to the Device section and create a device. Then, go to the section tokens and copy your device-token.
517 517  
518 -Test Uplink by click the button for 1 second
472 +[[image:image-20230802112413-46.png]]
519 519  
520 -[[image:image-20230802112413-41.png]]
521 521  
522 -[[image:image-20230802112413-42.png]]
475 +The device needs to enable the TLS mode and set the (% style="color:blue" %)**AT+TLSMOD=1,0**(%%) command.
523 523  
524 -[[image:image-20230802112413-43.png]]
477 +(% style="color:blue" %)**On the Connection Profile window, set the following information:**
525 525  
479 +* (% style="color:#037691" %)**Profile Name: “Any name”**
526 526  
527 -= 7. [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) =
481 +* (% style="color:#037691" %)**Broker Address: mqtt.tago.io**
528 528  
529 -== 5.1 Create device & Get Credentials ==
483 +* (% style="color:#037691" %)**Broker Port: 8883**
530 530  
531 -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.
485 +* (% style="color:#037691" %)**Client ID: “Any value”**
532 532  
533 -[[image:image-20230802112413-44.png]]
487 +(% style="color:blue" %)**On the section User credentials, set the following information:**
534 534  
535 -[[image:image-20230802112413-45.png]]
489 +* (% style="color:#037691" %)**User Name: “Any value”** (%%) **~/~/ Tago validates your user by the token only**
536 536  
537 -= =
491 +* (% style="color:#037691" %)**Password: “Your device token”**
538 538  
539 -Go to the Device section and create a device. Then, go to the section tokens and copyour device-token.
493 +* (% style="color:#037691" %)**PUBTOPIC: “Any value”**
540 540  
541 -[[image:image-20230802112413-46.png]]
495 +* (% style="color:#037691" %)**SUBTOPIC: “Any value”**
542 542  
497 +(% style="color:blue" %)**AT command:**
543 543  
544 -On the Connection Profile windowset the following information: (这边加一个截图)
499 +* (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
545 545  
546 -* Profile Name: “Any name”
547 -* Broker Address: mqtt.tago.io
548 -* Broker Port: 1883
549 -* Client ID: “Any value”
501 +* (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
550 550  
551 -On the sectioUsecredentials, set the following information:(这边加一个截图)
503 +* (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
552 552  
553 -* User Name: “Any value” Tago validates your user by the token only
554 -* Password: “Your device token”
555 -* PUBTOPIC: “Any value”
556 -* SUBTOPIC: “Any value”
505 +* (% style="color:#037691" %)**AT+CLIENT=<device name> or User Defined**
557 557  
558 -== 5.2 Simulatwith MQTT.fx ==
507 +* (% style="color:#037691" %)**AT+UNAME=<devicname> or User Defined**
559 559  
560 -[[image:image-20230802112413-47.png]]
509 +* (% style="color:#037691" %)**AT+PWD=“Your device token”**
561 561  
562 -[[image:image-20230802112413-48.png]]
563 563  
564 -Users can run the AT+PRO=3,5 command, and thpayload will be converted to JSON format.
512 +=== 3.7.2 Simulate with MQTT.fx ===
565 565  
566 -[[image:image-20230802112413-49.png]]
567 567  
568 -== 1.4. tago data ==
515 +[[image:image-20230802112413-52.png]]
569 569  
570 570  
518 +[[image:image-20230808105300-2.png]]
519 +
520 +
521 +Users can run the (% style="color:blue" %)**AT+PRO=3,5**(%%) command, and the payload will be converted to **JSON format**.
522 +
523 +[[image:image-20230808105217-1.png]]
524 +
525 +[[image:image-20230808105329-3.png]]
526 +
527 +
528 +=== 3.7.3 tago data ===
529 +
530 +
571 571  [[image:image-20230802112413-50.png]]
572 572  
573 -[[image:image-20230802112413-51.png]]
533 +[[image:image-20230802112413-51.png||height="184" width="696"]]
574 574  
575 -== 1.4. TLS mode ==
576 576  
577 -Users can choose to use SSL/TLS mode.
536 +== 3.8 TCP Connection ==
578 578  
579 -On the SSL/TLS section, check the option Enable SSL/TLS, and click OK.
580 580  
581 -The device needs tenable the TLS mode and set the AT+TLSMOD=1,0 command.
539 +(% style="color:blue" %)**AT command:**
582 582  
583 -* Profile Name: “Any name”
584 -* Broker Address: mqtt.tago.io
585 -* Broker Port: 8883
586 -* Client ID: “Any value”
587 -* User Name: “Any value” Tago validates your user by the token only
588 -* Password: “Your device token”
589 -* PUBTOPIC: “Any value”
590 -* SUBTOPIC: “Any value”
541 +* (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
591 591  
592 -[[image:image-20230802112413-52.png]]
543 +* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
593 593  
545 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
594 594  
595 -
547 +(% style="color:blue" %)**Sensor Console Output when Uplink:**
548 +
549 +[[image:image-20230807233631-1.png]]
550 +
551 +
552 +(% style="color:blue" %)**See result in TCP Server:**
553 +
554 +[[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