Page History

...

• Group ID

  • This identifies a logical grouping of Edge nodes and devices. This can be a region, a facility name, or any meaningful grouping of Edge Nodes within your application.

• Message Type

  • The message_type component of the topic namespace signals how the MQTT payload should be processed. The following message_type components are defined for the Sparkplug topic namespace:

    CL Modules Sparkplug message types and how they differ: Edge node BIRTH certificate. This is a startup message from an Edge node to announce its presence and share its configurations.

    CL Modules Sparkplug message types and how they differ: Notification of an edge node’s disconnection or failure.

    CL Modules Sparkplug message types and how they differ: Device BIRTH certificate. This is a startup message from a device to announce its presence and share its configurations.

    CL Modules Sparkplug message types and how they differ: Notification of a device’s disconnection or failure.

    CL Modules Sparkplug message types and how they differ: Data messages from an edge node which include edge node metric data.

    CL Modules Sparkplug message types and how they differ: Data messages from a device which include device metrics.

    CL Modules Sparkplug message types and how they differ: Command to an edge node.

    CL Modules Sparkplug message types and how they differ: Command to a device.

    CL Modules Sparkplug message types and how they differ: It represents the state of the primary host application. Edge nodes subscribe to it to get the online status of the host.

• Edge Node ID
  • The ID of the logical Edge Node. This is often the name of the system running Ignition with MQTT Transmission or Injectors.
• Device ID (Optional)
  • The ID of a device attached to the Ignition instance. This can be a PLC or logical grouping of tags that represent a physical or logical device connected to Ignition.

Payload

The payload contains the following :

...