Skip to Content
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.4
edited by Mengting Qiu
on 2025/07/29 13:59
Change comment: There is no comment for this version
To version 23.7
edited by Xiaoling
on 2024/05/29 09:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Dragino -NB/-CB device connection to AWS platform instructions
1 +Dragino NB device connection to AWS platform instructions
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -27,30 +27,38 @@
27 27  
28 28  a. Fill in any name
29 29  
30 +b. Configure the policy you created
30 30  
31 -b. Fill in * to Policy action and Policy resource (* stands for all)
32 +[[image:image-20240528173144-3.png||height="572" width="931"]]
32 32  
33 -[[image:image-20250103152135-2.png||height="777" width="1544"]]
34 34  
35 -
36 36  c. After clicking to enter the policy configuration page, follow the clicking sequence below to go to the json configuration interface, and then fill in the following fields in the "statement" keyword:
37 37  
37 +(% data-sider-select-id="7bc0f6db-481d-435a-ad0c-92cf0ede3ea4" %)
38 +(% data-sider-select-id="8026a4d9-df91-4895-b9c5-3d6ac9b46012" %)**{**
38 38  
39 -**{
40 - "Version": "2012-10-17",
41 - "Statement": [
42 - {
43 - "Effect": "Allow",
44 - "Action": "iot:*",
45 - "Resource": "*"
46 - }
47 - ]
48 -}**
40 +**~ "Version": "2012-10-17",**
49 49  
42 +**~ "Statement": [**
50 50  
44 +**~ {**
51 51  
52 -[[image:image-20250103151957-1.png||height="529" width="935"]]
46 +**~ "Effect": "Allow",**
53 53  
48 +**~ "Action": "",**
49 +
50 +**~ "Resource": ""**
51 +
52 +**~ }**
53 +
54 +**~ ]**
55 +
56 +**}**
57 +
58 +
59 +[[image:image-20240528173203-4.png||height="517" width="942"]]
60 +
61 +
54 54  d. Create this policy
55 55  
56 56  
... ... @@ -91,9 +91,9 @@
91 91  
92 92  (% style="color:blue" %)**5. When you click to create things, the certificate download page will pop up**
93 93  
102 +(% data-sider-select-id="398c8d35-75ff-4077-85bb-9e0377efa186" %)
103 +(% data-sider-select-id="087aa6c7-c542-4afc-9ce6-291538c31764" %)**This certificate is very important.**(%%) After creating the device, you must download the certificate of the device so that our NB device can connect normally.
94 94  
95 -**This certificate is very important.** After creating the device, you must download the certificate of the device so that our NB device can connect normally.
96 -
97 97  Please download all the following certificates and put them in a folder.
98 98  
99 99  [[image:image-20240528173926-10.png]]
... ... @@ -106,17 +106,9 @@
106 106  
107 107  = 4. Connect to AWS using Dragino-NB device =
108 108  
117 +== 4.1 Upgrade the firmware to configure TTS firmware to set the certificate ==
109 109  
110 -(% id="cke_bm_37736S" style="color:red; display:none" %)** **(% style="color:red" %)**Note: **(%%)In order to avoid problems with certificate writing, you need to set the serial port assistant to automatically add a newline character when sending commands, if there is no such newline character, the certificate written will be invalid.(Using the serial port assistant as an example)
111 111  
112 -[[image:image-20240822090554-1.png||height="501" width="656"]]
113 -
114 -
115 -== 4.1 For -NB /-NS model ==
116 -
117 -=== 4.1.1 Upgrade the firmware to configure TLS firmware to set the certificate ===
118 -
119 -
120 120  User can change device firmware to::
121 121  
122 122  * Update with new features.
... ... @@ -123,7 +123,7 @@
123 123  
124 124  * Fix bugs.
125 125  
126 -Firmware and changelog can be downloaded from : **[[Set up TLS certificate - Dropbox>>https://www.dropbox.com/scl/fo/1ykfsesmr3702tj3kp663/AOOyH1GiVEOGR41gASuiDk0?rlkey=1q7a1b5yvjgt87d16w8tt0cum&st=vdy765ut&dl=0||data-sider-select-id="830d1b64-cb24-48b3-91e4-49da5c3f0783"]]**
126 +Firmware and changelog can be downloaded from : **[[Set up TLS certificate - Dropbox>>url:https://www.dropbox.com/sh/sxrgszkac4ips0q/AAA7xVIHen982Nc0edNPaB-Wa/NB-IoT/Set%20up%20TLS%20certificate?dl=0&subfolder_nav_tracking=1||data-sider-select-id="830d1b64-cb24-48b3-91e4-49da5c3f0783"]]**
127 127  
128 128  Methods to Update Firmware:
129 129  
... ... @@ -131,239 +131,19 @@
131 131  
132 132  * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
133 133  
134 -=== 4.1.2 Configure certificate ===
135 135  
136 136  
137 -After upgrade the firmware, the serial port displays as follows：
136 +== 4.2 Configure certificate ==
138 138  
139 -[[image:image-20250306113602-1.png||height="401" width="856"]]
140 140  
141 -
142 -==== 4.1.2.1  Configure CA certificate ====
143 -
144 -
145 -Please input the certificate in PEM format for the user.
146 -
147 -Use the AT command AT+CACERT as follows:
148 -
149 -AT+CACERT=~-~-~-~--BEGIN CERTIFICATE~-~-~-~--
150 -
151 -MIIDQTCCAimgAwIBAgITBmyfz5m/jAo54vB4ikPmljZbyjANBgkqhkiG9w0BAQsF
152 -
153 -ADA5MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRkwFwYDVQQDExBBbWF6
154 -
155 -b24gUm9vdCBDQSAxMB4XDTE1MDUyNjAwMDAwMFoXDTM4MDExNzAwMDAwMFowOTEL
156 -
157 -MAkGA1UEBhMCVVMxDzANBgNVBAoTBkFtYXpvbjEZMBcGA1UEAxMQQW1hem9uIFJv
158 -
159 -b3QgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALJ4gHHKeNXj
160 -
161 -ca9HgFB0fW7Y14h29Jlo91ghYPl0hAEvrAIthtOgQ3pOsqTQNroBvo3bSMgHFzZM
162 -
163 -9O6II8c+6zf1tRn4SWiw3te5djgdYZ6k/oI2peVKVuRF4fn9tBb6dNqcmzU5L/qw
164 -
165 -IFAGbHrQgLKm+a/sRxmPUDgH3KKHOVj4utWp+UhnMJbulHheb4mjUcAwhmahRWa6
166 -
167 -VOujw5H5SNz/0egwLX0tdHA114gk957EWW67c4cX8jJGKLhD+rcdqsq08p8kDi1L
168 -
169 -93FcXmn/6pUCyziKrlA4b9v7LWIbxcceVOF34GfID5yHI9Y/QCB/IIDEgEw+OyQm
170 -
171 -jgSubJrIqg0CAwEAAaNCMEAwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMC
172 -
173 -AYYwHQYDVR0OBBYEFIQYzIU07LwMlJQuCFmcx7IQTgoIMA0GCSqGSIb3DQEBCwUA
174 -
175 -A4IBAQCY8jdaQZChGsV2USggNiMOruYou6r4lK5IpDB/G/wkjUu0yKGX9rbxenDI
176 -
177 -U5PMCCjjmCXPI6T53iHTfIUJrU6adTrCC2qJeHZERxhlbI1Bjjt/msv0tadQ1wUs
178 -
179 -N+gDS63pYaACbvXy8MWy7Vu33PqUXHeeE6V/Uq2V8viTO96LXFvKWlJbYK8U90vv
180 -
181 -o/ufQJVtMVT8QtPHRh8jrdkPSHCa2XV4cdFyQzR1bldZwgJcJmApzyMZFo6IQ6XU
182 -
183 -5MsI+yMRQ+hDKXJioaldXgjUkK642M4UwtBV8ob2xJNDd2ZhwLnoQdeXeGADbkpy
184 -
185 -rqXRfboQnoZsG4q5WTP468SQvvG5
186 -
187 -~-~-~-~--END CERTIFICATE~-~-~-~--}
188 -
189 -(% style="color:red" %)**Note: Be sure to add a terminator "}" at the end of the command. Otherwise, the command will not execute successfully.**
190 -
191 -[[image:image-20240528174408-14.png]]
192 -
193 -
194 -After successful execution, as shown in the following figure.
195 -
196 -[[image:image-20250306113849-2.png||height="742" width="456"]]
197 -
198 -Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
199 -
200 -
201 -==== 4.1.2.2 Configure client certificate ====
202 -
203 -
204 -Use the AT command AT+CLICERT as follows：
205 -
206 -AT+CLICERT=~-~-~-~--BEGIN CERTIFICATE~-~-~-~--
207 -
208 -MIIDWTCCAkGgAwIBAgIUYSpJUzfb4NTa76JJxd2th0fZA8swDQYJKoZIhvcNAQEL
209 -
210 -BQAwTTFLMEkGA1UECwxCQW1hem9uIFdlYiBTZXJ2aWNlcyBPPUFtYXpvbi5jb20g
211 -
212 -SW5jLiBMPVNlYXR0bGUgU1Q9V2FzaGluZ3RvbiBDPVVTMB4XDTI0MDUyNDA4MDI0
213 -
214 -NVoXDTQ5MTIzMTIzNTk1OVowHjEcMBoGA1UEAwwTQVdTIElvVCBDZXJ0aWZpY2F0
215 -
216 -ZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTdc1GQLVBohAeCJD6n
217 -
218 -6WTFAFrygTch90a5wUr2bhlVuDxvEhEKNcmu5vOCo5agmfLWb2VCxgezgvQOBYQ8
219 -
220 -1oTqXJNdl4tS0DICfqb/ogVHWGHRao67XyhbPNBS0j/nCPTIIk6+/NBeYPOjaG+p
221 -
222 -utfXE7SGIEcc3RevkYkUJx6y+WH7MLjj1mufuXBVWIL1RrfrIRPw6auVk7dhS5rU
223 -
224 -NvYcJa7Qd6gpAh1DzPj7ZECrv7fEIIBDEsSYOy6ToWtzqGIVcIAHBDfORB0Hcm+N
225 -
226 -7wG3KDf61P4aWkLlkP5pRUaUIQdVblxginmx2K3n8t/WP7QcfITa191rjEVVBXmk
227 -
228 -ROsCAwEAAaNgMF4wHwYDVR0jBBgwFoAUs8Caohh1ZGP8kjSn3rtxJiJJ9IswHQYD
229 -
230 -VR0OBBYEFCjwGwqD7FG9UCNm3wjFQX4HixzfMAwGA1UdEwEB/wQCMAAwDgYDVR0P
231 -
232 -AQH/BAQDAgeAMA0GCSqGSIb3DQEBCwUAA4IBAQBgqI49a4PBQZYrFM63TX3EHgdd
233 -
234 -N6Pj7AytjO+SrKNMCSo/OtIvhDTxOocr1vKrux1Tw5qmrllrIXLtlGtbmln5DS6a
235 -
236 -DTCLrjwcIFIabLxpx5DPY1WSMYvL04SW7d4Y+3SxOFNRotDSiomr8eIIac0d3HE2
237 -
238 -B5b0SnWZgWbrhjNUgvwo8l8tA9DOGIr2MeQ5kPjudOOiYSR3HC0v+jviBMV6VX8M
239 -
240 -LHVH3CRshHDKBGpV1NZ1RAm9EY/oRGtSiMsyjRh6hegC0vehwVxaC4w9qG0ASkzz
241 -
242 -42OOGfNqhYnYDiKTEIkazaoAFpTKDejWBaL7W5VpthUkQOl67IyX+ohuUKTo
243 -
244 -~-~-~-~--END CERTIFICATE~-~-~-~--}
245 -
246 -(% style="color:red" %)**Note: Be sure to add a terminator "}" at the end of the command. Otherwise, the command will not execute successfully.**
247 -
248 -[[image:image-20240528174630-16.png||height="553" width="747"]]
249 -
250 -Display (% style="color:blue" %)**"Successfully configured client certificate."**(%%) Configuration successful, otherwise configuration failed.
251 -
252 -
253 -==== 4.1.2.3 Configure client private key ====
254 -
255 -
256 -Use the AT command AT+CLIKEY, as shown below
257 -
258 -AT+CLIKEY=~-~-~-~--BEGIN RSA PRIVATE KEY~-~-~-~--
259 -
260 -MIIEpAIBAAKCAQEAxN1zUZAtUGiEB4IkPqfpZMUAWvKBNyH3RrnBSvZuGVW4PG8S
261 -
262 -EQo1ya7m84KjlqCZ8tZvZULGB7OC9A4FhDzWhOpck12Xi1LQMgJ+pv+iBUdYYdFq
263 -
264 -jrtfKFs80FLSP+cI9MgiTr780F5g86Nob6m619cTtIYgRxzdF6+RiRQnHrL5Yfsw
265 -
266 -uOPWa5+5cFVYgvVGt+shE/Dpq5WTt2FLmtQ29hwlrtB3qCkCHUPM+PtkQKu/t8Qg
267 -
268 -gEMSxJg7LpOha3OoYhVwgAcEN85EHQdyb43vAbcoN/rU/hpaQuWQ/mlFRpQhB1Vu
269 -
270 -XGCKebHYrefy39Y/tBx8hNrX3WuMRVUFeaRE6wIDAQABAoIBAFhAOcjvjBDGuaEw
271 -
272 -CxV3al49HfqnSZuwg0xWSztSm2qKDcwxsnSnEhO2b1vsTW9h0YGV9Vv8gg/Dvkmv
273 -
274 -23M7XqM4+IUraJsRZbl1etdcM4KQSCOZoF4Zyv+pXuq4pf31kQNCkHaikWzLUkUG
275 -
276 -FPQxr0vA49mCYwfd/ZL3ppM/0IWmxRwloV1Gb9q8iDBUcJGSDokZnT7diUxzzOcd
277 -
278 -+UJ6xUhFq1v46Y7vO+73XROLv34JEBC0bIw2ErL6+AbzhHwb2mkuSccG9Ks37g3Z
279 -
280 -dyyjjj8hm1wvHWepuWqEssaiS3HD5zAsI0v85xS8RwNj3zLfd8o1WC666n3CO+ij
281 -
282 -VdRmR4kCgYEA+/sEFxpfaRomqcLwJebZcZH06U1RfJFfnbH2/Q6fANf8zNxwWs9A
283 -
284 -O+jyk/CLhHYRIk6VIOMQmWwEYgJ2eAHfw2Diwj4/0eqkGu+yZOS6KTCewxSV73vc
285 -
286 -SvACramJy4y6yEgDN5onwR1XqfVMfA0LzTcSupHR/xvrpf/gCsNFPxUCgYEAyAFd
287 -
288 -nMUhJFSq3pOogxA43aJSkA8YuDS3jpBkKQ6vx81APpIMabQauOxFDt488TZGP3Yy
289 -
290 -lhpa/lfFIgu2K7CgV4dUp+JtJJoZ/F+ExxUUzdqB4zxzWywAcc3RebfwP6qASwFT
291 -
292 -G3mXYci4tgNWR+k5CSsuLXDk/OT5uo5GeGAEc/8CgYEAk6V8uxDP8STKnNRFpN/E
293 -
294 -b6CHciDE64m/DgbWY2cq0fK9BUjxaLRhvfj8EqVzCrWnyoNjLHcAJfW+B7PLuPvY
295 -
296 -IoJlvE1/Vb/4UnQ7ApVnY3VCwaoRRNc9uIcz+pAJ1sRqOarAf9cLDkPkNwktvM5k
297 -
298 -KOXpSnrhIms4w/bPT18l9xUCgYBsAMDKbXEuK0JyGw5+Z/4tQQCQpnZU0rLkm3ha
299 -
300 -64FkxaORplBprEZZ4cyQ8NW78/EPSAadI/JLMp5TejuPcDvFyGCgoBcMEuNBc1tC
301 -
302 -HlIzr3FAgl5Qt3wt+FTMA9YKq0nINxjn10s2FKwaLccj4f9YwiaXh0VAg22PnlDT
303 -
304 -pBYDhQKBgQCMwyKXJ4zYiDRdvLvgKzeuKaU4KNQItHE4KORPfkecjPoENt4bKxDw
305 -
306 -2EdNFQLIoqBHL1s+/8+SzhCI31V7pkTs1AqCxDExJS7+8Z5NQFQIo/jooUo0N80E
307 -
308 -y3ZZS6OLOXXscEqhMogf1grfbabXM9OkgTIq43cPQHtMGQiFAtIJkg==
309 -
310 -~-~-~-~--END RSA PRIVATE KEY~-~-~-~--}
311 -
312 -(% style="color:red" %)**Note: Be sure to add a terminator "}" at the end of the command. Otherwise, the command will not execute successfully.**
313 -
314 -[[image:image-20240528174702-17.png]]
315 -
316 -Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
317 -
318 -
319 -==== 4.1.2.4 Re-upgrade the firmware ====
320 -
321 -
322 -After completing the certificate configuration, Burn the [[bootloader>>https://www.dropbox.com/sh/u0uzvvnn58yrie4/AAAvvF_KRveNgmDejzp23ziLa/NB-IoT/Bootloader?dl=0&subfolder_nav_tracking=1]] firmware first, then re-burn the original working [[firmware>>https://www.dropbox.com/sh/u0uzvvnn58yrie4/AACREHllkTe0rATD4ZOqddyga/NB-IoT?dl=0]].
323 -
324 -
325 -==== 4.1.2.5 Overwriting Certificates on -NB/-NS Models ====
326 -
327 -
328 -The -NB/-NS modules (BC660K) do not support clearing certificates via AT commands or firmware updates.
329 -
330 -To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps:
331 -
332 -1. Overwrite Certificates:
333 -
334 -Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456).
335 -Example:
336 -
337 -
338 -
339 -== 4.2  For -CB /-CS model ==
340 -
341 -=== 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===
342 -
343 -
344 -User can change device firmware to::
345 -
346 -* Update with new features.
347 -
348 -* Fix bugs.
349 -
350 -Firmware and changelog can be downloaded from : **[[Set up TLS certificate - Dropbox>>https://www.dropbox.com/scl/fo/mk9u5ux3cfo94ke0s67ik/ADOIOdwIQfCO2WUZt0MxXyU?rlkey=7o6uaywrebbnsvuj4r0r694x6&st=smrmjj7t&dl=0||data-sider-select-id="830d1b64-cb24-48b3-91e4-49da5c3f0783"]]**
351 -
352 -Methods to Update Firmware:
353 -
354 -* Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
355 -
356 -=== 4.2.2 Configure certificate ===
357 -
358 -
359 359  After upgrade the firmware, the serial port displays as follows：
360 360  
361 -[[image:image-20250306114107-2.png||height="371" width="744"]]
141 +(% data-sider-select-id="8b6a9e23-dec0-476c-acd4-098aa19fe1f3" %)
142 +[[image:image-20240528174330-13.png||height="286" width="568"]]
362 362  
363 363  
364 -==== 4.2.2.1 Configure CA certificate ====
145 +=== 4.2.1 Configure CA certificate ===
365 365  
366 -(% style="color:red" %)**Note:You should select one of the certificates.Either CA1 or CA3 can be used**
367 367  
368 368  Please input the certificate in PEM format for the user.
369 369  
... ... @@ -416,12 +416,12 @@
416 416  
417 417  After successful execution, as shown in the following figure.
418 418  
419 -[[image:image-20250306134213-1.png]]
199 +[[image:image-20240528174502-15.png]]
420 420  
421 421  Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
422 422  
423 423  
424 -==== 4.2.2.2 Configure client certificate ====
204 +=== 4.2.2 Configure client certificate ===
425 425  
426 426  
427 427  Use the AT command AT+CLICERT as follows：
... ... @@ -473,7 +473,7 @@
473 473  Display (% style="color:blue" %)**"Successfully configured client certificate."**(%%) Configuration successful, otherwise configuration failed.
474 474  
475 475  
476 -==== 4.2.2.3 Configure client private key ====
256 +=== 4.2.3 Configure client private key ===
477 477  
478 478  
479 479  Use the AT command AT+CLIKEY, as shown below
... ... @@ -539,31 +539,14 @@
539 539  Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
540 540  
541 541  
542 -==== 4.2.2.4 Re-upgrade the firmware ====
322 +=== 4.3.3 Re-upgrade the firmware ===
543 543  
544 544  
545 -After completing the certificate configuration, Burn the [[bootloader>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AE23WqlQ8CKU4cuy-sP1JkM/Utility/NB-IoT%20Bootloader?rlkey=ojjcsw927eaow01dgooldq3nu&e=1&subfolder_nav_tracking=1&dl=0]] firmware first, then re-burn the original working [[firmware>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/ANd2flSqspRRXl-ksF6gUqk/LTE-M?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]].
325 +After the certificate configuration is completed, Re-upgrade to the firmware you originally used.
546 546  
547 547  
548 -==== 4.2.2.5 For -CB /-CS model Certificate setting error/change certificate ====
328 += 5. Configure draginoNB-device =
549 549  
550 -
551 -(% data-sider-select-id="7c5a8abc-e707-467b-ac02-db0a89098320" %)When you set the wrong certificate or you need to re-set another certificate.
552 -Please use the following three commands：
553 -
554 -(% style="color:blue" %)**AT+DELCLIKEY}**
555 -
556 -(% style="color:blue" %)**AT+DELCLICERT}**
557 -
558 -(% style="color:blue" %)**AT+DELCACERT}**(%%)
559 -(% style="color:blue" %)
560 -
561 -(% style="color:red" %)**Note: 1.When there is no certificate on the device, a deletion error will be displayed.
562 - 2.When the device already has a certificate, using the command to configure the certificate again will display a configuration error.**
563 -
564 -
565 -= (% data-sider-select-id="6b5deb69-539b-42e1-a7bc-a300eb1fea73" %)5. Configure draginoNB-device(%%) =
566 -
567 567  == 5.1 Configure the data format sent by the device ==
568 568  
569 569  
... ... @@ -589,7 +589,7 @@
589 589  == 5.4 Set the TLS mode ==
590 590  
591 591  
592 -(% data-sider-select-id="cf7bb573-8375-4479-9801-df8bb7dab3ba" style="color:blue" %)**AT+TLSMOD=1,2**
355 +(% style="color:blue" %)**AT+TLSMOD=1,2**
593 593  
594 594  To use the TLS mode certificate function, users need to configure the (% style="color:blue" %)**AT+TLSMOD**(%%) command.
595 595  
... ... @@ -600,21 +600,9 @@
600 600  (% style="color:blue" %)**AT+TLSMOD=1,2** (%%) ~/~/ Perform server and client authentication if requested by the remote server.(In AWS we recommend using this mode)
601 601  
602 602  
603 -(% data-sider-select-id="f443b9bc-1195-4fe2-965d-7de84f78747f" %)
604 -== 5.5 Set the MQOS ==
366 +Restart the device
605 605  
606 606  
607 -(% data-sider-select-id="cf7bb573-8375-4479-9801-df8bb7dab3ba" style="color:blue; font-weight:bold" %)**AT+MQOS**(% data-sider-select-id="cf7bb573-8375-4479-9801-df8bb7dab3ba" style="color:blue" %)**=XX （Depends on your server configuration）**
608 -
609 -Please find it in AWS's MQTT test client
610 -
611 -[[image:image-20240529164339-1.png||height="480" width="927"]]
612 -
613 -
614 -(% data-sider-select-id="fef22158-6e5e-46e4-b59e-fe457e562376" %)
615 -== 5.6 Restart the device ==
616 -
617 -
618 618  = 6. View data on AWS =
619 619  
620 620  == 6.1 Find MQTT test client in test ==
... ... @@ -635,3 +635,5 @@
635 635  [[image:image-20240528175133-19.png||height="563" width="1022"]]
636 636  
637 637  [[image:image-20240528175154-20.png||height="752" width="1042"]]
389 +
390 +
image-20240529164339-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20240814155410-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.kai
Size
... ... @@ -1,1 +1,0 @@
1 -77.8 KB
Content
image-20240822090554-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -75.4 KB
Content
image-20250103151957-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -53.9 KB
Content
image-20250103152135-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -121.6 KB
Content
image-20250306113602-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -32.7 KB
Content
image-20250306113801-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -65.1 KB
Content
image-20250306113849-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -65.9 KB
Content
image-20250306114107-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -33.7 KB
Content
image-20250306134213-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -67.1 KB
Content