MQTT messages emitted by the application are routed to a configurable topic. In this way, data consumers can deliberately subscribe only to those topics which are relevant to them. In addition, topics can be used to structure the data flows within a shop floor environment.
During commissioning of the data streaming feature (section Configuring MQTT data streaming) you defined a mandatory global MQTT topic. All messages generated by the current SINUMERIK Data Recorder instance will be sent to this topic. In addition to that you can define several sub-topics at the level of individual recording jobs (see section Creating a new job). Then, these messages can be routed to external MQTT brokers by using an MQTT client e.g. Flow Creator. The MQTT client needs to subscribe to this global topic or sub-topics that are defined in SINUMERIK Data Recorder. A possible strategy of structuring the data flows could be choosing a unique identifier of the machine as a global topic and use the topics defined at recording job level to describe the specific manufacturing operation.
Example:
global topic=”MACHINE_A”
job-level topic=”tapping/M8-40”
Data recorded by this job will be available on the IE Databus on the following topic:
“MACHINE_A/tapping/M8-40”
When using Flow Creator, you can directly forward to external MQTT broker with the same topic.