Hi,

Currently I am using DLMS simulator to act as meter for my dvelopment.

Below is the setup used
1. Created .xml file from meter using Manufacturer: Indian Standard, Authentication: PC
DLSM Simulator <----> DLMS Director
Media: Net (localhost), Interface: Wrapper - Working

2. Created .xml file from meter using Manufacturer: Indian Standard, Authentication: MR
DLSM Simulator <----> DLMS Director
Media: Net (localhost), Interface: Wrapper - Not Working
It shows No reason is given.

Good evening, GuruX.

Hope you are doing well.
I was trying to connect to my meter using client.net.
It seems like i got it connected but somehow received this error: Unacceptable frame
Is there any steps I could follow to resolve this issue?
Thank you in advance!

This is last 25 lines from trace:
Gurux.DLMS.Client.Example.Net.exe -S COM8:19200:8None1 -c 6 -a HighGMAC -C AuthenticationEncryption -T 4B464D09EBC1C5FC -A 53646E7967655365704C4533736F4B37 -B 414253695162566C64526564496B7276 -v 0.0.43.1.0.255 -w 1 -f 128 -t Verbose

Successfully connected to my meter using DLMS Director, but encountering issues when trying to establish a connection with DLMS.Client.Example.Net using the command line parameters from the last successful connection in DLMS Director. Specifically, the process gets stuck during the IEC sending phase. Any advice or suggestions on how to resolve this situation would be greatly appreciated. What steps should I take to troubleshoot and rectify this issue?

Hi Mikko,

I've been using the GXDlmsClient, where I would like to read the configuration and then save it, and then read the profiles.

Short explanation:

1. Read Association Views
2. Read Register and Extended Register attributes and values.
3. Read Data attributes and values
4. Read Clock attributes and values
5. Read Profile attributes (all but buffer)
6. Read one row from buffer for last read.
7. Save GXDLMSObjectCollection.

Please provide some solution I am not able to receive data
, But when I try to connect with normal socket code I am able to get some encrypted packet data.
Below is my code and output of the TCP socket without Gurux.net library

using System;
using System.Net;
using System.Net.Sockets;
using System.Text;

Hi there!

I´m getting an Not enought memory exception when reading a profile generic using the DLMS c# example app.
As soon as I was able to analize, it is because the meter negotiated pdu size is 512 but the raw data into the reply frame is 577 lenght.

Where could I increase the reply buffer size?

I saw another threads where you indicate it should be increased on the communication.c file... but that file is not into the c# app example.

Please find the comm logs:

Hi Gurux hope you're doing.
i need your guidance, i'm trying to gain access to my meter remotely over tcp/Ip by using the DLMSDirector .
i know all required parameters and security that i already use in local mode .
i have selected the NET " media" and put the IP address "Host name" and port of my meter.
but the meter didnt reply, of course we are in the same network . It would great if you give us a little help . thanks in advance.

I am having two Ethernet adapters been installed in my VM. While establishing TCP connection with IPV6 address family, my ethrnet adapter gets selected randomly, resulting failure in connection very frequently.

So, how to fix or where to make changes in the library so as to create a socket and bind it to the desired network interface.

I have an xml file with Date and Association objects.
I run the simulator:
-p 1000 -x sim.xml -t Verbose -N 1 -a Higt -P 1234567812345678 -c 48 -s 1 -l 0

Log:
DLMS HDLC Logical Name simulator start in ports 1000-1000.
Waiting 00:04:47 before next execution.
Server address: 1
Associations:
++++++++++++++++++++++++++++
Client address: 16 Without authentication.
Conformance:
Write, BlockTransferWithSetOrWrite
MaxReceivePduSize: 1024 MaxSendPduSize: 1024

I would be thankful if somebody could explain the meanings of

1. index
2. count

in the method below.

ReadRowsByEntry(GXDLMSProfileGeneric it, UInt32 index, UInt32 count)

Thank you.