Can't connect with Iskraemeco MT880

Thanks for the reply,
I tried with your parameters and I still having the problem. I configured the meter with SEP2 MeterView (Iskra Software) and the protocol driver was MeterConserth. When I used SEP2 MeterView Software I could read the meter without any problem.
MeterConserth is supported by Gurux?
Thanks in advance,
Diego

Hi,

You should ask Meterview from the meter vendor. You can also use GXDLMSDirector to read your meter.

BR,
Mikko

I also facing with the same problem.

Does Gurux support Consereth header in newer version?

Or is it possible somehow to read MT880 over Ethernet module without consereth header?

OK, I found solution for myself.

It is enough to add three consereth bytes on sending data.
Response also have consereth data, but gurux only takes data from 0x7E to 0x7E so it ignores leading three bytes.

When I finished with my testing, I could provide general solution for Iskra meters with consereth head bytes.
Device properties should have additional checkbox for consereth. Opposite than consereth is transparent Which is now "Use Serial port through ethernet."

Hi,

It would be great if you can share what bytes are needed. Our clients are reading Iskra meters using WRAPPER.

BR,

Mikko

But which module they have.
I'm using CM-e-3

According to MT880 documentation, I don't Know how it will be displayed on this forum, but you could always chack pdf document, this is just for discussion purposes

Consereth
Communication protocol (made by Iskraemeco) runs over TCP/IP protocol and enables
transparent sending of any sort of messages through TCP/IP networks

Several communications profiles are used in the meter:
 COSEM/DLMS over TCP/IP (using GPRS network)
 COSEM/DLMS over IEC 62056-46 (using local port, GSM CSD or CONSERETH over TCP/IP)
 IEC 62056-21 (using local port or CONSERETH over TCP/IP)

COSEM communication profiles

Three different communication profiles can be seen. The Figure 78 presents COSEM
communication profiles implemented in the meter. COSEM 3-layer, connection oriented,
HDLC based communication profile runs on local communication interfaces
(optical, RS485, RS232, CS) and on the GSM interface (see the Figure 78, left side).
TCP/IP based COSEM communication profile is implemented for use in conjunction
with a GPRS/UMTS communication interface (see the Figure 78, right side).

Consereth is described on page 146 (8.6.3. Consereth).

Long story, short story
thera are three leading bytes
Consereth Head
BYTE0 | BYTE1 | BYTE2
| | |_____ LENGTH (Low Byte)
| |
| |_____________ LENGTH (Hi Byte)
|
|_____________________ TYPE (Message ID)

MessageID € { 1, 2, 3 } Message Type | Description
| | |
| | |____ Data | Message is not interpreted –
| | | data is transferred to internal servers (RX)
| | | / transferred to the socket (TX)
| |
| |_______ Respond | Response to the request (not implemented).
|
|__________ Request | Message is interpreted.
| Sender receives response (not implemented).

The 1st byte of header contains TYPE (Message_ID) value, which is encoded
as presented in the Table 89. The meter only supports “Data” type messages.

The 2nd byte of header carries High Byte of the length and together with the
3rd byte of header which carries Low Byte determine the length of the payload message.
Length of the payload message is limited to 200 bytes.
If the message to be transmitted is larger than 200 bytes, the message is fragmented
to several Consereth packets, each containing maximum 200 bytes of text message.
When receiving Consereth messages, meter checks header message type.
Only Data message type is supported. Then Data length is parsed from the header.
If data length is not larger than 200 bytes, data message is passed to upper HDLC or
IEC 62056-21 server.

When HDLC or IEC 62056-21 server responds to the request, the response frame is given
to a Consereth header, and sent through TCP/IP socket. Meter always cumulates data to
be sent until the message is not larger than 200 bytes or until 30 ms timeout elapses
from last sending request. If more than 200 bytes need to be sent within 30 ms timeout,
message is divided to fragments of maximum size 200 bytes.

When no data is exchanged within the time out period configured in dedicated object,
the meter closes the active Consereth connection. Meter still keeps listening for
new connections on configured port.

Document:
http://www.telematicasistemi.it/en/documents/_01.category/manuali/MT880…

And some info about MT880.
When communication is one-on-one like optical head or Ethernet, physical address (HDLC) is 17 (0x11 in gurux GUI client).

But if we try to read meter over RS485 which could be connected with other meters, than it use different HDLC address. By default it is last two digits from serial number plus 16.

Landis has last four digits plus 1000.

I put these lines to do proof of concept with MT880

/*ivan consereth header*/
byte[] length = BitConverter.GetBytes((short)data.Length);
byte[] conserethHead = { 0x03, length[1], length[0] };
IEnumerable<byte> conserethData = conserethHead.Concat(data);
media.Send(conserethData.ToArray(), null);

Within ReadDLMSPacket (GXDLMSCommunicator.cs)

First lines from wireshark (reading registers with none authentication):
GURUX: 03:00:15:7e:a0:13:02:23:21:93:11:97:81:80:06:05:01:9a:06:01:9a:a1:cc:7e
METER: 03:00:21:7e:a0:1f:21:02:23:73:e6:c7:81:80:12:05:01:9a:06:01:9a:07:04:00:00
:00:01:08:04:00:00:00:01:cc:a2:7e
GURUX: 03:00:2e:7e:a0:2c:02:23:21:10:af:9f:e6:e6:00:60:1d:a1:09:06:07:60:85:74:05
:08:01:01:be:10:04:0e:01:00:00:00:06:5f:1f:04:00:40:1e:1c:ff:ff:3b:7f:7e
METER: 03:00:3a:7e:a0:38:21:02:23:30:34:e7:e6:e7:00:61:29:a1:09:06:07:60:85:74:05
:08:01:01:a2:03:02:01:00:a3:05:a1:03:02:01:00:be:10:04:0e:08:00:06:5f:1f:04
:00:00:1e:1c:05:00:00:07:1f:b1:7e

By the way, something is not OK with reading registers and in general by reading this meter with no authentication. Because, lot of things could not be read at all, and some things like Registers, I see that gurux read from meter, but it doesn't update GUI with results.

When I use Low level security then it is all fine. But I need to check couple of things to be sure what is going on.

Hi,

The idea is simple. I don't understand why they need this. Consereth is not defined on DLMS green book. This will make that Iskra CM-e-3 module is not supporting DLMS standard.

Because of your good work, I'll add this to work list and we'll add support for this to C# version.

I believe that you don't have access rights to the meter. After you have change access level you need to
refresh device objects.

BR,

Mikko

Yes, this is not the dlms standard. As you can see from MT880 document, consereth is made by iskraemeco.

I work with gurux and meterview (iskraemeco software) and watch wireshark.

First solution was shortcut, now I found that is better to wrapp media.Send and withinh wrapper method control sending packets. Now I have three start protocol, IEC, DLMS and ConserethDLMS :)

--
Also I don't undestand why did DLMS propose TCP DLMS.

For me it'll be enough to sent packets as on Serial, and TCP itself secured transmission.

But maybe I just skip something so far . . .

And I don't know if there is any list of tested meters with gurux.
Maybe this kind of topic could be useful for others.

For example, for me doesn't work initial settings for iskra meters (wrong addresing)

there is Client address 64, but for MT880 I have following
COSEM Application Associations | Client SAP | Server SAP
Public Association | 16 | 1
Management Association | 1 | 1
Management Association 2 | 2 | 1
Preestablished Association | 102 | 1

etc.

Hi,

Your idea is good. :-)

You should be able to send your data using HDLC framing without any extra bytes. There must be a good reason for this.

Initial settings may vary from the model of the meter.

Iskra Initial settings are used when you are reading your meter using the serial or optical port.
Initial settings are different when using TCP/IP connection with Iskra meters. :-(

BR,

Mikko

Hi,

Please, create a new topic if you have a new question. I'll answer there.

BR,
Mikko

Hi Ivan,
could you share the data you got from wireshark!
Thanks

Hello,

that was years ago, and I don't have that meters on my desk anymore.

BUT, it is your lucky day, I found in my files one wireshirk file, captured by using MeterView (official Iskra software).

It would be better if you could say what kind of problem do you have?

My solution was adding class for CONSERETH

public static class GetDataForSend
{
public static byte[] GetData(byte[] data, StartProtocolType startProtocol)
{
if (startProtocol == StartProtocolType.ConserethDLMS)
{
/*ivan consereth header*/
byte[] length = BitConverter.GetBytes((short)data.Length);
byte[] conserethHead = { 0x03, length[1], length[0] };
return conserethHead.Concat(data).ToArray();
}
return data;
}
}

the file is on my google drive. I hope you could reach it
https://drive.google.com/file/d/1YpUdNXdeFE_nQxjMnZk8dMnAN5YJehXb/view?…

here is the beginning of the communication (each packet starts with CONSERETH header 0x03 0x00 0xLength)

-> 03 00 0a 7e a0 08 02 23 21 93 bd 64 7e

<- 03 00 21 7e a0 1f 21 02 23 73 e6 c7 81 80 12 05 01 9a 06 01 9a 07 04 00 00 00 01 08 04 00 00 00 01 cc a2 7e

-> 03 00 2e 7e a0 2c 02 23 21 10 af 9f e6 e6 00 60 1d a1 09 06 07 60 85 74 05 08 01 01 be 10 04 0e 01 00 00 00 06 5f 1f 04 00 00 7e 1f ff ff 99 c8 7e

<- 03 00 3a 7e a0 38 21 02 23 30 34 e7 e6 e7 00 61 29 a1 09 06 07 60 85 74 05 08 01 01 a2 03 02 01 00 a3 05 a1 03 02 01 00 be 10 04 0e 08 00 06 5f 1f 04 00 00 7e 1f 05 00 00 07 62 2b 7e

-> 03 00 1c 7e a0 1a 02 23 21 32 f6 72 e6 e6 00 c0 01 40 00 01 00 00 2a 00 00 ff 02 00 98 47 7e

<- 03 00 25 7e a0 23 21 02 23 52 8c 54 e6 e7 00 c4 01 40 00 09 10 49 53 4b 54 38 38 30 4d 37 30 37 35 37 32 32 37 a1 3c 7e

-> 03 00 1c 7e a0 1a 02 23 21 54 c6 74 e6 e6 00 c0 01 40 00 0f 00 00 28 00 00 ff 02 00 1b 94 7e

<- 03 00 a6 7e a8 a4 21 02 23 74 69 8b e6 e7 00 c4 02 40 00 00 00 00 01 00 82 04 f4 01 82 05 28 02 04 12 00 08 11 00 09 06 00 00 01 00 00 ff 02 02 01 09 02 03 0f 01 16 00 00 02 03 0f 02 16 00 00 02 03 0f 03 16 00 00 02 03 0f 04 16 00 00 02 03 0f 05 16 00 00 02 03 0f 06 16 00 00 02 03 0f 07 16 00 00 02 03 0f 08 16 00 00 02 03 0f 09 16 00 00 01 06 02 02 0f 01 16 00 02 02 0f 02 16 00 02 02 0f 03 16 00 02 02 0f 04 16 00 02 02 0f 05 16 00 02 02 0f 06 16 00 02 04 12 00 1b 11 01 09 06 00 00 02 00 00 ff 11 b8 7e

-> 03 00 a6 7e a8 a4 21 02 23 74 69 8b e6 e7 00 c4 02 40 00 00 00 00 01 00 82 04 f4 01 82 05 28 02 04 12 00 08 11 00 09 06 00 00 01 00 00 ff 02 02 01 09 02 03 0f 01 16 00 00 02 03 0f 02 16 00 00 02 03 0f 03 16 00 00 02 03 0f 04 16 00 00 02 03 0f 05 16 00 00 02 03 0f 06 16 00 00 02 03 0f 07 16 00 00 02 03 0f 08 16 00 00 02 03 0f 09 16 00 00 01 06 02 02 0f 01 16 00 02 02 0f 02 16 00 02 02 0f 03 16 00 02 02 0f 04 16 00 02 02 0f 05 16 00 02 02 0f 06 16 00 02 04 12 00 1b 11 01 09 06 00 00 02 00 00 ff 11 b8 7e 03 00 0a 7e a0 08 02 23 21 71 a1 a0 7e