Changes for page Dragino NB device connection to AWS platform instructions

Last modified by Mengting Qiu on 2025/03/06 13:42

From version < 23.7 >

edited by Xiaoling
on 2024/05/29 09:56

To version < 24.6 >

edited by Xiaoling
on 2024/05/30 10:26

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- image-20240529164339-1.png

Details

Page properties

Content

@@ -34,9 +34,9 @@
  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:
--(% data-sider-select-id="7bc0f6db-481d-435a-ad0c-92cf0ede3ea4" %)
--(% data-sider-select-id="8026a4d9-df91-4895-b9c5-3d6ac9b46012" %)**{**
++**{**
++
  **~  "Version": "2012-10-17",**
  **~  "Statement": [**
@@ -99,9 +99,9 @@
  (% style="color:blue" %)**5. When you click to create things, the certificate download page will pop up**
--(% data-sider-select-id="398c8d35-75ff-4077-85bb-9e0377efa186" %)
--(% 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.
++**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.
++
  Please download all the following certificates and put them in a folder.
  [[image:image-20240528173926-10.png]]
@@ -114,9 +114,11 @@
  = 4. Connect to AWS using Dragino-NB device =
--== 4.1 Upgrade the firmware to configure TTS firmware to set the certificate ==
++== 4.1 For -NB /-NS model ==
++=== 4.1.1 Upgrade the firmware to configure TTS firmware to set the certificate ===
++
  User can change device firmware to::
  * Update with new features.
@@ -123,7 +123,7 @@
  * Fix bugs.
--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"]]**
++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"]]**
  Methods to Update Firmware:
@@ -131,18 +131,227 @@
  * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
++=== 4.1.2 Configure certificate ===
--== 4.2 Configure certificate ==
++After upgrade the firmware, the serial port displays as follows：
++[[image:image-20240528174330-13.png||height="286" width="568"]]
++
++==== 4.1.2.1  Configure CA certificate ====
++
++
++Please input the certificate in PEM format for the user.
++
++Use the AT command AT+CACERT as follows:
++
++AT+CACERT=~-~-~-~--BEGIN CERTIFICATE~-~-~-~--
++
++MIIDQTCCAimgAwIBAgITBmyfz5m/jAo54vB4ikPmljZbyjANBgkqhkiG9w0BAQsF
++
++ADA5MQswCQYDVQQGEwJVUzEPMA0GA1UEChMGQW1hem9uMRkwFwYDVQQDExBBbWF6
++
++b24gUm9vdCBDQSAxMB4XDTE1MDUyNjAwMDAwMFoXDTM4MDExNzAwMDAwMFowOTEL
++
++MAkGA1UEBhMCVVMxDzANBgNVBAoTBkFtYXpvbjEZMBcGA1UEAxMQQW1hem9uIFJv
++
++b3QgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALJ4gHHKeNXj
++
++ca9HgFB0fW7Y14h29Jlo91ghYPl0hAEvrAIthtOgQ3pOsqTQNroBvo3bSMgHFzZM
++
++9O6II8c+6zf1tRn4SWiw3te5djgdYZ6k/oI2peVKVuRF4fn9tBb6dNqcmzU5L/qw
++
++IFAGbHrQgLKm+a/sRxmPUDgH3KKHOVj4utWp+UhnMJbulHheb4mjUcAwhmahRWa6
++
++VOujw5H5SNz/0egwLX0tdHA114gk957EWW67c4cX8jJGKLhD+rcdqsq08p8kDi1L
++
++93FcXmn/6pUCyziKrlA4b9v7LWIbxcceVOF34GfID5yHI9Y/QCB/IIDEgEw+OyQm
++
++jgSubJrIqg0CAwEAAaNCMEAwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMC
++
++AYYwHQYDVR0OBBYEFIQYzIU07LwMlJQuCFmcx7IQTgoIMA0GCSqGSIb3DQEBCwUA
++
++A4IBAQCY8jdaQZChGsV2USggNiMOruYou6r4lK5IpDB/G/wkjUu0yKGX9rbxenDI
++
++U5PMCCjjmCXPI6T53iHTfIUJrU6adTrCC2qJeHZERxhlbI1Bjjt/msv0tadQ1wUs
++
++N+gDS63pYaACbvXy8MWy7Vu33PqUXHeeE6V/Uq2V8viTO96LXFvKWlJbYK8U90vv
++
++o/ufQJVtMVT8QtPHRh8jrdkPSHCa2XV4cdFyQzR1bldZwgJcJmApzyMZFo6IQ6XU
++
++5MsI+yMRQ+hDKXJioaldXgjUkK642M4UwtBV8ob2xJNDd2ZhwLnoQdeXeGADbkpy
++
++rqXRfboQnoZsG4q5WTP468SQvvG5
++
++~-~-~-~--END CERTIFICATE~-~-~-~--}
++
++(% style="color:red" %)**Note: Be sure to add a terminator "}" at the end of the command. Otherwise, the command will not execute successfully.**
++
++[[image:image-20240528174408-14.png]]
++
++
++After successful execution, as shown in the following figure.
++
++[[image:image-20240528174502-15.png]]
++
++Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
++
++
++==== 4.1.2.2 Configure client certificate ====
++
++
++Use the AT command AT+CLICERT as follows：
++
++AT+CLICERT=~-~-~-~--BEGIN CERTIFICATE~-~-~-~--
++
++MIIDWTCCAkGgAwIBAgIUYSpJUzfb4NTa76JJxd2th0fZA8swDQYJKoZIhvcNAQEL
++
++BQAwTTFLMEkGA1UECwxCQW1hem9uIFdlYiBTZXJ2aWNlcyBPPUFtYXpvbi5jb20g
++
++SW5jLiBMPVNlYXR0bGUgU1Q9V2FzaGluZ3RvbiBDPVVTMB4XDTI0MDUyNDA4MDI0
++
++NVoXDTQ5MTIzMTIzNTk1OVowHjEcMBoGA1UEAwwTQVdTIElvVCBDZXJ0aWZpY2F0
++
++ZTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMTdc1GQLVBohAeCJD6n
++
++6WTFAFrygTch90a5wUr2bhlVuDxvEhEKNcmu5vOCo5agmfLWb2VCxgezgvQOBYQ8
++
++1oTqXJNdl4tS0DICfqb/ogVHWGHRao67XyhbPNBS0j/nCPTIIk6+/NBeYPOjaG+p
++
++utfXE7SGIEcc3RevkYkUJx6y+WH7MLjj1mufuXBVWIL1RrfrIRPw6auVk7dhS5rU
++
++NvYcJa7Qd6gpAh1DzPj7ZECrv7fEIIBDEsSYOy6ToWtzqGIVcIAHBDfORB0Hcm+N
++
++7wG3KDf61P4aWkLlkP5pRUaUIQdVblxginmx2K3n8t/WP7QcfITa191rjEVVBXmk
++
++ROsCAwEAAaNgMF4wHwYDVR0jBBgwFoAUs8Caohh1ZGP8kjSn3rtxJiJJ9IswHQYD
++
++VR0OBBYEFCjwGwqD7FG9UCNm3wjFQX4HixzfMAwGA1UdEwEB/wQCMAAwDgYDVR0P
++
++AQH/BAQDAgeAMA0GCSqGSIb3DQEBCwUAA4IBAQBgqI49a4PBQZYrFM63TX3EHgdd
++
++N6Pj7AytjO+SrKNMCSo/OtIvhDTxOocr1vKrux1Tw5qmrllrIXLtlGtbmln5DS6a
++
++DTCLrjwcIFIabLxpx5DPY1WSMYvL04SW7d4Y+3SxOFNRotDSiomr8eIIac0d3HE2
++
++B5b0SnWZgWbrhjNUgvwo8l8tA9DOGIr2MeQ5kPjudOOiYSR3HC0v+jviBMV6VX8M
++
++LHVH3CRshHDKBGpV1NZ1RAm9EY/oRGtSiMsyjRh6hegC0vehwVxaC4w9qG0ASkzz
++
++42OOGfNqhYnYDiKTEIkazaoAFpTKDejWBaL7W5VpthUkQOl67IyX+ohuUKTo
++
++~-~-~-~--END CERTIFICATE~-~-~-~--}
++
++(% style="color:red" %)**Note: Be sure to add a terminator "}" at the end of the command. Otherwise, the command will not execute successfully.**
++
++[[image:image-20240528174630-16.png||height="553" width="747"]]
++
++Display (% style="color:blue" %)**"Successfully configured client certificate."**(%%) Configuration successful, otherwise configuration failed.
++
++
++==== 4.1.2.3 Configure client private key ====
++
++
++Use the AT command AT+CLIKEY, as shown below
++
++AT+CLIKEY=~-~-~-~--BEGIN RSA PRIVATE KEY~-~-~-~--
++
++MIIEpAIBAAKCAQEAxN1zUZAtUGiEB4IkPqfpZMUAWvKBNyH3RrnBSvZuGVW4PG8S
++
++EQo1ya7m84KjlqCZ8tZvZULGB7OC9A4FhDzWhOpck12Xi1LQMgJ+pv+iBUdYYdFq
++
++jrtfKFs80FLSP+cI9MgiTr780F5g86Nob6m619cTtIYgRxzdF6+RiRQnHrL5Yfsw
++
++uOPWa5+5cFVYgvVGt+shE/Dpq5WTt2FLmtQ29hwlrtB3qCkCHUPM+PtkQKu/t8Qg
++
++gEMSxJg7LpOha3OoYhVwgAcEN85EHQdyb43vAbcoN/rU/hpaQuWQ/mlFRpQhB1Vu
++
++XGCKebHYrefy39Y/tBx8hNrX3WuMRVUFeaRE6wIDAQABAoIBAFhAOcjvjBDGuaEw
++
++CxV3al49HfqnSZuwg0xWSztSm2qKDcwxsnSnEhO2b1vsTW9h0YGV9Vv8gg/Dvkmv
++
++23M7XqM4+IUraJsRZbl1etdcM4KQSCOZoF4Zyv+pXuq4pf31kQNCkHaikWzLUkUG
++
++FPQxr0vA49mCYwfd/ZL3ppM/0IWmxRwloV1Gb9q8iDBUcJGSDokZnT7diUxzzOcd
++
+++UJ6xUhFq1v46Y7vO+73XROLv34JEBC0bIw2ErL6+AbzhHwb2mkuSccG9Ks37g3Z
++
++dyyjjj8hm1wvHWepuWqEssaiS3HD5zAsI0v85xS8RwNj3zLfd8o1WC666n3CO+ij
++
++VdRmR4kCgYEA+/sEFxpfaRomqcLwJebZcZH06U1RfJFfnbH2/Q6fANf8zNxwWs9A
++
++O+jyk/CLhHYRIk6VIOMQmWwEYgJ2eAHfw2Diwj4/0eqkGu+yZOS6KTCewxSV73vc
++
++SvACramJy4y6yEgDN5onwR1XqfVMfA0LzTcSupHR/xvrpf/gCsNFPxUCgYEAyAFd
++
++nMUhJFSq3pOogxA43aJSkA8YuDS3jpBkKQ6vx81APpIMabQauOxFDt488TZGP3Yy
++
++lhpa/lfFIgu2K7CgV4dUp+JtJJoZ/F+ExxUUzdqB4zxzWywAcc3RebfwP6qASwFT
++
++G3mXYci4tgNWR+k5CSsuLXDk/OT5uo5GeGAEc/8CgYEAk6V8uxDP8STKnNRFpN/E
++
++b6CHciDE64m/DgbWY2cq0fK9BUjxaLRhvfj8EqVzCrWnyoNjLHcAJfW+B7PLuPvY
++
++IoJlvE1/Vb/4UnQ7ApVnY3VCwaoRRNc9uIcz+pAJ1sRqOarAf9cLDkPkNwktvM5k
++
++KOXpSnrhIms4w/bPT18l9xUCgYBsAMDKbXEuK0JyGw5+Z/4tQQCQpnZU0rLkm3ha
++
++64FkxaORplBprEZZ4cyQ8NW78/EPSAadI/JLMp5TejuPcDvFyGCgoBcMEuNBc1tC
++
++HlIzr3FAgl5Qt3wt+FTMA9YKq0nINxjn10s2FKwaLccj4f9YwiaXh0VAg22PnlDT
++
++pBYDhQKBgQCMwyKXJ4zYiDRdvLvgKzeuKaU4KNQItHE4KORPfkecjPoENt4bKxDw
++
++2EdNFQLIoqBHL1s+/8+SzhCI31V7pkTs1AqCxDExJS7+8Z5NQFQIo/jooUo0N80E
++
++y3ZZS6OLOXXscEqhMogf1grfbabXM9OkgTIq43cPQHtMGQiFAtIJkg==
++
++~-~-~-~--END RSA PRIVATE KEY~-~-~-~--}
++
++(% style="color:red" %)**Note: Be sure to add a terminator "}" at the end of the command. Otherwise, the command will not execute successfully.**
++
++[[image:image-20240528174702-17.png]]
++
++Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
++
++
++==== 4.1.2.4 Re-upgrade the firmware ====
++
++
++After the certificate configuration is completed, Re-upgrade to the firmware you originally used.
++
++
++== 4.2  For -CB /-CS model ==
++
++=== 4.2.1 Upgrade the firmware to configure TTS firmware to set the certificate ===
++
++
++User can change device firmware to::
++
++* Update with new features.
++
++* Fix bugs.
++
++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"]]**
++
++Methods to Update Firmware:
++
++* (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
++
++* Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
++
++
++
++=== 4.2.2 Configure certificate ===
++
++
  After upgrade the firmware, the serial port displays as follows：
--(% data-sider-select-id="8b6a9e23-dec0-476c-acd4-098aa19fe1f3" %)
  [[image:image-20240528174330-13.png||height="286" width="568"]]
--=== 4.2.1 Configure CA certificate ===
++==== 4.2.2.1 Configure CA certificate ====
  Please input the certificate in PEM format for the user.
@@ -201,7 +201,7 @@
  Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
--=== 4.2.2 Configure client certificate ===
++==== 4.2.2.2 Configure client certificate ====
  Use the AT command AT+CLICERT as follows：
@@ -253,7 +253,7 @@
  Display (% style="color:blue" %)**"Successfully configured client certificate."**(%%) Configuration successful, otherwise configuration failed.
--=== 4.2.3 Configure client private key ===
++==== 4.2.2.3 Configure client private key ====
  Use the AT command AT+CLIKEY, as shown below
@@ -319,14 +319,25 @@
  Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
--=== 4.3.3 Re-upgrade the firmware ===
++==== 4.2.2.4 For -CB /-CS model Certificate setting error/change certificate ====
--After the certificate configuration is completed, Re-upgrade to the firmware you originally used.
++(% data-sider-select-id="7c5a8abc-e707-467b-ac02-db0a89098320" %)When you set the wrong certificate or you need to re-set another certificate.
++Please use the following three commands：
++(% style="color:blue" %)**AT+DELCLIKEY}**
--= 5. Configure draginoNB-device =
++(% style="color:blue" %)**AT+DELCLICERT}**
++(% style="color:blue" %)**AT+DELCACERT}**
++
++
++(% style="color:red" %)**Note: 1.When there is no certificate on the device, a deletion error will be displayed.
++          2.When the device already has a certificate, using the command to configure the certificate again will display a configuration error.**
++
++
++= (% data-sider-select-id="6b5deb69-539b-42e1-a7bc-a300eb1fea73" %)5. Configure draginoNB-device(%%) =
++
  == 5.1 Configure the data format sent by the device ==
@@ -352,7 +352,7 @@
  == 5.4 Set the TLS mode ==
--(% style="color:blue" %)**AT+TLSMOD=1,2**
++(% data-sider-select-id="cf7bb573-8375-4479-9801-df8bb7dab3ba" style="color:blue" %)**AT+TLSMOD=1,2**
  To use the TLS mode certificate function, users need to configure the (% style="color:blue" %)**AT+TLSMOD**(%%) command.
@@ -363,9 +363,21 @@
  (% 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)
--Restart the device
++(% data-sider-select-id="f443b9bc-1195-4fe2-965d-7de84f78747f" %)
++== 5.5 Set the MQOS ==
++(% 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）**
++
++Please find it in AWS's MQTT test client
++
++[[image:image-20240529164339-1.png||height="480" width="927"]]
++
++
++(% data-sider-select-id="fef22158-6e5e-46e4-b59e-fe457e562376" %)
++== 5.6 Restart the device ==
++
++
  = 6. View data on AWS =
  == 6.1 Find MQTT test client in test ==
@@ -386,5 +386,3 @@
  [[image:image-20240528175133-19.png||height="563" width="1022"]]
  [[image:image-20240528175154-20.png||height="752" width="1042"]]
--
--

image-20240529164339-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Bei

Size

...	...	@@ -1,0 +1,1 @@
	1	+116.5 KB

Content

Changes for page Dragino NB device connection to AWS platform instructions

Summary

Details

Applications

Navigation