It may be wrong in some places but I'm trying to get an idea of how to implement our own IGXMedia.
The Socket passed into it comes from ServerSocket.accept() in another Java file (just for reference).
There may very well be authentication problems but in our code via GXDLMSReader we would expect those to appear then, it seems to get stuck initializing the connection.
Your meter is using WRAPPER and your listener is using HDLC framing.
Data that you are sending is WRAPPER frame that contains information from the connecting meter.
I don't know what meter you are using, but I believe that you need to wait until the meter has send identification message. Then connect using client address 1 and meter address 1.
I'm not quite sure what the data is. Usually there is a Logical Device name (FLAG id + serial number), but I don't know what this is.
I decoded the hex representation of the bytes into ASCII (above) and I got something that looked like this (with some nonprintable characters/invalid sequences):
CLE1054229000309
(It's a clou meter by the way).
---
I hjave switched to `InterfaceType.WRAPPER` and will see what happens (if anything). It's an ongoing project to be able to have our meters connect over TCP in such a manner (having a GXDLMSReader instance associated per socket) hence any help is always appreciated :)
Hi, Your meter is using…
Hi,
Your meter is using WRAPPER and your listener is using HDLC framing.
Data that you are sending is WRAPPER frame that contains information from the connecting meter.
<WRAPPER len="16" >
<SourceAddress Value="1" />
<TargetAddress Value="1" />
<PDU>
<Data="0A0210434C4531303534323239303030333039001889" />
</PDU>
</WRAPPER>
I don't know what meter you are using, but I believe that you need to wait until the meter has send identification message. Then connect using client address 1 and meter address 1.
I'm not quite sure what the data is. Usually there is a Logical Device name (FLAG id + serial number), but I don't know what this is.
BR,
Mikko
I decoded the hex…
I decoded the hex representation of the bytes into ASCII (above) and I got something that looked like this (with some nonprintable characters/invalid sequences):
CLE1054229000309
(It's a clou meter by the way).
---
I hjave switched to `InterfaceType.WRAPPER` and will see what happens (if anything). It's an ongoing project to be able to have our meters connect over TCP in such a manner (having a GXDLMSReader instance associated per socket) hence any help is always appreciated :)
Any idea as to how to decode…
Any idea as to how to decode wrapper correctly. Does GuruX support it?