1. Overview: Why the LOGO! 8.2 Web Server Solves LAN Remote Control
The Siemens LOGO! 8.2 (order code suffix 0BA8) ships with an integrated HTTP web server. That server exposes the LOGO!'s inputs, outputs, flags, network inputs, and program variables as a read/write tag list, renderable in any modern browser. From a smartphone on the same subnet the engineer can therefore click a button on screen and switch a discrete output without a dedicated app, an OPC server, or a VPN — only a working TCP/IP path between the phone and the LOGO!.
The web server is part of the LOGO! firmware; it is not an external add-on, and it is not a cloud service. The HTML it serves is generated inside the base module, so there is no separate hardware to mount, no licence to pay, and no remote service to be exposed unless the user explicitly opens the port through the corporate firewall.
This reference gives the exact procedure to:
- Enable the web server inside a LOGO!Soft Comfort 8.2 project and define users.
- Assign a static IP and verify reachability from a PC and from a phone.
- Open the standard status page from an iPhone or Android browser.
- Build a custom one-button page with LOGO! Web Editor (LWE) that sets
Q1. - Wire the web-driven value into the FBD so the LOGO! logic cannot overwrite it on the next scan.
- Apply user/password authentication, restrict exposure to the LAN, and (optionally) tunnel cellular access through a VPN.
- Run a verification checklist and a fault-finding matrix.
FS:04) and the LOGO! 8.3 update (FS:05). LOGO! 8.0 and 8.1 hardware does not include the extended web server described here — see Section 2.2. LOGO! 8 Firmware Generations and Web Server Capability
The "LOGO! 8" product family is delivered as a single hardware platform (the 0BA8 base module) with several firmware generations. The web server capability changed between generations, so it is essential to know the firmware line on the device before commissioning.
| Generation | Module ID | Firmware line | Web server | Custom pages via LWE | Status |
|---|---|---|---|---|---|
| LOGO! 8.0 | 0BA8 | FS:01 – FS:02 | Simple, read-only | Not supported | Legacy |
| LOGO! 8.1 | 0BA8 | FS:03 | Simple, read-only | Not supported | Legacy |
| LOGO! 8.2 | 0BA8 | FS:04 | Extended, read + write | Supported | Production |
| LOGO! 8.3 | 0BA8 | FS:05 | Extended, read + write, additional widgets | Supported | Current |
| LOGO! 8.4 | 0BA8 | FS:06 | Extended, read + write, TLS option | Supported | Latest |
Identify the firmware line on the device directly from the LOGO! keypad: Menu > Diagnostics > IP Address shows the IPv4 settings, then Menu > Diagnostics > Software reveals the FS:xx value. If the device shows FS:01 to FS:03 the extended web server is unavailable and a firmware update to LOGO!Soft Comfort 8.2 (or higher) followed by a project download is required. The firmware update is delivered by downloading the project to the module; the LOGO! bootloader reloads FS:04 or higher automatically if the PC is running LOGO!Soft Comfort 8.2 or newer.
3. Prerequisites
-
Hardware. One LOGO! 8.2 base module:
- Relay output:
6ED1052-1BB08-0BA1(8 DI / 4 DO relay) - Transistor output:
6ED1052-2BB08-0BA1(8 DI / 4 DO transistor) - Analog variant:
6ED1052-1MD08-0BA1or6ED1052-2MD08-0BA1 - Power supply 24 V DC (or 12/24 V DC for the
6ED1052-1HB08-0BA1variant), plus an Ethernet patch cable to a switch or router.
- Relay output:
-
Firmware. The base module must report at least
FS:04. Units built after Q4-2018 ship from factory with FS:04. - Programming tool. LOGO!Soft Comfort 8.2 (or higher) installed on a Windows PC. The installer is delivered through the Siemens Industry Online Support portal; access requires a free Siemens account.
- Network. A DHCP server on the same VLAN as the phone, or a static address plan that the phone can route to. A managed switch with VLAN support is optional but recommended for guest/IoT segmentation.
- Mobile device. iOS 12+ Safari, Android 8+ Chrome, or any modern browser that handles HTML5, CSS, and basic JavaScript. No app installation is required.
4. Enabling the Web Server in LOGO!Soft Comfort
- Open the project in LOGO!Soft Comfort 8.2.
- Choose
Tools > Web Server Configuration(or, depending on the tool revision,Extras > Web Server Settings). - Tick "Activate web server".
- Enter the listen port. The default is
80; change it only if another device on the LAN already holds port 80. - Define the user list. Up to 8 users, each with:
- Username (1 – 24 characters)
- Password (1 – 24 characters)
- Access level: Read or Read/Write
- Save the project and transfer it to the LOGO! module over Ethernet:
PC > LOGO!orF5in LOGO!Soft Comfort.
| Parameter | Default | Range | Comment |
|---|---|---|---|
| Web server enable | Off | On / Off | Must be On |
| Listen port | 80 | 1 – 65534 (avoid 8080 if used elsewhere) | Plain HTTP, no TLS in 8.2 |
| Max users | 0 | 0 – 8 | 0 = web server disabled |
| Session timeout | — | Session ends on power cycle or re-upload | No software timeout in 8.2 |
| Update interval | 2 s | Fixed in 8.2; 1 s possible in 8.4 | Standard page refresh |
5. Network Configuration
5.1 Static IP on the LOGO! Module
By default the LOGO! requests an address from DHCP. For a deterministic URL on the phone, a static address is preferred:
Menu > Settings > Network Settings > IP Address- Enter a free address on the LAN, e.g.
192.168.1.50. - Subnet mask
255.255.255.0. - Default gateway to the router IP, e.g.
192.168.1.1. - Apply and confirm with
OK.
If the LOGO! is left on DHCP, pin a reservation in the router using the device MAC (printed on the front flap and shown under Menu > Diagnostics > IP Address).
5.2 Verify Reachability from a PC
From a Windows PC on the same LAN, open a command shell:
ping 192.168.1.50
A reply confirms the layer-3 path. Then from the same PC, in a browser:
http://192.168.1.50
The standard LOGO! web page should load within 2 s and prompt for the user/password defined in Section 4.
5.3 Verify Reachability from a Phone
Connect the phone to the same SSID as the PC, then in Safari or Chrome type the same URL. The login prompt is identical. If the phone cannot reach the LOGO!, see the troubleshooting matrix in Section 13.
6. Standard Web Page — Read-Only Inspection
The standard page lists every digital input, digital output, flag, and analog variable defined in the project, refreshed every two seconds. Use it as a commissioning tool before deploying a custom page. No write operations are possible on the standard page; the on-screen buttons only navigate, they do not toggle outputs. For real control, proceed to Section 7.
| Section | Shows | Refresh | Writable from standard page |
|---|---|---|---|
| I/O status | Inputs I1 – I24 and outputs Q1 – Q20 | 2 s | No |
| Flags | M1 – M27, 8-bit groups M8 – M25 | 2 s | No |
| Analog | AM1 – AM16, AQ1 – AQ8 | 2 s | No |
| Network inputs | NI1 – NI64 (master/S7 mode only) | 2 s | No |
| Program ID | Project name, online status, firmware version | on load | No |
7. Custom Web Page with LOGO! Web Editor (LWE)
The LOGO! Web Editor is a drag-and-drop HTML5 designer bundled with LOGO!Soft Comfort 8.2 and newer. Use it to build a single-button page that writes a 1 to a network input, which the FBD program then maps to output Q1.
- In LOGO!Soft Comfort choose
Tools > LOGO! Web Editor. LWE opens in a new window with the project tags pre-populated from the FBD. - Click "New Page"; choose the Mobile template (480 px wide viewport).
- From the widget palette drag a Toggle Button onto the canvas.
- In the widget properties:
- Variable:
NI1(Network Input 1) - Label:
Pump Start/Stop - Color ON: green (#28a745)
- Color OFF: grey (#cccccc)
- Variable:
- Save the project file (
.lwe) and click "Upload to LOGO!". The custom pages are stored on the module and become reachable athttp://192.168.1.50/scc(the System Configuration & Control root path of the LOGO! web server). - Open that URL from the phone. The button now sets or clears
NI1on the LOGO!, and the FBD mapsNI1 → Q1(see Section 8).
7.1 LWE Widget Catalog
| Widget | Maps to | Use case |
|---|---|---|
| Toggle Button | Bit (NI, M, Q) | Start/stop a load |
| Momentary Button | Bit | Door release, jog command |
| Numeric Input | VW (16-bit signed word) | Threshold, setpoint |
| Slider | VW | Speed demand 0 – 100 % |
| Bar Indicator | VW (read-only) | Tank level, temperature |
| Lamp | Bit (read-only) | Status, alarm |
| Text Label | — | Static title |
8. Tag Mapping and FBD Integration
The web page cannot write directly to a physical output. It writes to a network input (NI) or flag (M); the FBD/LAD program then decides what to do with that value. This indirection is what protects the program from being overridden by the browser.
Example FBD fragment (LOGO!Soft Comfort diagram description):
[ NI1 ] --[ AND ]--[ Q1 ]
|
[ NOT Q1 ]
This is a classic toggle (R-S flip-flop) wired from a network input. When the user taps the LWE button, the LOGO! web server sets NI1 = 1 for 250 ms; the FBD latches Q1. Tapping again resets it.
To declare NI1 in LOGO!Soft Comfort:
- Open the program block where the toggle output is needed.
- Drag a Network Input function block from the Special / Network I/O palette.
- In the block properties set
NI1, type Bit, and tick Expose as web-server variable.
9. SVG Flow Diagram — Mobile-to-LOGO! Write Path
10. Mobile Browser and Authentication Configuration
The first time a browser connects to http://192.168.1.50 it prompts for the credentials configured in Section 4. Once authenticated, the browser stores a session cookie valid until the LOGO! is power-cycled or until the user list is re-uploaded. Practical tips for the mobile side:
- Use Private / Incognito mode on a shared phone so the password is not saved.
- Add the page to the phone home screen: Safari Share > Add to Home Screen; Chrome Android Menu > Add to Home screen. The icon launches the page in a chrome-less window that auto-uses the saved session.
- Avoid 3rd-party QR-code launchers — they do not always forward HTTP basic-auth headers; Safari/Chrome do.
- If the phone is in low-power mode, the 2 s polling can pause; bring the app to the foreground to force a refresh.
11. Security Hardening
| Control | Recommended value | Rationale |
|---|---|---|
| Web server access level for operators | Read/Write only, no project upload right | Prevents uploading a malicious program from the phone |
| User password length | ≥ 12 characters, mixed case + digit | Defeats trivial dictionary probes against the basic-auth realm |
| Network exposure | LAN only, no port-forward on the router | LOGO! 8.2 serves plain HTTP — exposing it to the Internet leaks credentials and allows output toggling |
| Port change | Default 80 is fine on a closed LAN; switch to a non-standard port (e.g. 8080) if multiple LOGO! modules are deployed to keep the URLs short and predictable | Operational convenience, not security |
| MAC ACL on the switch | Permit only the LOGO! MAC and the admin PC MAC | Layer-2 isolation from guest Wi-Fi |
| Firmware | Keep at the latest FS:xx available for the hardware | Newer firmware ships vulnerability patches and TLS-ready web-server hooks |
12. Cellular and Off-LAN Access
If the user must reach the LOGO! from a different network (a cellular phone on 4G/5G, a remote site, or a worker on a customer Wi-Fi), do not forward port 80 directly through the home or factory router. Two clean options exist:
- WireGuard tunnel. Run a small SBC (Raspberry Pi, industrial mini-PC) on the LAN with a static address. Install WireGuard, expose only the WireGuard UDP port on the router, and route the LOGO! subnet through the tunnel. The phone runs the official WireGuard app and talks to the LOGO! as if it were local.
-
Router-native OpenVPN / IPsec. Many industrial routers (Sentinel, EDR-810, SCALANCE M) ship with an OpenVPN server. Add the router to the LAN, terminate the tunnel there, and push a route to
192.168.1.0/24to the client.
Both options keep the web server on plain HTTP inside the tunnel and authenticate the tunnel at the network layer. For 24/7 availability use a watchdog script that pings the LOGO! every 60 s and raises an alarm if the web server stops responding.
13. Verification and Commissioning Checklist
- From a PC,
ping 192.168.1.50— replies expected. - Open the standard page in a desktop browser — input state changes when a real switch is toggled.
- Open the custom page in a phone browser, tap the
NI1button — the on-screen indicator flips and the physical relay (if wired) clicks within 250 ms. - Disconnect the network cable from the LOGO! — the web page shows "no connection" within 10 s.
- Re-connect the cable and refresh the page — values return within 2 s.
- Power-cycle the LOGO! — the web server restarts within 8 s; the browser prompts for the password again.
- Re-upload a different program from LOGO!Soft Comfort and confirm the user list is still active.
- Audit: from the PC, run
nmap -p 80 192.168.1.50; only port 80 should be open on the LOGO!.
14. Troubleshooting Matrix
| Symptom | Likely cause | Fix |
|---|---|---|
| Browser shows "Server not available" | Web server not enabled in the project | Re-upload the project with Activate web server ticked and at least one user defined |
| Browser prompts for password repeatedly | User has Read-only access but the page needs Write | Change the access level of that user to Read/Write |
| Button click changes the on-screen state but the relay does not click | LOGO! program does not route NI1 → Q1
|
Edit the FBD to wire NI1 into a flip-flop whose output is Q1 |
| Phone cannot reach the LOGO! but the PC can | Phone is on guest Wi-Fi or different VLAN | Connect the phone to the same SSID/VLAN, or add a static route on the router |
| Page is slow or buttons ignore taps | Browser is caching an old session | Force-reload (Safari: pull-to-refresh; Chrome: ⋮ > Reload) |
| "Service unavailable" on every page | LOGO! is in STOP / no valid program | Switch to RUN from the keypad or via the programming tool |
| Web page loads but value is always 0 | Project variable is the wrong address (e.g. M9 used as a retain not exposed) |
Map the toggle to a Network Input (NIx) which is exposed under "Network Inputs" in LWE |
| Login page does not appear, the browser shows a security error | URL was typed as https://
|
LOGO! 8.2 web server is HTTP only — use http://
|
| Custom page returns 404 after upload | LWE project uploaded but the LOGO! was not re-booted | Power-cycle the LOGO!; the bootloader re-reads the custom-page store on start-up |
| Web page is reachable but the value resets every 250 ms | FBD program is overwriting the tag | Replace the direct assignment with a latch (RS flip-flop) driven by NI1 |
| Date/time on the page is wrong | LOGO! real-time clock not synchronised | Set the clock from the keypad or via the web Setup page (Tools > Set Clock) |
15. Related Siemens Documentation
- Siemens Industry Online Support (SIOS) — main portal for LOGO! manuals, firmware, FAQs.
- Siemens LOGO! product page — order numbers, configurator, brochures.
- LOGO! 8 system manual — search "LOGO! 8 system manual" on SIOS; documents the web server API and access levels.
- LOGO! Web Editor (LWE) manual — bundled with LOGO!Soft Comfort 8.2; covers widget properties and tag binding.
FAQ
Does LOGO! 8.0 or 8.1 support mobile remote switching?
No. The simple web server in 8.0 and 8.1 is read-only — the standard page shows status but provides no write buttons. You need at least a 0BA8 standard with firmware FS:04 (LOGO! 8.2) for the extended web server, plus LOGO!Soft Comfort 8.2 for the Web Editor.
Can I use a dedicated iOS or Android app instead of a browser?
Yes. The LOGO! web server is plain HTTP, so any app that supports REST-style HTTP GET/POST against a fixed URL can drive outputs. Siemens does not publish an official mobile app for the 0BA8 series; the browser path is the manufacturer-supported route and works on Safari, Chrome, Edge, and Firefox.
How many users can control the LOGO! at the same time?
Up to 8 user accounts can be defined per project. The web server handles a small number of concurrent sessions; in practice 3 – 4 active phones work without noticeable lag because the polling interval is 2 seconds.
The web page updates every 2 seconds. Can that be made faster?
No, the standard page refresh is fixed at 2 s in firmware FS:04. The LOGO! Web Editor lets the designer choose a faster update for custom widgets (down to 250 ms in 8.3), but the controller itself samples at 250 ms internally. For motion or fast interlocks, use a hardwired input — do not rely on the web interface.
Why does my page ask for a password again every time I close the browser?
The session cookie is stored in volatile RAM on the LOGO! and is cleared on power cycle. Use the phone's home-screen shortcut (Safari Share > Add to Home Screen) to keep the session alive between browser launches, and avoid the browser's Clear-Cookies routine.
Is the HTTP traffic encrypted?
No, LOGO! 8.2 web server is plain HTTP. Keep it on a trusted LAN or tunnel it through WireGuard / OpenVPN. Firmware FS:06 (LOGO! 8.4) introduces TLS hooks for the web server; deploy a recent firmware if the network cannot be physically isolated.