Page History

...

• UUID.certificate.pem.crt
• UUID.private.pem.key
• AmazonRootCA1.pem

Anchor
engine engine

MQTT Engine

For this example we'll be using MQTT Engine. However, the steps are very similar for MQTT Transmission with regard to connection establishment. Using the Ignition Gateway Web UI, browse to the Igntion Ignition 'Config → > MQTT Engine /Transmission settings page'Settings > Servers' page. Now click the 'Certificates' tab as shown below:

...

This will allow MQTT Engine to buffer messages and reorder them should they be delivered out of order within a 3 second window. Generally 3 seconds seems to be plenty of time for the reordering with AWS IoT Core.

Anchor
transmission transmission

MQTT Transmission

Using the Ignition Gateway Web UI, browse to the Ignition 'Config > MQTT Transmission Settings > Servers' page. Now click the 'Certificates' tab as shown below:

Image Added

Now click the 'Create new Certificate' link. Then upload one of the three files previously downloaded when creating the IoT Core 'Thing'. Once completed, your Certificates page should look similar to the following with all three files.

Image Added

Now, click the 'Servers' tab as shown below.

Image Added

Select 'Create a new MQTT Server' link which will bring up the following page.

Image Added

Set the following.

• Name
  • AWS IoT Core
• URL
  • The URL that was captured from the AWS IoT Core setting page. It should be of the form: ssl://ENDPOINT_URL:8883
  • Example: ssl://a33fdj134jkj10-ats.iot.us-east-1.amazonaws.com:8883
• Server Set
  • Default
• Username
  • Blank
• Password
  • Blank
  • Note if a password was previously set, make sure to click the 'Change Password' checkbox and ensure the password fields are empty
• CA Certificate File
  • The 'Root CA' that was downloaded from AWS IoT Core
• Client Certificate File
  • The 'Client Cert' that was downloaded from AWS IoT Core
• Client Private Key File
  • The 'Client Private Key' that was downloaded from AWS IoT Core.

Leave all other fields blank and submit the configuration.

Image Added

Configure an Transmitter as shown below and use Ignition Designer to created an appropriate tag tree in the default provider Image Added

Image Added

The server connection will now show the connected client as '1 of 1'

Image Added

To confirm messages are published from Transmission, navigate to the Ignition logs and Refresh Transmission. This will cause the client to disconnect and reconnect and publish its BIRTH messages.

The SparkplugTransmissionClient logger will show the NBIRTH and DBIRTH messages pushed.

Image Added

To confirm messages are received as AWS IoT Core. ON your AWS account, navigate to AWS IoT > Test > MQTT test client.Image Added

Select and subscribe on # to receive all published messages

Image Added

On Transmission refresh you will see all DEATH messages published along with the new BIRTH messages. Image Added