I'm actually dealing with a strange behavior with a L+G E650. The problem is that the scaler, which is correctly read in the GXDLMSObjects 0f 0.1 is not applied if profile 1 is loaded. I did some investigation with the source code of the gurux assemblies and found out, that the AttributeIndex of the DemandRegisters in the "CaptureObjects" is 18 (instead of normal 2 or 3, on which the scaler is applied). This happens just with one single meter. The only difference compared to all other L+G E650 (which seem to work correctly) is that, this single meter reads production values (2.8.0, 2.8.1, 2.8.2, usw.), but I guess this should not be the reason for the wrong attribute index.
Have you any idea how this wrong attribute index can occur? Or overall, is there a list of possibly available attributes and it's meanings? Or is it may be necessary to apply the scaler also if attribute index 18 occurs.
A lot of questions, but many thanks for your support!
Have you modified your profile generic or is this made on the factory?
There are no 18 attributes on demand register. So this index is wrong. Meter seems to ignore attribute index and just gives the value. Can you modify this and set index to correct value?
Sorry for the delay, I didn't get (or accidently deleted) a mail of your comment.
I've no possibility to change the profile generic, it seems to be wrong configured from factory.
Actually, I use a workaround, that replaces the wrong attribute 18 with 2 in the CaptureObject, and that seems to work as expected. If you like I can give you the IP-Address and Port of the device with this strang behavior, so you can investigate by yourself. If necessary, pls send me a mail (I hope you see my mail address in my account, do you?), because I don't want to publish the IP-Address and Port to the web. But seriously, only if you aren't too busy, because I can live with my workaround.
We can configure one meter to work like this, so we don't need your meter. Thanks anyway.
I'll think what we do with this. I know that there are other meter readers who are fighting with the same problem. We'll try to find something for this.
ProfileGeneric
Hi,
Have you modified your profile generic or is this made on the factory?
There are no 18 attributes on demand register. So this index is wrong. Meter seems to ignore attribute index and just gives the value. Can you modify this and set index to correct value?
BR,
Mikko
ProfileGeneric
Hey Mikko
Sorry for the delay, I didn't get (or accidently deleted) a mail of your comment.
I've no possibility to change the profile generic, it seems to be wrong configured from factory.
Actually, I use a workaround, that replaces the wrong attribute 18 with 2 in the CaptureObject, and that seems to work as expected. If you like I can give you the IP-Address and Port of the device with this strang behavior, so you can investigate by yourself. If necessary, pls send me a mail (I hope you see my mail address in my account, do you?), because I don't want to publish the IP-Address and Port to the web. But seriously, only if you aren't too busy, because I can live with my workaround.
Thanks a lot, br
Andrea
ProfileGeneric
Hi,
We can configure one meter to work like this, so we don't need your meter. Thanks anyway.
I'll think what we do with this. I know that there are other meter readers who are fighting with the same problem. We'll try to find something for this.
BR,
Mikko