Connecting Siemens LOGO! 8.3 to Network and iPhone Access

Overview

The Siemens LOGO! 8.3 (6ED1052-xxx08-0BA1 / -0BA2 base modules) integrates an Ethernet interface, a built-in web server, and a customizable user page editor. This combination allows a LOGO! to be deployed as a small stand-alone controller for residential and light-commercial applications — including pool controllers, irrigation systems, lighting scenes, and HVAC sequencing — and to be monitored or operated from any browser-capable device on the same network, including an iPhone, iPad, Android phone, or PC.

This reference covers the most common deployment failure modes when transitioning from a direct point-to-point PC connection to a residential router, and from a desktop browser to a mobile browser. Symptoms typically include: the LOGO! web server responds on a direct PC link but not through a router; the iPhone Safari or Chrome browser times out or spins indefinitely; the user dashboard built in LOGO! Web Editor (LWE) is visible to the PC but not the phone; and HTTPS/SSL warnings cannot be cleared because the root certificate installation steps are unclear.

The complete solution requires correct static IP addressing, activation of access control in LOGO!Soft Comfort, configuration of the LWE project, router port and firewall handling, and (for HTTPS) installation of the LOGO! root certificate on iOS.

Prerequisites

• LOGO! 8.3 base module with Ethernet port (LOGO! 8.3 12/24 RCE, RCEo, 230 RCE, or 24 CE; verify with the order number suffix 0BA2 for the current 8.3 generation).
• LOGO!Soft Comfort (LSC) V8.3 or newer programming software — required for firmware 8.3 features and the matching LWE editor.
• LOGO! Web Editor (LWE) V1.0.x or V1.1.x — installed as a component of LOGO!Soft Comfort V8.3.
• Residential router with DHCP and at least one free 10/100 Mbps Ethernet port.
• PC with an Ethernet or Wi-Fi adapter.
• iPhone running iOS 12 or newer (for HTTPS root certificate installation) or iOS 11 and newer for HTTP-only access.
• Ethernet patch cable (Cat 5e or better) for the LOGO! to router link.

Confirm the firmware version on the LOGO! base module before proceeding: navigate to LOGO! Display > Diagnostics > Version on the device, or in LSC under Online > LOGO! > Identification. The firmware string should begin with FS: 02.04.00 or later for the 0BA2 hardware.

LOGO! 8.3 Hardware Reference

Per the LOGO! V8.3 Stay-in-Touch Webinar, the 8.3 generation ships in four base module variants:

Maximum configuration per base module is determined by the expansion bus; refer to the LOGO! 8.3 system manual, chapter "Maximum Setup", for the exact slot count. The Ethernet port is the integration point for both LSC online access and the on-board web server. The web server itself listens on TCP/80 (HTTP) and TCP/443 (HTTPS) and uses a self-signed certificate generated at first power-up.

Network Architecture and IP Addressing

When the LOGO! is wired directly to a PC with a crossover or patch cable, the PC typically assigns itself a link-local address (169.254.x.x / 16) and reaches the LOGO!'s default address (169.254.0.0/16 — verify with Online > Go Online in LSC). As soon as the LOGO! is connected to a router, both devices move into the router's address space and addressing must be made explicit.

Recommended LAN settings for a residential deployment:

To set a static IP on the LOGO!:

1. In LOGO!Soft Comfort, open the project and choose Tools > Transfer > Ethernet Connections.
2. Click Add. Enter 192.168.1.50 as the LOGO! IP and 255.255.255.0 as the subnet mask.
3. Mark the new entry as Active and click OK.
4. Transfer the configuration to the LOGO! via PC ↔ LOGO! or by writing it directly on the LOGO! display under Network Settings > IP Address.
5. Power-cycle the LOGO! to apply.

Reserve the LOGO! address in the router's DHCP table (or set a DHCP reservation by MAC) so a future DHCP lease cannot hand 192.168.1.50 to another device and create a duplicate-address conflict.

Step-by-Step: From Direct PC Link to Router Deployment

1. Confirm the direct connection still works

With the LOGO! connected directly to the PC (no router), browse to http://169.254.x.x (use the address displayed on the LOGO! under Diagnostics > IP Address). The login page should appear. If it does not, the web server is disabled — re-enable it from the LOGO! display under Settings > Web Server Access > Enable or via LSC Tools > Transfer > Access Control.

2. Configure the static address on the LOGO!

Use the procedure above to assign 192.168.1.50 / 255.255.255.0 / 192.168.1.1. Verify the change by reading back the address on the LOGO! display: Menu > Diagnostics > IP Address. The display should show 192.168.1.50 after power-cycle.

3. Connect LOGO! to the router

1. Disconnect the PC ↔ LOGO! patch cable.
2. Connect the LOGO! Ethernet port to a numbered LAN port on the residential router using a standard patch cable.
3. Confirm the link LED on the LOGO! Ethernet RJ45 is lit (green/yellow activity LED is normal; if dark, replace the cable or try another router port).

4. Test from the PC on the same router

From the PC (now connected via Wi-Fi or a different LAN port on the same router), open a browser and navigate to http://192.168.1.50. The LOGO! web server login page should appear within two seconds. If it does not, proceed to the troubleshooting matrix below before continuing.

5. Activate Access Control

Web server access from any browser — including the iPhone — is gated by Access Control. In LSC:

1. Select Tools > Transfer > Access Control.
2. Check Activate Access Control for Web Server.
3. Define user accounts: at minimum one administrator account with username and password. Add an operator-level account if read-only monitoring is needed.
4. Choose Access Type → HTTP/HTTPS and assign each user Read, Write, or Read/Write rights.
5. Click Apply, then transfer the project back to the LOGO!.

6. Test from the iPhone on Wi-Fi

Connect the iPhone to the same Wi-Fi SSID the PC is using. Open Safari and enter http://192.168.1.50. The LOGO! login page should render. If Safari reports "Safari cannot open the page because the server stopped responding", the most likely causes are:

• iPhone is on a guest SSID or a different VLAN than the LOGO!.
• The router's AP/client isolation is enabled (common on consumer mesh systems).
• HTTPS-only mode is forced by an iOS profile (corporate MDM) — switch Safari to allow HTTP.
• The LOGO! firewall (none on 8.3, but router firewall or iOS Private Relay feature may be interfering).

LOGO! Web Editor (LWE) Project Configuration

The LOGO! Web Editor is bundled with LOGO!Soft Comfort V8.3 and is used to build the responsive user page displayed in the browser. The LWE project is stored on the LOGO! in the user-program area and is downloaded as part of the program transfer.

1. In LSC, open the program. From the menu, choose Tools > LOGO! Web Editor. LWE opens in a new window.
2. Drop LOGO! variables onto the canvas: drag I1, I2, Q1, Q2, VW0, etc., from the variable tree on the right.
3. Bind each element to a widget (button, indicator, numeric display, slider). Mark each widget as Read or Write in the properties pane.
4. Click Project > Save and then Project > Transfer to LOGO!. The LWE pages are pushed to the LOGO! flash alongside the LSC program.
5. Verify on the PC browser: http://192.168.1.50. After login, the dashboard should appear with live values.

Per the LOGO! Web Editor Tips & Tricks document, dashboards are rendered server-side by the LOGO! web server and served at /logo_dashboard.html by default. The LWE project XML is stored at /lwe.xml on the LOGO! and can be inspected for debugging.

HTTPS and iOS Root Certificate Installation

The LOGO! 8.3 web server generates a self-signed certificate at first boot. iOS Safari, like most modern browsers, warns on self-signed certificates by default. To clear the warning, install the LOGO! root certificate into the iOS trust store.

1. From a PC on the same network, browse to https://192.168.1.50 and click through the browser warning to download the root certificate (PEM/CRT file).
2. Email or AirDrop the certificate to the iPhone. Alternatively, host the certificate on a local web server and download it directly.
3. On the iPhone, open the certificate. iOS prompts to install it under Settings > General > VPN & Device Management.
4. After installation, navigate to Settings > General > About > Certificate Trust Settings and enable full trust for the LOGO! root certificate.
5. Reopen Safari and navigate to https://192.168.1.50. The lock icon should now appear without warning.

For production deployments serving multiple devices, generate a permanent certificate using a CA, replace the LOGO! self-signed certificate, and distribute the CA chain to all clients. The LOGO! 8.3 firmware supports certificate replacement via SFTP push to the /cert folder.

Remote Access from Outside the Home Network

The initial failure mode is almost always LAN-side; once LAN access is confirmed, the same architecture extends to the WAN side. Two patterns are supported.

Pattern A — Port Forwarding

1. On the residential router, create a port-forwarding rule: external TCP 8443 → internal 192.168.1.50:443.
2. Reserve a DNS name with a dynamic DNS provider (Dyn, No-IP, DuckDNS) so the changing WAN IP is addressable.
3. From the iPhone on cellular data, browse to https://yourname.duckdns.org:8443.

Pattern B — VPN

For higher-security deployments, enable the router's VPN server (WireGuard, OpenVPN, or IPsec) and have the iPhone connect via the iOS VPN client. All traffic then traverses the encrypted tunnel, and the LOGO! remains invisible to the public internet. The Siemens LOGO! does not itself act as a VPN endpoint; the router or a separate firewall appliance handles this role.

LOGO! Cloud Connectivity (AWS)

LOGO! 8.3 supports the LOGO! Cloud broker and AWS IoT integration via the LOGO!Soft Comfort cloud connector. Pairing requires:

1. Create an AWS IoT Thing and download the certificates.
2. In LSC, open Tools > LOGO! Cloud and enter the AWS endpoint URL, Thing name, and certificates.
3. Transfer the configuration. The LOGO! publishes its variables to the AWS MQTT broker at the configured cadence.

Many AWS console screens have changed since the original LOGO! 8.3 documentation shipped; the modern path is AWS IoT Core > Manage > Things > Connect device → MQTT. If the AWS UI does not match the LOGO! manual, regenerate the certificates and use the newer MQTT over WebSockets configuration option in the LOGO! Cloud tool.

Troubleshooting Matrix

Verification Checklist

1. From the PC on the same router: ping 192.168.1.50 returns < 5 ms.
2. PC browser: http://192.168.1.50 shows the LOGO! login page within 2 seconds.
3. After login with admin credentials, the LWE dashboard renders with live values updating at the configured refresh interval (typically 1 s).
4. iPhone on same Wi-Fi: Safari to http://192.168.1.50 returns the login page.
5. iPhone login: dashboard renders identically to the PC; write operations on bound widgets (button toggles Q1, for example) take effect within 1 s and are visible on the LOGO! display.
6. For HTTPS: Safari to https://192.168.1.50 shows a closed padlock with no warning.
7. For external access: from cellular, the dynamic DNS URL with the configured external port returns the same login page.

Engineering Notes

• The LOGO! web server is single-threaded; concurrent sessions from multiple browsers will queue. For deployments with more than three concurrent dashboards, consider moving visualization to a higher-tier Siemens controller (S7-1200 Web API or S7-1500 with custom web pages) or a dedicated HMI panel.
• The LOGO! 8.3 web server refresh interval is configurable in LWE under Project > Properties > Refresh Interval. Setting it below 500 ms will noticeably load the LOGO! CPU and may interfere with program scan time.
• For pool-controller applications, wire the LOGO! inputs through an interposing relay or 24 V DC isolator. The LOGO! 8.3 12/24 RCE inputs are type 1 (IEC 61131-2) and sink 5 mA at 24 V; confirm sensor compatibility before commissioning.
• The LOGO! V8.3 Stay-in-Touch Webinar includes additional configuration walkthroughs and live demos of LWE features not covered in the printed system manual.