Skip to Content
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.1
edited by Mengting Qiu
on 2025/07/29 13:42
Change comment: There is no comment for this version
To version 30.1
edited by Mengting Qiu
on 2024/08/22 09:05
Change comment: Uploaded new attachment "image-20240822090554-1.png", version {1}

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
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  
38 38  
39 -**{
40 - "Version": "2012-10-17",
41 - "Statement": [
42 - {
43 - "Effect": "Allow",
44 - "Action": "iot:*",
45 - "Resource": "*"
46 - }
47 - ]
48 -}**
38 +**{**
49 49  
40 +**~ "Version": "2012-10-17",**
50 50  
42 +**~ "Statement": [**
51 51  
52 -[[image:image-20250103151957-1.png||height="529" width="935"]]
44 +**~ {**
53 53  
46 +**~ "Effect": "Allow",**
47 +
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  
... ... @@ -109,12 +109,12 @@
109 109  
110 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"]]
120 +[[image:image-20240814155410-1.png||height="328" width="563"]]
113 113  
114 114  
115 115  == 4.1 For -NB /-NS model ==
116 116  
117 -=== 4.1.1 Upgrade the firmware to configure TLS firmware to set the certificate ===
125 +=== 4.1.1 Upgrade the firmware to configure TTS firmware to set the certificate ===
118 118  
119 119  
120 120  User can change device firmware to::
... ... @@ -136,7 +136,7 @@
136 136  
137 137  After upgrade the firmware, the serial port displays as follows：
138 138  
139 -[[image:image-20250306113602-1.png||height="401" width="856"]]
147 +[[image:image-20240528174330-13.png||height="286" width="568"]]
140 140  
141 141  
142 142  ==== 4.1.2.1  Configure CA certificate ====
... ... @@ -193,7 +193,7 @@
193 193  
194 194  After successful execution, as shown in the following figure.
195 195  
196 -[[image:image-20250306113849-2.png||height="742" width="456"]]
204 +[[image:image-20240528174502-15.png]]
197 197  
198 198  Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
199 199  
... ... @@ -319,17 +319,12 @@
319 319  ==== 4.1.2.4 Re-upgrade the firmware ====
320 320  
321 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]].
330 +After the certificate configuration is completed, Re-upgrade to the firmware you originally used.
323 323  
324 324  
325 -==== 4.1.2.5 For certificate coverage of the -NB/-NS model ====
326 -
327 -For the -NB/-NS models, there is no AT command available to clear configured certificates. Therefore, if users do not wish to use the pre-configured certificates, they only need to follow the instructions above and use the AT+CACERT, AT+CLICERT, and AT+CLIKEY commands to assign custom meaningless characters to the device. This will overwrite the original certificates.
328 -
329 -
330 330  == 4.2  For -CB /-CS model ==
331 331  
332 -=== 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===
335 +=== 4.2.1 Upgrade the firmware to configure TTS firmware to set the certificate ===
333 333  
334 334  
335 335  User can change device firmware to::
... ... @@ -342,6 +342,8 @@
342 342  
343 343  Methods to Update Firmware:
344 344  
348 +* (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
349 +
345 345  * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
346 346  
347 347  === 4.2.2 Configure certificate ===
... ... @@ -349,7 +349,7 @@
349 349  
350 350  After upgrade the firmware, the serial port displays as follows：
351 351  
352 -[[image:image-20250306114107-2.png||height="371" width="744"]]
357 +[[image:image-20240528174330-13.png||height="286" width="568"]]
353 353  
354 354  
355 355  ==== 4.2.2.1 Configure CA certificate ====
... ... @@ -407,7 +407,7 @@
407 407  
408 408  After successful execution, as shown in the following figure.
409 409  
410 -[[image:image-20250306134213-1.png]]
415 +[[image:image-20240528174502-15.png]]
411 411  
412 412  Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
413 413  
... ... @@ -530,15 +530,9 @@
530 530  Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
531 531  
532 532  
533 -==== 4.2.2.4 Re-upgrade the firmware ====
538 +==== 4.2.2.4 For -CB /-CS model Certificate setting error/change certificate ====
534 534  
535 535  
536 -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]].
537 -
538 -
539 -==== 4.2.2.5 For -CB /-CS model Certificate setting error/change certificate ====
540 -
541 -
542 542  (% data-sider-select-id="7c5a8abc-e707-467b-ac02-db0a89098320" %)When you set the wrong certificate or you need to re-set another certificate.
543 543  Please use the following three commands：
544 544  
... ... @@ -626,3 +626,5 @@
626 626  [[image:image-20240528175133-19.png||height="563" width="1022"]]
627 627  
628 628  [[image:image-20240528175154-20.png||height="752" width="1042"]]
628 +
629 +
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