This guide will walk you though integrating an Iridium CloudConnect terminal to Azure IoT Hub using an available solution template.
If you do not have an IoT Hub, or need help getting the credentials for your IoT Hub, check out this guide:
Before continuing, you will need to ensure you have the proper information from Iridium, as well as have configured your AWS SQS queues so that you can establish a connection.
Account ID
, it can be found in the top-right menu in the AWS Console.Access Key ID
and Secret Access Key
.region
where your SQS queues are deployed.You will need to import two solution templates, one for the N-Link connection, and one for the IoT Hub connection. Follow the steps below to import the solution templates:
Click Solution Templates at the bottom of any page.
Find the Iridium CloudConnect quickstart template and click Import.
Follow the instructions below to import the template:
Access Key ID
from #2 above.Secret Access Key
from #2 above.AWS Region
from #2 above.AWS Account ID
from #2 above.Find the Iridium to Azure IoT Hub template and click Import.
Follow the instructions below to import the template:
You should receive an import result like this:
Additionally you should check the services list and ensure that all services are marked Healthy
.
Now that everything has been imported, you can start receiving data. For detailed instructions on how to use your Iridium terminal, please consult your Iridium product documentation.
AT+SBDWT=temp,26.2,hum,46
AT+CSQ (repeat until CSQ is >3)
AT+SBDIX
+SBDIX:<MO status>,<MOMSN>,<MT status>,<MTMSN>,<MT length>,<MT queued>
You want to see the MO status
of 0 to indicate that the message was successfully sent. At this point you can check the IoT Bridge to ensure there was activity on the MO Listener trigger, and IoT Hub to see data in the device twin.
Message to Device
to send a message to your device.AT+CSQ (repeat until CSQ is >3)
AT+SBDIX
AT+SBDRT