Image processing corrupted

[schneich]

The Problem

I check the webpage to see the current readings. The image is corrupted and a wrong reading is shown.

After refreshing the page (2min later), the image is shown correct and readings seem to be correct. Please note that this is still in the same round!

Version

15.4.0

Logfile

[0d00h00m00s] 2024-01-08T13:09:35 <INF> [MAIN] =================================================
[0d00h00m00s] 2024-01-08T13:09:35 <INF> [MAIN] ==================== Start ======================
[0d00h00m00s] 2024-01-08T13:09:35 <INF> [MAIN] =================================================
[0d00h00m00s] 2024-01-08T13:09:35 <INF> [MAIN] PSRAM size: 8388608 byte (8MB / 64MBit)
[0d00h00m00s] 2024-01-08T13:09:35 <INF> [MAIN] Total heap: 4382019 byte
[0d00h00m04s] 2024-01-08T13:09:39 <INF> [MAIN] Camera info: PID: 0x26, VER: 0x42, MIDL: 0x7f, MIDH: 0xa2
[0d00h00m04s] 2024-01-08T13:09:39 <INF> [SDCARD] Basic R/W check started...
[0d00h00m04s] 2024-01-08T13:09:39 <INF> [SDCARD] Basic R/W check successful
[0d00h00m04s] 2024-01-08T13:09:39 <INF> [SNTP] TimeServer not defined, using default: pool.ntp.org
[0d00h00m04s] 2024-01-08T13:09:39 <INF> [SNTP] Configuring NTP Client...
[0d00h00m04s] 2024-01-08T14:09:39 <INF> [SNTP] Time zone set to CET-1CEST,M3.5.0,M10.5.0/3
[0d00h00m04s] 2024-01-08T14:09:39 <INF> [SNTP] Time is already set: 2024-01-08 14:09:39
[0d00h00m04s] 2024-01-08T14:09:39 <INF> [MAIN] CPU frequency: 160 MHz
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [SDCARD] Folder/file presence check started...
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [SDCARD] Folder/file presence check successful
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [MAIN] Tag: 'v15.4.0', Release: v15.4.0 (Commit: 74d4f20), Date/Time: 2023-12-22 22:39, Web UI: Release: v15.4.0 (Commit: 74d4f20)
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [MAIN] Reset reason: Via esp_restart
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [WLANINI] SSID: csesnsas_IoT
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [WLANINI] Password: XXXXXXXX
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [WLANINI] Hostname: gaszaehler
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [WLANINI] RSSIThreshold: -75
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [MAIN] WLAN config loaded, init WIFI...
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [WIFI] Automatic interface config --> Use DHCP service
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [WIFI] Set hostname to: gaszaehler
[0d00h00m05s] 2024-01-08T14:09:40 <INF> [WIFI] Init successful
[0d00h00m07s] 2024-01-08T14:09:43 <WRN> [WIFI] Disconnected (201, No AP)
[0d00h00m11s] 2024-01-08T14:09:46 <INF> [WIFI] Connected to: csesnsas_IoT, RSSI: -56
[0d00h00m12s] 2024-01-08T14:09:48 <INF> [WIFI] Assigned IP: 192.168.30.23
[0d00h00m25s] 2024-01-08T14:10:00 <INF> [MAIN] Device info: CPU cores: 2, Chip revision: 300
[0d00h00m25s] 2024-01-08T14:10:00 <INF> [MAIN] SD card info: Name: SU04G, Capacity: 3886MB, Free: 3871MB
[0d00h00m27s] 2024-01-08T14:10:02 <INF> [MAIN] Initialization completed successfully
[0d00h00m29s] 2024-01-08T14:10:05 <INF> [LOGFILE] Set log level to ERROR
[0d00h01m13s] 2024-01-08T14:10:49 <ERR> [POSTPROC] main: Raw: 0NN71.554, Value: , Status: Rate too high - Read: 8871.554 - Pre: 8839.424 - Rate: 32.130
[0d00h16m13s] 2024-01-08T14:25:49 <ERR> [POSTPROC] main: Raw: 17771.524, Value: , Status: Rate too high - Read: 17771.524 - Pre: 8839.546 - Rate: 8931.978
[0d00h46m13s] 2024-01-08T14:55:49 <ERR> [POSTPROC] main: Raw: 711N7.172, Value: , Status: Rate too high - Read: 71137.172 - Pre: 8839.644 - Rate: 62297.528
[0d01h01m14s] 2024-01-08T15:10:49 <ERR> [POSTPROC] main: Raw: 711N7.174, Value: , Status: Rate too high - Read: 71137.174 - Pre: 8839.644 - Rate: 62297.530

Expected Behavior

correct readings :-)

Screenshots

No response

Additional Context

No response

[schneich]

Ah, sorry, I just realized, that my first screenshot is still in process state Aligning...

[caco3]

Yes, it can happen, that a corrupted image gets shown. This is not nice, but luckily internally everything is correct. It can happen when the image at the wrong time gets fetched by the UI.