hwawrap.blogg.se - Dlms protocol example

This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".

The cookie is used to store the user consent for the cookies in the category "Analytics". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. The static information of requested objects will be retrieved by the SCL itself, and the implementer only needs to fill in the dynamic values from meter registers (using Data Interface functions). The implementer’s role is to edit the initialization of structure variables to suit his requirement. The SCL will have a sample implementation to clarify the structure and semantics of each object and it’s supporting structures. If the implementer chooses to modify the static/dynamic subdivision of objects, the implementer will have to modify the static initialization of the objects in the Configuration interface to suit the new arrangement. The values for the static attributes of all supported objects are normally filled in the Configuration Interface. Implementers can modify this subdivision and choose which all attributes of an object need to be dynamic (where values change dynamically and need to be updated from meter) by minor editing in certain source files. The SCL as it ships, assumes a typical subset of object attributes to be static. Security interface: Security interface interconnects DLMS stack with crypto library required for supporting the encryption/authentication/signature requirements as per DLMS security suite. The SCL will process the request, take care of access-privilege checking and call appropriate methods in the data interface.

Capture Object lists for Profile, Push setupĭata interface: The Data interface to the Meter consists of a set of functions that are called on receipt of DLMS get/set or actions request from a client (or their SN equivalents).

Complete OBIS and/or SN list of supported objects supported.

Multiple associations may be configured with different Application Contexts, Authentication Mechanisms and Conformance block services: The DLMS SCL provides a rich configuration interface. Implementers of the SCL can configure:

PRIME NB OFDM PLC Application identification.

PRIME NB OFDM PLC MAC network administration data.PRIME NB OFDM PLC MAC functional parameters.PRIME NB OFDM PLC Physical layer counters.