Instable, stop responding after 3-10 days

[tomasenskede]

The Problem

I've used AI on the edge for my watermeter since January 17. I've encountered stops on January 19, January 23, January 27, and February 8. Is this frequency of stops normal, and is there a way to enhance its stability? I recently updated to version 15.5.0 today, anticipating improved stability. Could there be another factor causing these stops?

Version

15.5

Logfile

[0d00h00m25s] 2024-02-08T20:53:32 [MAIN] Device info: CPU cores: 2, Chip revision: 101
[0d00h00m25s] 2024-02-08T20:53:32 [MAIN] SD card info: Name: SL16G, Capacity: 15193MB, Free: 15152MB
[0d00h00m27s] 2024-02-08T20:53:34 [MAIN] Initialization completed successfully
[0d00h00m28s] 2024-02-08T20:53:34 [WIFI] Connected to: HermanssonHD, RSSI: -89
[0d00h00m30s] 2024-02-08T20:53:36 [LOGFILE] Set log level to ERROR
[0d00h01m25s] 2024-02-08T20:54:32 [POSTPROC] main: Raw: 01503.6445, Value: , Status: Neg. Rate - Read: - Raw: 01503.6445 - Pre: 1504.6445
[0d00h06m25s] 2024-02-08T20:59:30 [POSTPROC] main: Raw: 01503.6445, Value: , Status: Neg. Rate - Read: - Raw: 01503.6445 - Pre: 1504.6445
[0d00h11m25s] 2024-02-08T21:04:30 [POSTPROC] main: Raw: 01503.6463, Value: , Status: Neg. Rate - Read: - Raw: 01503.6463 - Pre: 1504.6445
[0d00h16m25s] 2024-02-08T21:09:30 [POSTPROC] main: Raw: 01503.6475, Value: , Status: Neg. Rate - Read: - Raw: 01503.6475 - Pre: 1504.6445
[0d00h21m25s] 2024-02-08T21:14:30 [POSTPROC] main: Raw: 01503.6568, Value: , Status: Neg. Rate - Read: - Raw: 01503.6568 - Pre: 1504.6445

Reload Show Full Log Show Older Log Files

### Expected Behavior

_No response_

### Screenshots

_No response_

### Additional Context

_No response_

[SybexX]

As I understood you, you used v15.4.0, maybe it could be related to this #2823 or your very poor WiFi reception "Connected to: HermanssonHD, RSSI: -89"

[caco3]

Please provide a full debug log containing what ever you mean with "stopping".
And please update to 15.6.0 as we fixed a critical bug.

[tomasenskede]

New issue;

I did update to 15.6.0 and now I have 7505.0153 (!) why?

[SybexX]

That's the PreValue, apparently he recognized the 1 as 7 during the previous reading.
The currently read value is correct.

[friedpa]

Just set the PreValue again and use MaxRate for preventing such huge steps in the reading

[SybexX]

Doesn't the system do it by itself because PreValue is too old?

[caco3]

No, the PreValue is just used for a plausibility check. See https://jomjol.github.io/AI-on-the-edge-device-docs/Correction%20Algorithm/#prevalue

[SybexX]

I thought that the setting "PreValueAgeStartup" resets the PreValue

[caco3]

hmm, good point. I actually do not know what happens after PreValueAgeStartup expires. i also would expect that the PreValue in such case gets ignored, but will it then simply use the new raw value' I don't know.

[SybexX]

habe mal nachgeguckt:
wenn ich nichts übersehen habe, sollte PreValue bei der ersten Runde mit den gelesenen Wert ersetzt werden, wenn AllowNegativeRates aktiviert ist. Ist AllowNegativeRates deaktiviert, muß PreValue manuel gesetzt werden, wegen if (!NUMBERS[j]->AllowNegativeRates){}

[tomasenskede]

Lets see if it reads correct from now...

[tomasenskede]

[SybexX]

Did you set the RSSI Threshold to 0 because of your poor WiFi?

[tomasenskede]

yes!

[tomasenskede]

Neg. Rate - Read: - Raw: 01506.8384 - Pre: 55070.6175
55050.6175 previous value

[tomasenskede]

"Keep equidistance of" ? where do I find this option?

[SybexX]

[caco3]

Your ROIs are too small, check the documentation for examples!

[tomasenskede]

Neg. Rate - Read: - Raw: 01507.1673 - Pre: 54864.6060

Again

[caco3]

Neg. Rate - Read: - Raw: 01507.1673 - Pre: 54864.6060

Well, we told you already that you have to set the initial PreValue.
But first you have to set the Reference Image, marks and ROIs properly!

[tomasenskede]

Now it has been running stable until yesterday evening

Current readout...

The aligment isnt as good as in the

and

[caco3]

The reference marks should be as far apart as possible. Also the one around the m3 should be smaller.
I suggest to use the 2.5 on the top and add a sticker at the bottom.

The early transition are caused by a bug in 15.5 resp. 15.6 and will be reverted in the next release

[caco3]

We just released v15.7.0 which hopefully fixes this issue.