Hi - I am attempting to connect to an Iskraemeco ME162 Meter using an OPTO USB Serial device, I am able to read live values from the Meter using Test of IEC1107 software supplied from Meter Test equipment where I purchased the OPTO USB device.

Hello Gurux team and community,

I'm trying to establish a connection with a DLMS meter using the Python bindings for gurux_dlms and gurux_net libraries. I am using a standard HDLC-over-TCP configuration.

My Setup:

Connection Type: TCP/IP

Protocol: HDLC Wrapper (InterfaceType.HDLC)

Host IP: 192.168.1.1 -- ip is not actual ip

Port: 8080

Client Address: 16

Server Address: 1

Authentication: Authentication.NONE

i used your example driver in python and C# and simulator to, can you tell me more about how to use and how to connect and how to get data form metter or should i use your example code to connect realtime to metter

Hello Mikko,

Is there any way to confirm ciphered push (via tcp/ip 4059) in GXDLMSDirector?

After "Notifications-Start" all push data is visible in Notification window. I can decipher it in DLMS Translator window as well. Unfortunately meter got no confirmation from GXDLMSDirector so it use as many retries count as written in PushSetup object.

Best regards, Andrew.

Good day

i Am in need of assistance to connect a Metcom MCS301-C341C to DLMS Director over RS485 i am using a RS485-USB converter to try and connect to the meter but have not had luck in getting a response from the meter please may you guide me through the settings
setting i have tried on the DLMS Director are attached below

Interface: HDLC
Authentication: Reader
Password: 12345678
Client Address: 4
Baud Rate: 9600
Data Bits: 8
Parity: NONE
Stop bits: One
Flow Control: None

Hi Mikko. In cpp server example, there is a code for creating a push object, like this:
 

Out of Memory Error occurred when billing profile is queried by DLMS agent to server in L&T TCP Wrapper Meter. But it works when queried through GuruxDLMSDirector. Below are the access rights used:

Mode of Communication - Serial
Type of Communication - TCP Wrapper
Security Type - Authentication & Encryption
Security Suite - Suite 0
Invocation Counter OBIS - 0.0.43.1.3.255
Block Cipher Key - 1234567890123456
Authentication Key - 1234567890123456