Page History

...

The document comprises these sections:

Provisioning the 'Thing'

Before configuring MQTT Engine or MQTT Transmission, you must register a 'thing' connection in AWS IoT Core. Begin by browsing to AWS IoT Core in your AWS account. Make sure you are in the same AWS region that you intend to connect the MQTT Module to. Begin by expanding 'Secure' and click 'Policies' as shown below.

...

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

Anchor
engine engine

Configuring MQTT Engine

Using the Ignition Gateway Web UI, browse to the Ignition 'Config > MQTT Engine 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

Configuring 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:

...

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

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

...

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.

...

Select and subscribe on # to receive all published messages

On a Transmission refresh Refresh you will see all DEATH messages published on the disconnect along with the new BIRTH messages on the reconnect.