Read DLMS EDMI ATLAS MK10E seem wrong in Obis Code List and Data readout

Forum Rules

Before commenting read Forum rules

Don't comment the topic if you have a new question.

You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.

By TOMMY KRISTIAN HARI , 10 November, 2016
Forums
DLMSDirector

Read DLMS EDMI ATLAS MK10E seem wrong in Obis Code List and Data readout.

Comparing Eziview DLMS Reader with GURUX Director (Just take some items)

1. OBIS Code [1.0.32.7.0.255] L1 Voltage Inst. value
2. OBIS Code [1.0.51.7.0.255] L2 Current Inst. value
3. OBIS Code [1.0.31.7.0.255] L1 Current Inst. value
4. OBIS Code [1.0.52.7.0.255] L2 Voltage Inst. value
5. OBIS Code [1.0.14.7.0.255] Supply frequency Inst. value

In Gurux result have difeerent in their text description also the value read.
Attached the detail

Administrator

9 years 7 months ago

Hi,

Description is wrong. We are fixing this OBIS code issue. It it fixed for next release.

TOMMY KRISTIAN HARI

9 years 7 months ago

Thanks, Please check the data reading also, it seem incorrect.

May i know the schedule the next release?
Many hanks

TOMMY KRISTIAN HARI

9 years 7 months ago

Click the image that i have attached, you will see the comparison the data readed

Kurumi

9 years 6 months ago

Hi,

There are few differences between apps.
Scaler:
We are showing scaler as multiply. Eziview is showing as value read from the meter (Power of 10).
Example. GXDLMSDirector 0,1 Eziview -1 or GXDLMSDirector 100 Eziview 2.
Unit: GXDLMSDirector is shown string value of unit. Eziview numeric value read from the meter.
Value type is float 32. We have fix error for float 32 and float 64. Get latest version from GXDLMSDirector.

BR,

Mikko

TOMMY KRISTIAN HARI

9 years 6 months ago

Dear Sir,

I have try to test the updated version, but the data reading seem still wrong.
May you look at the attached screenshot.

many thansk

Kurumi

9 years 6 months ago

Dear Sir,

Can you read register 1.0.14.7.0.255 from your meter and send trace here.
Just those two lines where register is read and reply for it.
You can get trace Selecting "Show Log" Under Tools menu.

BR,

Mikko

TOMMY KRISTIAN HARI

9 years 6 months ago

As belo, 3 times read. the frequescy should be aroun 50 Hz

Log created 2:53:04 PM
2:53:07 PM Read object type Register index: 2
7E A0 19 03 25 10 1F BD E6 E6 00 C0 01 C1 00 03 01 00 0E 07 00 FF 02 00 47 3F 7E
2:53:07 PM Received data
7E A0 15 25 03 30 28 A9 E6 E7 00 C4 01 C1 00 17 42 47 F4 BD CD 77 7E
2:53:09 PM Read object type Register index: 2
7E A0 19 03 25 32 0F BF E6 E6 00 C0 01 C1 00 03 01 00 0E 07 00 FF 02 00 47 3F 7E
2:53:09 PM Received data
7E A0 15 25 03 52 3C E9 E6 E7 00 C4 01 C1 00 17 42 47 F5 C3 EC F4 7E
2:53:11 PM Read object type Register index: 2
7E A0 19 03 25 54 3F B9 E6 E6 00 C0 01 C1 00 03 01 00 0E 07 00 FF 02 00 47 3F 7E
2:53:11 PM Received data
7E A0 15 25 03 74 08 AD E6 E7 00 C4 01 C1 00 17 42 47 F5 C3 EC F4 7E

Kurumi

9 years 6 months ago

Dear Sir,

It seems that your meter is sending float as little endian byte order. (https://en.wikipedia.org/wiki/Endianness). It should send as a big endian.
You should contact your meter manufacturer and ask to fix this.

BR,

Mikko

TOMMY KRISTIAN HARI

9 years 6 months ago

sorry,
is it mean that in DLMS data format is fixed in float as little endian byte order?

Thanks

Kurumi

9 years 6 months ago

Hi,

Sorry, I was wrong. There is a issue on our C# code. We are using BitConverter.ToSingle and it expects that data is on Little Endian format.
In DLMS data format is Big Endian. Including float32 and float64.

We'll fix this ASAP. There will be new version today.

BR,

Mikko

TOMMY KRISTIAN HARI

9 years 6 months ago

Dear Sir,

Many thanks,
i had tested, now the data readout was same with eziview.

Best Regards
TOMMY