Upgrading LOGO! Soft Comfort V8.2.1 to V8.3: Compatibility Guide

David Krause11 min read
HMI ProgrammingSiemensTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Upgrading LOGO! Soft Comfort V8.2.1 to V8.3: Compatibility Guide

The decision to upgrade LOGO! Soft Comfort (LSC) from V8.2.1 to V8.3 depends almost entirely on the target hardware generation. Siemens ships LSC V8.3 as the mandatory programming environment for the new LOGO! 8.3 (OBA8) base modules, but the same installer remains backward compatible with LOGO! 6, 7, and 8 (OBA6/OBA7/OBA8) programs. For users who own only legacy modules, the functional gain is limited to three deliverables: encrypted program upload, LOGO! cloud connectivity, and the bundled LOGO! Web Editor V1.1.0. This reference walks through the compatibility matrix, the new feature set, the migration path, and the verification steps required after the upgrade.

1. Overview of the LSC V8.3 Release

LOGO! Soft Comfort V8.3 is the engineering environment for the LOGO! logic module family. Siemens publishes LSC V8.3 as a free-of-charge upgrade that can be installed on top of any existing licensed V8.x installation. Unlike a full version, the upgrade installer preserves prior license keys and registered projects while exposing new functionality and the latest device firmware compatibility.

The headline change in V8.3 is not a rewrite of the FBD/Ladder editor. The ladder, FBD, and UDF editors are functionally identical to V8.2.x. The release is positioned as a hardware-enablement package for LOGO! 8.3 modules (catalog suffix ...08-0BA0) and as a security/cloud extension for existing LOGO! 8.0/8.1/8.2 units.

Compatibility rule: LSC V8.3 can program every LOGO! generation from LOGO! 6 (OBA6) through LOGO! 8.3 (OBA8). Conversely, LSC V8.2.x cannot program a LOGO! 8.3 module because V8.2 lacks the device firmware descriptor for the new hardware.

For official Siemens documentation of the LOGO! 8 system, refer to the LOGO! 8 system manual on the Siemens Industry Online Support portal:

2. Hardware Compatibility Matrix

The following table consolidates supported target hardware for each Soft Comfort version. Use it before opening any project in V8.3.

LOGO! Generation Catalog Suffix Programmed by LSC V8.2.x Programmed by LSC V8.3 Cloud Access
LOGO! 6 (OBA6) ...-0BA0 (06 series) Yes Yes (backward) No
LOGO! 7 (OBA7) ...-0BA0 (07 series) Yes Yes (backward) No
LOGO! 8.0 (OBA8) ...-0BA0 (08 series, early) Yes Yes Yes (with V8.3)
LOGO! 8.1 (OBA8) ...-0BA1 Yes Yes Yes (with V8.3)
LOGO! 8.2 (OBA8) ...-0BA2 Yes Yes Yes (with V8.3)
LOGO! 8.3 (OBA8) ...-0BA3 / ...-0BA8 No Yes (required) Yes

The user-reported module in the field report, 6ED1052-1MD08-0BA0, is a LOGO! 8.3 base module with display, 230 V AC supply, 8 digital inputs, and 4 relay outputs (LOGO 230RCE variant). Any project bound for that module must be edited with LSC V8.3 or later; V8.2.1 will refuse to download.

3. Functional Changes Between V8.2.1 and V8.3

Three primary feature deltas exist. Each one is bounded by target hardware and firmware, not by Soft Comfort version alone.

3.1 Encrypted Program Upload

V8.3 introduces upload protection that uses a project-level password to encrypt the program stored in the LOGO! 8 module's flash. Without the password, the program cannot be retrieved from the device—only its behavior can be observed via online monitoring. Earlier V8.2.x builds transfer programs in clear form.

Enable encryption from Tools → Options → Protection or by selecting Protect program in module during the transfer dialog. The encrypted upload requires LOGO! 8 firmware ES (Engineering Status) revision 1.16.0 or higher on the target device.

3.2 LOGO! Cloud Connectivity

Cloud access was introduced with LOGO! 8.2 firmware and is exposed through the Soft Comfort transfer dialog starting with V8.3. The V8.3 release replaces the manual configuration workflow of V8.2.1 with a guided wizard that provisions AWS IoT or Siemens MindSphere credentials via the LOGO! CMR (Communication Module for Remote). For installations using 6ED1057-1EA01-0BA8 (LOGO! CMR2020) or 6ED1057-1EA00-0BA0 (LOGO! CMR2040), the V8.3 wizard is the supported path.

3.3 Bundled LOGO! Web Editor V1.1.0

The V8.3 download packages the LOGO! Web Editor (LWE) V1.1.0. LWE generates custom HTML dashboards that run on the LOGO! 8 web server, using variable tags from the LSC project as data bindings. V1.1.0 adds:

  • Drag-and-drop widget palette (numeric input/output, slider, indicator lamp, trend chart).
  • User-rights management with three privilege tiers.
  • Support for LOGO! 8.2 and 8.3 firmware; legacy LOGO! 8.0/8.1 modules receive V1.0.x widgets only.
  • Direct upload from LWE to the target device over the same Ethernet interface used by LSC.

If the deployment uses only the standard LOGO! on-board web pages (status of I/Os, variable table), the Web Editor upgrade does not deliver any visible change.

4. New Features Specific to LOGO! 8.3 Hardware

Several capabilities that ship only with LOGO! 8.3 base modules are unlocked exclusively by LSC V8.3:

  • 16 kB program memory (up from 8 kB on LOGO! 8.0/8.1/8.2) — allows up to 400 function blocks.
  • Extended retentive memory — 250 remanent flags plus 250 remanent bytes across all base modules.
  • Data log on SD card — built-in CSV logging of any variable or process value to a micro-SD card inserted in the LOGO!.
  • Web server TLS — HTTPS for the on-board web pages and for LWE dashboards.
  • LOGO! Access Tool 2.0 — read/write variable access via HTTPS API.

These hardware-bound capabilities remain invisible to owners of LOGO! 6/7/8.0–8.2 modules. Migrating to V8.3 alone does not deliver them; the device firmware revision must be ES 1.20.0 or higher, which is factory-burned on LOGO! 8.3 modules.

5. Prerequisites

Before installing LSC V8.3, confirm the following:

  1. Windows version: Windows 10 (64-bit) or Windows 11. Windows 7 SP1 is supported but Microsoft has retired mainstream support.
  2. Existing license: A registered LSC V8.x license is preserved by the upgrade installer. Run the upgrade on top of the existing install directory, typically C:\Program Files\Siemens\LOGO Soft Comfort V8.3.
  3. Free disk: 1.5 GB for the upgrade package, additional 500 MB after extraction.
  4. Ethernet or USB cable: For transferring programs to LOGO! 8 devices. LOGO! 6 and 7 require the PC-LSC USB cable or serial adapter.
  5. Admin rights: Required for installer privilege escalation.

6. Step-by-Step Upgrade Procedure

Follow this sequence to upgrade an existing LSC V8.2.1 installation to V8.3 without losing settings.

  1. Close any open instance of LOGO! Soft Comfort.
  2. Back up the project library: copy %USERPROFILE%\Documents\Siemens\LOGO\LSC Projects to an external drive.
  3. Export license information: Help → License Manager → Export. Save the resulting .bin file.
  4. Download the upgrade package from the Siemens Industry Online Support portal entry for LOGO! Soft Comfort V8.3.
  5. Run the installer and select Upgrade existing installation.
  6. When prompted, point the installer to the existing install directory and confirm the language packs to retain.
  7. Restart the PC to clear USB driver caches used by the LOGO! PC cable.
  8. Re-import the license file via Help → License Manager → Import.
  9. Open one archived V8.2.1 project and validate it with File → Project → Check Consistency.
Do not uninstall V8.2.1 before installing V8.3. The upgrade installer preserves the original folder; if you uninstall first you lose the registration entries that bind the upgrade to your existing license.

7. Verification After Upgrade

After the upgrade, run the following checks before redeploying to production hardware.

7.1 Project Integrity Check

Open each project that was archived in step 2 of the upgrade. For every project:

  • Compile with F5 or Project → Compile. LSC reports any block that V8.3 no longer supports.
  • Compare the block count and I/O references to the V8.2.1 baseline.

7.2 Online Test Against a Target Device

Connect to the active LOGO! 8 module via Ethernet and verify:

  1. The Device Information dialog shows firmware ES 1.20.x (or the production release on your site) and reports a successful handshake.
  2. Online monitoring shows real-time updates of variable values.
  3. Perform one upload (PC → LOGO) and one download (LOGO → PC) to confirm bidirectional communication.

7.3 Web Editor Smoke Test

For installations using the LOGO! web server:

  1. Launch the bundled LOGO! Web Editor V1.1.0.
  2. Open a backup project with at least one analog tag.
  3. Add a trend widget bound to the tag and deploy.
  4. Browse to http://<LOGO-IP> from a workstation on the same subnet and confirm the trend updates in real time.

7.4 Cloud Connectivity Check

If the project uses the LOGO! CMR for cloud telemetry:

  1. In LSC, open Tools → Cloud Connection.
  2. Confirm that the wizard detects the LOGO! CMR on the network and successfully applies the previously issued X.509 certificate.
  3. Verify a single message lands in the configured AWS IoT topic or MindSphere tenant.

8. Migration Path from LOGO! 6 / LOGO! 7 to LOGO! 8.3

Users running LOGO! 6 (OBA6) modules on V8.2.1 software may upgrade Soft Comfort without touching their existing programs. There is no benefit to running the new editor against legacy devices other than consolidation onto a single installation.

For users planning to migrate the application (not just the editor) from LOGO! 6 to LOGO! 8.3:

  1. Open the LOGO! 6 project in LSC V8.3. The editor converts OBA6 blocks automatically.
  2. Re-bind any Ni1000/LG-Ni1000 temperature inputs to the LOGO! 8.3 AM2 RTD module (6ED1055-1MD00-0BA2) or AM2 PT100 module.
  3. Update Ethernet configuration: LOGO! 6 does not have an on-board Ethernet port. Migration requires either a LOGO! 8 CSM (Communication Signal Module) or direct swap to a LOGO! 8 BM with Ethernet.
  4. Reassign network variables. The LOGO! 6 S7-style variable naming scheme is replaced by LOGO! 8 VM (Variable Memory) addressing (e.g., VW0 → VM0).
  5. Validate the converted program against the new I/O map before powering production loads.

9. Troubleshooting Matrix

Symptom Likely Cause Corrective Action
V8.3 refuses to open a V8.2.1 project Project file corrupted or saved in non-LSC binary format Open in V8.2.1, export as .lsc, then import into V8.3
Encrypted upload reports "ES revision too low" LOGO! 8 module firmware below ES 1.16.0 Perform firmware update via Tools → Update Firmware; module must remain powered during update
Cloud wizard cannot detect LOGO! CMR Network segmentation or CMR in client mode with wrong gateway Verify CMR DIP switches; ping CMR IP from PC
Web Editor V1.1.0 widgets do not render Browser caches old web pages Hard refresh (Ctrl+F5) and clear site data
LOGO! 8.3 module not visible in transfer dialog V8.2.1 still active or wrong Ethernet subnet Confirm V8.3 build number; verify PC and LOGO! share subnet mask
License rejected after upgrade License was bound to original V8.2.1 installation ID Re-import exported .bin license; if lost, contact Siemens license support via Siemens Industry Online Support
Transfer dialog shows font mismatch V8.3 changed the editor default font Cosmetic only; revert via Tools → Options → Editor → Font

10. Field-Proven Caveats

  • Bug-fix policy: Siemens has not published a fixed list of bug fixes from V8.2.1 to V8.3. Treat V8.3 as a feature release, not a maintenance release, for projects on legacy LOGO! hardware.
  • Font change: OBA6 developers notice a different default editor font in V8.3. The change is cosmetic and does not affect compiled behavior. Revert via Tools → Options → Editor.
  • Coexistence: LSC V8.3 and V8.2.1 can be installed side-by-side on the same Windows workstation only if they are kept in separate program directories. Default installations overwrite each other.
  • Web server exposure: The default on-board web server publishes variable values over plain HTTP. For production deployments, activate user-rights management in LWE and restrict access via firewall rules.
  • Old-stock modules: Distributors may continue to ship V8.2.x-compatible modules until inventory is exhausted. Keep at least one licensed V8.2.1 installation available to support these units until end-of-life is confirmed by your supplier.

11. Recommendation by Use Case

Use Case Recommended Action
Single LOGO! 6 module in production No upgrade required. Stay on V8.2.1.
LOGO! 8.0–8.2 modules using only local I/O Optional. Upgrade only if you want encrypted upload or cloud.
LOGO! 8.0–8.2 modules with custom LWE dashboards Upgrade to V8.3 to obtain LWE V1.1.0 widget set.
Any LOGO! 8.3 module present or planned Mandatory upgrade to V8.3. V8.2.x cannot program 8.3 hardware.
Multi-site fleet with mixed LOGO! generations Upgrade centrally to V8.3 for consolidation; retain one V8.2.1 image for legacy units.
Starter kit purchased with WinCC Bundle licenses carry forward to V8.3; upgrade is free.

12. Related Documentation References

For deeper specifications, refer to the official Siemens documentation set:

Is LOGO! Soft Comfort V8.3 free if I already own a V8.x license?

Yes. Siemens publishes the V8.3 upgrade as a free-of-charge installer that runs on top of an existing licensed V8.x installation and preserves the original license keys.

Will V8.3 add new programming functions to my existing LOGO! 8.2 module?

No. The FBD and Ladder editors are functionally unchanged from V8.2.x. New capabilities such as encrypted upload, LOGO! cloud connectivity, and LOGO! Web Editor V1.1.0 are exposed by V8.3, but they depend on the module's firmware generation rather than the editor version.

Does V8.3 improve anything for LOGO! 6 modules?

Functionally no. The editor opens and saves LOGO! 6 projects, but the underlying program logic, I/O count, and on-board features of the OBA6 module remain identical to V8.2.x. The visible difference is limited to a new default editor font.

Can I keep V8.2.1 and V8.3 installed at the same time?

Yes, provided you install them in separate directories and avoid the default installation path for one of them. Side-by-side installations are useful when one site still runs older LOGO! modules that need a V8.2.x editor.

Do I need V8.3 to program a LOGO! 8.3 base module such as 6ED1052-1MD08-0BA0?

Yes. The LOGO! 8.3 module firmware (ES 1.20.0 and above) is not recognized by LSC V8.2.x. LSC V8.3 is the minimum supported engineering environment for any device with the ...08-0BA8 catalog suffix.

Back to blog