Machine Integration & Data Capture¶
Home / Engineering / System Design / CAM Pipeline / Machine Integration
Status: Skeleton
This document is a starting point. Sections marked with TBD need to be filled in.
Purpose¶
Handle the transfer of validated manufacturing plans to the physical machine (Sinumerik One controller), manage execution, and capture machine telemetry that feeds back into AutoCAM and simulation models.
Responsibilities¶
- Send validated NC programs, fixture information, and stock details to the machine
- Manage the interface with the Sinumerik One controller
- Stream machine telemetry during cutting for model training and process monitoring
- Close the feedback loop: real-world data improves AutoCAM decisions and simulation accuracy
What Gets Sent to the Machine¶
- G-code (validated NC program)
- Generated fixture information (e.g. soft-jaw geometry)
- Stock specification
- Clamping setup and tool requirements (as needed)
Controller Simulation for Development¶
A virtual controller environment (e.g. Siemens VNCK / Create MyVirtualMachine) can be used to develop and validate machine interactions before the physical machine is available. This also serves as part of the CI/testing pipeline.
Interfaces¶
| Direction | System | Data |
|---|---|---|
| Input | Machine Simulation | Selected plan with validated NC program and assets |
| Output | Physical machine (Sinumerik One) | NC program, tool data, work offsets, fixture models |
| Output | AutoCAM Pipeline | Machine telemetry and cutting data for model training |
| Output | Operations Integration | Job status, completion events |
Open Questions¶
- What is the exact OPC UA interface available on our Sinumerik One variant?
- What machine data should be captured and at what frequency?
- Storage and retention strategy for high-frequency telemetry data