Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 195 views
  • Users 0 members are here
Related

Azure IoT Central Getting Started Guide

joelpa

In the section below of the 'Getting Started Guide', the last line refers to an archive "SelfSignedCertificateGeneration.zip" but I see no path, link or anyway to find the archive.  I cannot move forward without the certificates.

 

Create X.509 certificates

For easier onboarding and test, a self-signed certificate will be used. OpenSSL executed from Windows PowerShell command-line tool, is used to generate the certificates.

Note however that this method is not recommended for production!

The script file and root certificates are provided separately in this archive:

SelfSignedCertificateGeneration.zip

  • 0

    Hi Joel,

     

    Thanks for pointing this out.

     

    I have updated the tutorial linking to the SelfSignedCertificateGeneration.zip file.

    for download.

     

    -Josh

     

  • 0 in reply to jafoste4

    Thanks Josh, the link was very helpful!  I have succeeded in connecting to Verizon and am provisioned at Azure IOT Central, however no data or device info is being transmitter.  Suggestions?  BTW I assumed that stepping over the debug breakpoints is the correct thing to do.  That results in 1 thread running.

    Regards

  • 0 in reply to joelpa

    Hi Joel,

     

    How do you know it connected successfully? Did you connect to the terminal via tera term and view it connect?

     

    I assume when you say step over debug breakpoints your refering to hitting the resume correct?

     

    Thx,

    Josh

  • 0 in reply to jafoste4

    Also try to send data to the board to verify your connection is correct. When connected, go to Settings in the dashboard, turn an led on and then hit save.

     

    -Josh

  • 0 in reply to jafoste4

    Hi,

     

    Also just to make you aware, i have pushed an update today that enabled SAS authentication, no longer requireing the x509 certificates. The documentaiton is updated.

     

    -Josh

  • 0 in reply to jafoste4

    >>How do you know it connected successfully?

    Azure IOT central device status changed from registered to provisioned

     

    >>Did you connect to the terminal via tera term and view it connect?

    Please explain how.  I am not aware but that would be very useful.

     

    >> I assume when you say step over debug breakpoints your refering to hitting the resume correct?

    I had been 'stepping over breakpoints" several times, thanks for the tip.

     

    >>Also just to make you aware, i have pushed an update today that enabled SAS authentication, no longer requireing the x509 certificates.    The documentaiton is updated.

    Oh Joy!  I had been using SAS and when I switched to x509 it worked!  I had believed SAS was simpler but with the update either should work?

    Thank you for the support.  I feel like I am on the bleeding edge of the Monarch-Go from AVnet.

  • 0 in reply to joelpa

    Hi Joel,

     

    I am happy to help here!

     

    To connect to a terminal do the following.

     

    1. Download / install Tera Term or another terminal program - https://ttssh2.osdn.jp/index.html.en

    2. Connect P6 (debug link) on lpc55s69-evk to your PC (this also powers the board)

    3. Open Tera Term

    4. Open Setup -> Serial Port

    5. Set the following accordingly and select ok

     

    Both x509 and SAS should work if you get the latest source code from github. SAS is a lot simpiler to setup/use for development in my opinion.

     

    -Josh

  • 0 in reply to jafoste4

    MQTT dies after some point.  It happens every time  I found a discussion on freeRTOS and this appears to be a common problem.

    https://forums.freertos.org/t/aws-mqtt-connection-dies-after-some-point/8977/35    The good part is way at the bottom with a small timing graph.  There is also a patch but Azure mods complicate things.

    https://github.com/aws/amazon-freertos/pull/2064/files

     

    I thought this was worth sharing and perhaps others are having the same issue.. Here is a snippet with the PINGRESP

     

    ..>>>>>>>>>>>>>>>>>>>>>>

    OK

    205 3403734 [Microsoft Azure] [INFO ][MQTT][3403734] (MQTT connection 0x200129d0) MQTT PUBLISH operation queued.

    206 3403744 [Microsoft Azure] Successfully Publi

    > to LOC_TELEMETRY Topic

     

    OK

    AT+SQNSSENDEXT=1,69

    > 705E98443E9E453BC75B158D8C552851589928F91E2FBEA2B00EC070225EEB3E5ED1065721C8F50BFC97A

    OK

    213 3635826 [iot_thread] [ERROR][MQTT][3635826] (MQTT connection 0x200129d0) Failed to receive PINGRESP within 1000 ms.

    214 3635826 [iot_thread] [INFO ][MQTT][3635826] (MQTT connection 0x200129d0) Network connection closed.

     

    +SQNSRING: 1,69

    AT+SQNSRECV=1,69

     

    +SQNSRECV: 1,69559B50340B75228FD0ACAE39677C87F336F29D12D87F33B7A31A3FFACD24EFFC2CB770A

     

    OK

    215 3647991 [Microsoft Azure] [WARN ][MQTT][3647991] (MQTT connection 0x200129d0) Attempt to use closed connection.

    216 3648001 [Microsoft Azure] [ERROR][MQTT][3648001] (MQTT connection 0x200129d0) New operation record cannot be created for a closed connection

    217 3648015 [Microsoft Azure] Unsuccessfully Publish to CELLULAR_TELEMETRY Topic

    218 3648022 [Microsoft Azure] Disconnect

    219 3648026 [Microsoft Azure] [INFO ][MQTT][3648026] (MQTT connection 0x200129d0) Disconnecting connection.

    220 3648036 [Microsoft Azure] [INFO ][MQTT][3648036] (MQTT connection 0x200129d0) Network connection closed.

    AT+SQNSH=1

     

    OK

    221 3648070 [Microsoft Azure] [INFO ][MQTT][3648070] (MQTT connection 0x200129d0) Network connection destroyed.

    222 3648080 [Microsoft Azure] Invalid Application State!!

    223 3648085 [Microsoft Azure] Closing Azure Demo

     

     

    Rehards,

    Joel