PROFILE GENERIC OBJECT

<< Click to Display Table of Contents >>

Navigation:  Multi-Protocol MasterOPC Server > DLMS PROTOCOL PLUG-IN > DLMS PROTOCOL DESCRIPTION > DLMS OBJECTS >

PROFILE GENERIC OBJECT

Profile Generic object - all-purpose profile. This interface class is dedicated for storing and access to data groups - so called «captured objects». The captured objects are attributes or object attribute elements. The captured object are collected periodically (load profile) or when a certain condition occurs (event logs). All-purpose profile is the main method to obtain the archived values of the device. Currently only load profiles are supported - event logs are not supported.

Number

Attribute

Data type tag

1

Logic name of the object

Line

2

Data buffer

Array or packed array

3

List of captured objects

Array

4

Capture period

32 bit unsigned integer

5

Sorting method

Listing

6

Occupied entries

32 bit unsigned integer

7

All entries

32 bit unsigned integer

The main purpose of Profile Generic is to obtain the archived values (power profile, monthly and daily statistics).

At startup, the driver initializes the power profile - determines the archive type (hourly, half-hour, daily or monthly) and also receives a list of captured objects. After that, it checks for the compliance of the captured objects list with the parameters of the Capture Object OBIS tags - if the profile specified for the tag is not found among the captured objects, no polling is performed. The list of captured object must also include the "Meter time" parameter (OBIS - 0.0.1.0.0.255). Otherwise, no power profile polling is performed.

At startup, the driver defines the current meter time, shifts the profile polling start time (read depth) as specified in the device settings, and starts the sequential reading of records (the number of the records read is also specified in the setting). The reading is completed, the current time in each polling cycle is compared with the last read record, and if more than 1 capture period has passed (half an hour, hour, day, month - depending on the profile type), new profile records are read.

Note. Only profiles with standard time intervals (half hour, hour, day, month) are supported - profiles with a different time interval are not supported