Billing Profile Data not getting With Range Selector

By Bhaumik, 27 September, 2023
Forums
DLMSDirector

Hi Mikko,

We have tried to read the Billing Profile Object from the Indian standard (IS16444) supported meter.

From all other profiles generic objects we are able to read using Range Selector because, in that, the First obis code is of Clock where as in the billing profile it is Billing Date.

Hence the Range selector is not working for the billing profile.

Can you please check into that and provide an update on how to read using the range selector?

Kurumi

1 month 3 weeks ago

Hi,

The meters that we have support the date and time for the billing profile. Is the data type of the billing date UInt32? How many rows there are? Some meters support only reading by entry where you need to use the start index and count.

BR,
Mikko

Bhaumik

1 month 3 weeks ago

Hi Mikko,

Thanks for the update.

There are a total of 13 entries (12 months + 1 current Billing) in the meter for the Billing Profile.

The Data Type of the Billing date is OctetString.

If we want to read the Billing profile using the Range selector with the Billing Date (0.0.0.1.2.255), Is it possible?

Can you please provide your suggestion?

Kurumi

1 month 3 weeks ago

Hi,

If the first item is 0.0.0.1.2.255 and the data type is UInt32 you can use the normal read-by-range method to read this.

If it doesn't work, add a hex trace from this and I'll check it from the bytes.
Some meter manufacturers in India doesn't implement range selector if there are only a few rows and you need to read them all and then make parsing on the client end.

BR,
Mikko