Course Overview for Siemens PLC (Intermediate Level — SIMATIC S7-300 with TIA Portal V16)
Course Objectives
Minimize downtime and reduce reliance on machine makers, indirectly enhancing productivity.
Most unplanned stoppages are not a failed controller. They are a field device, a network fault, or a condition the program is correctly reporting but nobody on site can read — so every stoppage escalates to the machine maker. This course trains the team to read an existing S7-300 program in TIA Portal V16, go online with a running machine, interpret the controller’s own diagnostics, and isolate a fault to field, program or network before calling the OEM. The focus is interpretation and method, not writing new code.
Methodology
Software: TIA Portal V16 (STEP 7 Professional)
Delivery: Instructor-led with live demonstrations on S7-300 hardware
Who Should Attend
Engineer and above
Duration
2 Days
Course Content
Day 1 — Understanding the System and Reading the Program
S7-300 Hardware and Architecture
- CPU, signal modules and rack / slot rules — and how slot position decides I/O addresses.
- Micro Memory Card as load memory, work memory, and retentive M / T / C / DB areas.
- The scan cycle, cycle monitoring time, and why it changes how you read everything online.
TIA Portal V16 and Existing Plant Projects
- Project view, project tree, and the software and licences the plant needs to be self-sufficient.
- Opening an existing project — including migrating a STEP 7 V5.x project and what does not survive.
- Archives, working folders, and which copy is the master.
Hardware Configuration and Addressing
- Reading the configured rack against the physical panel; order number and firmware matching.
- How a program address maps to a terminal in the panel.
- Analog channels: measuring range, wire break, scaling, and what a reading stuck at full scale means.
Program Structure and Block Types
- OB1, OB100, OB35 and the error OBs (OB82, OB86, OB121, OB122) — and why a missing one stops the CPU.
- FC, FB, instance and global DB; absolute addressing such as DB10.DBW20.
- Following the call structure, and recognising mode control, step chains, interlocks and alarm words.
Reading the S7-300 Instruction Set
- Bit logic, set / reset and edge detection.
- S7-300 timers and counters (S_ODT, S5T#10s, S_CU / S_CUD) and IEC timers where the OEM used them.
- Recognising LAD, FBD, STL and SCL — enough STL to read old OEM code.
- Reading interlocks backwards, from the output that will not energise to the condition blocking it.
Going Online with a Running Machine
- Connecting over MPI, PROFIBUS or Ethernet, and why a connection fails.
- Program status: what the green highlight shows and what it hides.
- Watch tables, and modify value versus force — including why a forgotten force becomes a future breakdown.
Day 2 — Diagnosing Faults and Restoring Production
Diagnostics Fundamentals
- Decoding the CPU LEDs — RUN, STOP, SF, BF, DC5V, FRCE.
- The diagnostic buffer: reading entries and separating the original cause from its consequences.
- Module and station diagnostics, cycle time and memory load; CPU web server where supported.
Systematic Fault-Finding
- Triage first: field, program, network or power.
- Symptom to signal — find the output, find its coil, trace the conditions; using cross-reference.
- Comparing offline against online to find undocumented changes.
- Worked cases: a sequence stuck at a step; an analog reading frozen; an intermittent stop with no alarm.
PROFIBUS DP, MPI and PROFINET Faults
- DP addresses, baud rate, termination, repeaters, and reading the BF LED.
- Recovering after a slave, drive or I/O module is replaced — addresses and GSD files.
- Common failures: wrong address or device name, duplicate IP, bad termination, damaged or badly earthed cable.
HMI and Alarm Handling
- Tracing an on-screen value or alarm back to the controller tag behind it.
- Bit alarms versus analog limit alarms, and how alarm words are organised.
- Using alarm history to find the first alarm among the consequential ones.
Backup, Restore and Safe Modification
- Upload from device — what can and cannot be recovered.
- A plant backup routine, and the MMC procedure for replacing a failed CPU.
- Download in RUN or STOP, what happens to DB actual values, and what must never be touched — safety blocks, protected OEM blocks, warranty.
Downtime Reduction in Practice
- Building the in-house capability: access, software, licences, spare adapters and cards.
- The documentation set every machine should have, and how to get it from the machine maker.
- Spares strategy now that the S7-300 range is past order stop.
- Guided case study: one full breakdown, from first alarm to restored production.


