HisTrend w/Scooters and Scale fails when file size over 2G per day

I sounds to me like you're just hitting the practical limits of LGH. You should seriously consider using AVEVA Historian here. It is already included under some commercial plans, but even if it isn't in your case, even the cheaper "Local" Edition will probably be an improvement. You can also try it with some limitations even without a license.

It can certainly scale better on the storage side, but the biggest benefit you might see is on retrieval: it supports "best fit" retrieval that is better suited to trending than returning all the detailed raw data, but can still represent the overall signal well. 

I sounds to me like you're just hitting the practical limits of LGH. You should seriously consider using AVEVA Historian here. It is already included under some commercial plans, but even if it isn't in your case, even the cheaper "Local" Edition will probably be an improvement. You can also try it with some limitations even without a license.

It can certainly scale better on the storage side, but the biggest benefit you might see is on retrieval: it supports "best fit" retrieval that is better suited to trending than returning all the detailed raw data, but can still represent the overall signal well. 

Thank you.
Yes, it seems like it's due to the limitations of LGH, similar to the 2GB restriction in Access Database.
We have redesigned it to reduce the number of tags requiring LogData and increased the deadband.
But I'm not sure if there's a solution.
For example, is there a patch available for installation?
As the number of InTouch Tag Licenses increases, are there alternative measures available that don't involve Historian?
Thank you.

Hi,

As indicated by Elliott, the amount of data is well beyond our intentions for the LGH files and firmly in the range where Historian is the best practice and reference architecture. Even if the 2GB size constraint would be improved, the amount of data accumulated over time requires a proper process historian.

Thank you very much.

Historian is indeed a fantastic program, but it is somewhat expensive.
Perhaps removing many features and offering a specialized sales bundle could be a solution.
For example, an InTouch 100k + Historian Core (Tier-1 ONLY) bundle.
Historian Core would only include basic recording functions and be designed to work exclusively with the Trend feature in InTouch.

Alternatively, InTouch could be paired with Timescale using PostgreSQL.

Just a small suggestion, and thank you very much.

Thank you for the feedback.

If you haven't already, I recommend that you check out InTouch Unlimited.

• Unlimited tags
• Historian Included (from 500 tags with Standard to Unlimited tags in Premier edition)
• Com Drivers included
• Unlimited remote clients
• Pro and Premier editions include AVEVA Reports

Read more here: InTouch HMI pricing (aveva.com)

Hi, thank you for your reply.

I have a small suggestion. Since the current naming convention for .idx and .lgx files is YYMMDD00, could it be changed to YYMMDDHHmmss? For example, files generated in a day could be named like 240904080000.lgh, 240904090000.lgh, and 240904100000.lgh. This adjustment would resolve the issue.

Thank you.

Hi, thank you for your reply.

I have a small suggestion. Since the current naming convention for .idx and .lgx files is YYMMDD00, could it be changed to YYMMDDHHmmss? For example, files generated in a day could be named like 240904080000.lgh, 240904090000.lgh, and 240904100000.lgh. This adjustment would resolve the issue.

Thank you.