Resolving SITRANS LUT400 Browser Firmware Compatibility Errors

Resolving SITRANS LUT400 Browser Firmware Compatibility Errors

The Siemens SITRANS LUT400 series of ultrasonic level controllers is engineered for continuous level, volume, flow, and pump control applications across water/wastewater, chemical, and process industries. When commissioning, calibrating, or maintaining a LUT420, LUT430, or LUT440, engineers connect to the device's integrated web server using a standard browser over USB. One of the most common commissioning roadblocks is the browser rejection message "The Browser revision is not compatible with the device firmware." This article provides a complete diagnostic, recovery, and verification workflow for this specific compatibility error, with emphasis on legacy units like the LUT430 with serial PBD/E9190219, hardware revision 1.00.00-00, and firmware revision 1.01.01-04.

1. Problem Description and Symptom Matrix

The failure manifests under a tightly defined set of conditions that engineers must verify before assuming any other cause:

When the first symptom is reported, the engineer should collect the firmware and loader revisions from the device's local display menu Information > Device Information or from the bar-coded label on the enclosure before any tool is changed.

2. Affected Devices, Hardware, and Firmware Branches

The SITRANS LUT400 family comprises three primary models, all sharing the same web server firmware family but differing in I/O and feature sets:

• SITRANS LUT420 - Open-channel flow and basic level measurement; single current loop, no relays.
• SITRANS LUT430 - Pump and flow controller with up to 6 relays, dual current loops, HART 7.
• SITRANS LUT440 - Full-featured unit with batch processing, totalizer, and advanced pump control algorithms.

The browser-compatibility issue is bound to the firmware version, not the model. The known-firmware tree of interest is:

The factory-loaded firmware on early LUT430 units (shipped 2013-2014) was firmware revision 1.01.01-04 paired with loader revision 2.01.01-00. These units predate the new web UI bundle introduced with firmware 1.02.01-00, and Siemens distributes a version-pinned "SITRANS LUT400 Web Browser" installer for each branch. The compatibility table is published in Siemens support entry ID 109776905.

3. Root Cause Analysis

The LUT400 web server serves a versioned HTML/JS application bundle that includes a build marker file version.txt shipped inside the device. The browser installer on the PC maintains its own minimum-compatibility manifest. During the HTTPS handshake, the embedded browser plugin on the PC performs the following checks in sequence:

1. Reads /fw_version from the device over USB CDC ACM at 115200 bps, 8N1.
2. Reads the bundled version.txt from the device's onboard flash.
3. Cross-references both against its own compat.xml manifest in C:\Program Files (x86)\Siemens\SITRANS LUT400 Web Browser\.
4. If the device's web bundle is older than the minimum version the installed browser can serve, it raises the rejection banner. If the device's web bundle is newer than the bundle the installed browser can serve, it raises the same banner.

When the installed PC browser was downloaded from the Siemens support page after firmware 1.02.01-00 was released, and the LUT430 is still running firmware 1.01.01-04, the compat.xml minimum-firmware entry reads 1.02.00-00, but the device reports 1.01.01-04. The check fails, and the banner appears.

A secondary root cause is the USB CDC ACM driver. The LUT400 enumerates as a USB Communications Device Class, Abstract Control Model device. If Windows loads the generic Microsoft usbser.sys driver (in-box since Windows 10 1709) or an older usbcdc.sys, the COM port opens, but some installations (especially Windows 7 x64) report the device under Ports (COM & LPT) as USB CDC Serial Port Emulation with driver version 6.0.2600.3 (Windows XP-era). This older driver does not properly set the RS-232 line-control transitions expected by the LUT400 bootloader when the firmware updater pushes a new image. The result is a partial flash that locks the device into the same error loop.

4. Pre-Repair Verification

Before applying any of the corrective paths below, complete these checks. They prevent unnecessary firmware uploads and isolate the failure layer.

1. Confirm firmware and loader revisions from the device's local HMI. Navigate to Menu > Information > Device Information. Note the firmware, loader, and hardware revisions exactly as displayed.
2. Verify USB enumeration. Open Device Manager and expand Ports (COM & LPT). The LUT400 should appear as USB CDC Serial Port Emulation (COMx). Record the COM number.
3. Test loopback communication. Use a serial terminal at 115200 bps, 8N1, no flow control, on the COM number. Power-cycle the device and watch for the bootloader banner LUT400 Boot v2.01.01. If the banner does not appear, the USB cable or driver is suspect, not the browser.
4. Validate the PC browser version. Open Help > About in the installed Siemens LUT400 Web Browser application. Compare the installed version against the Siemens compatibility table for the device's firmware.
5. Validate AC mains and loop power. The LUT400 draws up to 0.6 A at 24 V DC loop. Insufficient loop power during a firmware upload can corrupt the flash and brick the device. Verify at least 20 V DC is present at the input terminals before proceeding.

5. Solution Path A - Install the Legacy Web Browser Bundle

This path is correct for any LUT400 with firmware revision 1.01.01-04 or earlier. It does not require touching the device firmware.

5.1 Obtain the version-pinned installer

Download the SITRANS LUT400 Web Browser installer from Siemens support entry 62103148. The entry contains multiple installer revisions under its version history. Select the installer tagged "for firmware 1.01.01-04 and earlier". Always cross-check the SHA-256 of the downloaded executable against the value published on the Siemens entry.

5.2 Remove any newer installation

Open Control Panel > Programs and Features and uninstall any existing SITRANS LUT400 Web Browser entry. Also remove SITRANS LUT400 USB CDC Driver. Reboot before continuing so that any locked files are released.

5.3 Install the version-pinned browser

1. Run the downloaded installer as Administrator.
2. Accept the default install path C:\Program Files (x86)\Siemens\SITRANS LUT400 Web Browser\.
3. When prompted to install the USB CDC driver, select Install driver.
4. Reboot when prompted.

5.4 Connect to the device

1. Launch the Siemens LUT400 Web Browser from the Start menu.
2. Connect the USB cable between the PC and the LUT400's mini-USB service port.
3. Confirm the COM port assigned to the device in Device Manager.
4. In the browser, click Connect. The login page should now load without the version-mismatch banner.
5. Default credentials: User Admin, Password 1234 (or the customer-configured password if changed in Security > Passwords).

6. Solution Path B - Update Firmware to 1.02.01-00

Path B is correct when the engineer needs new features, when multiple units need to be standardized to a single firmware level, or when the legacy browser installer is no longer available. The latest released firmware is 1.02.01-00, and the matching procedure is documented in Siemens support entry 61649208. The firmware image itself is published under entry 109477166.

6.1 Prerequisites for firmware update

• PC with the latest Siemens LUT400 Web Browser installed.
• USB mini-B cable, data-grade (not charge-only).
• Loop power stable at 20 V DC or higher for the full update duration (typically 4-8 minutes).
• Configuration backup file (.xml) exported from the device.
• LUT400 firmware image LUT400_FW_1.02.01-00.fwu downloaded and verified.

6.2 Update procedure

1. Connect to the device using the version-pinned browser. Confirm successful login.
2. Navigate to Communication > Firmware Update.
3. Click Choose File and select the .fwu image.
4. Click Update. The device reboots into the bootloader, and the progress bar appears.
5. Do not disconnect the USB cable, do not remove loop power, and do not close the browser during the update. A power interruption during the write cycle can corrupt the bootloader.
6. When the update completes, the device reboots into firmware 1.02.01-00. The browser will refresh and prompt for re-login.

6.3 Post-update validation

1. Re-login with the default or customer credentials.
2. Navigate to Information > Device Information and confirm firmware reads 1.02.01-00 and loader reads 2.01.01-00.
3. Restore the configuration backup from Parameters > Load from File.
4. Run a quick loop test: Diagnostics > Loop Test, force 4 mA and 20 mA, verify the reading at the DCS or HART master.

7. Hardware/Software Compatibility Matrix

The full matrix is published under Siemens support entry 109776905. The condensed version for the LUT400 web browser application is reproduced below.

Siemens publishes a release note per firmware version that documents the exact supported transducer list, HART command set additions, and resolved advisories. The release note for 1.02.01-00 is referenced from entry 109477166.

8. USB CDC ACM Driver: Correct Installation

On Windows 7 x64, the in-box usbser.sys does not include the LUT400's USB descriptors. On Windows 10 1809 and later, the Microsoft CDC driver handles the device natively and the Siemens installer is not required. The steps below address the legacy case.

1. Open Device Manager. The LUT400 should be visible under Universal Serial Bus controllers as Unknown device or as USB Serial Converter.
2. Right-click and select Update driver.
3. Choose Browse my computer for driver software and point to C:\Program Files (x86)\Siemens\SITRANS LUT400\Drivers\.
4. Accept the unsigned-driver prompt (Windows 7 only). The device relocates to Ports (COM & LPT) as USB CDC Serial Port Emulation (COMx).
5. Open the port properties and set Bits per second = 115200, Data bits = 8, Parity = None, Stop bits = 1, Flow control = None.

9. HART Field Device Integration

The LUT400 is registered as a HART 7 field device. The complete HART Field Device Specification is published as HART_Field_Device_Specification.pdf (Siemens attachment 109477167). The relevant configuration parameters exposed via HART are:

During HART burst mode, the LUT400 can broadcast the four variables plus loop current and %-of-range at a configurable update rate between 0.5 s and 60 s. The Device Variable code assignments are documented in section 6 of the HART specification.

10. Transducer Configuration and Verification

Browser access is the only way to map a transducer to a LUT400 measurement channel. Per the Operating Instructions (A5E33329501), the standard commissioning steps after firmware update are:

1. Navigate to Setup > Transducer > Transducer Enable (3.3) and select the connected Siemens transducer (e.g. ST-H, echomax XPS-10, XPS-15, XRS-5).
2. Set the Material (liquid, solid, or mixed).
3. Set the Mounting (vessel type: vertical, horizontal, open channel, or Parshall flume).
4. Enter the Empty distance (distance from transducer face to the empty process point) and Span (process full distance from empty point).
5. Run Auto-Suppression to mask false echoes from fixed obstructions.
6. Verify with a known-level reference (water at a calibrated dip-tube).

If the measurement does not track the reference, follow the diagnostic tree in section 8.6 of the Operating Instructions: verify terminal connections, check transducer field wiring, check any junction box connections, and check that transducer is enabled. The same diagnostic path is summarized in Siemens support entry 109793894.

11. Down-Scale and Up-Scale Fault Behavior

Per the HART Field Device Specification, the LUT400 reports hardware or processing errors via the analog loop current:

The mode is selected under Diagnostics > Fault Mode. For safety-instrumented systems, NAMUR NE 43 compliance is required and the down-scale or up-scale mode must be explicitly selected.

12. Verification Procedure After Repair

Run the following sequence to confirm the browser-compatibility error is fully resolved and the device is fit for service.

1. Disconnect the USB cable, wait 10 s, reconnect. Confirm the COM port re-enumerates.
2. Launch the Siemens LUT400 Web Browser, click Connect, log in.
3. Confirm no version-mismatch banner appears on the login page.
4. Navigate to Information > Device Information. Confirm firmware, loader, and hardware revisions match the expected values.
5. Click through every setup menu and confirm all configured parameters match the commissioning record.
6. Force a loop test at 4 mA and 20 mA. Read back the loop current at the DCS analog input. The error should be within 0.02 mA.
7. Trigger a HART burst from the master, confirm PV, SV, TV, FV values track the engineering units within the published accuracy (typically +/- 0.25 % of span or 6 mm, whichever is greater).
8. Re-seat the wiring cover and torque the cover screws to 2.0 N-m. Re-apply the loop voltage. Confirm the device enters Run mode within 5 s of power-up.

13. Preventive Maintenance and Field Practice

To prevent recurrence, observe the following practices during plant rollouts and turnarounds.

• Maintain a single firmware version across the entire fleet, ideally the latest released (1.02.01-00 at the time of this writing). The compatibility table at 109776905 is the authoritative source.
• Standardize the Siemens LUT400 Web Browser installer across all engineering laptops. Bundle the installer into the engineering workstation image to remove version drift.
• Document the firmware and loader revisions in the asset record. The four values to capture on commissioning sign-off are: model (LUT420 / LUT430 / LUT440), serial number, hardware revision, firmware revision, and loader revision.
• Export a parameter backup file (.xml) to the plant historian after every configuration change. This backup is the fastest way to recover a unit after an accidental factory-reset.
• During HART loop checks, request the long-tag (32-character) and the unique device identifier to confirm the correct device is being addressed when multiple LUT400 units share a multidrop loop.

14. Quick-Reference Troubleshooting Matrix

FAQ