InTouch log file (.lgh) to CSV or Excel?

I'll ask my colleagues, but I believe the HistData thing is what is offered natively right now. It is our intention to improve this.

AVEVA Reports may also be an option if you have it.

Hi!

The question is if it is a one time thing or if the export should be done on a regular basis, keep in mind that Historian has a LGH import utility, but i guess if you have Historian available, then you would use historian for logging data and not LGH files.

But I have in several projects used InTouch stand-alone, saving csv files based on InTouch History (and LGH files), but in that case I was good to go under the limit of HistData.

Additionally, depending on the number of records you could save data to a table and generate CSV files from this.

But for a full 'History' experience, AVEVA Historian is the best option.

Hi Richard Köhlerstrand ,

Thank you for your prompt reply.

The customer is utilizing the .LGH file and has observed gaps in the trend when using the HisttrendChart Wizard, prompting the query if these gaps stem from the LGH raw data or if they are an issue with the HisttrendChart wizard. It appears that the gaps in the trend are a known issue, and AVEVA has released a hotfix to address this.

Regards,

Arul

Thank you for explaining the background of your question, I hope you get that sorted out and get reliable data in your application.

If possible, it would be interesting to get your results of the issue once resolved, was this an issue in storing data, or did the gaps in your trend come from a retrieval of data from history (LGH) issue.

If it is an issue in storing data then its something to keep an eye open for.

May I also ask what version you are experiencing this issue in?

There is a very old utility (Developed for InTouch 9.5 SP1) called HistLogReader which is able to read LGH files and then display tag data contained within the file. This tag data can then also be exported to a csv format.



Unfortunately, this is going to be an internal use only utility limited to AVEVA tier 2 tech support. If you do ever see a need for utilizing this utility, you will have to contact them. On top of this, the utility no longer works for 2023 LGH files, presumably due to the changes made to the LGH files in this version. ( https://softwaresupportsp.aveva.com/#/knowledgebase/details/000042110?lang=en_us )

It would be interesting to see if more people request this sort of utility to actually become published and maintained for the newest versions. I have been on a couple of calls now where it would have been useful to know if the InTouch Trend was at fault, or if it was the data itself. Judging from Rickard's post, it sounds like AVEVA is actively looking to enhance this area of functionality, so we shall see. 


I will note here as well that judging from your other responses in this thread, it sounds like you were running into the problem with viewing data past midnight on an 2023 R2 InTouch Historical Trend, which, as you noted, is a known issue: https://softwaresupportsp.aveva.com/#/knowledgebase/details/000042431?lang=en_us

Thank you Adam! much appreciated that you share that this might be a known issue in 2023 R2, it will save some time if we encounter this in upgrade projects, I had missed the support article that you refer to.

Though I see that the hotfix is included in 2023 R2 Patch 01 so perhaps as long as we are using the latest version this might not be an issue any longer.

(From 2023 R2 Patch 01 InTouch readme file )

The problem has been resolved after applying the Hotfix. For 2023R2, the hotfix is necessary, while for P01, the hotfix is already included.

Thank you all for your advice.