Resolving LOGO! 8.3 Communication Error: LSC Version Mismatch Fix
The Siemens LOGO! 8.3 logic module (article numbers ending in 0BA1) frequently produces a "Remote device cannot be accessed" error in LOGO! Soft Comfort (LSC) even though the host PC pings the device successfully. The root cause is not network layer failure but a tooling/firmware version mismatch: LOGO! Soft Comfort V8.2.x does not list the LOGO! 8.3 device type in its hardware catalog, so the project upload/download handshake fails at the application layer. This reference documents the symptom, root cause, complete resolution procedure, compatibility matrix, and field-proven workarounds for the LOGO! 8.3 generation (6ED1052-1FB08-0BA1, 6ED1052-1MD08-0BA1, 6ED1052-2MD08-0BA1, and related variants).
169.254.0.0/16 is the IANA-reserved Automatic Private IP Addressing (APIPA) block. It is auto-assigned by hosts when no DHCP server responds. Although it works for direct point-to-point LOGO! commissioning links, do not treat it as a routable industrial network. After commissioning, reassign the LOGO! a fixed 192.168.x.x or 10.x.x.x address.1. Problem Description
A field engineer configures a Windows PC with a static IP of 169.254.0.10/16 and connects directly (point-to-point) to a LOGO! 8.3 base module configured at 169.254.0.9/16. The PC executes:
C:\> ping 169.254.0.9
Haciendo ping a 169.254.0.9 con 32 bytes de datos:
Respuesta desde 169.254.0.9: bytes=32 tiempo<1ms TTL=255
Respuesta desde 169.254.0.9: bytes=32 tiempo=1ms TTL=255
Respuesta desde 169.254.0.9: bytes=32 tiempo=1ms TTL=255
Respuesta desde 169.254.0.9: bytes=32 tiempo=1ms TTL=255
Estadísticas de ping para 169.254.0.9:
Paquetes: enviados = 4, recibidos = 4, perdidos = 0 (0% perdidos)
Layer-3 connectivity is healthy (TTL=255 confirms the LOGO! itself is responding, not a router). However, when the operator invokes Tools → PC → LOGO! or clicks the online upload/download button in LOGO! Soft Comfort V8.2.1, the following dialog appears:
"The remote device cannot be accessed."
The error is misleading: the OS confirms bidirectional ICMP and TCP/IP reachability, so the network stack is intact. The fault lies in the LSC application, which does not recognize the LOGO! 8.3 device type identifier in its catalog.
2. Affected Hardware and Firmware
| Article Number | Generation | FW Required | LSC Minimum | Notes |
|---|---|---|---|---|
| 6ED1052-1MD08-0BA0 | LOGO! 8.2 | FS 04–FS 06 | V8.2 | Legacy; still serviced |
| 6ED1052-1MD08-0BA1 | LOGO! 8.3 | FS 01+ | V8.3 | New device type, new catalog entry |
| 6ED1052-1FB08-0BA1 | LOGO! 8.3 | FS 01+ | V8.3 | Base module with display & Ethernet |
| 6ED1052-2MD08-0BA1 | LOGO! 8.3 | FS 01+ | V8.3 | Higher-I/O variant |
| 6ED1052-1CC08-0BA1 | LOGO! 8.3 | FS 01+ | V8.3 | Pure (no display) variant |
The 0BA1 suffix is the manufacturing variant identifier that Siemens uses to distinguish LOGO! 8.3 hardware from the prior 0BA0 (8.2) and 0BA2 (8.1) generations. New hardware shipped in 2022+ bundles the older LSC V8.2.1 DVD by default in some markets, which is the source of the confusion on initial commissioning.
3. Root Cause Analysis
LOGO! Soft Comfort uses a device descriptor (vendor ID, device ID, firmware version triplet) in its Hardware Catalog → LOGO! Base Module tree to select the correct program interpreter and parameter set. The V8.2.1 catalog ships with these entries:
- LOGO! 8 (0BA0 Standard)
- LOGO! 8.1 (0BA1 / 0BA2)
- LOGO! 8.2 (0BA0)
There is no LOGO! 8.3 entry in the LSC V8.2.1 catalog. When the user attempts an online connection, LSC queries the device, receives the LOGO! 8.3 firmware signature, and rejects it because the descriptor is unknown. The error string "remote device cannot be accessed" is the generic fallback message thrown by the communication library when the device-class handshake fails — LSC does not distinguish between "no route," "wrong protocol," and "unknown firmware" at the user layer.
3.1 Confirming the Diagnosis
Open LOGO! Soft Comfort and inspect the catalog. If you see Device selection → LOGO! BM with entries ending only at LOGO! 8.2, you are running a pre-8.3 build. Field verification procedure:
- Launch LOGO! Soft Comfort.
- Select Help → About. Confirm the build number.
- Open File → Project Properties → Hardware. The right-hand dropdown lists supported base modules.
- If the highest entry is "LOGO! 8.2", LSC must be upgraded to V8.3 or later.
3.2 Layer-3 Diagnostic Checklist (Excluded Causes)
| Check | Expected | Actual in reported case | Verdict |
|---|---|---|---|
| Ping ICMP echo | Reply TTL=255 | Reply TTL=255, 0% loss | Pass |
| ARP resolution | MAC returned | Returned | Pass |
| Port 80 (LOGO! Web server) | HTTP 200 if enabled | Reachable | Pass |
| Port 8080 (LSC transfer) | TCP SYN/ACK | Reachable | Pass |
| Windows Firewall inbound rule for LSC | Allowed | Allowed | Pass |
| LSC device catalog recognizes LOGO! 8.3 | Yes | No (V8.2.1) | FAIL — root cause |
4. LOGO! 8.3 Hardware Specifications
| Parameter | LOGO! 8.3 (6ED1052-1FB08-0BA1) |
|---|---|
| CPU type | ARM Cortex-A8 compatible |
| Program memory | 8,500 function blocks (4,000 retentive) |
| Integrated I/O | 8 DI (24 V DC) / 4 DO (relay or transistor) |
| Ethernet interface | RJ45, 10/100 Mbit/s, auto-MDIX |
| Supported protocols | S7 (PUT/GET), Modbus TCP, HTTP, DHCP, NTP, SMTP, SNMP |
| Default IP (factory) | 169.254.0.9 / 255.255.0.0 |
| Web server port | 80 (HTTP) / 443 (HTTPS in newer FS) |
| Supply voltage | 24 V DC (6ED1052-1Mx08) or 115/230 V AC (6ED1052-1FB08) |
| Operating temperature | 0 °C … +55 °C horizontal, 0 °C … +45 °C vertical |
| Approvals | CE, cULus, FM, RCM, KC, EAC |
5. LOGO! Soft Comfort Compatibility Matrix
| LSC Version | Build No. | LOGO! 8.x support | LOGO! 8.3 support | Status |
|---|---|---|---|---|
| V8.0 | 8.0.x | 8.0 | No | EOL — do not use |
| V8.1 | 8.1.x | 8.0 / 8.1 | No | Legacy |
| V8.2 | 8.2.1 | 8.0 / 8.1 / 8.2 | No | Shipped in many 2022 kits |
| V8.3 | 8.3.x | All 8.x incl. 8.3 | Yes | Required for 0BA1 hardware |
Only LSC V8.3 contains the LOGO! 8.3 device descriptor in its hardware catalog. The 0BA1 module will not respond to a project upload or download initiated by an LSC V8.2.x client.
6. Resolution Procedure
6.1 Prerequisites
- PC with Windows 10 (1809+) or Windows 11, .NET Framework 4.7.2+.
- Siemens Industry Online Support account (free registration).
- LOGO! 8.3 hardware powered and reachable via ping.
- Ethernet patch cable (Cat 5e or better) — direct connection is acceptable, no switch required.
6.2 Step-by-Step: Upgrade LSC to V8.3
- Open a browser and navigate to the Siemens Industry Online Support download portal.
- Search for "LOGO! Soft Comfort V8.3" or use the direct product filter for article number
6ED1052-1FB08-0BA1. - Select "Software Upgrade LOGO! Soft Comfort V8.3". The file is marked as export-restricted and is gated behind Siemens' extended registration.
- Complete the extended registration form (full name, company, address, end-use declaration). Submit.
- Await the automated export-control email. Siemens' published turnaround is 2 to 3 working days; exceptional cases may extend this.
- Once the approval email arrives, return to the download portal and retrieve the upgrade package (typically
LOGO_Soft_Comfort_V8_3.exeor similar). - Run the installer with administrator privileges. The installer is in-place compatible — existing V8.2 projects upgrade automatically.
- Reboot the PC if prompted.
- Launch the new LSC. Verify under Help → About that the version string shows
8.3.x. - Reopen the project. Open File → Project Properties → Hardware. The hardware dropdown now lists LOGO! 8.3.
- Click Tools → PC → LOGO! (or the upload button). The "remote device cannot be accessed" error is replaced with a successful handshake.
6.3 Step-by-Step: Configure Static IP (Replacing APIPA)
- From the LOGO! onboard display, navigate Settings → Network → IP Address.
- Disable DHCP. Enter static IP, subnet mask, and gateway.
- Example industrial-safe configuration:
LOGO! IP: 192.168.10.50 Subnet Mask: 255.255.255.0 Gateway: 192.168.10.1 - Apply. The LOGO! reboots the Ethernet stack (~3 s).
- Re-ping from the PC. Confirm latency < 5 ms and 0% loss.
6.4 Step-by-Step: Configure PC Network Adapter
- Open Control Panel → Network and Sharing Center → Adapter Settings.
- Right-click the Ethernet adapter → Properties → IPv4 → Properties.
- Select Use the following IP address:
IP: 192.168.10.100 Subnet mask: 255.255.255.0 Default GW: (leave blank for point-to-point) - Confirm with OK. Close all dialogs.
- Open CMD and run
ping 192.168.10.50 -t. Expect TTL=255 replies within 2 ms.
7. Verification Procedure
- Launch LOGO! Soft Comfort V8.3.
- Create a new blank project (or open the existing migrated project).
- From Tools → PC → LOGO!, confirm the connection dialog reports the device as LOGO! 8.3 with its current firmware FS version.
- Click Upload from LOGO! → PC. The current running program is read into LSC.
- Verify that the function block diagram round-trips without warnings or implicit conversions.
- Click PC → LOGO! (Download). The project is compiled, transferred, and a green status banner confirms successful transfer.
- Toggle a digital input on the LOGO! and observe the corresponding bit change in the LSC online monitor (yellow highlight on the active function block).
- Cycle power to the LOGO! to confirm project retention (LOGO! retains the program in non-volatile flash; no battery required).
8. Alternative Connection Methods (Workarounds)
If the LSC V8.3 upgrade is delayed by the export-control registration, the following channels remain fully functional and require no firmware-specific tooling:
8.1 LOGO! Web Server
- Open a browser and navigate to
http://169.254.0.9(or the configured IP). - The default credentials prompt (admin / LOGO!) appears on the login page.
- From the web UI you can: view I/O status, view variables, set the LOGO! to RUN/STOP, edit the message text, and force outputs in service mode.
- No plugin required; works on any operating system with a browser.
8.2 Modbus TCP
| Register Address | Function Code | Meaning |
|---|---|---|
| 00001 – 00024 | FC 02 | Digital inputs (DI1–DI24) |
| 01001 – 01024 | FC 01 | Digital outputs (DQ1–DQ24) |
| 03001 – 03032 | FC 04 | Analog inputs (AI1–AI16, 16-bit) |
| 04001 – 04032 | FC 03 / 04 | Analog outputs / flags |
| 05001 – 05100 | FC 03 / 06 | Variable memory (VM) |
Any Modbus master (Energy Meter, HMI, SCADA, Python pymodbus) can read/write the LOGO! 8.3 without LSC at all. The default Modbus TCP port is 502. This channel is ideal for SCADA integration during the LSC upgrade wait.
8.3 S7 PUT/GET (ISO-on-TCP, port 102)
LOGO! 8.3 acts as an S7 server for up to 4 concurrent connections. A TIA Portal HMI or S7-1200 CPU can read/write VM areas using PUT/GET blocks without LSC involvement.
8.4 SD Card Project Transfer
- Insert a microSD into the LOGO! (slot on the left side of the base module).
- Use the onboard menu Card → LOGO! → Card to export the program to SD.
- Power down, swap the SD into a PC card reader.
- Open the
.lscfile from the SD in LOGO! Soft Comfort V8.3 (or higher).
This is the canonical workaround for the LSC-V8.3 upgrade wait: build the project offline in V8.3, export to SD, then load onto the LOGO! physically.
9. Troubleshooting Matrix
| Symptom | Likely Cause | Fix |
|---|---|---|
| "Remote device cannot be accessed" + ping fails | Cable, IP, mask, or VLAN mismatch | Verify link LEDs, IP/subnet, disable PC firewall briefly |
| "Remote device cannot be accessed" + ping OK | LSC V8.2 client vs LOGO! 8.3 firmware | Upgrade LSC to V8.3 |
| Ping OK, web server unreachable | HTTP disabled or wrong port | Enable web server under Settings → Webserver |
| Ping OK, Modbus timeout | Modbus disabled or wrong FC | Enable Modbus server under Settings → Modbus |
| LSC hangs on "Connecting..." | Multiple network adapters active | Disable Wi-Fi/VPN adapters; specify adapter in LSC options |
| Transfer succeeds but changes not stored | LOGO! in STOP without confirm prompt | Accept the "Save retentive data?" prompt |
| Connect to 0BA0 works, 0BA1 fails | Same V8.2 LSC issue | Upgrade LSC to V8.3 |
10. Siemens Export-Restriction Registration Notes
Recommended project workflow to absorb the delay:
- On day one: submit the export-registration form immediately after receiving new LOGO! 8.3 hardware.
- On day one: continue using LSC V8.2 to maintain legacy 0BA0 sites.
- On day one: use the LOGO! web server or Modbus TCP for I/O verification on the new hardware.
- On day 3–4: receive the approval email and complete the LSC V8.3 download.
- On day 4: full programming, upload, and download is unblocked.
11. Frequently Asked Questions
Why does my LOGO! 8.3 return "remote device cannot be accessed" even though ping succeeds?
The ICMP ping proves the network layer is healthy. The error is thrown by LOGO! Soft Comfort V8.2.x because its device catalog does not contain a descriptor for the LOGO! 8.3 generation (0BA1 hardware). Upgrade to LOGO! Soft Comfort V8.3 or later to add the LOGO! 8.3 entry to the hardware catalog.
Can I use the 169.254.0.0/16 APIPA range as a permanent industrial IP scheme?
No. The 169.254.0.0/16 block is reserved by IANA (RFC 3927) for Automatic Private IP Addressing. Hosts auto-assign addresses in this range only when no DHCP server responds. Use it for temporary point-to-point commissioning, then assign a fixed IP in 192.168.0.0/16 or 10.0.0.0/8 for production.
Which LSC version is required for LOGO! 6ED1052-1FB08-0BA1?
LOGO! Soft Comfort V8.3 or later. LSC V8.2.1 is the highest build that does not recognize the LOGO! 8.3 device class; downloading to or uploading from a 0BA1 module fails with "remote device cannot be accessed." The V8.3 upgrade is gated by Siemens export-restriction registration that typically takes 2 to 3 working days.
Is the LOGO! 8.3 backward compatible with LOGO! 8.2 programs?
Yes. Programs authored in LSC V8.2 and saved as .lsc are auto-migrated when opened in LSC V8.3. The migration is non-destructive; you can save back to the original version provided no V8.3-only function blocks are used. Always archive the pre-migration .lsc as a baseline.
How do I connect to a LOGO! 8.3 without LOGO! Soft Comfort installed?
Use the LOGO! web server on port 80 (browse to http://<ip>) for status, I/O forcing, and RUN/STOP control, or use Modbus TCP on port 502 with any Modbus master (SCADA, HMI, energy meter, or a pymodbus Python script). The web server and Modbus server are firmware-level features and do not depend on the LSC client version.
What firmware FS version ships on a new 6ED1052-1FB08-0BA1?
Factory-fresh units ship with firmware FS 01. Siemens releases bug-fix FS increments (FS 02, FS 03, ...) via the Industry Online Support portal as free firmware updates. Each new FS is fully backward compatible with prior program files. Check the current FS level under LOGO! Menu → Diagnostics → Firmware.
Why does my new LOGO! 8.3 kit ship with LSC V8.2.1 instead of V8.3?
Several regional sales kits bundle the DVD edition of LSC V8.2.1 because the V8.3 download is export-restricted and cannot be pre-bundled on physical media that crosses customs borders. The expectation is that the customer performs the free V8.3 download and extended registration after purchase.