This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TIDEP0084: stackArmor doesn't provide required credentials

Part Number: TIDEP0084
I'm trying to evaluate the TIDEP0084 Sub-1 GHz Sensor to Cloud Industrial IoT Gateway Reference Design for Linux Systems from TI.
Section 3.1.2.7.2 AWS Certificates and Configuration From stackArmor stipulates
To connect the IoT Gateway to the AWS IoT service, the gateway needs authentication certificates provisioned by AWS. For these certificates, as well as a unique AWS URL, see the stackArmor web page[8]. Return to this guide once obtaining the following:
• certificate.pem.crt
• private.pem.key
• public.pem.key
• root-CA.crt
• a URL to the AWS host that should be used

I provided all the relevant information and requested the credentials, to no avail. I received a canned answer asking for more details, when I've already communicated the only goal was to evaluate the TIDEP0084.

  • Is the stackArmor support for the TIDEP0084 terminated?
  • What are the alternatives?

Thank you and best regards,

  • The factory team have been notified. They will respond here.
  • Dear Rei VILO:

    We regret the inconvenience caused, but we are providing a fully hosted and managed IOT service that demonstrates the Sensor data in a stackArmor Developed Dashboard and Application hosted by us in AWS. Our terms of service do not allow us to share such access without first ascertaining the use case and the organization behind the request. For convenience, the terms of service are reproduced below.

    Please read the following terms of service for access to the demo dashboard –

    • You must have the Board and sensors already purchased and setup prior to requesting for access to the Dashboard.
    • Based on our terms of service, this demo dashboard is only available to bonafide companies or organizations that share their intent of use and their use case description with us.
    • We must be able to verify your organization, your website and your contact information prior to making access available

    We understanding if you are unwilling or unable to share this information, and encourage you to use the AWS IOT Gateway to setup your own demo environment. You can find out more information about the AWS IOT solution in the link below.

    Sincerely,

    GP

     

  • Thank you for your answers. Actually, I provided all the information and comply with the requisites.

    I've just sent you a private message with more details.
  • Rei,

    Have you been able to access the demo yet?

    Jason Reeder
  • CloudPalGP said:

    We regret the inconvenience caused, but we are providing a fully hosted and managed IOT service that demonstrates the Sensor data in a stackArmor Developed Dashboard and Application hosted by us in AWS. Our terms of service do not allow us to share such access without first ascertaining the use case and the organization behind the request. For convenience, the terms of service are reproduced below.

    Unfortunately, those terms of service are mentioned neither on the Sub-1 GHz Sensor to Cloud Industrial IoT Gateway Reference Design for Linux Systems (ACTIVE) TIDEP0084main page nor on Element14 6100023_US -  Development Kit, SimpleLink Sub-1GHz Sensor to Cloud, US Version page, as they should be.

    If the TIDEP0084 kit is only for "bonafide companies or organizations", please mention it clearly before a would-be customer proceeds with the order.

    Failing to mention it may qualify as false advertising and/or hidden defect.

  •  

    Thank you for the update.

    The answer is no, unfortunately. I'm still waiting for the credentials from stackArmor to connect to AWS.

    It looks like the TIDEP0084 kit is only for "bonafide companies or organizations". 

    The question now is: is there an alternative solution I can use with a MQTT broker running on a local server?

  • Rei,

    Have you seen this document:www.ti.com/.../swru533.pdf? It describes an IBM demo as well as a locally hosted demo that does not have any dependencies on StackArmor.

    Jason Reeder

  • Thanks for the hint.

    I've focused so far on the main document, i.e. Sub-1 GHz Sensor to Cloud Industrial Internet of Things (IoT) Gateway Reference (Rev. C) (tiduci9) as the additional document Sub-1 GHz Sensor-to-Cloud Linux® E14 Kit (swru533) comes from a reseller.

    Having two competing documents is rather confusing. Why the former document doesn't mention the latter?

    Furthermore, on page 8 of document swru533, the link Local Gateway (see Section 8) points to Troubleshooting page 19, not the expected local gateway.

    As the micro-SD card has been used for the procedure of document tiduci9, I need to find and restore the image of the pre-flashed micro-SD card mentioned in document swru533.

    I'll give a try and let you know.

  • Hey Rei,

    You can create the image yourself by simply cloning the Sensor To Cloud repo (git://git.ti.com/apps/tidep0084.git) and run the setup_beaglebone.sh script. If you do not have the wireless cape that comes with the IoT kit then do not agree to setup wireless.

    When launching the gateway you can provide the following parameters to the 'run_demo.sh' script to select which cloud provider you want: 'aws', 'ibm', 'quickstart

    , or 'localhost'. The ibmoption requires some additional steps mentioned in the document Jason provided, and aws is the StackArmor option. You can choose quickstart to view data on the cloud with the IBM quickstart gui, or localhost to view information locally. The localhost webserver is hosted on port 1350, so you can navigate to <bbb_ip_addr>:1350 to view the web gui

  • Thank you for the useful pointers. I managed to get it working!

    I would suggest to consolidate the two PDF documents swru533 and tiduci9 into one single document.

    Now, the question is how to interface this with a local MQTT server.