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.
Forums
Hello Mikko,
While reading a Landis+Gyr meter directly with GXDLMSDirector, last version, I see there are not cumulative demand register listed, codes like [1.1.1.2.x ] does not even appear in GXDLMSDirector
in GXDLMSDirector DemandRegister only show current averages
in MAP110 DemandRegister show also cumulative codes, like 1.1.1.2.0, 1.1.1.2.1, ...
OK, at first glance it *seems* a problem of access rights.. but how it's possible I can read those same codes with user NONE and no password with MAP110.
If needed, I can send you by mail reading trace log in hex of MAP110 to see what does exactly when reading those codes, and why can't be read with Director. Or any test you consider.
Thanks
Image
Hi Hernan,
Hi Hernan,
I believe that those demand registers are not in Association view.
Are you reading your meter with Map120 using IEC 62056-21 and not DLMS?
I believe that is the reason.
BR,
Mikko
Hello, yes, those registers
Hello, yes, those registers seems not to be in association view. I am not using IEC 62056-21, the reading is done via direct serial port 232 configured as HDLC.
Is there any way to read those registers?
Thank you
PD: I've sent you an e-mail with trace log of communication MAP110 does to reads those codes.
Hi Hernan,
Hi Hernan,
You can add those registers manually to GXDLMSDirector.
1. Select device.
2. Select "Add Object" from "Edit" manu.
3. Select object type and set OBIS code.
Note! If OBIS code or object type are wrong, meter returns an error when you try to read them.
BR,
Mikko
Hello, I've already added the
Hello, I've already added the object with edit, for example 1.1.1.2.1.255
But it also gives error: "Read-Write denied".
With GXDLMSDirector: "Read-Write denied".
TX: 7E A0 2E 03 21 BC CA AE E6 E6 00 C0 03 C1 03 00 05 01 01 01 02 01 FF 04 00 00 05 01 01 01 02 01 FF 02 00 00 05 01 01 01 02 01 FF 03 00 0F 3C 7E
RX: 7E A0 16 21 03 FA D2 86 E6 E7 00 C4 03 C1 03 01 03 01 03 01 03 17 B2 7E
Same answer with Java: "Read-Write denied".
TX: 7E A0 19 03 21 DC 1F D6 E6 E6 00 C0 01 C1 00 03 01 01 01 02 01 FF 02 00 F4 A7 7E
RX: 7E A0 11 21 03 FC C5 B4 E6 E7 00 C4 01 C1 01 03 73 82 7E
Curious if it is a problem of access rights because MAP110 reads it without authentication.
Now I've discovered that even in Director -> Tools->OBIS Codes, there is also an error message in the description, will it be an old issue? I've attached the screenshot
BR,
Hernan
Hi,
Hi,
You are using Logical Name referencing. Change "Logical Name referencing" to false and re-read association view.
BR,
Mikko
Finally ! Director reads a
Finally ! Director reads a value, here the log:
10:19:26 Read object type Register index: 2
TX: 7E A0 11 03 21 9E D1 52 E6 E6 00 05 01 02 BC 80 EE 84 7E
10:19:26
RX: 7E A0 18 21 03 18 8C EC E6 E7 00 0C 01 00 14 00 00 00 00 00 00 04 B0 F7 C1 7E
Still description has that message "Access Error : Device reports a hardware fault"
So, as I understand, many values can be read with Logical Name Referencing, but for some other codes its needed to switch to Short Name referencing, plus read association view, and only then access the object, a very weird protocol to tackle, I congratulate your patience.
Thank you!
Hi Hernan,
Hi Hernan,
Is this error message shown when you read this register?
Yes, you need to re-read association view if you change the reference type.
BR,
Mikko
Hello,
Hello,
No, the message doesn't show, but it's in lgz.obx, to see it in GXDLMSDirector
Tools-> Obis Codes -> Landis+Gyr-> 1.1.1.2.1.255 and 1.1.1.2.2.255
And inside of lgz.obx file:
<GXObisCode>
<LogicalName>1.1.1.2.1.255</LogicalName>
<Description>Access Error : Device reports a hardware fault</Description>
<Interface>Register</Interface>
<ObjectType>3</ObjectType>
<Attributes>
<GXDLMSAttributeSettings>
<Index>2</Index>
<Type>Int32</Type>
</GXDLMSAttributeSettings>
</Attributes>
</GXObisCode>
<GXObisCode>
<LogicalName>1.1.1.2.2.255</LogicalName>
<Description>Access Error : Device reports a hardware fault</Description>
<Interface>Register</Interface>
<ObjectType>3</ObjectType>
<Attributes>
<GXDLMSAttributeSettings>
<Index>2</Index>
<Type>Int32</Type>
</GXDLMSAttributeSettings>
</Attributes>
</GXObisCode>
<GXObisCode>
Those codes should be cumulative power maximums for rates 1,2 (and 3 is not even present).
Maybe they stayed that way because of this trouble that can't be read with Logical Name Referencing
Best Regards,
Hernán
Hi Hernán,
Hi Hernán,
Re-start GXDLMSDirector. There is "New Manufacturer Settings Available" -menu.
Press that and update manufacturer settings. Read association view again (Select Refresh from File-menu) and descriptions are correct.
BR,
Mikko
For some reason, after the
For some reason, after the update, almost all obis codes have disappeared....
Hi,
Hi,
Did you re-read association view? Objects are there, but descriptions are missing. Is this the case?
BR,
Mikko
There is no problem now, I
There is no problem now, I was pointing out is that in the menu
Tools-> Obis Codes -> Landis+Gyr-> there is nothing after the update.
before the update there was error messages in codes ex. 1.1.1.2.1.255
now the form is empty
Hi Hernán,
Hi Hernán,
Yes, we are using standard DLMS values here. We tested this with couple different DLMS meters and clear the values and start to use the default ones.
BR,
Mikko