I am using Arduino client code on ESP32 to read meter in MR mode with LLS.
I downloaded the latest version of Arduino and using MR association with encryption. I get a message on terminal as
I have created 25,000 virtual meters using 'Gurux.DLMS.Simulator.net' but not able to read all meters simultaneously. it is randomly fails. success count is randomly changing from 5% to 40%. Majority meters are not replying any response and I am getting timeout error.
I have already tuned up all TCP connection settings & concurrent settings, so there is no configuration related issue at OS level.
We have noticed that the OBIS of the capture objects differ between the Map110 and GXDLMSDirector tools.
The Map110 UI scales the values, while GXDLMSDirector does not. However, if the scalars for each of the registers are read and applied to the GXDLMSDirector values, you'll see that the values are identical. The active and apparent power registers have a scalar of 0.1, which is further scaled by 0.001 to get kW and kVA instead of W and VA in Map110. Current and voltage both have a scalar of 0.01.
I am using Arduino client code on ESP32 to read meter in MR mode with LLS. I am able to read the Manufacturer name and Active Energy successfully. But when I read Serial Number with obis code 0.0.96.1.0.255 I get the ASCII string on HPL meter but a Octet String on Secure Meter.
I use the code as under
cosem_init(BASE(ldn), DLMS_OBJECT_TYPE_DATA, "0.0.96.1.0.255"); // OBis for Serial No
com_read(BASE(ldn),2); // Read
obj_toString(BASE(ldn), &data);
Hi
I am using DLMSDirector and RS-485 to get data from Holley DTSD545S meter. But when i am trying to connect "Failed to receive reply from the device in given time " error appeared. What should I do?
here is my device properties: https://www.dropbox.com/scl/fi/zjyqh2jrb6x3dzfn74mzs/Gurux-device-prope…
I'm using the following versions of the Gurux Python libraries:
gurux-dlms==1.0.181
gurux-common==1.0.13
gurux-net==1.0.22
gurux-serial==1.0.2
My DLMS meter only supports Short Name (SN) referencing, and I use the Python SDK (GXDLMSClient) to read register values.
During association view parsing (getAssociationView() → parseSNObjects()), I observed that the object with OBIS code 1.0.15.8.0.255 is returned with short name = 0, while all other similar objects are assigned valid short names (24, 48, etc.).
Hii ...
I have successfully compiled the client and server source code from dlms c libraries. I am using server source code as simulated smart meter in my PC (I'm not using real smart meter). How to setup the tcp port (both client and server side) and access the data from simulated smart meter ?