I will say that it tends to crash more often when the script is run more frequently [Now(3000) vs Now(10000)] but it crashes either way. I also tried to reduce the number of data points because the script in the above post has 4 data series consisting of 10 minutes of data which is stored at 3 second intervals so the graph is showing 200 x 4 data points.
I've update the script so the red and green limit and target lines only consisted of 2 data points each. I created arrarys full of 'None' and only updated the first and last array elements. I'm not sure if that actually reduces the amount of data the graph has to deal with, but I tried. The crashes still occur.
LimitH = [None]*DataHtag.rowCount
Target = [None]*DataHtag.rowCount
LimitL = [None]*DataHtag.rowCount
for row in range(DataHtag.rowCount):
if (row==0) or (row==DataHtag.rowCount-1):
LimitH[row]=27.0
Target[row]=3.0
LimitL[row]=-27.0
I don't know the best way to send you the series configuration. But I'll include some screen shot, if there's a better way please let me know what you'd prefer
My post from yesterday (5/23) shows the script used to bind the 'example' data source. The script is pulling the tag history of the tag 'Realistic0'. The tag history is being stored in a MS SQL express database.
This is strange too, script returns data set but an error icon is displayed and the chart is diplaying the data
Here's a screen shot of the series information. Series 0 is the blue data line and Series 1 is the upper red limit.
You mean like this...(I have 16GB of memory)
I also see similar behavior from the designer when it crashes.
The memory usage and CPU% drop back down to normal shortly after crashing