If you had a Trace Graph with too many fans for any given Lot, you could hit a Timeout trying to display ..
you will find in your log something like:
[MESBackgroundTask-1] ERROR com.sepasoft.trace.rpc.TraceRPCProxy -
Failed: getLotTraceByLotUUID com.inductiveautomation.ignition.client.gateway_interface.GatewayException: Read timed out
The attached window and objetcs (UDT and script) will help you show in a Table how complex your Lot is bypassing the Trace Graph Timeout
Applies To and Version Info
Import the window "win LotTraceAnalysis.proj"
In your Global Script Library import "global_LotTraceScript.proj"
In your Tag Browser, Import the UDT "GWLotTraceUDT.xml" then create Tag using the Data Type Instance using that UDT
The Tag "Processing" in the UDT acts a a Tag Events triggering the Script
and the Script code is
(Scripts and UDT courtesy of Pete L.)
Lots, Trace Graph, Timeout
Track and Trace
Configuration, Lot. Lot UUID, Lot Name
Created By Philippe Timothee Created Date Jun 20, 2019 20:45
Last Modified By Philippe Timothee Last Modifed Date Jun 20, 2019 22:34