In Automation Builder choose File > New Project, select an empty project, then Add Object or Insert Device and pick the exact AC500-eco CPU, for example PM564-T-ETH, from the AC500 catalogue. The device tree then shows the CPU with its onboard I/O, interfaces (ETH1, COM1), I/O bus and the PLC application. Name the project after the machine and save it before adding I/O or logic.
- Pick the CPU by the exact order type on the label: T (transistor) and R (relay) variants differ
- The device tree mirrors the real panel: CPU, interfaces, I/O bus, then modules
- Save often and keep one project per machine with a version number in the file name
- The application node is where the program lives; configuration nodes describe hardware
An Automation Builder project is two things in one file: a hardware configuration that must match the real panel, and the PLC application with your logic. Getting the first right saves hours of “configuration mismatch” errors later.
Step 1: Create the Project File
- Start Automation Builder and choose File > New Project.
- Select an empty project, name it
SW_Conveyor_AC500eco_v01and choose a folder you back up. - Click OK. An empty device tree appears.
| Naming rule | Example | Why |
|---|---|---|
| Machine or line name first | SW_Conveyor | Find the project by machine, not by date |
| Controller family | AC500eco | Avoid opening with the wrong package |
| Version suffix | _v01, _v02 | Roll back after a bad change, match what is in the PLC |
| No spaces or special characters | Underscores only | Avoids path and archive problems |
Step 2: Insert the AC500-eco CPU
- Right-click the project root and choose Add object / Insert device.
- Open the AC500 catalogue and select the eco CPU family.
- Pick PM564-T-ETH (or the exact type on your CPU label) and click Add.
- Rename the CPU node
PLC_Conveyor.
Step 3: Read the Device Tree
Click each block in the drawing to see what that part of the device tree is for. The tree is the software picture of the hardware in Fig. 1 of Lab 1.
Click or tab to any node of the device tree.
Step 4: Set Basic CPU Parameters and Save
- Double-click the CPU and review the parameters. Leave defaults for now; note the setting that decides whether the CPU starts in RUN after power up.
- Open ETH1 and enter
192.168.0.10/255.255.255.0so the project matches the CPU from Lab 2. - Open the application and check that a
PLC_PRGprogram and a cyclic task exist (they are created by default). - Choose Project > Check all / Build. Fix anything red.
- Save with Ctrl+S.
Practice Exercise
Create a second project for a PM554-T-ETH CPU and compare its onboard I/O node with PM564. Write down the differences, then delete the practice project.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| CPU type not in catalogue | Package missing or old Automation Builder | Install AC500 V2 package / update Automation Builder |
| Build error after adding CPU | Firmware version not supported by the project | Select the CPU version matching your hardware |
| Project will not open on another PC | Different Automation Builder version | Use the same or newer version; archive the project with libraries |
| Application node missing | Device added without application | Right-click CPU, add the PLC application |
Frequently asked questions
How do I create a new project in ABB Automation Builder?
Choose File > New Project, select an empty project, then insert the AC500 CPU matching your hardware from the device catalogue. Configure its interfaces, check the application and save.
What is the device tree in Automation Builder?
It is the structured view of your hardware and software: CPU, onboard I/O, communication interfaces, the I/O bus with expansion modules and the PLC application.
Does the CPU type in the project have to match exactly?
Yes. The order type and firmware must match the real CPU or the download will report a configuration mismatch.
Where is the PLC program stored in the project?
Under the application node of the CPU: PLC_PRG, other POUs, global variables and the task configuration.