Dlms Meter Reading Software
All the requests and their corresponding responses are defined in the Standard using the. However, in our tools and libraries, the specific instances of requests and responses are presented in a XML notation, like in the following: This is a ReadRequest element. How can we send such a request to the meter? Of course, the XML lines cannot be sent directly. They must be first encoded into a byte sequence known as a protocol data unit (PDU), according to the rules specified in the Standard. We will not go into the details of the encoding. Instead, in our target program, we will use our xmlpdu library, that implements the encoding and decoding procedures.
DLMS COSEM (IEC 62056) Automatic Meter Reading. I think the Elster meters must be compliant with DLMS COSEM and it was possible to reverse engineer what.
The unrestricted version provides logging of meter reads to.csv files. It also can generate automatic monthly reports emailed to individual meter users. Once purchased, all updates to the software are free. The software will work with EKM v.2, v.3, and v.4 smart meters. Meter reads give Total kWh, Reverse kWh and Maximum Demand, plus Instantaneous Current, Voltage, Power, Power Factor, as well as 6 months of monthly records stored on board the meter, including 4 Time-of-Use Rates for 4 Daily Time Periods and 6 Seasons. Meters return quite a bit of additional data.
Each entry is a structure of 4 elements: • The first element (LongUnsigned) is the ClassId of the instance. • The second element (Unsigned) is the version number of the class of the instance. • The third element is the logical name of the instance. • Finally, the fourth element lists the access rights of the attributes and methods of the instance. Finally, as we know the parameters, we can send a GetRequestNormal to read the 'digits' of the energy register: Here is the response: We read the scaler with this request: And the response is: Finally the active energy is: ActiveEnergy = 2003 * 10 -2 = 20.03 Wh = 0.02003kWh.
Size: 6.1 MB, Price: Free, License: Freeware, Author: Gurux Ltd (gurux.fi) 2 Gurux DLMS Director is designed to simplify communication with DLMS/COSEM devices. Gurux DLMS Director is designed to simplify communication with DLMS/COSEM devices. DLMS (Device Language Message Specification) is a widely used standard (IEC 62056) in. Size: 4.7 MB, Price: Free, License: Freeware, Author: Gurux Ltd.
Simple maths when you know that the meter pulse rate is 1 imp = 1 Wh. The code is simply an analogRead and triggers a serial transmission when a certain threshold is reached, i.e.
Finally, we parse the received XML using any appropriate method. To summarize: all request/response exchanges follow these five steps: • Have the XML of a request. • Encode the XML to PDU using XmlToPdu(). • Send the PDU to the other side and get a response PDU, using HDLCSendReceive(). • Decode the response PDU into XML with PduToXml().
The system may be easily for specific market's requirements. Branded package will inherit your custom name, copyright, logos, icons, website links, and other elements of corporate identity.
Send request to change to DLMS mode. Packet is formatted as follows: 0x06 '0' Z '2' 0x0D 0x0A without the quotations. Z is the requested connection speed. The device might respond to this but not all of them do. It is safe to continue with connection initialization even without reply. If device is DLMS/COSEM compliant and meter do not answer anything it is in DLMS mode.
We will ignore it. If the association fails, then the response will look like this: The association result is not null. The value of the AcseServiceUser element is an error code. How to read data from a SN meter The service used to read data from a short name referencing meter is the ReadRequest. This is a very simple service. Here is an example: A ReadRequest allows to read several attributes at once, still, in the example, we just want to read one single attribute, therefore 'Qty' is set to 1.
Connection Initialization The connection initialization depends on the connection type and the device. Some devices require IEC62056-21 protocol handshake before starting to communicate using DLMS protocol. IEC62056-21 Handshake In serial port connection default IEC62056-21 settings are: Bitrate 300, 7E1.
• AttributeId is the attribute number of the attribute we want to read. The AttributeId can be found in the Blue Book. The ClassId and the InstanceId can be found in the object list. According to the Blue Book, the object list is the attribute 2 of the object 0.0.40.0.0.255, and, the ClassId is 15 (Association LN). Therefore, the GetRequestNormal to read the object list looks like this: The response can be a GetResponseNormal, as here:.
The software is a $30 one time cost, no monthly or annual fees. We also help you to write your own software, by either communicating with the meter directly (harder) or interfacing with the EKM Push system (quite easy). To get started visit our For more information about how to set up EKM Dash, we encourage you to visit our online, which includes a series of tutorials that will help you get started with the software.
+ deviceSerialNumber + '! R n' Send query to the device containing '/?!' And a new line (0x0D 0x0A) without the quotations. This requests the identity information from the device. The device responds with serial number and the maximum connection speed. The reply data is formatted as follows: /XXXZ Ident and a line change XXX is the manufacturer name Z is the maximum baud rate Ident is the Identification info of the device. Z is the most important part of the device and is defined in single number: 0 - 300 Bd 1 - 600 Bd 2 - 1 200 Bd 3 - 2 400 Bd 4 - 4 800 Bd 5 - 9 600 Bd 6 - 19200Bd 7, 8, 9 - reserved for later extensions.
The packet can be generated with AARQRequest method and it uses UseLogicalName and Authentication properties so make sure these are set to correct values. If password is defined all data do not nesessary do not fit to one message so data must be split to multible messages with SplitDataToPackets method. Send this command using data handling methods described in.
For example, a SN meter would send this response: The Association Result A value of zero indicates that the request succeeded. Any other value indicates a failure.
Because this takes so long it is recommended to save this information for future use as it doesn't change unless meter software is updated. The data structure varies between manufacturers and device models. The reply data is parsed using ParseObjects method in GXCOSEM Component.
To learn more about setting up Dash on your computer, click the link to see some EKM Dash tutorials in our online. Setup Instructions: Information: When making settings in a meter using the Dash software, you will be prompted for your meter password. This password is '0' by default. To purchase a registration key for the EKM Dash, go to our EKM Dash product page here:.
Instead, in our target program, we will use our ezhdlc library, that implements the whole HDLC traffic and just exposes three routines: HDLCConnect(); Establishes an HDLC connection with the peer layer. HDLCSendReceive(DataToSend, DataReceived); Sends data to the peer layer and receives the response from the peer layer.
Tariff number). F Defines the storage of the data, identified by A to E (e.g.
The Dash can also display a visual representation of your data. Seen here: Please Note: pulse count data from water and/or gas meters, provided by the Omnimeter Pulse v.4, can only be visually presented when using the EKM Push system. The EKM Dash can also retrieve v.3 and v.4 Omnimeter data directly from the system. This is very easy to setup. It allows you to take Push data and create.csv files, graphs and spreadsheets, store an unlimited number of reads on your local hard drive, send data to wattvision, create email reports, and more.
The EKM Dash Registration Key can be purchased for $30 here:. EKM Dash Tutorial Videos.
A flowchart of the compliance assessment process is given in Fig. Fig 2: Compliance assessment process overview The conformance test report is automatically generated during each test campaign. It is a digitally signed text file, containing the following elements: • Date of testing • Identification of the test tool and license owner • Identification of the manufacturer as declared in the CTI file • Identification of the IUT as declared in the CTI file • A summary of results for each test suite • The result of each test case • A copy of the CTI file • Digital signature, allowing to check the authenticity of the conformance test report.
The continuous development of DLMS/ COSEM open communications protocols for data retrieval, updation and reconfiguration of metering devices has enabled diverse operators to access safely and quickly data from metering equipment provided by diverse manufacturers. Among the many open protocols like MODBUS, ANSI, DLMS, the DLMS/COSEM (IEC 62056) was chosen by India. MODBUS was more towards process instrumentation and ANSI the meter protocol used in North America. The IEC 62056 is an open protocol exclusively evolved for Metering purpose.
This object list is very small. It has only two entries. Each entry describes one object instance using a structure of 4 elements.
Dlms Meter Reading Software
Otherwise the two requests are the same. The Proposed MaxPdu Size is the size of the longest PDU that the client is able to store. The value 'FFFF' means 'no limits'. The AssociationResponse The meter's response to an AssociationRequest is an AssociationResponse.
Kalkitech Grid Communication services help utilities to transition to key technologies and protocols like IEC 61850 based substation and distribution automation. They also enable simulation of potential deployment scenarios, build test setups and labs for evaluation as well as provide engineering and configuration tools that are critical to such deployments. The Kalkitech Grid Automation team enables OEMs to adopt and upgrade IEC 61850 investments to suit various utility and interoperability requirements. Kalkitech Grid Automation services help utilities to transition to key technologies and protocols like IEC 61850 based substation and distribution automation. They also enable simulation of potential deployment scenarios, build test setups and labs for evaluation as well as provide engineering and configuration tools that are critical to such deployments. The Kalkitech Grid Automation team enables OEMs to adopt and upgrade IEC 61850 investments to suit various utility and interoperability requirements.
And the DLMS/COSEM protocol. The problem is not trivial, and to be able to design a solution, we first need to know more about some of the main concepts of the COSEM/DLMS standard. The Physical Device The Physical device, is our meter, it supports one or more communication profiles.
Other use cases where the server is within the gateway and the client is in the central office are also feasible. Before the actual metering information can be exchanged an association has to be build up, which is initiated by the client. The DLMS client can then access the interface object model inside the server. Once an association exists the DLMS server is also able to send notifications to the client without an explicit request. DLMS/COSEM supports clock synchronization and transmission of measurement data and profiles.
Now the connection is established. Association View Association View describes what kind of objects meter offers. Call.of.duty.modern.warfare.2 - razor 1911. Structure of Association View varies by used Authentication. The association view is requested using data from GetObjects method. Send this request using data handling methods described in. The reply data is very large so this can take very long time (even hours with slow connection like terminal and if the connection is bad).
Once the full reply is received parse it with ParseAAREResponse method. This method sets the relevant settings to the GXCOSEM component and return a collection of manufacturer specific tags if there was any.
You can think Profile Generic as a Table. To get the column information generate message using method Read with following parameters: Long or Short Name, 1, 1, ObjectType.ProfileGeneric, 3 The reply data is parsed with ParseObjects method and it returns the collection of data objects that are the columns. Reading Reading is generally split in two. Reading of 'regular' data objects and profile generic objects. General Data Objects Data objects are read using Read method. The parameters are defined as follows: Data: Logical or short name Packet Position: Always 1 Total Packet Count: Always 1 Interface Class: Object Type of the requested item, ex.
Automatic Meter Reading (AMR) AggreGate can collect consumption, diagnostic and status data from water, gas, heat, and electric meters and store this data in the AggreGate Server's database for billing, troubleshooting and analyzing. AggreGate Platform plays the role of Meter Data Management (MDM) software, but it also shares collected data with other systems.
Further the deregulation raised the need for integrating meter data with the business processes of stakeholders. The MBC process which begins with meter reading / downloading was the starting point of contention due to variety of protocols. With different makes of meters, the data collection for an automated process was a challenge.
Also the DLMS COSEM object model looks fairly heavy weight. I would be very interested to hear how you get on with this. First post btw. Reading through the experiences had by those in my earlier links, I'm optimistic that it is not a great leap to take it from Elster specific meter reading to something more general purpose. I think the Elster meters must be compliant with DLMS COSEM and it was possible to reverse engineer what much of the information comprised of - with documentation I think it could be relatively easy to modify.
This open protocol based on IEC 62056 helps to overcome most of the challenges for data acquisition from energy meters. The difficulties faced by the utilities to have successful remote metering deployments and the consequent difficulty in accounting energy losses due to proprietary protocols are well known. The Indian Companion Specification (ICS) is intended to provide a field level basis for efficient and secure transfer of electricity metering data in an open manner with judicious application of features and protocols of the International Standard. The Indian Companion Specification (ICS) was evolved by BIS as an Indian Standard IS 15959 which inherits the IEC 62056 series of standards.
The IEC TC13 WG14 groups the DLMS specifications under the common heading: 'Electricity metering data exchange - The DLMS/COSEM suite'. DLMS/COSEM protocol is not specific to electricity metering, it is also used for gas, water and heat metering.
Server and Client address are device manufacture debended. You can ask Server and Client address from the manufacturer.
Water Meter Reading Software
From: The start date or row index of the requested period* To: The end date or row index of the requested period* *If row indices are used the logical name of the first column must be null. The reply data is parsed using GetValue that returns a two dimensional table of values. Disconnect The disconnect message must be sent always before disconnecting even if the device doesn't reply to it. Disconnect message is generated using Disconnect method and might not get a reply. Before sending request it's important to be sure that it can fit in packet sizes.