Learn how a Siemens CPU runs your automation program. Work with a level crossing, a bottling line and a robot cell in live simulations, then introduce faults and watch the response. The lessons explain the Siemens tools behind those machines: OBs, optimized blocks, SCL, F-CPUs and PROFINET. You can see when the code runs, where its data lives and how the controller reaches the field.
How a Siemens CPU decides when your code runs: the startup pass, the main cycle and the interrupt OBs that preempt it. Use a live railway level crossing to follow that sequence. The lesson includes a logic-analyzer view of the CPU and shows how optimized and standard DBs affect addressing.
Find where your data lives: PLC tags, local variables and the process image. Work with the address areas (%I inputs, %Q outputs, %M bit memory), compare absolute and symbolic addressing, then see how optimized access changes the way you reach a variable.
Compare the same logic written four ways, side by side. Ladder resembles the wiring an electrician reads; FBD connects gates, SCL handles maths, and GRAPH describes a machine as a sequence of steps. Use the examples to choose a language for each block in your project.
The four block types and what each is for: organization blocks the OS calls, functions with no memory, function blocks with an instance DB, and global DBs for shared data. Single vs multi-instance, and the library discipline that keeps a fleet on one codebase.
Define a User-Defined Type once, version it, then use it in DBs, FB interfaces and HMI bindings. A change to that shared definition reaches every use of the type. Work with structs and arrays of UDTs, and organise the tag table so that you can find the data you need.
Build the operator's screen with WinCC Unified or Comfort panels. Bind screen objects to PLC tags, configure the alarm system, trends & recipes, then use the faceplate pattern to reuse one screen object for each motor on the line.
Connect the CPU to field devices. Identify the IO-controller and IO-devices, use the GSDML, assign device names & check the topology view. Work with ET 200 distributed I/O and compare RT with IRT to see which traffic gets a guaranteed slot on the wire.
Follow the separate, protected safety program in Safety Integrated. The lesson covers F-blocks & the F-runtime group, PROFIsafe telegrams over the same wire, F-addresses & passivation and reintegration, then connects SIL/PL to the safety lifecycle.
Configure a positioning axis with Technology Objects and use the PLCopen-style MC_ instructions (Power, MoveAbsolute, MoveJog) to command a servo. Work through homing, then see what the S7-1500T adds when an application needs cams and gearing.
Go online to investigate a running machine. Monitor blocks live, use watch & force tables, the diagnostic buffer that timestamps recent CPU and module events, system & supervision diagnostics, the Trace tool, and the built-in web server to inspect CPU diagnostics through a browser.
Structured Control Language end to end: declarations & #temp variables, IF/CASE/FOR/WHILE, REGION folding, calling FBs & FCs from code, slice access (%MW10.%X0), and patterns for maths and loops that are easier to express in SCL than in ladder.
The memory-layout deep dive: how optimized access packs and reorders variables for speed, why there are no byte offsets, the cost of standard access & absolute addressing, retentivity, and migrating an old standard-DB project without breaking every HMI tag.
Follow how the network exchanges data: the provider/consumer model, the bus cycle & update times, RT vs IRT scheduling, the GSDML file, assigning device names & the DCP protocol, and reading a topology mismatch from the diagnostics.
How a safety telegram stays trustworthy over an ordinary network: the F-message wrapper, the consecutive number & CRC, the F-monitoring time & watchdog, F-destination/source addresses, and the passivation that sends a faulty channel to its safe state.
Compare master copies with types in the project & global libraries. Follow a version change through the uses of a type, deploy a corporate library across a fleet, and keep twenty machines working from the same maintained source.
Identify the controllers in the cabinet: S7-1200, S7-1500 and its fail-safe F variant, the ET 200SP/pro distributed controllers, the S7-1500 Software Controller on a PC, and legacy S7-300/400. Use the controller-selection ladder to match a CPU to the machine you need to control.
TIA Portal brings PLC programming (STEP 7), HMI (WinCC), drives, safety and networks into one integrated framework. They share a project and its tags. Use the interactive integration map to follow how those parts connect and where each engineering task belongs.
How a safety program becomes demonstrably safe: inspect the collective F-signature, which acts as a tamper-evident fingerprint. Edit an F-block in the simulation and watch the signature change. Work through the acceptance test fault by fault, use the Safety Administration editor, and follow the change-management rules for who re-tests what and who signs.
Compare FCs with FBs in detail: how their memory differs, where Siemens' built-in instructions (TON, MOVE, SCALE_X…) fit as FCs & FBs, and how to read each interface section: Input, Output, InOut, Static, Temp, Constant & Return. Use the interactive tour to follow each section through to its pins.
Continue from Track 08's safety program to its validation. Change the collective F-signature in the simulation, run a six-step acceptance test with measured stop times, and learn the change-management rules for the acceptance protocol. The lesson is live; open it to work through the checks.