Recent changes to Infrastructure

Infrastructure modified by h-hermsen

h-hermsen — Mon, 20 Sep 2021 19:12:35 -0000

Infrastructure modified by h-hermsen

h-hermsen — Mon, 20 Sep 2021 19:11:34 -0000

--- v3
+++ v4
@@ -17,10 +17,9 @@
 **Information and guides**
 [Sparkplug™ information](General Sparkplug info) | [Preview how-to](Preview how-to) | [Setup a test system with Ignition Primary Host](Setup a test system with Ignition Primary Host) | [Add SparkplugB to an existing CODESYS project](Add SparkplugB to existing CODESYS project)

-
+[[section bgcolor=white color=black align=left]]
 ![SparkplugB Architecture](https://forge.codesys.com/prj/mqttsparkplugb/screenshot/mqtt%20sparkplug%20b%20architecture.png?raw)

-[[section bgcolor=white color=black align=left]]
 ## MQTT-Server

 This is maybe the simplest part of the Sparkplug infrastructure. Once you have an MQTT V3.1.1 compliant server up and running on hardware sized to manage all the expected traffic, configure the appropriate access controls for the level of risk of your application, and that's it!

Infrastructure modified by h-hermsen

h-hermsen — Mon, 20 Sep 2021 19:10:58 -0000

--- v2
+++ v3
@@ -20,42 +20,42 @@

 ![SparkplugB Architecture](https://forge.codesys.com/prj/mqttsparkplugb/screenshot/mqtt%20sparkplug%20b%20architecture.png?raw)

-[[section bgcolor=lightgrey color=black align=left]]
+[[section bgcolor=white color=black align=left]]
 ## MQTT-Server

 This is maybe the simplest part of the Sparkplug infrastructure. Once you have an MQTT V3.1.1 compliant server up and running on hardware sized to manage all the expected traffic, configure the appropriate access controls for the level of risk of your application, and that's it!
 MQTT communicates over a single (inbound to the server) TCP port. This means every other node in the network need only have outbound firewall rules, which on most systems are allow all by default.
 If required, many Open Source MQTT Server implementations are available which offer multiple server instances for redundancy, high availability, and scalability. Sparkplug is able to take advantage of these MQTT features with no extra effort.

-[[section bgcolor=white color=black align=left]]
+[[section bgcolor=lightgrey color=black align=left]]
 ## MQTT Edge of Network Node (Edge)

 An MQTT Edge of Network Node (EoN) is any V3.1.1 compliant MQTT Client application that manages an MQTT Session and provides the physical and/or logical gateway functions required to participate in the Topic Namespace and Payload definitions of Sparkplug over MQTT. 
 In CODESYS context the EoN is instantiated once within a program on a PLC near the edge of the network. 
 Usually a single EoN instance per outgoing connection is necessary. The EoN node is responsible for any local protocol interface to existing legacy devices like other PLCs, RTUs, Flow Computers, Sensors, etc. and/or any local discrete I/O or any logical internal variables. 

-[[section bgcolor=lightgrey color=black align=left]]
+[[section bgcolor=white color=black align=left]]
 ## MQTT Enabled Device (a 'Sparkplug')
 This represents any device, sensor, or hardware that directly connects to MQTT infrastructure using a compliant MQTT 3.1.1 connection with the payload and topic notation as outlined in the Sparkplug specification. 
 **Note that it will be represented as an EoN node in the Sparkplug topic payload.**

-[[section bgcolor=white color=black align=left]]
+[[section bgcolor=lightgrey color=black align=left]]
 ## Device/Sensor

 The Device/Sensor represents any physical or logical device connected to the MQTT EoN providing any data, process variables or metrics. This can be seen as any data from PLCs, RTUs, Flow Computers, Sensors, etc. and/or any local discrete I/O or any logical internal variables. 

-[[section bgcolor=lightgrey color=black align=left]]
+[[section bgcolor=white color=black align=left]]
 ## SCADA/IIoT Host Node (Primary Node)

 The SCADA/IIoT Host Node is any MQTT Client application that subscribes to and publishes messages. 
 In typical SCADA/IIoT infrastructure implementations, there will be only **one** Primary SCADA/IIoT Host Node responsible for the monitoring and control of a given group of MQTT EoN nodes. Sparkplug does support the notion of multiple critical Host applications. This does *not* preclude any number of additional MQTT SCADA/IIoT Nodes participating in the infrastructure that are in either a pure monitoring mode, or in the role of a hot standby should the Primary MQTT SCADA/IIoT Host go offline.

-[[section bgcolor=white color=black align=left]]
+[[section bgcolor=lightgrey color=black align=left]]
 ## MQTT Application Node

 An MQTT Application Node is any non-primary MQTT SCADA/IIoT Client application that consumes the real-time messages or any other data being published with proper permission and security.We

-[[section bgcolor=lightgrey color=black align=left]]
+[[section bgcolor=white color=black align=left]]
 ## Roles and functions

 Function        | MQTT Broker | EoN Node | Device/Sensor | SCADA/IIot Host node | Application Node

Infrastructure modified by h-hermsen

h-hermsen — Mon, 20 Sep 2021 19:09:45 -0000

--- v1
+++ v2
@@ -1,12 +1,12 @@
 [[startpage]]
-[[section align=right]]
-
-@hermsen
-@i-campbell
-
+[[section bgcolor=darkgrey color=white align=right]]
 [[img src=https://forge.codesys.com/svn/prj,cfunit,code/trunk/www/logo_codesys_forge.png height=96p align=left]][[img src=https://forge.codesys.com/prj/mqttsparkplugb/screenshot/co5e%20sparkplug%20bolt%20logo%20round%20blue.png height=96p align=left]]

-[[section bgcolor=white color=black align=center]]
+[[members]]
+Sparkplug™ and the Sparkplug™ logo are trademarks of the Eclipse Foundation
+Copyright © 10/11/19 Eclipse Foundation, Inc. https://www.eclipse.org/legal/efsl.php
+
+[[section bgcolor=darkgrey color=white align=center]]
 # SparkplugB Infrastructure Definitions
 **This Page**
 [MQTT-Server](#MQTT-Server) | [EoN](#EoN) | [Sparkplug](#Sparkplug) | [Device/Sensor](#Device/Sensor) | [SCADA/IIoT Host Node](#SCADA/IIoT Host Node) | [MQTT Application Node](#MQTT Application Node) | [Roles and functions](#Roles and functions)

Infrastructure modified by h-hermsen

h-hermsen — Wed, 11 Aug 2021 19:55:26 -0000

@hermsen
@i-campbell

SparkplugB Infrastructure Definitions

General Sparkplug info
Infrastructure | Security | Messages

Information and guides
Sparkplug™ information | Preview how-to | Setup a test system with Ignition Primary Host | Add SparkplugB to an existing CODESYS project

MQTT-Server

This is maybe the simplest part of the Sparkplug infrastructure. Once you have an MQTT V3.1.1 compliant server up and running on hardware sized to manage all the expected traffic, configure the appropriate access controls for the level of risk of your application, and that's it!
MQTT communicates over a single (inbound to the server) TCP port. This means every other node in the network need only have outbound firewall rules, which on most systems are allow all by default.
If required, many Open Source MQTT Server implementations are available which offer multiple server instances for redundancy, high availability, and scalability. Sparkplug is able to take advantage of these MQTT features with no extra effort.

MQTT Edge of Network Node (Edge)

An MQTT Edge of Network Node (EoN) is any V3.1.1 compliant MQTT Client application that manages an MQTT Session and provides the physical and/or logical gateway functions required to participate in the Topic Namespace and Payload definitions of Sparkplug over MQTT.
In CODESYS context the EoN is instantiated once within a program on a PLC near the edge of the network.
Usually a single EoN instance per outgoing connection is necessary. The EoN node is responsible for any local protocol interface to existing legacy devices like other PLCs, RTUs, Flow Computers, Sensors, etc. and/or any local discrete I/O or any logical internal variables.

MQTT Enabled Device (a 'Sparkplug')

This represents any device, sensor, or hardware that directly connects to MQTT infrastructure using a compliant MQTT 3.1.1 connection with the payload and topic notation as outlined in the Sparkplug specification.
Note that it will be represented as an EoN node in the Sparkplug topic payload.

Device/Sensor

The Device/Sensor represents any physical or logical device connected to the MQTT EoN providing any data, process variables or metrics. This can be seen as any data from PLCs, RTUs, Flow Computers, Sensors, etc. and/or any local discrete I/O or any logical internal variables.

SCADA/IIoT Host Node (Primary Node)

The SCADA/IIoT Host Node is any MQTT Client application that subscribes to and publishes messages.
In typical SCADA/IIoT infrastructure implementations, there will be only one Primary SCADA/IIoT Host Node responsible for the monitoring and control of a given group of MQTT EoN nodes. Sparkplug does support the notion of multiple critical Host applications. This does not preclude any number of additional MQTT SCADA/IIoT Nodes participating in the infrastructure that are in either a pure monitoring mode, or in the role of a hot standby should the Primary MQTT SCADA/IIoT Host go offline.

MQTT Application Node

An MQTT Application Node is any non-primary MQTT SCADA/IIoT Client application that consumes the real-time messages or any other data being published with proper permission and security.We

Roles and functions

Function	MQTT Broker	EoN Node	SCADA/IIot Host node	Application Node
Relay Messages	x
publish xDATA		x
publish xBIRTH		x
publish DDEATH		x
Last will NDEATH		x
Read xCMD		x	?	x
Read xDATA			x	x
publish xCMD			x
publish STATE			x
last will STATE			x
Read STATE		x	x	x
Read xBIRTH			x	x
Read xDEATH			x	x