Softwell ABB Drive — Handwritten M-Step Manual
Day 01 - Drive Composer Pro Connection, Upload & Motor ID
Practical Outcome: Install Drive Composer Pro V2.9, connect ACS580/ACS880 through USB or Ethernet, upload parameter backup, run setup assistant and complete motor identification.
A. Step-by-Step Procedure
Parameter Reference
99.04 = DTC control mode 99.06 = Motor nominal voltage 99.07 = Motor nominal current 99.08 = Motor nominal power 99.09 = Motor nominal frequency 99.10 = Motor nominal speed 99.13 = Motor ID run selection 96.06 = Restore factory defaults
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 - Drive Composer Pro Connection, Upload & Motor ID.
- 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 - Drive Composer Pro Connection, Upload & Motor ID | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Show online connection, uploaded backup file, motor data entry screen, ID run result and saved parameter backup.
Expected Result and Runtime Behavior
Day 01 - Drive Composer Pro Connection, Upload & Motor ID 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 ABB Drive — Handwritten M-Step Manual
Day 02 - Parameter Groups, Application Macros & Speed Reference
Practical Outcome: Understand ABB parameter groups, apply standard macros, configure start/stop source, speed reference and basic limits.
A. Step-by-Step Procedure
Typical Parameter Checklist
Group 10 = Digital input / output settings Group 20 = Start / stop / direction commands Group 22 = Speed reference selection Group 23 = Speed control / ramps Group 30 = Limits and protections Group 31 = Fault functions Group 99 = Motor data and control mode
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 - Parameter Groups, Application Macros & Speed 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 - Parameter Groups, Application Macros & Speed Reference | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Create a parameter change sheet showing macro name, command source, reference source, ramps and speed limits.
Expected Result and Runtime Behavior
Day 02 - Parameter Groups, Application Macros & Speed Reference completes with the stated configuration or code behavior, no unresolved diagnostic, a repeatable verification result and a saved evidence record.
Softwell ABB Drive — Handwritten M-Step Manual
Day 03 - I/O Configuration, Monitoring & Fault Diagnostics
Practical Outcome: Wire and test digital/analog I/O, monitor live status, diagnose alarms/faults and prepare a troubleshooting checklist.
A. Step-by-Step Procedure
Diagnostics Checklist
Check 01 actual values before reset. Check terminal status before changing DI assignment. Check Group 31 fault functions and history. Check motor current during acceleration. Check DC bus voltage before opening panel.
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 - I/O Configuration, Monitoring & Fault Diagnostics.
- 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 - I/O Configuration, Monitoring & Fault Diagnostics | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Submit I/O test sheet, monitor screenshots and one fault diagnostic note with probable cause and corrective action.
Expected Result and Runtime Behavior
Day 03 - I/O Configuration, Monitoring & Fault Diagnostics 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 ABB Drive — Handwritten M-Step Manual
Day 04 - Fieldbus Communication with PLC / SCADA
Practical Outcome: Configure ABB drive fieldbus for EtherNet/IP, PROFIBUS or Modbus communication and test control word, status word and speed reference.
A. Step-by-Step Procedure
PLC Mapping Example
Drive_CmdWord : WORD // PLC to Drive Drive_SpeedRef : INT // PLC to Drive Drive_StatusWord : WORD // Drive to PLC Drive_ActualSpeed : INT // Drive to PLC Drive_FaultCode : WORD // Drive to PLC
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 - Fieldbus Communication with PLC / SCADA.
- 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 - Fieldbus Communication with PLC / SCADA | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Demonstrate fieldbus start/stop, speed command, status word monitoring and communication fault reaction.
Expected Result and Runtime Behavior
Day 04 - Fieldbus Communication with PLC / SCADA 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 ABB Drive — Handwritten M-Step Manual
Day 05 - Advanced Drive Features, Backup & Final Capstone
Practical Outcome: Use advanced monitoring, trends, safety awareness, PID/application features and complete final ABB drive commissioning demonstration.
A. Step-by-Step Procedure
Final Handover Folder
01_Pre_Backup.acp 02_Final_Backup.acp 03_Parameter_Change_Report.pdf 04_IO_Test_Checklist.xlsx 05_Fieldbus_Tag_List.xlsx 06_Final_Commissioning_Report.pdf
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 - Advanced Drive Features, Backup & Final Capstone.
- 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 - Advanced Drive Features, Backup & Final Capstone | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Daily Practice / Viva
Participant must demonstrate full commissioning flow and submit final backup, parameter report and troubleshooting note.
Expected Result and Runtime Behavior
Day 05 - Advanced Drive Features, Backup & Final Capstone completes with the stated configuration or code behavior, no unresolved diagnostic, a repeatable verification result and a saved evidence record.
Frequently Asked Questions About ABB ACS580 / ACS880 Drive Composer Pro 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 Drive Composer 2.x, ACS580 or ACS880 firmware, motor nameplate data and the selected fieldbus option. 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.