HI Mikko,

I am trying to convert string value to GXTime.

In that got

GXTime gXTime = new GXTime("07:00:00");

String '07:00:00' was not recognized as a valid DateTime.

Can you please provide update in c#. As I have to convert multiple entries.

I have EM101+ DLMS Cat C3 IS15959 Meter, Lauritz and Knudsen.
I'm Reading the meter through DLMS Director.

1. What are the config properties ?
2. Like What manufacturer should be selected? Indian Standards or L&T?
3. what should be the interface ? HDLC or Wrapper or what ?
4. what should be the client, logical, server, physical addresses ?
5. what baud rate should be set ?
6. What about authentication ?
7. To read clock do i require a password?

Hello,
I want to read an energy meter using its RS232 port with GXDLMS Director.

The meter I am using is L&T EM101+ DLMS Cat C3 IS15959.

I do not have a RS232-to-USB cable with a DB9 connector right now. I have a MAX3232 RS232-to-TTL converter and an FT232RL USB-to-TTL module.

My idea is:
Meter (RS232) → MAX3232 → TTL → FT232RL → USB → GXDLMS Director

Will this work?
Can I convert RS232 to TTL using the MAX3232, then convert TTL to USB using the FT232RL, and read the meter normally with GXDLMS Director?

Hi,

I am trying to perform firmware upgrade to the meter, using the C source code available in github by modifying the code slightly.

Modifications:-
1. Commented all objects read. Post connection establishment, i have called imageupdatefromfile() function.

Hi, I am newbie with DLMS. I am testing Gurux.DLMS.Python and I am working with a meter simulation software. I am able to use the Gurux.DLMS.Client.Example.python giving the command "main.py -S /dev/ttyS0 -c 16 -s 1 -a None" and the simulator works fine. When I sniff the frames, at first step the python code send the SNRM frame:

7e 0a 07 03 21 93 0f 01 7e

the simulator answers with UA response

7e a0 20 21 03 73 73 98 81 80 14 05 02 00 80 06 02 00 80 07 04 00 00 00 01 08 04 00 00 00 01 ce 6a 7e

We are trying to import P384 Client Digital Signature certificate to meter and we are getting OtherReason. The reproducing steps:
1. We import successfully in meter your P384 Root CA Certificate that has CN=Root CA 384.
2. We create P384 Private key and use Get Certificate.. from context menu.
3. We select Digital Signature and enter Client System Title and create certificate.
4. In Certificate tab we use Info.. from context menu.
5. In Info window it shows that Issuer CN=Root CA 256 and this is the reason meter rejects this certificate