Hello Team,
I'm inquiring whether there is a utility available to export InTouch log file data (.lgh) to Excel or CSV format. I'm aware that the HistData wizard can be used for exporting to .csv, but it has limitations on the duration (max 42 days) and range, limited to trend configuration.
Softwaretoolbox offers a utility called "LGH File Inspector" which supports this, but I'm interested in knowing if there are any native options within InTouch for this purpose.
Regards,
Arul
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 )
