Hi, when I want to set Destination properties of GXDLMSPushSetup when ServiceType is Hdlc ,
gurux change obis code to Ascii format and write something like :
but when I use meter Own software to set this property it's write obis logical name as hex value like :
<!-- 0.2.22.0.0.255 -->
<OctetString Value="0002160000FF" />
I wanted to know which format is correct and also is there way to force gurux to write it as hex not ascii?
The content of the Destination attribute is not defined by the DLMS standard and it can be anything. There is usually a TCP/IP address and port number when a Push message is sent using a TCP/IP connection. Meters that I have seen don't use Destination property when HDLC service type is used.
I'm wondering why the OBIS code is given in the destination attribute. Do you have multiple serial ports in your meter?
I think because this meter wants to enable push setup on Optical and Rs485 port simultaneously,
it used such mechanism. I upload this meter Obis list for Push setup and iecHdlcSetup in below.
my problem is that destination field type in dlms blue book is OctetString. and you use Ascii for it value setting. but also you can parse hex value Correctly when I read value with GxdlmsDirector.
I think when you writing value for destination when service type is hdlc , you should write it as hex value and not ascii value
I have to think about how to solve this problem. I understand why your meter manufacturer has implemented it like this and the DLMS standard allows it. The problem is that the idea is different than the other meter manufacturers.
It will take some time before the new version can be released where this can be handled.
Hi,
Hi,
The content of the Destination attribute is not defined by the DLMS standard and it can be anything. There is usually a TCP/IP address and port number when a Push message is sent using a TCP/IP connection. Meters that I have seen don't use Destination property when HDLC service type is used.
I'm wondering why the OBIS code is given in the destination attribute. Do you have multiple serial ports in your meter?
BR,
Mikko
I think because this meter
I think because this meter wants to enable push setup on Optical and Rs485 port simultaneously,
it used such mechanism. I upload this meter Obis list for Push setup and iecHdlcSetup in below.
my problem is that destination field type in dlms blue book is OctetString. and you use Ascii for it value setting. but also you can parse hex value Correctly when I read value with GxdlmsDirector.
I think when you writing value for destination when service type is hdlc , you should write it as hex value and not ascii value
Hi,
Hi,
I have to think about how to solve this problem. I understand why your meter manufacturer has implemented it like this and the DLMS standard allows it. The problem is that the idea is different than the other meter manufacturers.
It will take some time before the new version can be released where this can be handled.
BR,
Mikko
I'll appreciate if you can
I'll appreciate if you can create a ticket for this، so that wouldn't forgotten.
Hi,
Hi,
I need to check first that this is not causing any problems with other meters.
BR,
Mikko
Hi,
Hi,
Get the latest version from GXDLMSDirector (9.0.2208.0101).
This is now working. Let me know if you have any problems.
BR,
Mikko
Thank you. I'll check it and
Thank you. I'll check it and let you know the result. But I use c# version. Did you change only GXDLMSDirector or also changes made to dlms dll ?
Hi,
Hi,
This is improved for C# component, but you can easily test this with GXDLMSDirector.
BR,
Mikko
Thank you
Thank you