Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

The "Logical Name (LN) referencing" mode uses OBIS addresses OBIS address of objects.

The "Short Name (SN) referencing" mode does not use OBIS address but a numerical address in the range of 16 bits.

The individual data entities are presented in so-called COSEM objects (Companion Specification for Energy Metering), which are the instances of COSEM classes (COSEM interface classes, COSEM IC). The types of COSEM classes are specified in the document "COSEM Identification System and Interface Classes, Ed. 10.0", i.e. DLMS Blue Book. Each COSEM class has own identification number ("class_id") and the attributes with the sequence number. The attribute helps to get a specific parameter of given data entity.
Each instance has its initial SN address (base_name), which is also the the  address of the first attribute of class. "logical_name" is the first attribute of all COSEM classes. When reading this attribute, a user can obtain OBIS address of data entity that is presented by given class. The address of other attributes are in the "Short Name referencing" mode calculated according to this formula:

...

The attributes can be static or dynamic depending on whether their value is static (i.e. unchanging, set by a producer or in configuration of device) or dynamic (changing). In D2000 System, we recommend to configure only the dynamic attributes because as the own value of measured data entity is in dynamic attributes. If it is necessary, for the interpretation of value in dynamic attribute, other static or dynamic attributes can be are read automatically. See more information in the section Supported COSEM classes.

In the following tables you can find the supported COSEM classes. The attributes that represents own value the value of data entity (i.e. value that is important for a user) are characterized marked as "Yes, value of entity" in the column "Support in D2000". The static attributes are read automatically and characterized as "Automatically read".


Kotva
podporovane_triedy
podporovane_triedy
Supported COSEM classes

Data
class_id = 1, version = 0
Basic class that contains data entity accessible via attribute "value".
AttributeAttribute value typeAttribute descriptionSupport in D2000
1.logical_name (static)octet-string (text)OBIS address of data entity which is represented by an instance of this class.Yes, separate I/O tag
2.value (dynamic)CHOICE (see supported types of attribute values)Own The value of data entity.Yes, value of entity

...

Register
class_id = 3, version = 0
A class with data entity value that is accessible via attribute "value". The multiply coefficient, which is gained by static attribute "scaler_unit", is used automatically.
AttributeAttribute value typeAttribute descriptionSupport in D2000
1.logical_name (static)octet-string (text)OBIS address of data entity which is represented by an instance of this class.Yes, separate I/O tag
2.value (dynamic)CHOICE (see supported types of attribute values)Own The value of data entity.Yes, value of entity
3.scaler_unit (static)-Technical units and multiply coefficient.Automatically read



Extended register
class_id = 4, version = 0
 class with data entity value that is accessible via attribute "value". The multiply coefficient, which is gained by static attribute "scaler_unit", is used automatically.  A time stamp, which has been gained by the reading of dynamic attribute "capture_time", is added to the entity value.
AttributeAttribute value typeAttribute descriptionSupport in D2000
1.logical_name (static)octet-string (text)OBIS address of data entity which is represented by an instance of this class.Yes, separate I/O tag
2.value (dynamic)CHOICE (see supported types of attribute values)Own The value of data entity.Yes, value of entity
3.scaler_unit (static)-Technical units and multiply coefficient.Automatically read
4.status (dynamic)CHOICE (see supported types of attribute values)Status of the value. The standard does not specify the interpretation of this value. Mostly, it is a numerical value and you can find necessary information about its interpretation in a device manual.Yes, separate I/O tag
5.capture_time (dynamic)date_timeTime stamp of data entity value.Automatically read



Demand register
class_id = 5, version = 0
A register for measurement of accumulation energy supply in given period. See more info in DLMS Blue Book.
AttributeAttribute value typeAttribute descriptionSupport in D2000
1.logical_name (static)octet-string (text)OBIS address of data entity which is represented by an instance of this class.Yes, separate I/O tag
2.current_average_value (dynamic)CHOICE (see supported types of attribute values)Current situation of energy supply that is accumulated since the beginning of the period.Yes, value of entity
3.last_average_value (dynamic)CHOICE (see supported types of attribute values)Value of energy accumulated in last period.Yes, value of entity
4.scaler_unit (static)-Technical units and multiply coefficient.Automatically read
5.status (dynamic)CHOICE (see supported types of attribute values)Status of the value. The standard does not specify the interpretation of this value. Mostly, it is a numerical value and you can fined necessary information about its interpretation in a device manual.Yes, separate I/O tag
6.capture_time (dynamic)date_timeTime stamp of data entity value in the attribute "last_average_value".Automatically read
7.start_time_current (dynamic)date_timeTime stamp of the beginning of accumulated energy measurement with current status in the attribute "current_average_value".Automatically read
8.period (static)double-long-unsignedInterval period between two changes in data entity value in the attribute "last_average_value". The value is in seconds.Yes, separate I/O tag
9.number_of_periods (static)long-unsignedPeriod count that are used for calculation of data entity value in the attribute "last_average_value".
If "number_of_periods" > 1, "last_average_value" represents "sliding demand".
If "number_of_periods" = 1, "last_average_value" represents "block demand".
Yes, separate I/O tag

...