Replies: 4 comments 1 reply
-
|
Have you tried to change CamGainceiling to e.g. x16? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I was not aware of the CamGainceling option. Set it to x16 and also got misreadings. However if the meter does not change, I turn it on temporarily because it's not the heating season yet, there are false readings but they correct themselves in subsequent readings (neg. rate). Regrading dimming the Led: I actually have some polarizing foil at home which got me the best results on my other meter. I may case however it still required carefully positioning of the led. Do you think my last digits are to dark and that's the issue of the misreadings ? |
Beta Was this translation helpful? Give feedback.
-
|
I rather assume that the border around the last digit is causing the problem. |
Beta Was this translation helpful? Give feedback.
-
|
I did try the non-quantized versions dig-class11_1910_s2 and dig-class11_2000_s2 with the same results. However this was before your suggestion of increasing CamGainceling. If I understand the docs correctly the non-quantized models are more accurate but take more processing power so I chose those instead of the q versions. My idea would be to rerun with the other models (in normal picture mode), upping the CamGainceling in between if errors occur and moving to the next model if needed. Should I prefer the quantized versions over the non-quantized version for this attempt ? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone, this meter has been quite a challenge but I've managed to get it working with an error rate of 3 per day.
https://www.messtechnik.at/wordpress/produkte/warmezahler/kompakt-warmezahler/funk-wohnungswaermezaehler-modelle/elf2/
The display has no backlight and the digits are very dim, maybe the battery is almost depleted. The positing of the led is also quite tricky, if i try to aim it above or below the digits nothing is visible on the display at all. Aiming it on the left and sacrificing the last digit got me some usable results. The downside of this is that the digits to the right are a bit dark.
I currently have some false readings with a 5 recognized as 9.

So far i've tried all available digits models, I'm currently using dig-class11_1701_s2.tflite. Normal and greyscale mode but I always get some errors.
Heres my ROI Setup:

Whats also a bit puzzling, the seconds digit seems to be tight enough drawn, however in the recognition it picks
up a portion of the third digit. Is this some kind of aligment marker issue ?
Any ideas how to improve this would be greatly anticipated. I'm also thinking about training my own model.
Would the image quality be sufficient for this ?
Config:
Beta Was this translation helpful? Give feedback.
All reactions