Softwell SINAMICS G120 — Handwritten M-Step Manual
Day 01 - Connection & First Commissioning
Practical Outcome: Connect SIMATIC STARTER V5.7 with SINAMICS G120 via USB/Ethernet, upload parameters, compare online/offline and complete quick commissioning.
A. Step-by-Step Procedure
Parameter / Wiring Reference
p0010 = 30 // Factory reset preparation p0970 = 1 // Factory reset p0304 = 400 // Rated motor voltage p0305 = 2.05// Rated motor current p0307 = 0.75// Rated motor power p0310 = 50 // Rated frequency p0311 = 1395// Rated speed p0971 = 1 // Save RAM to EEPROM
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 Day 01 - Connection & First Commissioning.
- 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
Record software version, controller/device firmware, driver and license status.
Save the project/archive name, modified block/object and parameter list.
Capture a verified screenshot, trend, alarm, tag table or measured value.
Write the pass condition, fault tested, correction made and final observation.
| Practical | Day 01 - Connection & First Commissioning | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Prepare one screenshot or handwritten note for communication setting, parameter list, wiring check, troubleshooting point and final test result of Day 01.
Expected Result and Runtime Behavior
Day 01 - Connection & First Commissioning completes with the stated configuration or code behavior, no unresolved diagnostic, a repeatable verification result and a saved evidence record.
Skills & Tools You Will Learn
Important automation skills are arranged for job-level, project-level and Industry 4.0 learning.
Softwell SINAMICS G120 — Handwritten M-Step Manual
Day 02 - Drive Macros: Fixed Speed & Analog Reference
Practical Outcome: Commission SINAMICS G120 using macro-based control for terminal commands, fixed speeds and analog speed reference.
A. Step-by-Step Procedure
Parameter / Wiring Reference
p0015 = 1 // Macro 1 example p1080 = 0.00 // Minimum frequency p1082 = 50.0 // Maximum frequency p1120 = 5.0 // Ramp-up time p1121 = 5.0 // Ramp-down time p1001 = 10.0 // Fixed speed 1 p1002 = 25.0 // Fixed speed 2 p1003 = 40.0 // Fixed speed 3
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 Day 02 - Drive Macros: Fixed Speed & Analog Reference.
- 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
Record software version, controller/device firmware, driver and license status.
Save the project/archive name, modified block/object and parameter list.
Capture a verified screenshot, trend, alarm, tag table or measured value.
Write the pass condition, fault tested, correction made and final observation.
| Practical | Day 02 - Drive Macros: Fixed Speed & Analog Reference | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Prepare one screenshot or handwritten note for communication setting, parameter list, wiring check, troubleshooting point and final test result of Day 02.
Expected Result and Runtime Behavior
Day 02 - Drive Macros: Fixed Speed & Analog Reference completes with the stated configuration or code behavior, no unresolved diagnostic, a repeatable verification result and a saved evidence record.
Softwell SINAMICS G120 — Handwritten M-Step Manual
Day 03 - Macro 7 PROFINET PLC Communication
Practical Outcome: Configure G120 with Compact / Siemens PLC style fieldbus control using PROFINET, telegram, control word, status word and speed reference.
A. Step-by-Step Procedure
Parameter / Wiring Reference
// Telegram 1 common word mapping PLC -> Drive PZD1 = STW1 Control Word PLC -> Drive PZD2 = Speed Setpoint Drive -> PLC PZD1 = ZSW1 Status Word Drive -> PLC PZD2 = Actual Speed STW1 bit 0 = ON/OFF1 STW1 bit 1 = OFF2 enable STW1 bit 2 = OFF3 enable STW1 bit 7 = Fault acknowledge
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 Day 03 - Macro 7 PROFINET PLC Communication.
- 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
Record software version, controller/device firmware, driver and license status.
Save the project/archive name, modified block/object and parameter list.
Capture a verified screenshot, trend, alarm, tag table or measured value.
Write the pass condition, fault tested, correction made and final observation.
| Practical | Day 03 - Macro 7 PROFINET PLC Communication | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Prepare one screenshot or handwritten note for communication setting, parameter list, wiring check, troubleshooting point and final test result of Day 03.
Expected Result and Runtime Behavior
Day 03 - Macro 7 PROFINET PLC Communication completes with the stated configuration or code behavior, no unresolved diagnostic, a repeatable verification result and a saved evidence record.
Why Choose Softwell Automation
Learn automation with practical examples, industrial troubleshooting approach and complete IT/OT learning path.
Softwell SINAMICS G120 — Handwritten M-Step Manual
Day 04 - Macro 21 Modbus RTU / USS Communication
Practical Outcome: Configure RS485 communication for Modbus RTU or USS and test register-based control, status and speed reference.
A. Step-by-Step Procedure
Parameter / Wiring Reference
// Typical serial settings for lab Protocol = Modbus RTU / USS Slave address = 3 Baud rate = 9600 or 19200 Parity = Even Stop bits = 1 Cable = Shielded twisted pair RS485 Termination = ON at both ends only
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 Day 04 - Macro 21 Modbus RTU / USS Communication.
- 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
Record software version, controller/device firmware, driver and license status.
Save the project/archive name, modified block/object and parameter list.
Capture a verified screenshot, trend, alarm, tag table or measured value.
Write the pass condition, fault tested, correction made and final observation.
| Practical | Day 04 - Macro 21 Modbus RTU / USS Communication | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Prepare one screenshot or handwritten note for communication setting, parameter list, wiring check, troubleshooting point and final test result of Day 04.
Expected Result and Runtime Behavior
Day 04 - Macro 21 Modbus RTU / USS Communication completes with the stated configuration or code behavior, no unresolved diagnostic, a repeatable verification result and a saved evidence record.
Course Contents / Curriculum
The curriculum follows a practical sequence from fundamentals to project integration.
Softwell SINAMICS G120 — Handwritten M-Step Manual
Day 05 - Macro 17–20 Two-Wire / Three-Wire Control
Practical Outcome: Commission terminal-based two-wire and three-wire control circuits with safe start/stop, jog, direction, fault reset and final viva.
A. Step-by-Step Procedure
Parameter / Wiring Reference
// Final handover checklist [ ] Correct macro selected [ ] Motor nameplate data verified [ ] Ramp-up / ramp-down tested [ ] DI/AI wiring checked [ ] PROFINET or Modbus tested if used [ ] Fault reset verified [ ] p0971 = 1 EEPROM save done [ ] STARTER backup archived
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 Day 05 - Macro 17–20 Two-Wire / Three-Wire Control.
- 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
Record software version, controller/device firmware, driver and license status.
Save the project/archive name, modified block/object and parameter list.
Capture a verified screenshot, trend, alarm, tag table or measured value.
Write the pass condition, fault tested, correction made and final observation.
| Practical | Day 05 - Macro 17–20 Two-Wire / Three-Wire Control | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Prepare one screenshot or handwritten note for communication setting, parameter list, wiring check, troubleshooting point and final test result of Day 05.
Expected Result and Runtime Behavior
Day 05 - Macro 17–20 Two-Wire / Three-Wire Control completes with the stated configuration or code behavior, no unresolved diagnostic, a repeatable verification result and a saved evidence record.
Frequently Asked Questions About SIMATIC Starter V5.7 SINAMICS G120 Handwritten Manual
Who can join this training?
Students, freshers, working engineers, maintenance teams and corporate plant engineers can join based on their requirement.
Is practical training included?
Yes. The training is focused on PLC, SCADA, HMI, VFD, communication, troubleshooting and project based practice.
Can I request online or corporate training?
Yes. Softwell Automation provides classroom, online, corporate and in-plant training options.
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 STARTER V5.7 where supported, the SINAMICS control-unit firmware, drive object, telegram and motor data. Enter the exact lab-tested software, firmware and hardware in the record below before course delivery; never assume cross-version compatibility.
Software build, firmware, device catalog, driver, communication interface and license status.
Use an isolated training system. Follow electrical, mechanical, process and cybersecurity controls before energizing or downloading.
Keep the source project, parameter/code export, screenshot/trend, fault test, correction and final pass result.
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
Change one approved input or parameter, predict the result, execute the test and explain any difference.
Explain the data flow, safety boundary, first diagnostic check and recovery method without opening the answer.
Add one useful function while preserving the original pass criteria, alarm behavior and rollback path.
Combine at least three practicals, submit a versioned project and evidence pack, and demonstrate repeatable recovery.
Content status: Substantively reviewed and expanded 17 July 2026. Verify release-specific details against the linked official documentation.
Five-Day Practical Navigation
Complete each day in sequence and retain the code/parameter file, runtime proof, diagnosis record and signed conclusion.