Softwell Digital Practical Manual
Practical 01 - Create GOT2000 Project
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Create GOT2000 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
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 | Create GOT2000 Project | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Create GOT2000 Project is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Talk to Automation Advisor
Get expert guidance for course selection, corporate training, project support and practical learning path.
Softwell Digital Practical Manual
Practical 02 - Select GOT Model
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Select GOT Model.
- 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 | Select GOT Model | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Select GOT Model is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Skills & Tools You Will Learn
Important automation skills are arranged for job-level, project-level and Industry 4.0 learning.
Softwell Digital Practical Manual
Practical 03 - Configure PLC Connection
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Configure PLC Connection.
- 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 | Configure PLC Connection | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Configure PLC Connection is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 04 - Create Base Screen
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Create Base Screen.
- 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 | Create Base Screen | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Create Base Screen is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Why Choose Softwell Automation
Learn automation with practical examples, industrial troubleshooting approach and complete IT/OT learning path.
Softwell Digital Practical Manual
Practical 05 - Add Lamp Object
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Add Lamp Object.
- 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 | Add Lamp Object | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Add Lamp Object is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Course Contents / Curriculum
The curriculum follows a practical sequence from fundamentals to project integration.
Softwell Digital Practical Manual
Practical 06 - Add Switch Object
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Add Switch Object.
- 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 | Add Switch Object | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Add Switch Object is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Frequently Asked Questions About GOT2000 HMI Programming Manual GOT HMI Practical 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.
Softwell Digital Practical Manual
Practical 07 - Add Numerical Display
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Add Numerical Display.
- 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 | Add Numerical Display | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Add Numerical Display is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 08 - Add Numerical Input
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Add Numerical Input.
- 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 | Add Numerical Input | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Add Numerical Input is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 09 - Create Motor Control Screen
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Create Motor Control Screen.
- 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 | Create Motor Control Screen | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Create Motor Control Screen is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 10 - Alarm Display Setup
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Alarm Display Setup.
- 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 | Alarm Display Setup | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Alarm Display Setup is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 11 - History Display Setup
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 History Display Setup.
- 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 | History Display Setup | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
History Display Setup is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 12 - Trend Graph Setup
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Trend Graph Setup.
- 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 | Trend Graph Setup | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Trend Graph Setup is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 13 - Recipe Data Practical
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Recipe Data Practical.
- 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 | Recipe Data Practical | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Recipe Data Practical is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 14 - User Security Setup
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 User Security Setup.
- 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 | User Security Setup | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
User Security Setup is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 15 - Screen Navigation
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Screen Navigation.
- 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 | Screen Navigation | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Screen Navigation is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 16 - GOT Simulator Test
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 GOT Simulator Test.
- 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 | GOT Simulator Test | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
GOT Simulator Test is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 17 - Download to GOT
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Download to GOT.
- 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 | Download to GOT | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Download to GOT is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 18 - Communication Diagnostics
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Communication 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 | Communication Diagnostics | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Communication Diagnostics is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 19 - Backup GOT Project
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 Backup GOT 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
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 | Backup GOT Project | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Backup GOT Project is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
Softwell Digital Practical Manual
Practical 20 - Final GOT2000 HMI Project
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, GOT HMI project, PLC tags/devices or simulator
A. Step-by-Step Procedure
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 GOT2000 HMI 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
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 | Final GOT2000 HMI Project | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Final GOT2000 HMI Project is completed, verified and documented inside the GOT2000 HMI Programming Manual workflow.
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 GT Works3 Version 1.x or the installed GT Designer3 release, GOT firmware, PLC driver and transfer interface. 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.