Configuring LOGO! Soft Comfort V8.1 Update Centre for Updates

Overview of the LOGO! Soft Comfort Update Centre

The Update Centre is an integrated utility inside Siemens LOGO! Soft Comfort (LSC) that queries a Siemens-hosted XML service to determine whether the locally installed LOGO! Soft Comfort build (and any matching LOGO! hardware firmware service packs) is the most recent revision. When the tool reports "no update available" or returns an HTTP/transport error, the message is often the same dialog text regardless of whether the software is current or whether the request failed. This ambiguity is a recurring commissioning-time complaint because field engineers cannot distinguish between (a) the local LSC being on the latest build, (b) the URL endpoint being unreachable, or (c) the HTTP service returning an unexpected payload. This reference walks through the URL behaviour, the three official channels that resolve the ambiguity, and the procedure to manually reconcile the locally installed version against the current Siemens-published release.

Update Centre URL and Endpoint Configuration

The Update Centre inside LSC V8.1 calls the address:

This URL is a landing page redirector, not a direct XML/RPC endpoint. The LSC client is expected to follow the HTTP 301/302 redirect to the SiePortal Product Support entry identified by pnid=13617 (the LOGO! product tree). The redirect chain typically terminates at:

Inside SiePortal, the Product Support page exposes three sub-tabs the Update Centre consumes:

If a corporate proxy or firewall strips the User-Agent: LOGOSoftComfort/8.1 header on outbound HTTP, the redirect will fail and LSC will display a generic "error" dialog even though the upstream SiePortal service is healthy. Always validate connectivity from the engineering workstation first using a browser pointed directly at the redirect target.

Interpreting Update Centre Status Messages

LSC V8.1 collapses three distinct server responses into two visible dialog strings:

Three Official Channels for LOGO! 8 Update Information

When the Update Centre is inconclusive, three Siemens-authoritative sources can be polled directly. Treat them in the order listed — earlier sources are the most reactive to new releases.

Channel 1: SiePortal Product Support Entry (pnid=13617)

The Product Support tree for LOGO! is anchored at entry ID 13617. Filter the entry list by Entry Type = Download to see every released installer, service pack, and firmware companion package:

Sort the resulting table by Release Date (descending). The first row whose title contains "LOGO! Soft Comfort" is the most recent LSC build. Cross-reference the article number with the build number shown in Help → About inside LSC.

Channel 2: SiePortal Product Innovation Documents

Each functional state of the LOGO! 8 hardware (FS:01 through FS:04 as of LSC V8.1) ships with a dedicated Product Innovations bulletin. These documents catalogue the firmware delta, the new instructions supported in LSC, and any retired features. The FS:04 bulletin is published at:

This document is the authoritative reference for the functional state of the LOGO! 8 base module (order number suffix ...0BA8) currently shipping. Newer functional states are appended as new document numbers and announced through the SiePortal notification feed.

Channel 3: SiePortal Product Notes (dtp=ProductNote)

For change-log-equivalent information that the Update Centre does not surface, query the entry type Product Note at:

Each note carries a publication date and a category tag (compatibility, security advisory, functional state release, end-of-life). Subscribe to the RSS feed for this filter to be notified of new releases without polling the web page manually.

LOGO! 8 Hardware Generation and Functional State Mapping

The LOGO! 8 family (marketing designation LOGO! 8, type designation suffix 0BA8) is released in incremental functional states (FS). Each FS is firmware-locked to a specific LSC minimum version. The mapping that matters when interpreting the Update Centre is:

Manual Verification Procedure: Determining the Current Release

When the Update Centre is unreachable or ambiguous, perform the following five-step reconciliation between the local install and the current Siemens release.

1. Capture the local LSC build: Open LSC, choose Help → About LOGO! Soft Comfort. Record the full version string (e.g. LOGO! Soft Comfort V8.1.0 - Build 12345) and the Installation Date.
2. Query SiePortal directly: Browse to https://support.industry.siemens.com/cs/products?dtp=Download&mfn=ps&pnid=13617&lc=en-WW. Sort by Release Date descending and locate the highest entry whose title begins with LOGO! Soft Comfort. Record its article number and release date.
3. Cross-reference functional state: Open the most recent Product Innovations document for the LOGO! 8 FS you currently own (FS:04 reference is document 109742269). Confirm whether the minimum LSC version listed for that FS matches your local build.
4. Compare release dates: If the SiePortal release date is later than your LSC installation date, an update exists. If equal or earlier, the local install is current.
5. Decision branch:
   • If an update exists and the destination LSC version supports your hardware FS → download via the SiePortal article link (do not rely on the in-app link if HTTP was failing).
   • If no update exists → record the reconciliation evidence (build string + SiePortal capture) in the project commissioning folder.

Verifying LOGO! Hardware Firmware Version On-Device

The on-device firmware string is authoritative — the LSC install version is a separate version space from the device firmware. To read the firmware of a connected LOGO! 8 base module:

1. Connect the LOGO! to the engineering PC via Ethernet.
2. In LSC, choose Tools → Transfer → LOGO! → Online (or press Ctrl+D).
3. Once online, open Tools → Device Information (menu location varies by LSC build; in V8.1 it is under Tools → Diagnostics).
4. Read the Firmware Version field. Compare against the functional-state table above.
5. Record the Article Number shown in the device info — this confirms the variant (e.g. 6ED1052-1MD08-0BA2 for LOGO! 12/24RCE with FS:02).

If the firmware field reads FW: V1.08.xx, the device is on the original FS:01 OBA8 build. If it reads FW: V1.09.xx or higher, it is on FS:02 or later.

Working in Offline or Air-Gapped Environments

Many production networks restrict outbound HTTP from engineering workstations. In that case, the Update Centre cannot reach www.siemens.com/logo-update and will return the generic "error" dialog. The recommended workflow for an air-gapped PC:

1. Download the latest LSC installer on an internet-connected workstation using the SiePortal article URL captured in the previous section.
2. Copy the installer (a signed .exe or ZIP) onto approved removable media.
3. Verify the SHA-256 hash of the installer against the value published on the SiePortal download page.
4. Install on the air-gapped workstation using Setup.exe /silent (LSC supports the standard InstallShield silent flag set).
5. Suppress the Update Centre prompt at next launch via Extras → Options → Update Centre → "Do not check for updates" to avoid false alarms.

Update Centre Error Codes and Resolution Matrix

Commissioning Checklist for LOGO! 8 FS:04 Deployments

When the engineering workstation is first provisioned against a LOGO! 8 FS:04 fleet, verify the following items before commissioning the first cabinet:

Modbus TCP Feature Verification on LOGO! 8 Generation

Modbus TCP server capability was introduced on LOGO! 8 with functional state FS:02 and is preserved in FS:03 and FS:04. To verify the feature is active on a deployed base module:

1. Open the web server of the LOGO! (default http://<LOGO_IP>) and authenticate with the device password.
2. Navigate to Modbus TCP in the left navigation. If the entry is missing, the device firmware predates FS:02.
3. Confirm the Modbus TCP Enable toggle is ON and the listening port is 502.
4. From a Modbus master (e.g. a test HMI or mbpoll on the engineering PC), poll holding register 0 — the LOGO! will echo a known marker byte if the server is responding.
5. If the device is on FS:01 firmware, the Modbus TCP toggle is absent in the web UI; either upgrade the physical module to FS:02 (or higher) or use the legacy LOGO! 7 protocol over RS-485 instead.

Project Compatibility Between LSC Versions

Opening an LSC project saved in a newer version on an older LSC install is blocked by design. The compatibility direction matrix is:

If the Update Centre reports the local install is up to date but a colleague insists a newer build exists, the most common cause is that the colleague has a different channel of LSC installed (e.g. a service-rep-only internal release that is not published on SiePortal). Confirm both parties are checking the same pnid filter and the same locale code (lc=en-WW, lc=en-UK, etc.).

Field-Proven Caveats

• The Update Centre dialog does not report the device firmware — only the LSC install version. Even if LSC is "up to date", a separately purchased LOGO! 8 base module may carry a different firmware than the one currently in service. Always verify on-device firmware during commissioning.
• Siemens does not publish a formal changelog between LOGO! 8 minor service packs. Differences are usually localised to installer metadata, certificate refreshes, and bug fixes that do not change the supported instruction set. Major feature additions land at the next functional state.
• On the original LOGO! 8 (FS:01) modules, the Update Centre may report a phantom upgrade target for FS:02 modules. This is expected: the tool only knows the LSC build number, not the device FS.
• The demo installer available from SiePortal is feature-complete but watermarks the printed circuit diagram with a "DEMO" stamp. Do not use the demo installer for production projects.