You need Communication unit CU-E20 / E21 / E22.
If you have that, you need to enable it.
If you can access your meter example using optical head, change Logical Device address from 0 to 1 and
you can check your communication module settings. Example listening port number.
I have an L+G E650 test unit, and am attempting to setup communications.
I do not have the serial interface, so will have to use TCP/IP only.
The unit was configured with an IP address of 192.168.110.10.
When connecting, I get the following error message:
"No connection could be made because the target machine actively refused it"
I have confirmed the IP address via ping...so it can only be an incorrect port assignment. I am using the default port 4059 which is selected when I choose 'Landis+Gyr' via 'File' ->'Add Device' -> 'Device Settings' menu. Can you suggest a different port?
I Know that is original question outdated, but at the moment I'm working with Landis+Gyr ZMD410 and E22 modules.
About connection problems, it could be module settings. I have couple of modules on my desk, and after closer look on each parameter (I read communication unit with MAP120 official Landis+Gyr Software) and there is one parameter that indicates time Window which presents when the module is active. By default it is not set on Always and that could be one problem about connecting over ethernet.
Second thing is socket closing. After reading meter, GXNet calls client.Close(); which lefts device in some odd state. After analyzing with wireshark I have noticed that there is no FIN signaling over the network.
So, it is recommanded to use client.Shutdown(SocketShutdown.Both); than client.Close();
There is one method which use same pattern, but I don't Know when this function is called.
Is there any reason to not close connection with Shutdown(SocketShutdown.Both)?
"
When you are finished sending and receiving data, use the Shutdown method to disable the Socket. After calling Shutdown, call the Close method to release all resources associated with the Socket.
"
We have added shutdown to c# network component. Our clients are reading a lot of different meters and this is not a very common error. They are also using CU-P42 module, but I was thinking that there is a delay before the meter is read again. They are not polling data all the time. Usually once a day, etc.
So I believe that meter closes TCP/IP connection after a while even if FIN is not sent.
Landis+Gyr E650 setup
Hi,
Shortly, YES.
You need Communication unit CU-E20 / E21 / E22.
If you have that, you need to enable it.
If you can access your meter example using optical head, change Logical Device address from 0 to 1 and
you can check your communication module settings. Example listening port number.
BR,
Mikko
Landis+Gyr E650 setup
Thanks for the reply. I will be starting a project soon using the L+G E650.
Connecting to L+G E650
Hi again..
I have an L+G E650 test unit, and am attempting to setup communications.
I do not have the serial interface, so will have to use TCP/IP only.
The unit was configured with an IP address of 192.168.110.10.
When connecting, I get the following error message:
"No connection could be made because the target machine actively refused it"
Where am I going wrong?
Connecting to L+G E650
Hi,
Your IP address or port is not correct. Your error means that TCP/IP connection can't established.
BR,
Mikko
Connecting to L+G E650
I have confirmed the IP address via ping...so it can only be an incorrect port assignment. I am using the default port 4059 which is selected when I choose 'Landis+Gyr' via 'File' ->'Add Device' -> 'Device Settings' menu. Can you suggest a different port?
Connecting to L+G E650
Hi,
Your port can be anything. You should check this from manual.
You can try with port 1000.
BR,
Mikko
E22 and GXNet.cs
I Know that is original question outdated, but at the moment I'm working with Landis+Gyr ZMD410 and E22 modules.
About connection problems, it could be module settings. I have couple of modules on my desk, and after closer look on each parameter (I read communication unit with MAP120 official Landis+Gyr Software) and there is one parameter that indicates time Window which presents when the module is active. By default it is not set on Always and that could be one problem about connecting over ethernet.
Second thing is socket closing. After reading meter, GXNet calls client.Close(); which lefts device in some odd state. After analyzing with wireshark I have noticed that there is no FIN signaling over the network.
So, it is recommanded to use client.Shutdown(SocketShutdown.Both); than client.Close();
There is one method which use same pattern, but I don't Know when this function is called.
Is there any reason to not close connection with Shutdown(SocketShutdown.Both)?
Kind regrads,
Ivan
E22 and GXNet.cs
Hi,
This is a very good point. The first version from the network component was made about 15 years ago and I can't remember why it's not called.
I created an issue from this. We'll test this for a few days and the new version is released on this week. It's coming as part of next GXDLMSDirector.
www.gurux.fi/node/13267
BR,
Mikko
E22
Just one notice, I only occured that problem with Ethernet CU-E22 module (2013) but not with GPRS module CU-P42 (2013).
And also, there wasn't any problem with Iskra MT880 and their CM-e-3 ethernet module.
Short part from the book C# Network Programming by Richar Blum
https://ibb.co/9vwVCh4
And from MSDN
https://docs.microsoft.com/en-us/dotnet/api/system.net.sockets.socket?v…
"
When you are finished sending and receiving data, use the Shutdown method to disable the Socket. After calling Shutdown, call the Close method to release all resources associated with the Socket.
"
E22 and GXNet.cs
Hi Ivan,
We have added shutdown to c# network component. Our clients are reading a lot of different meters and this is not a very common error. They are also using CU-P42 module, but I was thinking that there is a delay before the meter is read again. They are not polling data all the time. Usually once a day, etc.
So I believe that meter closes TCP/IP connection after a while even if FIN is not sent.
Thanks from this info.
BR,
Mikko
Ok
You are welcome :)
Yeah, but that is small touch to work correctly.
Usually devices have 24h reset.
As I said, I didn't realize this problem using CU-P42, but only with CU-E22 module.
Kind regards,
Ivan