Note: This class is available to those who have attended previous TW Controls classes and is a self paced review. While Tim is present, he is not guiding the curriculum.

Some topics others have benefited from:

Fundamentals and Logic. Revist the core components of your PLC trainer. Spend the first hour ensuring your wiring is correct and that you can establish communication with your PLC using the appropriate software (e.g., Studio 5000 or Connected Components Workbench).

• Wiring and Communication: Confirm your connections between the PLC, power supply, and I/O devices. Practice uploading and downloading a blank program to the PLC to confirm your communication is stable.

• Basic Programming: Create a simple start/stop circuit using pushbuttons and a motor. Expand on this by adding a latching function.

• Timers and Counters: Practice with timers (TON, TOF) and counters (CTU, CTD) by programming a sequence. For example, program a button press to start a motor for a set duration, or to count the number of times a sensor is activated before an action is triggered.

Advanced Systems. More complex systems that are common in industrial settings.

• Analog I/O: Focus on an analog signal, such as a 4-20mA or 0-10VDC input. Use scaling instructions (CPT, SCL) to convert the raw data from your analog device into meaningful engineering units. Practice using this scaled value to control an output, like a variable frequency drive (VFD).

• Ethernet Communications: Configure and troubleshoot an Ethernet I/O module or a VFD connected over the network. Practice adding the device to your PLC's I/O configuration and exchanging data. A practical exercise would be to program an alarm that activates if the Ethernet connection to a device is lost.

Troubleshooting and Review. Focus to diagnosing and resolving common issues. This is the most crucial part of your practice, as it prepares you for real-world scenarios.

• Deliberate Faults: Introduce a fault to your system. This could be a loose wire, an incorrect IP address, or a simple programming error. Use your newfound skills to systematically trace and fix the issue.

• Documentation and Review: End the day by reviewing your code and documenting your solutions. This not only helps you recall the information later but also prepares you for real-world projects where clear, well-documented code is essential.

Project Development. Sometimes you just need a little time and equipment to debug an upcoming project.