Conformance tells what services device can offer. When client made connection it gives proposed conformance where client describes services what it wants to use.
Meter checks what services it supports and returns negotiated conformance. Using negotiated conformance client will know what kind of functionality is available,
All services here are not necessary supported by the client or meter. There are no limitations in DLMS standard to tell what is minimum functionality what meter must offer,Note! Supported services might depend from Authentication level because each authentication level has own association.
You can see proposed and negotiated conformances in GXDLMSDirector when you select the meter. Negotiated conformance is updated when connection to the meter is established.
Conformances that meter can offer are listed in association xDLMS Context Info-tab.
General protection
Is General Protection supported by the meter or is client interested from General Protection. General Protection is used to secure connection between client and the meter using Symmetric or ASymmetric ciphering or General Signing.If general-protection is selected, following methods are used.
- GeneralGloCiphering
- GeneralDedCiphering
- GeneralCiphering
- GeneralSigning
- GloGetRequest
- GloGetResponse
- GloSetRequest
- GloSetResponse
- GloEventNotification
- GloMethodRequest
- GloMethodResponse
- GloInitiateRequest
- GloReadRequest
- GloWriteRequest
- GloInitiateResponse
- GloReadResponse
- GloWriteResponse
- GloConfirmedServiceError
- GloInformationReport
- DedReadRequest
- DedWriteRequest
- DedInitiateResponse
- DedReadResponse
- DedWriteResponse
- DedConfirmedServiceError
- DedUnconfirmedWriteRequest
- DedInformationReport
General block transfer
General Block Transfer mechanism is used to transport data that size is longer than PDU size.Read
Is Read supported by the meter or is client interested from Read. Read is used with Short Name Referencing to read value from the meter.Write
Is Write supported by the meter or is client interested from write data to the meter. Write is used with Short Name Referencing to write value to the meter.Un-confirmed write
Is Unconfirmed Write supported by the meter or is client interested from write unconfirmed data to the meter. Unconfirmed Write is used with Short Name Referencing to write value without confirmation from success to the meter.Attribute0 supported with set
Is Attribute Set supported by the meter or is client interested from write data with Attribute 0 to the meter. Attribute 0 Set means that all COSEM object's attributes can be write one message.Priority Mgmt supported
Is Priority Management supported by the meter or is client interested from Priority Management. Priority Management is used by Logical Name referencing to handle urgent messages.Attribute0 supported with get
Is Attribute get supported by the meter or is client interested from read data with Attribute 0 from the meter. Attribute 0 Get means that all COSEM object's attributes can be read with one message.Block transfer with get or read
Is Block transfer supported by the meter or is client interested from read data with blocks from the meter. Read Block transfer is used to read data from the meter that is not fit to one PDU. Example reading historical data might take more than one PDU and then block transfer is used.Block transfer with set or write
Is Block transfer supported by the meter or is client interested from writing data with blocks to the meter. Write Block transfer is used to write data from the meter that is not fit to one PDU. Example updating image (Firmware) might take more than one PDU and then block transfer is used.Block transfer with action
Is Block with action transfer supported by the meter or is client interested from sending action data with blocks to the meter. Action Block transfer is used to send action data from the meter that is not fit to one PDU. Example Public Key transfer might take more than one PDU and then block transfer with action is used.Multiple references
Is multiple references supported by the meter or is client interested from multiple references. Multiple references is used when reading or writing several object with one request. Example ReadByList is using it.Information report
Is Information reports supported by the meter. Information reports is used with Short Name ReferencingData notification
Is Data Notification supported by the meter.Access
Is Access service supported by the meter or is client interested from Access service. Using Access service client can make several Read, Write or Action requests with one command.Parameterized access
Is parameterized access supported by the meter or is client interested from parameterized access. Parameterized access is used with Short Name Referencing to read selected objects.Get
Is Get supported by the meter or is client interested from Get. Get is used with Logical Name Referencing to read value from the meter.Set
Is Set supported by the meter or is client interested from Set. Set is used with Logical Name Referencing to write value to the meter.Selective Access
Is selective access supported by the meter or is client interested from selective access. Selective access is used with Logical Name Referencing example if Profile Generic is read by range or entry.Event Notification
Is Event Notification supported by the meter.Meter is using Event Notifications with Logical Name referencing to send events for given target. Example if power down occurred. Note! Client do not need to have connection to the server when event notification is send.