How to Learn PLC Programming From Zero in 8 Weeks

To learn PLC programming from zero in 8 weeks, study about 6 hours a week and build one small project each week in a free simulator, starting with a lamp that follows a switch and ending with a program that has a timer, a counter, an analog value and an HMI screen. You will not be an expert after 8 weeks, but you will be able to read, write and test basic ladder logic. Here is the plan.

What do you need before you start?

You need a laptop, a free simulator and a notebook. You do not need a PLC. A simulator runs the same logic, and you can use the free PLC simulator and ladder logic simulator in a browser from day one. When you want a vendor tool, use the Siemens TIA Portal course, the CODESYS course or the OpenPLC course, which all run without hardware.

Set a routine you can keep. Two study sessions of about two hours and one build session of about two hours make 6 hours.

Weeks 1 and 2: inputs, outputs and your first rung

Week 1 is about what a PLC is and how it meets the world. Learn the parts: CPU, power supply, input cards, output cards. Learn the field devices that connect to them: push buttons, limit switches, proximity sensors, lamps, contactors. Learn the difference between a normally open and a normally closed contact, and why a stop button is usually wired normally closed. Your project is a lamp that follows a switch. It is small, and it proves that you can address an input and an output and run a program.

Week 2 is the most important week of the plan, because the start/stop seal-in circuit appears in almost every machine. A start button sets a coil, a contact of that coil holds it on, and a stop button breaks the circuit. Build it for a motor. Then add an overload contact and an emergency stop input to see how real conditions enter the rung. Our post on the start/stop seal-in circuit walks through it rung by rung, and the ladder logic symbols cheat sheet helps you read the diagrams.

Weeks 3 and 4: time and counting

In week 3 you meet timers: on-delay (TON), off-delay (TOF) and pulse (TP). Your project is a delayed start for two motors, so the second starts five seconds after the first. Then make a flasher using two timers. Both exercises teach the same lesson: a timer is a small memory with a preset and an accumulated value.

Week 4 adds counters: count up, count down and both. Your project is a parts counter that lights a lamp when it reaches ten, with a reset button. Test it by forcing the input on and off, and watch the count. If you see a double count, you have met edge detection, a good topic to learn properly. Read about PLC timers and counters to compare your results with a worked example.

At the end of week 4, the most useful thing you can learn is how the controller runs your program. The PLC scan cycle explains why the order of rungs matters and why an output changes at the end of a scan, not in the middle.

Weeks 5 and 6: numbers and structure

Week 5 introduces compare instructions and math, then analog signals. Most sensors for level, pressure and temperature give a 4 to 20 mA signal. The PLC turns it into an integer, and you must scale that integer into an engineering value. Take a level transmitter with a range of 0 to 5 m. At 12 mA the signal is halfway through its span, so the level is 2.5 m. Build the scaling, then add a high-level alarm at 4 m. This is the exercise that separates people who have copied rungs from people who understand the signal chain. A short companion is instrumentation for PLC engineers.

Week 6 is about structure. Real programs are not one long list of rungs. Learn to put repeated logic in a function block, such as one motor-control block that you reuse for three motors, and to name tags clearly. Rewrite your week 2 motor logic as a block and call it three times. The program will be shorter, and a fault in the block is fixed once.

Weeks 7 and 8: HMI, faults and a final project

Week 7 adds the operator screen. Build one HMI page with a start button, a stop button, a running lamp and a numeric display of the analog value. Learn how HMI tags map to PLC tags. If you want depth, the HMI design course covers screens, alarms and navigation, and our post on the difference between HMI and SCADA explains where this leads next.

Week 8 is about finding faults and finishing. First, break your own program on purpose: swap a normally open contact for a normally closed one, delete a seal-in contact, and use the wrong data type. Find each fault using the online view and a method, not guesswork. Then finish a project that joins everything: a tank filling system with a start/stop, a pump, a level sensor with scaled analog value, a high-level alarm, a timer-delayed restart and an HMI screen. Write a one-page summary with a diagram, the tag list and one problem you solved.

What slows beginners down?

• Watching without building. Videos feel like progress. Pause and rebuild every example yourself.
• Switching brands every week. Pick one for eight weeks. The logic transfers later.
• Skipping the electrical basics. Ladder logic is a model of circuits, and it is hard to read without them.
• Never testing failures. A program that only works in the happy case is not finished.
• Not saving work. Keep every project in a folder with a clear name, because those files become your portfolio.

For a portfolio layout, see how to build an engineering portfolio from course projects. If you want a longer, week-by-week estimate with different paces, read how long it takes to learn PLC programming.

What comes after week 8?

Choose one of three next steps. Go deeper on a brand with the Allen-Bradley Studio 5000 course or a second platform. Go wider with SCADA, drives or panel design. Or go for structure and proof with a free internship.

The free PLC internship gives you a guided project path. It is free to join, there is no application or interview, you start on any date, and the length runs from one week to 24 months. It is training, not employment, and there is no stipend. The certificate and other documents are optional paid add-ons, shown in your currency before you pay and verifiable at /verification. If your college asks for an internship, see the free internships page; credit is for your university to decide.

Eight weeks is short, but it is enough to change a beginner into someone who can build, test and explain a small control program. Keep the routine, finish each weekly project, and the confidence follows. For a wider view of the options, the free PLC training guide lists every course and simulator in one place.

Take the free course

Free

PLC programming · Beginner · Free

Siemens TIA Portal

Free

PLC programming · Beginner · Free

OpenPLC: IEC 61131-3 on Arduino, ESP32 and Raspberry Pi

Free

PLC programming · Beginner · Free

CODESYS and IEC 61131-3 Programming

Free

PLC programming · Beginner · Free

PLC and Electrical Troubleshooting for Maintenance Teams