Sparkplug Troubleshooting: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
= Introduction = | = Introduction = | ||
A Sparkplug system typically consists of an MQTT broker, Sparkplug edge nodes, and one or more Sparkplug host applications. Various kinds of issues can arise in a Sparkplug system. Since the Sparkplug edge nodes and host applications commonly connect to the MQTT broker, one group of issues is related to such MQTT connections. Then, there are issues specific to Sparkplug edge nodes, and issues specific to Sparkplug host applications. Also, even if the Sparkplug edge node and the host application successfully communicate with the MQTT broker, they may not "understand" themselves properly. | A Sparkplug system typically consists of an MQTT broker, Sparkplug edge nodes, and one or more Sparkplug host applications. Various kinds of issues can arise in a Sparkplug system. Since the Sparkplug edge nodes and host applications commonly connect to the MQTT broker, one group of issues is related to such MQTT connections. Then, there are issues specific to Sparkplug edge nodes, and issues specific to Sparkplug host applications. Also, even if the Sparkplug edge node and the host application successfully communicate with the MQTT broker, they may not "understand" themselves properly. | ||
| Line 8: | Line 7: | ||
* [[Troubleshooting Sparkplug Edge Nodes]] | * [[Troubleshooting Sparkplug Edge Nodes]] | ||
* [[Troubleshooting Sparkplug Host Applications]] | * [[Troubleshooting Sparkplug Host Applications]] | ||
= Troubleshooting Tools = | |||
== Other Sparkplug components == | |||
As in similar cases where two or more communication parties are involved, if you have a situation in which your Sparkplug host application does not receive data from your Sparkplug edge node (or cannot send commands to it), you can get insight into the situation by replacing one or both these Sparkplug components with a different one. For example, if your host application cannot receive data from your edge node, but it can receive data from other edge nodes, the problem is likely in your edge node, and not in the host application. | |||
Similar procedure can be used for problems related to MQTT communication with the broker (try a different Sparkplug component, or a different broker). | |||
== SparkplugCmd Utility == | |||
== MQTT Explorer == | |||
== Wireshark == | |||
Revision as of 15:23, 20 October 2025
Sparkplug is a trademark of Eclipse Foundation, Inc. "MQTT" is a trademark of the OASIS Open standards consortium. Other related terms are trademarks of their respective owners. Any use of these terms on this site is for descriptive purposes only and does not imply any sponsorship, endorsement or affiliation.
Introduction
A Sparkplug system typically consists of an MQTT broker, Sparkplug edge nodes, and one or more Sparkplug host applications. Various kinds of issues can arise in a Sparkplug system. Since the Sparkplug edge nodes and host applications commonly connect to the MQTT broker, one group of issues is related to such MQTT connections. Then, there are issues specific to Sparkplug edge nodes, and issues specific to Sparkplug host applications. Also, even if the Sparkplug edge node and the host application successfully communicate with the MQTT broker, they may not "understand" themselves properly.
For troubleshooting discussions related specifically to Sparkplug edge nodes or host applications, see
Troubleshooting Tools
Other Sparkplug components
As in similar cases where two or more communication parties are involved, if you have a situation in which your Sparkplug host application does not receive data from your Sparkplug edge node (or cannot send commands to it), you can get insight into the situation by replacing one or both these Sparkplug components with a different one. For example, if your host application cannot receive data from your edge node, but it can receive data from other edge nodes, the problem is likely in your edge node, and not in the host application.
Similar procedure can be used for problems related to MQTT communication with the broker (try a different Sparkplug component, or a different broker).
SparkplugCmd Utility
MQTT Explorer
Wireshark
(tbd)
MQTT Explorer...
