MaxDLMS reads your DLMS/COSEM electricity meters over TCP/IP, RS-485 or optical probe and stores every load profile in your own MySQL database, with no gaps. Monthly energy reports, tariffs and invoices, alerts and an API come from the same Windows service.

Every DLMS meter on a campus, a factory or a building portfolio keeps a detailed load profile, but the vendor's reading tool is usually a manual, one-meter-at-a-time job, and the data ends up in spreadsheets or a closed system.
MaxDLMS reads all your meters on a schedule, stores every interval in a database you own, and turns it into energy reports and invoices your finance team can use.
One Windows service collects, stores, checks and reports. The web UI runs from the same program.
Load profiles and registers read from every meter on a schedule, with scaler and unit discovery and per-meter capture periods.
TCP/IP (WRAPPER) meters, RS-485 buses (HDLC) from a COM port or a serial-to-Ethernet converter, and optical-probe reads (IEC 62056-21).
What to read is worked out from what is stored, so after an outage each meter is caught up from where it stopped, saved meter by meter.
Holley (field-proven), ION, Landis+Gyr and generic DLMS models. New makes are added in the web UI. Security: None, Low (password) or HLS.
MySQL is the record. Exact copies go to SQL Server, SQLite or another MySQL server, and a SQL Server push feeds other systems.
Daily and monthly energy per meter or for the whole site, plus a readings browser with CSV and Excel export.
E-mail and webhook alerts when meters stop answering, the network drops or a database copy falls behind.
Meters, status, readings, energy and billing over /api/v1, with API keys and scopes, JSON or CSV.
Manual corrections and imports are versioned: who changed what and when, with the meter's own value kept so it can be restored.
Served by MaxDLMS itself, on your network. Screenshots from a demo system with 109 simulated meters.
The whole estate at a glance. How many meters answered, which did not and why, when the last sweep ran and when the next one starts.
Every meter in one list. Connection, meter model, newest stored reading and status, with a clear reason when a meter or a port fails.
Energy you can trust. Daily energy computed only from measured intervals. Missing days are shown as missing, never as zero.
Monthly energy report. Energy per meter for the month, on screen, as Excel or through the API, and exported automatically on a schedule.
Every interval, every channel. Browse any meter's load profile in your time zone and export it to CSV or Excel.
One program on one Windows PC on your meter network.
On a schedule, every meter's load profile is read from where the database left off.
Each meter is saved as soon as it finishes, in UTC, and copied to any mirrors.
Silent meters, port failures and lagging mirrors raise alerts by e-mail or webhook.
Energy charts, monthly reports, invoices and the API, from measured data only.

For campuses, landlords, industrial parks and utilities that recharge energy to tenants, departments or customers:
Every campus meter read automatically over TCP/IP into the university's own MySQL database, with full load-profile history, energy reports and a web UI for the facilities team.
/api/v1 with API keys and scopes; JSON or CSV; documented in the web UI.Straight answers about MaxDLMS. Anything else? Ask us below.
DLMS/COSEM electricity meters. Holley meters are field-proven at the University of Jordan; ready models also exist for ION, Landis+Gyr and generic DLMS meters, and any other DLMS meter is added as a model in the web UI: addressing, security, capture period and channels, with no new software.
Over TCP/IP (DLMS WRAPPER, one IP address per meter), over RS-485 serial buses (HDLC) from a COM port or a serial-to-Ethernet converter, or with an optical probe (IEC 62056-21) for manual reads.
Nothing is lost. MaxDLMS works out what to read from what is already stored, so after an outage it back-fills each meter's load profile from where it stopped, oldest first and in small slices, and saves each meter as soon as it finishes.
In your own MySQL database, on your network. Exact copies can be kept in SQL Server, SQLite or another MySQL server, and readings can be pushed to a SQL Server table for other systems. Nothing goes to a cloud unless you want it to.
Yes. Tariffs with time-of-use periods and blocks are assigned per meter. Invoices are priced only from measured intervals, numbered without gaps, frozen when issued and corrected with credit notes. The monthly energy report and invoice drafts can be exported to Excel on a schedule.
Yes, through a REST API with API keys and scopes (read, readings, meters, billing), CSV and Excel exports, the SQL Server push, or the database itself.
At the University of Jordan in Amman, reading 109 DLMS meters across the campus over TCP/IP into MySQL.
Have another question? Send it to us or write to support@maxenergic.com.
Tell us how many meters you have, their make and how they are connected, and our engineers will propose the right setup.