Error 1077 in Sub VI chart node property code

Question

Hi all,
I've finally worked out how to be able to change the data that is plotted in a strip chart, the code I have below works fine if it is added into my global loop, however it takes a lot of room and I'm trying to place it in a sub VI. However, when I do this I get the 1077 error on one of the property nodes, if I click ignore it moves onto the next node etc. I read in other posts that the problem had resulted from the order in which the code was executed, but I can't see where I could have gone wrong. If someone could point it out to me that would be great.
As for what this sub vi does, the max and min arrays store the max and min values of the y axes to be configured on the front panel, there is 6 strip charts and 20 data strands which can be plotted. When the user selects the data they want plotted in the strip chart, the property node of that strip chart is used to hide all the plots except the one selected and adjust the axes to the required scale. If someone could point out where I have gone wrong here that would be greatly appreciated!!
Stirling
Attachments:
Chart Config.png ‏47 KB

Answer 1

I looked at simplifying your code as a challenge.  Attached is a VI (LV 8.2.1) and a screenshot of the block diagram.  Since I was creating from scratch, I didn't have your actual rings or waveform charts.  I just created 2 rings and 2 waveform chart references.  These can be scaled to as many as you need.
If this is going in a subVI, you may want to make the rings and references as arrays, so you won't need numerous connector terminals for each ring and reference control.  If you do that, you can eliminate the build array functions for those before the loops.  It would also make the subVI more scaleable.
I also broke the property nodes into 2 loops.  As it was, you were setting the property nodes 20 times for each of 6 charts.  Only the active plot and visible? needed to be looped through 20 times.  The actYscale, Max, and Min were the same for each of the 20 iterations, so they only needed to be done once.
One other possibility would be to do a defer panel updates before, then allow them after the code, so there aren't as many screen refreshes while the loops iterate.
Message Edited by Ravens Fan on 08-18-2007 09:17 PM
Attachments:
Multi chart mod.vi ‏28 KB
Multi chart mod.png ‏11 KB