Changes for page Dragino -NB/-CB device connection to AWS platform instructions
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.13
edited by Mengting Qiu
on 2025/07/29 14:18
on 2025/07/29 14:18
Change comment:
There is no comment for this version
To version 34.1
edited by Bei Jinggeng
on 2025/01/03 15:21
on 2025/01/03 15:21
Change comment:
Uploaded new attachment "image-20250103152135-2.png", version {1}
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 5 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Dragino -NB/-CBdevice connection to AWS platform instructions1 +Dragino NB device connection to AWS platform instructions - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Bei - 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 Policyactionand Policy resource (* standsfor 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 ... ... @@ -114,7 +114,7 @@ 114 114 115 115 == 4.1 For -NB /-NS model == 116 116 117 -=== 4.1.1 Upgrade the firmware to configure T LS 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-202 50306113602-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-202 50306113849-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 ... ... @@ -322,37 +322,9 @@ 322 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 323 324 324 325 -==== 4.1.2.5 Certificate Management for -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 remove existing certificates or test certificate upload functionality, users may overwrite them with dummy data. 331 - 332 -To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps: 333 - 334 -**Scenario A:** Clearing Existing Certificates 335 - 336 -1. **[[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"]]** 337 - 338 - 339 -2. Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456). 340 -Example: 341 - 342 -AT+CACERT=123456} 343 - 344 -AT+CLICERT=123456} 345 - 346 -AT+CLIKEY=123456} 347 - 348 -2. Upload Valid Certificates (Optional): 349 - 350 -After overwriting, users may proceed to upload new valid certificates if needed. 351 - 352 - 353 353 == 4.2 For -CB /-CS model == 354 354 355 -=== 4.2.1 Upgrade the firmware to configure T LS firmware to set the certificate ===335 +=== 4.2.1 Upgrade the firmware to configure TTS firmware to set the certificate === 356 356 357 357 358 358 User can change device firmware to:: ... ... @@ -365,6 +365,8 @@ 365 365 366 366 Methods to Update Firmware: 367 367 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 + 368 368 * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**. 369 369 370 370 === 4.2.2 Configure certificate === ... ... @@ -372,7 +372,7 @@ 372 372 373 373 After upgrade the firmware, the serial port displays as follows: 374 374 375 -[[image:image-202 50306114107-2.png||height="371" width="744"]]357 +[[image:image-20240528174330-13.png||height="286" width="568"]] 376 376 377 377 378 378 ==== 4.2.2.1 Configure CA certificate ==== ... ... @@ -430,7 +430,7 @@ 430 430 431 431 After successful execution, as shown in the following figure. 432 432 433 -[[image:image-202 50306134213-1.png]]415 +[[image:image-20240528174502-15.png]] 434 434 435 435 Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure. 436 436 ... ... @@ -553,15 +553,9 @@ 553 553 Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure. 554 554 555 555 556 -==== 4.2.2.4 Re-upgrade the firmware ====538 +==== 4.2.2.4 For -CB /-CS model Certificate setting error/change certificate ==== 557 557 558 558 559 -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]]. 560 - 561 - 562 -==== 4.2.2.5 For -CB /-CS model Certificate setting error/change certificate ==== 563 - 564 - 565 565 (% data-sider-select-id="7c5a8abc-e707-467b-ac02-db0a89098320" %)When you set the wrong certificate or you need to re-set another certificate. 566 566 Please use the following three commands: 567 567 ... ... @@ -649,3 +649,5 @@ 649 649 [[image:image-20240528175133-19.png||height="563" width="1022"]] 650 650 651 651 [[image:image-20240528175154-20.png||height="752" width="1042"]] 628 + 629 +
- 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