What laptop specs do you need for PLC programming?

Which specs decide the laptop for PLC programming?

Four numbers decide the purchase: a quad-core x86 CPU at 2.3 GHz or faster, 32 GB of RAM, a 512 GB SSD and a 17-inch screen at 1920 x 1080. Every other line on the spec sheet is secondary.

The software splits into two classes, and that drives the numbers. Lightweight suites aimed at small controllers install natively and run on modest hardware. The big vendors ship their packages inside a Windows virtual machine, and a machine like that reserves RAM by the gigabyte and disk by the tens of gigabytes. The 2.3 GHz floor matches the processor speed that published virtual-machine requirements list as their baseline. Four cores let you give each VM two while the host keeps two. The SSD floor exists because each VM image is a full Windows install before your first project lands. Backlit keyboards, card readers and battery claims are comfort features; buy them last.

How much RAM do the virtual machines need?

Count 6 GB for the Windows host, 2 GB for the programming software and 8 GB for each virtual machine you open at once. Two machines reach 24 GB, which sets the buying number at 32 GB.

A VM reserves its allocation for as long as it runs; the host gets nothing back. Fall short and Windows pages to the SSD, and the editor freezes between clicks while the download crawls. The 8 GB per machine is not generous: Windows 11 lists its own minimum below that, so an 8 GB allocation leaves the suite inside the VM room to work. Packages that ship as ready-made VMs push harder. One commercial application publishes 500 GB of disk and a RAM requirement above this whole figure for its VM alone, and that is the top of the market. On many current laptops the memory is soldered, so the figure you order is the figure you keep for the life of the machine.

How big should the screen be for ladder logic and tag tables?

Buy a 17-inch panel at 1920 x 1080. A cheap 15-inch laptop still ships a 1366 x 768 screen, and at that width you scroll horizontally inside every rung and tag table you open.

Ladder editors lay the power rail, the contacts, the coils and the rung comments across the width. Tag databases show name, address, data type, scaling and comment side by side. On 1366 pixels you scroll sideways through both; on 1920 you mostly do not. Function block editors grow in both directions, and the extra rows over a 768-row panel save a scroll on every edit. At 100 percent scaling, editor text on a 17-inch 1080p panel is comfortable at arm's length from a bench chair; on a 13-inch panel the same setting has you leaning in.

Skip the 3840 x 2160 option. Windows scales a 17-inch 4K panel to 150 or 200 percent to keep text readable, which lands the effective desktop between 1920 x 1080 and 2560 x 1440. Editor windows that predate high-DPI support blur at the 150 percent setting. The 1080p panel shows the same rungs with no premium on price or battery.

If you keep a desk, add a 24-inch external monitor at 1920 x 1080 and drive it from the laptop's HDMI port. A common pairing is a 15-inch laptop plus that monitor at the desk, and the laptop alone on the cart. One cost of 17 inches: fewer standard bags list that size, so check the bag's stated screen size before you order.

Which ports does the laptop need on the bench?

Insist on a built-in RJ45 Ethernet jack and at least two USB-A 3.0 ports, one for the USB-to-serial adapter and one for a memory stick, plus HDMI out for a second screen at the desk.

Current controllers commission over Ethernet: a patch cable, an address on the laptop's network card and the programming software. That is why the built-in jack earns its slot. A USB Ethernet adapter works, but it occupies a port you will want back. The 9-pin serial port left laptops years ago, so the USB-to-serial adapter is standard kit for older serial gear and RS-485 networks; carry two, because they fail at the worst time. When a Modbus RTU device answers nothing, the adapter, the slave address and the wiring are the first three things to sort, and our Modbus RTU troubleshooting article walks that order. A USB-C dock that carries power, Ethernet and monitors keeps the desk tidy; on the cart, the built-in ports still win.

Worked example: two vendors, two virtual machines

Take a job for two controller vendors at once: 6 GB for the Windows host, 2 GB for the editor, 8 GB for each of two virtual machines. The total demand is 24 GB, so a 16 GB laptop pages to disk and the 32 GB build keeps 8 GB in reserve.

The RAM side, line by line:

Open the second VM on the smaller build and demand exceeds installed by 8 GB. Windows pages to the SSD while both VMs run, and every rung edit waits behind that queue. On the larger build the same session stays in RAM with 8 GB spare.

Disk follows the same arithmetic. Windows 11 lists a 64 GB storage minimum, the editor and the project archive take 40 GB, and each VM gets a 64 GB virtual disk. That is 64 + 40 + 128 = 232 GB, and a 512 GB SSD covers it with about 280 GB free for trend exports and backups. Cores: assign two to each VM and leave two for the host; ladder logic is not a compute load.

Decision: two VMs at once needs the larger RAM build. One VM beside native tools fits the smaller one.

Which build should you buy?

Pick by your software list. One lightweight suite runs native on the smaller build with a 15.6-inch screen. Two vendors or two virtual machines need the larger build and a 17-inch panel. A desk build adds a 24-inch monitor instead of a bigger laptop.

Move off the middle row only when a package publishes its own VM requirement above what the row carries. The application that ships as a VM and lists a RAM figure above the row's and 500 GB of disk for itself moves you to 64 GB and 1 TB before you install it.

Recommendation: buy the 32 GB, 17-inch middle row if you expect to touch more than one vendor's software, because the big suites run inside virtual machines and two at once is the normal working case. Stay on the 16 GB, 15.6-inch row only while you write logic for one lightweight suite, and move up before you install the first VM-based package.

What to ask for, line by line: quad-core CPU at 2.3 GHz or faster; the RAM figure from the worked example unless you are certain of the single-suite future; 512 GB SSD; 17.3-inch screen at 1920 x 1080; built-in RJ45; at least two USB-A 3.0 ports; HDMI out. In the bag go two USB-to-serial adapters, a wired three-button mouse and a short patch cable.

Which screen are you actually specifying?

The laptop spec stops at the desk. The panel on the machine, the board above the line and the screen in the lobby are separate devices, sized by viewing distance at about 30 ft per inch of letter height, not by the laptop's own screen.

The wall board follows distance: the guide to screen size and viewing distance works that figure into letter heights and screen sizes for lobbies, lines and loading docks. The touch panel you will design for the machine is a separate plan again; start with how to plan a touchscreen operator interface for factory controls. When the argument on the job is whether a given screen is an operator control or a status board, the factory status display article draws that line. For the boards themselves, we build small offline Android screens that play from a memory card with no network and no subscription; the shop-floor screens and andon-style boards category shows that side.

Questions