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 kurmi,

we have implemented the Gurux server in esp32 and it is working fine, but the issue is with the push. I couldn't able to send the push with security. Can you please guide me through it.

BR
Vinaykumar.

Hello,

I have a clean smart meter (ZIV) for testing that I want to use to control different areas of an industrial warehouse, although this is unrelated to my problem ;).

The thing is, when I read information from the device using GXDLMSDirector, such as the “Current association,” I get the following error: “Cannot convert an object of type ‘System.byte[]’ to type ‘System.Objec[]’.”

This has happened to me with several OBIS devices, and I wanted to know if there is any kind of solution, because I am unable to connect it to the Python API.

Hello,

first of all, thanks for all the work, this project is pure gold!
We are using GXDLMSDirector to connect to an MT382 meter via optical interface. Connecting to the meter works. However, when trying to read the association view, we receive the error "GetObjects failed. Failed to receive reply from the device in given time".

Increasing the timeout does not fix it.

Hi
Firstly thank you for this tool.
I have been going through the docs and I have managed to do the following:

1. Installed GXDLMSDirector to my windows pc
2. Managed to run the AMI server using docker
3. Compile and upload the arduino server (Meter simulator) to arduino mega without any issues

My challenge:

Hi,

Iam trying to read Apator OTUS meter via Wrapper.
I have security packages and manufacturer tool, but I can not read the meter so far.
I can read some objects trough public association, but I need to read management association.
I can read the configuration of meter via maanufacturer tool and I can see the management access is HLSGMAC and client address etc. But I can not manege the gurux settings.
Could you please help.
I can share the communication log of manufacturer tool by e mail.

Many thanks

I have a Landis+Gyr E660 with an Ethernet module E66C.
I can connect to it using the Interface Wrapper (client address 10, logical server 1, physical server 1, authentication set to none).

However, with this setup I only receive serial numbers and similar information.
I need to read the actual metering data.

Any advice on how to properly connect to it would be greatly appreciated.

how do i change the mechanism name that's used to connect to a meter?

i'm trying to connect to an L&G E355, "Management Access" port (1) using GMAC, but i'm running into these bugs:

- when i change the "Authentication" drop-down in the "Device Properties" dialog, and click "OK". the "General/Command line parameters" textbox doesn't update. i have to select a different meter and then return back to the meter i edited for that textbox to update and reflect the option that I selected in the dialog.

I am using the NXP AN12837SW reference design for my smart metering project with the MKM35Z512VLL7 controller. Now I want to transfer/send my .bin file to uart terminal through serial wire(not in gsm) for firmware upgrade.
Could you please clarify the following points:
1. How to load the (.bin) file in Gurux, How to divide it into 256-byte chunks and How to add CRC/AES Encryption data for transmission?
2. What is protocol/documentation available for image transfer?
3. Can we send the firmware without OBIS code through uart?