Softwell Digital Practical Manual
Practical 01 - Create GX Works3 Project
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 GX Works3 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 GX Works3 Project | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Create GX Works3 Project is completed, verified and documented inside the GX Works3 PLC 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 PLC Series and CPU
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 PLC Series and CPU.
- 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 PLC Series and CPU | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Select PLC Series and CPU is completed, verified and documented inside the GX Works3 PLC 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 Communication
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 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 | Configure Communication | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Configure Communication is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 04 - Create Device Labels
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Device Labels.
- 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 Device Labels | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Create Device Labels is completed, verified and documented inside the GX Works3 PLC 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 - Digital Input Test
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Digital Input 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 | Digital Input Test | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Digital Input Test is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Course Contents / Curriculum
The curriculum follows a practical sequence from fundamentals to project integration.
Softwell Digital Practical Manual
Practical 06 - Digital Output Test
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Digital Output 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 | Digital Output Test | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Digital Output Test is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Frequently Asked Questions About GX Works3 PLC Programming Manual MELSEC PLC 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 - Start Stop Ladder Logic
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Start Stop Ladder Logic.
- 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 | Start Stop Ladder Logic | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Start Stop Ladder Logic is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 08 - Timer Practical
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Timer 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 | Timer Practical | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Timer Practical is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 09 - Counter Practical
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Counter 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 | Counter Practical | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Counter Practical is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 10 - Analog Scaling Logic
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Analog Scaling Logic.
- 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 | Analog Scaling Logic | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Analog Scaling Logic is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 11 - Data Register Practical
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Data Register 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 | Data Register Practical | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Data Register Practical is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 12 - Interlock Logic
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Interlock Logic.
- 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 | Interlock Logic | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Interlock Logic is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 13 - Alarm Bit Logic
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Bit Logic.
- 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 Bit Logic | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Alarm Bit Logic is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 14 - Convert and Build Project
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Convert and Build 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 | Convert and Build Project | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Convert and Build Project is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 15 - Write to PLC
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Write to PLC.
- 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 | Write to PLC | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Write to PLC is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 16 - Online Monitor Test
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Online Monitor 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 | Online Monitor Test | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Online Monitor Test is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 17 - Device Batch Monitor
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Device Batch Monitor.
- 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 | Device Batch Monitor | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Device Batch Monitor is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 18 - Connection Troubleshooting
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Connection Troubleshooting.
- 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 | Connection Troubleshooting | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Connection Troubleshooting is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 19 - Mini Machine Sequence
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 Mini Machine Sequence.
- 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 | Mini Machine Sequence | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Mini Machine Sequence is completed, verified and documented inside the GX Works3 PLC Programming Manual workflow.
Softwell Digital Practical Manual
Practical 20 - Final GX Works3 PLC Project
Philosophy: Open the software, open the Softwell manual, and perform the practical.
Setup: Engineering laptop, Mitsubishi PLC or simulator, Ethernet/USB connection
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 GX Works3 PLC 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 GX Works3 PLC Project | Pass condition | Observed result matches the stated objective and can be repeated. |
|---|---|---|---|
| Evidence filename | ________________ | Trainer / self-check | ________________ |
Expected Result
Final GX Works3 PLC Project is completed, verified and documented inside the GX Works3 PLC 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 GX Works3 Version 1.x or the installed release, iQ-F or iQ-R CPU firmware, module profiles and simulator version. 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.