Efficient combination of reading billing data and instantaneous values

Our data concentrators of the MUC family are mainly used to record load profiles or meter readings and to generate daily or monthly reports for billing.

Increasingly, our customers are also using the available Modbus TCP option to record instantaneous values permanently and at high frequency. This allows not only billing in retrospect, but also monitoring and controlling the current operation of the facility or property. The meters only have to be read out often enough.

Readout and database

Our data concentrators are designed to collect all read out values and log them for further processing at a later stage. The readout interval of the meters therefore defines which and how much data is included in the reports.

Although this can also be modified, for example, that only the last value of a report period is included, the data still ends up in the database first. This leads to high memory usage and of course small delays when reports have to be created. lt is a fact that the data concentrator has to process all data.

For the retrieval of the instantaneous values via Modbus TCP itself, however, the data in the database is not needed. These are retrieved continuously anyway. In addition, other values are usually of interest here, e.g. instantaneous voltages and currents versus the continuous energy counter register.

The convenient trick: meter entry twins

To combine both efficiently, we have two options with our devices.

There is a parameter MUC_LOGCYLCE_DIVIDER=xxx, which can be entered manually in the app/chip.ini file. Therefore, only every xxxth read value ends up in the database. In simple cases this serves the purpose, e.g. xxx=15 with minutely readout writes only the 15 min values into the database.

The more flexible and comfortable way is to create a meter twice in the meter list. One meter is configured for meter reading (reading billing data) like normal. Its relevant values (e.g. active energy import and active energy export) are activated accordingly.

A copy of this meter is then configured for Modbus, so a different, shorter readout interval is specifically set and at least the relevant, instantaneous values (e.g. active power, voltage and current) are given a Modbus register address. However, this meter is deactivated for the report.

Zählerliste_meter list

Configured in this way, the meter is regularly read out at longer intervals in order to record its data in the database, and then at shorter intervals in the meantime to make the data available via Modbus with high temporal resolution.

This covers both applications in a resource-efficient way: high-resolution instantaneous values and aggregated history data for the meter reading history.

Categories:
Categories

Similar Posts

Our technical support in the field – Part 2

read more

Our technical support in the field – Part 1

read more

Third party cookies & scripts

This site uses cookies. For optimal performance, smooth social media and promotional use, it is recommended that you agree to third party cookies and scripts. This may involve sharing information about your use of the third-party social media, advertising and analytics website.
For more information, see privacy policy and imprint.
Which cookies & scripts and the associated processing of your personal data do you agree with?

You can change your preferences anytime by visiting privacy policy.