Elgama EMS using protocol IEC 62056

7 posts / 0 new
Last post
jpaa07
Elgama EMS using protocol IEC 62056

Hi,

Can I read an Elgama EMS meter using protocol IEC 62056 ?
Because I am trying to connect with DLMSDirector but it does not work.
Do you have any solution for that?
Thank you very much!

kurumi
kurumi's picture
Elgama EMS using protocol IEC 62056

Hi,

Meters do not answer if server or client address is wrong.
Because we do not have this meter you can try with this:

Select Landis+Gyr and try to connect. If this fails, change starting protocol from IEC to DLMS.
If it still fails let me know.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

Administrator
Administrator's picture
Elgama EMS

Hi,

We sent inquiry for the manufacturer but they newer answered.
If your meter is Gama 300 there is a DLMS label but we do not know settings.

Gurux Administrator

deivy311
ELGAMA - Optical probe - problem with meter response

Dear Kurumi,
I am trying to receive data from an ELGAMA meter through optical probe, and I am using the native software to compare the sent and received strings with the GURUX.DLMS.Conformance.Test.

I modified a piece of code, in order to avoid changing to "MODE E", this way:

byte controlCharacter = (byte)'1';// "2" HDLC protocol procedure (Mode E)
//Send Baudrate character
//Mode control character
byte ModeControlCharacter = (byte)'1';//"2" //(HDLC protocol procedure) (Binary mode)

After this, I made the respective changes for BaudRate. Nevertheless, I haven't been able to accomplish the same response than the one on the native software.

In my attempts, I cannot get this very last part: .P0.().`

The native software response is the following.
You will notice a piece of response that I included, which is the part that differs from the Gurux response, where I suspect the problem is placed. This process apparently makes a purge of the buffers in some specific flags locations, that is not made with the Gurux code.

Is this problem familiar to you?

-------------- Native software response (dump view) ---------------------
[09/08/2018 10:54:30]Changed baudrate: 300

[09/08/2018 10:54:30]Disabled RTS

[09/08/2018 10:54:30]Enabled DTR

[09/08/2018 10:54:30]Changed line control: Databits 7, Parity even, StopBits 1

[09/08/2018 10:54:30]Changed flow control: ControlHandShake 0x01, FlowReplace 0x00, XonLimit 0, XoffLimit 0

[09/08/2018 10:54:30] Written data (COM4)
2f 3f 21 0d 0a /?!..
[09/08/2018 10:54:30] Read data (COM4)
2f 45 47 4d 35 45 50 51 53 31 32 39 2e 32 33 2e /EGM5EPQS129.23.
31 37 4d 53 0d 0a 17MS..
[09/08/2018 10:54:31] Written data (COM4)
06 31 35 31 0d 0a .151..
[09/08/2018 10:54:32]Changed baudrate: 9600

[09/08/2018 10:54:32]Disabled RTS

[09/08/2018 10:54:32]Enabled DTR

[09/08/2018 10:54:32]Changed line control: Databits 7, Parity even, StopBits 1

[09/08/2018 10:54:32]Changed flow control: ControlHandShake 0x01, FlowReplace 0x00, XonLimit 0, XoffLimit 0
----------------- Missing response in Gurux code (Line view)------------------------
[09/08/2018 10:54:32]
5282171 IRP_MJ_DEVICE_CONTROL - Request operates a serial port (COM4)
STATUS_SUCCESS
IOCTL_SERIAL_PURGE - Request cancels the specified requests and deletes data from the specified buffers
Flags - 0x0000000f

[09/08/2018 10:54:32]
5282173 IRP_MJ_DEVICE_CONTROL - Request operates a serial port (COM4)
STATUS_SUCCESS
IOCTL_SERIAL_PURGE - Request cancels the specified requests and deletes data from the specified buffers
Flags - 0x00000008
---------------- Continuation of native software response -------------------------------

[09/08/2018 10:54:32]Changed baudrate: 9600

[09/08/2018 10:54:32]Disabled RTS

[09/08/2018 10:54:32]Enabled DTR

[09/08/2018 10:54:32]Changed line control: Databits 7, Parity even, StopBits 1

[09/08/2018 10:54:32]Changed flow control: ControlHandShake 0x01, FlowReplace 0x00, XonLimit 0, XoffLimit 0

[09/08/2018 10:54:32] Read data (COM4)
01 50 30 02 28 29 03 60 .P0.().` -------> Missing response

------------------------------------------------------------------

Did I make myself clear enough? Feel free to ask for any additional information.
Thank you in advance for any help you can provide.

kurumi
kurumi's picture
ELGAMA - Optical probe - problem with meter response

Hi,

Your meter is using 62056-21, not DLMS. That is totally different protocol. You can't use GXDLMSDirector or GURUX.DLMS.Conformance.Test tool to read your meter.

http://www.gurux.fi/DLMSCOSEMFAQ

BR,
Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org

deivy311
ELGAMA - Optical probe - problem with meter response

Thank you for your reply.
So, it is not possible to communicate with this meter with the Gurux resources?
Any guess of how I can accomplish that?

Thank you in advance.

kurumi
kurumi's picture
ELGAMA

Hi,

You can use software from the meter manufacturer or made your own.
We are not supporting IEC 62056-21 because there are so many variations between the meter manufacturers.

BR,

Mikko

________________________________________
Mikko Kurunsaari
Gurux Ltd
Hermiankatu 6-8 H 33720 TAMPERE, FINLAND
Phone: +358 3 265 1244
Home page: http://www.gurux.org