Actions
Forum Thread Details
  • State Verified Answer
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 9 subscribers
  • Views 2297 views
  • Users 0 members are here
Related

Azure OOB demo connection issue.

skruglewicz

Hello,

I had the demo working once with your Monarch free trial template.

I set it up from the helpful Workshop#2 video's and docs.

 

When the 7 day trial was up I created a new Monarch template on a new free trial version. I configured the MCU Project with the Device info as before.

 

But now when I debug the app,  it is doing some communication but the results are not showing up on the IotCentral dashboard.?

where is the data going?

DO I have to use a different MQTT broker?

I'm at a lost here?

 

Thanks in advance

Steve K

Parents
  • 0 in reply to skruglewicz

    Hi Steve,

     

    The things that can change when you create a new templace instance are the device info and primary key information.

     

    I'd probably start my debug by verifying the following files within your IDE are configured correctly for the new template/device.

     

    msft_Azure_IoT_cientcredential.h

    msft_Azure_IoT_cientcredential_keys.h

     

    If those are configured correctly please let me know and I can help further.

     

    -Josh

  • 0 in reply to jafoste4

    I'll check again, but I believe I followed your directions in your workshop part2?

     

    On Iot Central I opened my device which I created on my 2nd free 7 day template. I Opened the "Connect" dialog  and using the information to fill in the following info in the code

     

    1) In your MCU application, navigate to msft_Azure_IoT\demo section

    then open :

    msft_Azure_IoT_clientcredential.h

     

     

    Copy the Scope ID (ID Scope) and Device ID values to the header file

         #define clientcredentialAZURE_IOT_SCOPE_ID ""

         #define clientcredentialAZURE_IOT_DEVICE_ID ""

     

     

    Edit line #22, adding the Azure DPS provisioning service as the MQTT Broker Endpoint

    "global.azure-devices-provisioning.net"

     

    2) This application also includes some code to support the simpler Shared Access Signature (SAS) authentication. This requires SAS Primary Key for connecting your real device also needs to be added. While still in this Device      Connection window, click on Shared Access Signature (SAS) then copy to the clipboard the Primary key that is displayed…

     

     

    Back in MCUXpresso, under the msft_Azure_IoT\demo section that you accessed before, open

    msft_Azure_IoT_clientcredential_keys.h

    and edit line 14, adding the SAS Primary Key that you have just copied from the      Azure IoT Central application

         #define keyDEVICE_SAS_PRIMARY_KEY       ""

     

    I'll try again

    Steve K

Reply
  • 0 in reply to jafoste4

    I'll check again, but I believe I followed your directions in your workshop part2?

     

    On Iot Central I opened my device which I created on my 2nd free 7 day template. I Opened the "Connect" dialog  and using the information to fill in the following info in the code

     

    1) In your MCU application, navigate to msft_Azure_IoT\demo section

    then open :

    msft_Azure_IoT_clientcredential.h

     

     

    Copy the Scope ID (ID Scope) and Device ID values to the header file

         #define clientcredentialAZURE_IOT_SCOPE_ID ""

         #define clientcredentialAZURE_IOT_DEVICE_ID ""

     

     

    Edit line #22, adding the Azure DPS provisioning service as the MQTT Broker Endpoint

    "global.azure-devices-provisioning.net"

     

    2) This application also includes some code to support the simpler Shared Access Signature (SAS) authentication. This requires SAS Primary Key for connecting your real device also needs to be added. While still in this Device      Connection window, click on Shared Access Signature (SAS) then copy to the clipboard the Primary key that is displayed…

     

     

    Back in MCUXpresso, under the msft_Azure_IoT\demo section that you accessed before, open

    msft_Azure_IoT_clientcredential_keys.h

    and edit line 14, adding the SAS Primary Key that you have just copied from the      Azure IoT Central application

         #define keyDEVICE_SAS_PRIMARY_KEY       ""

     

    I'll try again

    Steve K

Children
No Data