Apply the ten tracks to a bottle-capping cell. Define the data, write the reusable logic, add the operator's screen, connect the field I/O and guard the machine with the F-CPU safety program. Each build step uses a concept from the course, so you can follow that concept from its lesson into the running cell. Complete the build, then run the simulation.
Click through the steps in order, or select a different order to explore the sandbox. Each step adds a piece to the cell above, explains the relevant course concept and links back to its track. Once all six pieces are in place, press ▶ Run cell to cap bottles, and hit the E-stop to see the F-CPU safety layer override the standard machine command in this simulation.
The project brings these parts together: data → logic → I/O → HMI → safety → diagnostics. Follow each part from its definition to its role in the cell. The F-CPU handles the safety function; an HMI button or an interlock in ordinary PLC logic is not a substitute for that safety program.
🧠 How it thinks: the scan cycle & OBs (T01), the process image & tags (T02), and the four languages (T03) determine how the program runs.
🧩 How it's built: blocks & reuse (T04), UDTs (T05), libraries & versioning (D5) let you use FB_Capper as a reusable block for each cell.
🔌 How it connects: WinCC HMI (T06), PROFINET & the field (T07), and the internals (D3) connect the cell to operators and I/O.
🛡️ How it stays safe & alive: the fail-safe F-CPU (T08) and PROFIsafe (D4) handle the safety side. Motion (T09) and diagnostics (T10) cover movement and the information you use to investigate faults.
In this capping cell, the operator's HMI "Start" button is pressed but the cell won't cap. The E-stop is released. Where do you look first?