Portland Community College | Portland, Oregon

Faults can be in PLC controllers, pneumatic driven robots, DC, AC, stepper, or servo motor driven robots, can be electrical, electro-mechanical, and mechanical in nature.

Currently, we will work on SMC trainers.

Requires students to come to the lab after school to work in groups on equipment as a part of homework.

Upon completion of the course students should be able to:

• Trace signals at different points in schematics of mechatronic systems.
• Trace and probe signals on mechatronic systems guided by schematics. 
• Judge whether signals behave normally.
• Troubleshoot faults in mechatronic systems following a systematic methodology.

The course will include instructor delivered lectures and demonstrations stressing key topics in the course. In preparation for the lecture portion of the course, students will be expected to complete all reading and homework assignments. Students may build, analyze and trouble-shoot increasingly complex mechatronics systems in class. 

Students may be required to come to the lab after school to work in groups on equipment as a part of homework.

Assessment of student performance in this course will be in the form of written and/or practice-based questions. Some formal reports and presentations may also be required.

Mechatronics Troubleshooting

·         Levels of troubleshooting

·         Types of PLC faults

·         Status and diagnostic indicators

Mechatronics Power Supply Troubleshooting

·         Power supply circuit operation

·         Mechatronics power supply problems

·         Power supply troubleshooting methods

Mechatronics Input Troubleshooting

·         Discrete inputs

·         Testing discrete input devices

·         Testing discrete input modules

Mechatronics Output Troubleshooting

·         PLC force function

·         Forcing PLC inputs and outputs using variable tables

·         Testing PLC discrete output devices

·         Testing PLC discrete output modules

Trouble-shooting methodology

• Forming an objective problem statement
• Forming a clear mental picture of the entire system involved in the problem
• Designing and then carrying out quick and definitive tests to isolate the problem to a subsystem.
• Developing lists of all possible causes of the problem in an isolated sub-system.
• Designing quick and definitive tests to verify whether a possible cause is the true cause or not.
• Prioritizing to see which possible causes to check first based on the ease of the check and the probability of the cause
• Gathering and using clues to judge which path to follow. (Given the clues, what is the likely cause? Training of this judgment)