DLMS Simulator .NET | Invalid Read values and errors when simulating

By Incidencias, 8 May, 2025
Forums
Gurux.DLMS

Greetings,

Im currently using DLMS Simulator to simulate a device, but im struggling to first read the device data correctly, I firstly used the integrated read function of the simulator, the conexion is correct and I generate a .xml but I get "invalid" values from the reads:

Command: "Gurux.DLMS.Simulator.Net.exe -h (ip) -p 4059 -i WRAPPER -c 2 -s 1 -a Low -P (password) -t Verbose -o fileoutput.xml"

Then I tried GXDLMSDirector, with this app I did not get any problems reading from the device, moreover I tried the "save values as " function that creates a very similar .XML file and this time with all the correct values read.
But when I try to simulate from this more complete XML, I get this extrange error:

Command: Gurux.DLMS.Simulator.Net.exe -p 4059 -i WRAPPER -x Directorvalues.xml
Error: String '10:10:10' was not recognized as a valid DateTime.

I can not find a reference of the '10:10:10' sting anywhere inside the XML

Thanks for your support.

Incidencias

2 weeks 1 day ago

Hello,

My PC is using the spanish format

DATE: DD/MM/YYYY
TIME: 24h

Thanks for your quick response

Kurumi

2 weeks 1 day ago

Hi,

I need the exact time format that your PC is using.
You can get it if you run "time" in the command line.

If you can send the simulator XML to me by email, I can check it on Monday.

BR,
Mikko

Incidencias

1 week 5 days ago

Hello,

If I run tme "time" command in my cmd I get the next result:
"La hora actual es: 11:32:01,56"

About sending the XML... it is a 20675 line file with some confidential data.
What objects do you need to analyze? if you still need the complete file, tell me where can I find your email and I''l send you the file with some data censored.

Thanks.

Kurumi

1 week 5 days ago

Hi,

The comma in milliseconds is the reason. The fixed version is released this week.

BR,
Mikko

Incidencias

1 week 4 days ago

Greetings,

Curiously enough doing some testing, I managed to correctly virtualize the device by reading less objects with the director, no update required. I only read:

"Association LogicalName"
"Clock"
"Register"
"SapAssignment"
"Data"

Then I generated a smaller XML, and this way I managed to run a simulation with no errors.
There is only one thing I don't undestand, there are two data objects that change values in virtualization from the XML:

0.0.96.1.0.255 Device ID 1, manufacturing number Value: "0000000002"
0.0.42.0.0.255 COSEM Logical device name Value: "GRX2"

Those values are different in the .XML loaded, and we need to keep them as they are, we did not notice any more noticeable changes in the values.

Many thanks for your support