How cybusio/example-how-to-connect-heidenhain-dnc works
1. heidenhain-example-commissioning-file.yml – This YAML file is used for commissioning, meaning it configures and defines connection parameters and device-specific settings for the Heidenhain system.
2. nodered-flow.json – This JSON file represents a Node-RED flow that likely shows how data and control signals are processed between systems (or between a Node-RED environment and the physical device).
• Main components:
• Heidenhain DNC Device: The target hardware which the commissioning file is meant to configure.
• Commissioning File (YAML): Represents the configuration/connection settings and “rules” used to commission or invoke the connection with the device.
• Node-RED Flow: Acts as the middleware or orchestrator, processing inputs/outputs, routing messages, and handling any transformations necessary in communicating with the Heidenhain device.
• (Optional) External Systems: If the lesson covers integration with broader systems (for monitoring, data logging or UI), include a component that represents these external elements.
• And illustrate relationships:
• That the Commissioning File provides parameters/settings that are consumed by either the Node-RED flow or a dedicated configuration module (if envisioned).
• Architectural patterns and principles:
• Although a full MVC or microservices pattern isn’t used here, the design still separates configuration (commissioning file) from process orchestration (Node-RED flow), underscoring the principle of separation of concerns.
• Use clear labels: Label nodes such as “Commissioning File (YAML),” “Node-RED Flow,” and “Heidenhain DNC Device.”