• Not Answered

Identifying Size of Download Script for SLS / CSLS Prior to Download

We have seen an issue on a number of occassions where an SLS (or CSLS) is unable to be downloaded, with an error during the download indicating that the download script is too large.  This is typically on SIS module which have considerable amounts of logic in them, and the resolution is to remove some of the logic, but I am wondering if anyone knows of a way to identify in advance when this may be a problem (similar to how we can monitor the FreeTime / Control Expansion on a controller, to identify when they are near their limit)?  It doesn't appear to be associated with any of the diagnostic parameters that are visible for an SLS.

As I understand it, the script for an SLS is only generated during the process of downloading it, and it is stored within the DeltaV database (so not easily accessible information).