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

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

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?