Generic Profile large data extract

By DuddyS , 10 January, 2024
Forums
Gurux.DLMS

We are extracting 200 days of profile data using ReadRowsByRange(). No issues here.

The entire process takes 30 to 60 minutes to complete, which is comparable with L+G own tool set.

Is there anything available in the Gurux library to provide progress information on this long running process; i.e. the start and end dates are known, and the date/time for the data being extracted/returned from the meter could be determined by record date, which again could be determined by record number and record interval.

Kurumi

2 years 5 months ago

Hi,

At first. Don't read all the data at once because it will take a long time. It's better to read day by day. This will help when the connection is bad. If there are any problems with the connection you can continue from the last read date.

This will also help you to show the progress of the reading.

It's possible to peek at the progress with C#, but it's better to do it as I described above.

BR,
Mikko

DuddyS

2 years 5 months ago

We tested the option of reading day by day and it did work, but it almost doubled the time to recover the complete, large profile, hence the reason we went back to the single 'big block' read.

Seems that the meter (in our case E355) takes some time to process each ReadRowsByRange request, from a few seconds to 10s of seconds, hence the increased time to read day by day for up to 200 days.

If you know any reason for this, or options for speeding up the meter response time we'd be grateful to hear back from you.

Kurumi

2 years 4 months ago

Hi,

ReadRowsByRange is very fast for most of the meters and usually it works well with Landis+Gyr meters. It's sad if it's not working with your meter, but there is nothing that you can do to improve it.

Is your meter sending data as encrypted (ciphered) or is it coming without encryption?

BR,
Mikko

DuddyS

2 years 4 months ago

Hi Mikko,

Absolutely no problem with ReadRowsByRange.

As you say it works very well and download times compare very favourably with the L+G dMAP tool.

So we don't have a problem, rather it would be really great for us to be able to view the progress of the Load Survey (long running) download so we can present a meaningful status to a technician on site. In this way the user can have confidence that the Load Survey download is in progress, otherwise our application appears to hang for a long time (30 minutes in the case of 200 days of LS data). Time taken is not the issue and is expected for these large volume data extracts.

In an earlier response you told me that the C# library does have this capability, to provide a progress/status update for ReadRowByRange, but I haven't been able to find anything relating to this in the code.

If you could provide some pointers on what calls we need to make during the download operation it would be highly appreciated.