wrong high values

[modenet]

hi, I juest update metern.
I see daily strange spikes on the charts linked to wrong data in the csv:
14:00,1112011965,6119,1363,957,235,24.06,63.75,64.12,74.50,22.69,23.69,19.81,23.06,0.00,41.31,41.81
14:05,29306206,6146,1363,1082702548,266,24.06,64.12,64.50,74.25,22.69,23.69,19.81,23.06,0.00,41.31,41.81
14:10,29306385,6176,1082696649,1082698048,,24.06,64.50,64.88,75.25,22.69,23.69,19.81,23.06,0.00,40.50,42.25
14:15,29306566,6208,1082690649,1082693697,30,23.88,65.00,65.25,75.00,22.69,23.69,19.81,23.06,0.00,40.38,41.75

the problem is related to pass over values: I have set them well, for each meterns, but if very high data (out of scale) arrives, they are still accepted

[jeanmarc]

Obviously you have spikes because the values returns by your com apps are wrong. 1112011965 to 29306206, 1363 to 1082696649..
Check them and you'll get good graphs

[modenet]

the problem was about that the values were higher than the "pass over", and were accepted. why?
I can't understand the "pass over" configuration.

[jeanmarc]

Your com app give wrong value, you simply can't have a higher value than the pass-over one.
meterN can't detected if the value returned is wrong,i could add a check if it's over pass-over.

The principle is simple as that:
- A meter should always increase until it pass-over (Like all real meters does). Let's say your electrical meter count up to 100kWh: the pass-over value is 100k, if you meter is over it restart from 0. Your com app can't return 100.001kWh, it should return 1Wh.
-Also, you can disable pass-over (by setting to 0), so your meter increase until infinity.

Make you choice and correct your com apps

[modenet]

ok, now I have understand the scope of the "pass over"; for my point of view it was a filter: values higher than the pass over had not to be accepted.

I analyzed the problem: once or twice a day my fv metern read from 123solar values out of scale and after that I saw a negative high value. it uses "pool123s energy" which read data from 123solar.
both metern and 123solar are updated.

what do you propose to manager these peak?

[jeanmarc]

pool123s return values reported by your inveter. What protocol are you using ? The values are ok in 123solar ?

Maybe you can tweak it, at around line 35

Code: Select all

..
$KWHT = round($memarray["KWHT$invtnum"] * 1000); // Wh
if ($KWHT <= $YOURPASSOVER && $KWHT > 0 ) {
 echo "$METERID($KWHT*Wh)\n";
} else {
 die("Abording: wrong data\n");
}            

[modenet]

pool123s return values reported by your inveter. What protocol are you using ? The values are ok in 123solar ?

I'm using RS485 to connect my Aurora inverter. in 123 solar values are always ok.

Maybe you can tweak it, at around line 35

Code: Select all

..
$KWHT = round($memarray["KWHT$invtnum"] * 1000); // Wh
if ($KWHT <= $YOURPASSOVER && $KWHT > 0 ) {
 echo "$METERID($KWHT*Wh)\n";
} else {
 die("Abording: wrong data\n");
}            

thanks, I'll try.

ps why did you remove the native integration from metern to 123solar?

[jeanmarc]

Odd, i have no issue here.
Counters shall increase, why would you want negative value ? In case of production reinjection, you can have an energy imported and exported meters. As you can see, i got EIMP, EEXP ones.

[modenet]

my question was different: why did you remove in the download section the pool123 and the pooler comapps?
they are necessary for anyone start using metern + 123solar
thanks for your work

[jeanmarc]

sorry i misunderstood
They haven't been removed, it's packed in comapps_examples