Resolving LogoSoft V8.4 'Unable to Access Remote Device' Error

1. Problem Overview

Engineers commissioning a Siemens LOGO! 8 logic module with LOGO!Soft Comfort V8.4 (also written LogoSoft V8.4) frequently encounter the dialog error "Unable to access the remote device" when attempting a download, online change, or network scan. The error is a generic connection-failure message raised by the LOGO!Soft Comfort Ethernet transfer layer when the engineering PC cannot establish a TCP session to the LOGO! 8 base module on TCP/10005 (LOGO! transfer protocol) and TCP/80 (web server).

The fault is observed most often on the LOGO! 8.3 and LOGO! 8.4 hardware revisions, with part numbers in the 6ED1052-1xxxxx-0BAx family, including the commonly deployed 6ED1052-1MD08-0BA0 (LOGO! 8 with display, 24 V supply, 8 DI / 4 DO, integrated Ethernet). The same dialog appears on 6ED1052-1HB08-0BA0 (relay output), 6ED1052-1FB08-0BA0 (without display), and the 230 V variants 6ED1052-1MD08-0BA1 / 6ED1052-1HF08-0BA1.

2. Affected Hardware and Software

The official device manual for the 6ED1052-1MD08-0BA0 is the LOGO! 8 System Manual, entry ID 109741041. Always cross-reference the manual's chapter "Network configuration" and "LOGO!Soft Comfort online functions" before changing network settings on a production system.

3. Root Cause Analysis

The dominant root cause for the "Unable to access the remote device" dialog is a subnet mismatch between the engineering PC and the LOGO! base module. When the LOGO! and the PC are not in the same IP subnet, the operating system TCP/IP stack on the PC will not deliver frames to the LOGO! MAC address because the destination IP is considered "remote" and must be reached through a gateway. If no gateway exists or the route is unreachable, the transfer socket times out, and LOGO!Soft Comfort reports the failure as "Unable to access the remote device."

3.1 How IPv4 Subnets Determine Reachability

An IPv4 address is a 32-bit value typically written as four decimal octets. The subnet mask defines which leading bits identify the network and which trailing bits identify the host. With a /24 mask (255.255.255.0) the first three octets define the network, and the fourth octet (0–255) defines the host.

Example with a /24 subnet mask:

• PC IP: 192.168.0.20 / 255.255.255.0 → network 192.168.0.0/24, host range .1 – .254
• LOGO! IP: 192.168.0.10 / 255.255.255.0 → same network 192.168.0.0/24 → reachable
• LOGO! IP: 192.168.1.10 / 255.255.255.0 → different network 192.168.1.0/24 → unreachable without a router

If the PC is connected through a USB-Ethernet adapter, that adapter is a separate NIC with its own IP configuration. The same rule applies: the first three octets of the USB-Ethernet adapter and the LOGO! must match on a /24 mask.

3.2 Secondary Causes

4. Preconditions Before Changing Network Settings

1. Verify the LOGO! firmware version and IP configuration from the on-board display: LOGO! → Menu → Network → IP Address / Subnet Mask. Write down all four octets exactly as displayed.
2. Record the PC's IP and subnet on the active Ethernet adapter that is physically wired to the LOGO!. On Windows, run ipconfig /all in an elevated command prompt. Identify the adapter by description (e.g., "Realtek PCIe GbE Family Controller" for onboard, "ASIX AX88179" for USB-Ethernet).
3. Confirm that only one active path exists between the PC and the LOGO!. If both onboard Ethernet and a USB-Ethernet adapter are connected, disable all other NICs in Device Manager or unplug them.
4. Disable any VPN client (Cisco AnyConnect, WireGuard, OpenVPN, FortiClient) and corporate endpoint protection temporarily. Many enterprise VPN clients bind to the active NIC and hijack routing.
5. If the engineering PC sits in a managed domain, obtain local admin rights; changing the IPv4 address of an adapter requires elevation.

5. Step-by-Step Solution: Aligning the PC and LOGO! Subnets

Two working paths exist. Choose the one that fits the network policy on the engineering PC.

5.1 Option A — Change the PC's IP to Match the LOGO!

1. Open Control Panel → Network and Sharing Center → Change adapter settings.
2. Right-click the wired adapter connected to the LOGO! → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties.
3. Select Use the following IP address and enter:

   IP address:        192.168.0.20     (any free host in the LOGO! subnet)
   Subnet mask:       255.255.255.0
   Default gateway:   <blank>          (leave empty for direct PC-to-LOGO! link)
   

4. Click OK twice. The Windows TCP/IP stack re-binds within ~2 seconds.
5. Verify with ipconfig /all that the new IP is bound and the link is up (Media State: "Enabled", Dhcp Enabled: "No").
6. Open an elevated cmd and execute ping 192.168.0.10 -t (replace with the LOGO!'s actual IP). A reply of <2 ms with no loss confirms L3 reachability.
7. Launch LOGO!Soft Comfort V8.4 → Tools → Transfer → PC → LOGO!. The transfer dialog should now show the LOGO! in the discovered-device list with its IP and part number.

5.2 Option B — Change the LOGO!'s IP from the On-Board Display

1. On the LOGO! display, navigate: Menu → Network → IP Address.
2. Use ◀/▶/▲/▼ to set the four octets. Confirm each with OK.
3. Set Subnet Mask to 255.255.255.0 unless the plant uses a different mask. If the plant network is 255.255.0.0, set the first two octets of the LOGO! to match the PC's first two octets.
4. Press ESC back to the main screen. The LOGO! applies the new IP without restart; existing Ethernet connections drop briefly (~3 s) while the IP changes.
5. On the PC, set the active adapter to the same subnet (e.g., 192.168.0.20/24 if the LOGO! is now 192.168.0.10/24) and ping to verify.

6. Configuring the LOGO!Soft Comfort V8.4 Transfer Channel

1. Start LOGO!Soft Comfort V8.4.
2. Open the project that matches the connected LOGO! hardware (or create a new one sized to 6ED1052-1MD08-0BA0: 400 function blocks, 250 retentive markers, 64 digital/analog I/O flags).
3. Choose Tools → Options → Interface.
   • For Ethernet: select Ethernet TCP/IP and pick the correct adapter. If multiple NICs are present, the correct one shows the same IP you set in step 5.
   • For USB cable (6ED1057-1AA01-0BA0 USB): select USB.
4. Click Detect. The dialog polls the network for LOGO! devices and shows each base module's MAC, IP, and device name.
5. If the LOGO! appears, select it and click OK. The main toolbar's transfer buttons (PC → LOGO!, LOGO! → PC, Compare) become active.
6. If no device is detected, open a command prompt and verify L3/L4 reachability before continuing:

   ping 192.168.0.10
   telnet 192.168.0.10 10005
   telnet 192.168.0.10 80
   

   A successful TCP open on 10005 confirms that the LOGO! transfer service is listening and the firewall on the PC is not blocking it.

7. Verification Procedure

Run the following checklist to prove the connection is healthy before transferring program changes.

1. Physical layer: LINK LED on the LOGO! RJ45 is solid green. PC adapter shows "Enabled" link speed of 100 Mbit/s full-duplex (LOGO! 8 supports 10/100 Mbit/s, auto-negotiation).
2. Layer 3: ping returns 0% loss, RTT < 5 ms on a direct cable.
3. Layer 4: telnet <LOGO_IP> 10005 opens a blank socket. telnet <LOGO_IP> 80 returns the LOGO! web server HTML banner.
4. Application: Browser http://<LOGO_IP> shows the LOGO! web server with the variables view. Default credentials (if password set in the project) are required for write operations; read access is anonymous.
5. LOGO!Soft transfer: Tools → Transfer → PC ↔ LOGO! completes with "Transfer successful" and a green status bar. The transfer log shows the firmware version and project CRC.
6. Round-trip: LOGO! → PC reads back the same project. Compare should report "Identical".

8. Alternative Connection Paths

8.1 Direct Peer-to-Peer (1:1 Cable)

LOGO! 8 supports auto-MDIX, so a straight-through or crossover Cat5e patch cable works identically. This is the cleanest configuration for laptop-to-LOGO! commissioning on the shop floor and eliminates any switch-induced DHCP or VLAN issues.

8.2 Through a Managed Switch

If a switch is in the path, disable Spanning Tree on the LOGO! port or enable PortFast, otherwise the first 30–60 s of transfer will be blocked. Also confirm that the switch is not blocking multicast, because LOGO!Soft discovery uses a UDP broadcast on port 17585 (LOGO!Soft comfort discovery protocol) in addition to TCP/10005.

8.3 LOGO! CMR (Remote Connection)

The LOGO! CMR (6GK7142-7BX00-0AX0) and the LOGO! 8.4 CMR2020 (6GK7142-7EX00-0AX0) provide 4G/UMTS or Ethernet WAN access to remote LOGO!s. The "Unable to access the remote device" error appears identically on LOGO!Soft when the CMR is offline, the SIM has no data plan, or the public IP NAT hairpin is not allowed. Confirm the CMR signal-strength LEDs and the SIM APN.

8.4 VPN / Remote Maintenance Routers

When the LOGO! is on a remote site behind a SCALANCE M or MOXA EDR router, ensure the local routing table on the PC has a route to the LOGO! subnet via the VPN tunnel adapter. route print will show the persistent route. Many engineers forget that a Windows VPN adapter takes over the default gateway while connected, breaking the local link to a directly attached LOGO!.

9. Common Pitfalls and Edge Cases

9.1 Wi-Fi vs. Wired Confusion

If the PC is connected over Wi-Fi to a corporate LAN, and the LOGO! is wired directly to the PC's Ethernet port, LOGO!Soft might select the Wi-Fi adapter as "active" because of metric order. Force the wired adapter by unchecking "Auto-detect" in Options → Interface and selecting the wired adapter explicitly.

9.2 DHCP Lease Expiry Mid-Session

If the PC is set to DHCP and the network has no DHCP server, Windows will fall back to APIPA 169.254.x.x after ~30 s. The LOGO! default IP is 192.168.0.10, which is not in the APIPA range, so the connection will fail. Set a static IP on the PC side as the long-term fix.

9.3 Multiple LOGO! on the Same Network

When several LOGO! modules are on the same LAN, change the default IP of each to a unique address. The LOGO! has no DHCP server, but it can be a DHCP client if the project option "Obtain IP address automatically" is enabled. In commissioning, prefer static IP so the engineering PC's Hosts file or known-IP list can address each one.

9.4 Windows Firewall on a Domain PC

Corporate GPOs may push strict Windows Defender Firewall rules that block inbound and outbound on TCP/10005. Ask the IT admin to add a firewall rule:

New-NetFirewallRule -DisplayName "LOGO!Soft V8.4 transfer" `
  -Direction Inbound -Program "C:\Program Files\Siemens\LOGO!Soft Comfort V8.4\LSC.exe" `
  -Action Allow -Profile Any
New-NetFirewallRule -DisplayName "LOGO!Soft V8.4 transfer (out)" `
  -Direction Outbound -Program "C:\Program Files\Siemens\LOGO!Soft Comfort V8.4\LSC.exe" `
  -Action Allow -Profile Any

9.5 Project Mismatch (Different FS Version)

LOGO!Soft V8.4 will refuse to download a project compiled for FS:04 firmware onto a base module running FS:02. The transfer dialog then raises a variant of "Unable to access the remote device" with a "device does not support the program" sub-message. Match the firmware using Tools → Options → Device Family → LOGO! 8.3 / 8.4.

10. Network Configuration Reference

11. Troubleshooting Matrix

12. Security Considerations

The LOGO! 8 base module's web server and transfer service have no built-in user authentication for the transfer channel (TCP/10005). Anyone with L3 reachability can upload a new program. In a production environment, isolate the LOGO! on a private VLAN, restrict the firewall to the engineering workstation's IP, and set a program password in the project (File → Properties → Password) to prevent unauthorized read-back.

If remote maintenance is required, terminate the connection at a SCALANCE S615 or similar industrial security appliance and require VPN client authentication. Disable the LOGO! web server if it is not used: Tools → Ethernet Connections → Web server access = off in the project.

13. Frequently Asked Questions