Not All OBIS Codes Read by GXDLMS/COSEMDirector

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 pierrej , 18 December, 2014

Hi,

We've got a Itron SL7000 761 meter. I managed to read the OBIS codes from the meter (Authentication: Low, IEC), but the OBIS codes for the load profile are not there. The ones I'm interested in, are:

Active Energy Aggregate: 1.1.1.29.0.255
Import Apparent Energy Aggregate: 1.1.9.29.0.255
Import Reactive Energy Aggregate: 1.1.3.29..0.255

The Load Profile Generic codes that are there, gives the "Access Error : Device reports scope of access violated" error, reported elsewhere on this forum.

Can anyone help on this?

Regards
Pierre

Kurumi

11 years 6 months ago

Hi,

SL 7000 is older meter and it is not fully DLMS/COSEM compatible.
Everything else works OK, but profile generics (historical data) is not implemented
in standard way. They have implemented it in own way.

We will check this tomorrow if we can find a way to fix this.

BR,

Mikko

Hi Mikko,

Thanks for the response, we have an ACE6000 (Itron) meter, with exactly the same symptoms.

Regards
Pierre

Kurumi

11 years 6 months ago

Hi Pierre,

We updated new version from GXDLMSDirector.
We improved Actaris SL 7000 and ACE 6000 support.

All COSEM objects are not implement to the Actaris meter and meter returns wrong error code for that (access violation).

Get latest version and let me know if you still have something.

All profile generics data is not shown correctly because Actaris is using own, non standard way to show data.

BR,

Mikko

pierrej

11 years 4 months ago

We could read all load profile values we require (for the SL7000), by using the Gurux objects, and we are generating a load profile file, with the correct values, but the only thing I cannot work out is to calculate the "End Of Period" values, does somebody know how to do that? I'm pasting the GuruX output as well as the AcePilot output underneath:

GuruX:
=======================================================
07 DE 0C 12 FF 0F 13 12 FF 80 00 FF | 000000 | FF FF FF FF FF 0F 14 15 FF 80 00 FF | 000000 | 0 | 0 | 0 |
FF FF FF FF FF 0F 1C 22 FF 80 00 FF | 000000 | 0 | 0 | 0 |
FF FF FF FF FF 0F 20 22 FF 80 00 FF | 000000 | FF FF FF FF FF 0F 1E 15 FF 80 00 FF | 000000 | FF FF FF FF FF 0F 1E 1C FF 80 00 FF | 000000 | 0 | 0 | 0 |
FF FF FF FF FF 0F 26 2D FF 80 00 FF | 000000 | 0 | 0 | 0 |
0 | 0 | 0 |
6 | 6 | 1 |
7 | 8 | 1 |
8 | 7 | 1 |
7 | 7 | 1 |
7 | 8 | 1 |
7 | 7 | 1 |
8 | 7 | 1 |
7 | 7 | 1 |
7 | 8 | 1 |
7 | 7 | 1 |

AcePilot:
End of Period Channel 1 (Wh) Channel 2 (VAh) Channel 3 (varh) Events
18-12-2014 03:20 PM 0 0 0 "Power Cut:
Measurement Start Start 03:19:18 PM
Short Period Start 03:19:18 PM End 03:20:21 PM
"
03:30 PM 0 0 0 "Power Cut:
Short Period Start 03:28:34 PM
"
03:32 PM 0 0 0 "Power Cut:
Short Period End 03:32:34 PM
Power Cut Time 1 03:30:21 PM Time 2 03:30:28 PM
"
03:39 PM 0 0 0 "Power Cut:
Short Period Start 03:38:45 PM
"
03:42 PM 0 0 0
03:45 PM 6 6 1
03:48 PM 7 8 1
03:51 PM 8 7 1
03:54 PM 7 7 1
03:57 PM 7 8 1
04:00 PM 7 7 1
04:03 PM 8 7 1
04:06 PM 7 7 1
04:09 PM 7 8 1
04:12 PM 7 7 1

The values I require to calculate/read are 03:20 PM, 03:30 PM, 03:32 PM, 03:39 PM, 03:42 PM etc.

Kurumi

11 years 4 months ago

Hi,

Actaris meter do not fully support COSEM standards with profile generics (historical data).

It returns array of values where 07 DE 0C 12 FF 0F 13 12 FF 80 00 FF is date time.

You can get correct date time value using GXClient's ChangeType.

BR,

Mikko

Hi Mikko,

Thanks, but the DateTime fields I'm looking for are for the End Of Period of the load profile periods, the DateTime fields you are referring to is when there is a power up/down on the meter and the DateTime gets logged.

I've also sniffed the serial port when AcePilot reads the load profile, but can not work it out from there either, but there must be a way AcePilot is calculating the End of Period times.

When there is no error on the meter, no time gets send back to the client, except if one must specifically ask for an OBIS code for the End of Period DateTimes.

Please let me know your thoughts.

Regards,
Pierre