From 4b5c87e48f4a877c91e93d994ede4fdd9dbf7364 Mon Sep 17 00:00:00 2001 From: fhb Date: Sun, 16 Apr 2023 11:56:04 +0200 Subject: [PATCH] Update NUMBER.MaxRateValue.md updated the MaxRateType description. --- .../parameter-pages/PostProcessing/NUMBER.MaxRateValue.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md index 2936cff..ef48000 100644 --- a/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md +++ b/param-docs/parameter-pages/PostProcessing/NUMBER.MaxRateValue.md @@ -1,6 +1,6 @@ # Parameter `.MaxRateValue` Default Value: `0,05` -Maximum allowed change of a reading, if exceeded the reading will be rejected. Depending on the settings of `.MaxRateType` it is either treated as the difference between the two measurements (AbsoluteChange) not taking the set time interval into account or as the difference per minute (RateChange). +Maximum allowed change between two readings, if exceeded the last reading will be rejected. Depending on the settings of `.MaxRateType` the `MaxRateValue` is either treated as the difference between the two measurements (`AbsoluteChange` = difference) not taking the set time interval into account or as the difference normalized to the interval (`RateChange` = difference per minute). If negative rate is disallowed and no maximum rate value is set, one false high reading will lead to a period of missing measurements until the measurement reaches the previous false high reading. E.g. if the counter is at 600,00 and it's read incorrctly as 610,00, all measurements will be skipped until the counter reaches 610,00. Setting the MaxRateValue to 0,05 leads to a rejection of all readings with a difference > 0,05, in this case 610,00. The rejection also applies to correct readings with a difference > 0,05!