Every S7-1500 ships with a web server that most plants leave dark. Lit up correctly, it is the cheapest maintenance tool you own; lit up carelessly, it is a write path into production.
What you get without writing code
Diagnostics buffer readable in a browser (the CPU’s own event history — the first place to look after any incident), module states across the whole Profinet tree, watch tables served live, alarm views, and file access to the memory card (data logs!). For a maintenance technician with a tablet, that covers the majority of “what is wrong with it” moments without a Portal laptop.
User-defined pages go further: HTML pages served by the CPU, exchanging tags through simple directives — a machine status page, counters, next-maintenance indicators. It is not SCADA and must not try to be (small pages, slow refresh, no process control from the browser) — the sweet spot is read-mostly machine health pages.
The access model, non-negotiable
Users and roles configured in the CPU (viewer vs technician vs nobody), HTTPS enabled, default anonymous access disabled, and the web server reachable from the maintenance network segment only — the same X1/X2 separation logic as everything else on the machine. Log the credentials in the machine dossier; a web server nobody can log into after a personnel change is dead weight.
FAQ
Does the web server load the CPU? It is budgeted communication load — fine for its purpose; a browser auto-refreshing ten watch tables at 1 s from three laptops is abuse the cycle time will report.
Can I download data logs through it? Yes — DataLog files on the card are downloadable via browser, which turns week-long capture jobs into a URL.
Zone Otomasyon configures web diagnostics as standard handover on new machines. Included, not extra.