Philosophy: Open the software, open the Softwell manual, and perform the practical.
SCL ProgrammingPLC LogicFunctionsAutomation
Software: TIA Portal with SCL / Structured Control Language editor Setup: Engineering laptop, PLC simulator or training PLC, sample I/O tags
A. Step-by-Step Procedure
01
STEP 01
Create FB_Sequence_Control in SCL.
v
02
STEP 02
Declare StepNo as static integer.
v
03
STEP 03
Use CASE StepNo OF to build sequence steps.
v
04
STEP 04
Add transition conditions for Start, SensorDone and Reset.
v
05
STEP 05
Monitor StepNo while running simulation.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Machine Sequence in SCL.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Machine Sequence in SCL
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
SCL sequence logic moves through machine steps in the correct order.
P18
Softwell Digital Practical Manual
Practical 18 - SCL Diagnostics Watch Table
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SCL ProgrammingPLC LogicFunctionsAutomation
Software: TIA Portal with SCL / Structured Control Language editor Setup: Engineering laptop, PLC simulator or training PLC, sample I/O tags
A. Step-by-Step Procedure
01
STEP 01
Create a watch table for SCL block inputs, outputs and static variables.
v
02
STEP 02
Add key variables such as StepNo, RunMemory and FaultCode.
v
03
STEP 03
Go online or start simulation.
v
04
STEP 04
Force or modify inputs carefully as per trainer instruction.
v
05
STEP 05
Observe how SCL variables change during execution.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for SCL Diagnostics Watch Table.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
SCL Diagnostics Watch Table
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Watch table helps diagnose SCL logic and internal variables.
P19
Softwell Digital Practical Manual
Practical 19 - Optimize and Comment SCL Code
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SCL ProgrammingPLC LogicFunctionsAutomation
Software: TIA Portal with SCL / Structured Control Language editor Setup: Engineering laptop, PLC simulator or training PLC, sample I/O tags
A. Step-by-Step Procedure
01
STEP 01
Open one completed SCL block.
v
02
STEP 02
Add clear comments above major logic sections.
v
03
STEP 03
Rename unclear variables to meaningful names.
v
04
STEP 04
Remove unused temporary variables.
v
05
STEP 05
Compile and confirm zero errors after cleanup.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Optimize and Comment SCL Code.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Optimize and Comment SCL Code
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
SCL code is readable, maintainable and compiles cleanly.
P20
Softwell Digital Practical Manual
Practical 20 - Final SCL Programming Project
Philosophy: Open the software, open the Softwell manual, and perform the practical.
SCL ProgrammingPLC LogicFunctionsAutomation
Software: TIA Portal with SCL / Structured Control Language editor Setup: Engineering laptop, PLC simulator or training PLC, sample I/O tags
A. Step-by-Step Procedure
01
STEP 01
Build one integrated SCL project using motor latch, analog scaling and sequence logic.
v
02
STEP 02
Add fault code generation and watch table diagnostics.
v
03
STEP 03
Call all required SCL blocks from the main program.
v
04
STEP 04
Run simulation or hardware test for the complete flow.
v
05
STEP 05
Archive the final project and record expected results.
B. Verification Checklist
The project/configuration completes without an unresolved compile or device error.
Online, simulation or runtime values respond in the expected sequence for Final SCL Programming Project.
Critical addresses, parameters, units and initial states are checked against the lab sheet.
The saved project can be reopened and the result reproduced without hidden manual correction.
C. If the Result Is Wrong
Symptom
Probable cause
Diagnostic check
Corrective action
Compile or configuration error
Unresolved device, tag, type, address or parameter
Open the first diagnostic entry and trace it to the configured object
Correct the source item, compile again and save a new evidence record
No online/runtime response
Wrong connection, command source, permissions or scan state
Monitor live values from input through logic to output
Restore the verified connection/state and repeat one controlled test
Unstable or unexpected value
Scaling, initial state, timing or version mismatch
Compare raw and engineering values and review the installed version
Correct scaling/state, reset the lab safely and retest
D. Student Evidence Record
Environment
Record software version, controller/device firmware, driver and license status.
Project evidence
Save the project/archive name, modified block/object and parameter list.
Runtime evidence
Capture a verified screenshot, trend, alarm, tag table or measured value.
Conclusion
Write the pass condition, fault tested, correction made and final observation.
VERIFIED SCREENSHOT / TREND / TAG-TABLE EVIDENCE
Insert a real capture from the learner's lab. Do not use a fabricated software screenshot.
Practical
Final SCL Programming Project
Pass condition
Observed result matches the stated objective and can be repeated.
Evidence filename
________________
Trainer / self-check
________________
Expected Result
Final SCL project demonstrates reusable functions, function blocks, diagnostics and complete machine logic.
Authentic Training Evidence
Watch Related Siemens PLC Training Videos
See Softwell Automation's practical teaching style directly on this page. The selected lesson and complete series help learners and companies verify the technology coverage before making an enquiry.
Featured practical: TIA Selection Tool and Automation Part Selection
Verify: Test minimum, midpoint, maximum and divide-by-zero prevention in the calling block.
Interlock with clear priority
Separate permissive, start and fault-reset decisions.
MotorPermissive := EStopHealthy AND GuardClosed AND NOT Overload;
IF ResetFault AND OverloadHealthy THEN
MotorFault := FALSE;
END_IF;
MotorRun := StartCmd AND MotorPermissive AND NOT MotorFault;
Verify: Force each permissive false and confirm the output drops safely.
FOR loop across an array
Process a bounded array and avoid an index outside the declared range.
Total := 0.0;
FOR Index := 0 TO 9 DO
Total := Total + Samples[Index];
END_FOR;
Average := Total / 10.0;
Verify: Test known sample values and compare the calculated average.
CASE state machine
Keep transitions visible and define a safe default state.
CASE State OF
0: IF StartCmd THEN State := 10; END_IF;
10: IF StepDone THEN State := 20; END_IF;
20: IF CycleDone THEN State := 0; END_IF;
ELSE
State := 0;
END_CASE;
Verify: Test normal transitions, reset and an invalid state.
Rising-edge command
Run a one-scan action from a maintained operator command.
StartEdge(CLK := StartCmd);
IF StartEdge.Q THEN
BatchCounter := BatchCounter + 1;
END_IF;
Verify: Hold StartCmd true and confirm the counter changes only once.
Reusable alarm limits
Create consistent warning and trip logic with hysteresis handled by the caller.
HighWarning := ProcessValue >= WarningLimit;
HighTrip := ProcessValue >= TripLimit;
StatusCode := 0;
IF HighWarning THEN StatusCode := 1; END_IF;
IF HighTrip THEN StatusCode := 2; END_IF;
Verify: Sweep the process value through both limits and record transitions.
Practice, Viva and Mini-Project
Practice: Modify one input, predict the result, execute the code and compare the output.
Viva: Explain the data flow, failure behavior, safe-use boundary and recovery method.
Mini-project: Combine at least three examples into one reviewed, versioned solution with an evidence pack.
Acceptance: A second learner can run the saved solution and reproduce the documented result.
Before You Start: Prerequisites, Tested Version, Safety and Evidence
This manual is a practical training workbook, not a substitute for the installed product manual or the site's approved engineering procedure. Record the exact software, firmware, license and hardware before following a step because menus and supported functions can vary by release.
Tested-version planning scope: Confirm TIA Portal V18 or V19 SCL, the target controller firmware, data-access mode and current IEC-style syntax. Enter the exact lab-tested software, firmware and hardware in the record below before course delivery; never assume cross-version compatibility.
Environment record
Software build, firmware, device catalog, driver, communication interface and license status.
Safe lab boundary
Use an isolated training system. Follow electrical, mechanical, process and cybersecurity controls before energizing or downloading.
Evidence pack
Keep the source project, parameter/code export, screenshot/trend, fault test, correction and final pass result.
Technical review
Last reviewed by Softwell Automation Technical Training Team on 17 July 2026.
Field
Learner record
Verification
Software / firmware
________________
Matches the training device and official compatibility information
Project / backup
________________
Saved before and after the practical
Pass evidence
________________
Runtime value, trend, alarm, diagnostic or report attached
Fault tested
________________
Symptom, cause, check and corrective action documented
Practice, Viva and Extension Challenge
Practice
Change one approved input or parameter, predict the result, execute the test and explain any difference.
Viva
Explain the data flow, safety boundary, first diagnostic check and recovery method without opening the answer.
Extension challenge
Add one useful function while preserving the original pass criteria, alarm behavior and rollback path.
Graded mini-project
Combine at least three practicals, submit a versioned project and evidence pack, and demonstrate repeatable recovery.