Continuing on the theme of inbuilt vs MID metering. See also:
Here’s an interesting result from a Grant R290 unit I helped install back in February.
Performance using the Level 3 bundle: 4.33 so far: https://heatpumpmonitor.org/system/view?id=1088
Running SCOP as reported by the local Econet API is settling to ~7.4! ![]()
So why are we seeing such a difference?
Zooming in on a short run period around the 25th of March where conditions are fairly stable:
Axioma Heat meter:
- Flow temperature: 36.02C
- Return temperature: 32.91C
- DT: 3.11K
- Flow rate: 15.01 L/min
- Heat output: 3232W
- Assumed specific heat = 3232÷((15.01÷60)×3.11) = 4154 J/kg.K (expected result)
Grant R290 inbuilt sensors
- Flow temperature: 34.80C
- Return temperature: 31.82C
- DT: 2.98K (~4% less)
- Flow rate: 18.27 L/min (~22% more)
- Heat output: 4387W (36% more)
- Assumed specific heat = 4387÷((18.27÷60)×2.98) = 4834 J/kg.K (strangely high!?)
Electric power is much better only a 0.2% difference!
really remarkably good only 0.25% difference here over a longer period!
The Econet API reported a COP of 6.3 over the 5:20-6:20am period selected above, even though it’s heat output / electrical input measurements suggest: 4387÷746.7 = 5.9. Perhaps it’s doing a running average or something. The MID metering COP for the same period is 4.33.
Cross checking the % of ideal Carnot using the MyHeatpump app gives 54.8% for the MID metered performance, which is towards the higher end of the range we would expect (but within the expected / realistic range). A COP of 6.3 would be 80% of carnot which is clearly too high.
I think @glyn.hudson spotted that Grant may have removed the COP/SCOP metrics from their app and so they may well be well aware of this accuracy issue, but it’s an another interesting data point on the variability in the quality of built in metering - and as I’ve said before - I do want the quality of built in metering to improve as I think higher accuracy built in metering is the right way to scale heat pump monitoring longer term - even though that would reduce the need for our product ![]()










