Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Draft] add records for TD-3511 in upper austria #519

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

ajuch
Copy link

@ajuch ajuch commented Apr 19, 2022

I wanted to read out more values provided by the TD-3511 meters in upper austria. They provide the following additional data points (under "Kundenschnittstelle" -> "Welche Daten werden ausgegeben?"):

name OBIS unit
Zählerstand Energie R+ 3.8.1 varh
Zählerstand Energie R- 4.8.1 varh
momentane Blindleistung Q+ 3.7.0 var
momentane Blindleistung Q- 4.7.0 var

These values are not important for billing, but seem interesting for me.

I added them but it seems that VIF=fb values are proprietary. So maybe reading out these values makes only sense in combination with more context. I don't expect this pull request to be merged but maybe to get inputs on how to handle these values or additional data in similar meters if there is any interest in them.

image

@ajuch ajuch marked this pull request as draft April 19, 2022 20:03
@r00t-
Copy link
Contributor

r00t- commented Dec 30, 2022

i'm not familiar with OMS, and i just looked at MeterOMS for the first time.
it seems weird to me how MeterOMS hardcodes a mapping between OMS/mbus record types ("VIFs") and OBIS codes.
while such behaviour is suggested in the OMS specification ("5.1.3 OBIS Code"),
it would appear to more sense to make those identifiers available as a new identifier type in vzlogger, to allow using vzlogger's existing (and runtime-configured) mapping capability?
your requirement should turn into a simple matter of defining a channel in vzlogger.conf.
(not sure if/how this can be implemented in a backwards compatible way.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants