Labview 5.0.1, Solaris 8 on a Ultrasparc 5Imagine two very simple vis:1) subtest.vi: Has a control and an indicator, both 1D-arrays of 'DBL'. Thecontrol is wired directly to the indicator, both arrays are empty, thevi issaved and the front panel is NOT open.2) memtest.vi: Has a 'FOR' loop with a 'DBL' constant in it which is connectedto the border of the loop, indexing is enabled. 100000 is wired to 'N'. theoutput of this loop (an array of 100000 'DBL' values = 800kB) is wired to'array size' which again is wired to an 'I32' indicator.If you run 'memtest.vi', the profiler will report approx. 800kB ofmemory usedby memtest.vi. So far, so good. Now, if I insert 'subtest.vi' betweenthe loopand 'array size' (Again: the front panel of subtest.vi is NOT open), theprofiler will report approx. 1600kB of memory and the timing statistics clearlyshow, the the array gets copied.What's going on here? The 'G Reference' clearly states, that under thesecircumstances the array should not be copied.NI support says:"According to R&D, this is the expected behavior on a Sun." and"The G Reference Manual was written with theMac OS and Windows OS as references."I can't believe it. This makes Labview useless for me. Has anybody else experienced this? Any hints, ideas ... are welcome.TIAThomas-- Thomas LudwigInstitute of MineralogyUniversity of Heidelberg, Germany

LabVIEW

Why get arrays copied when a subvi is called?

Author

Thomas Ludwig wrote:

The problem is a bug in Labview 5.0.x. Today I received the 5.1 upgrade
and now it behaves as expected.

NI still was not able to tell me that it's a bug in 5.0 and that the
problem is solved in 5.1...

Thanks again to Kevin and David.

Regards,
Thomas
--
Thomas Ludwig
Institute of Mineralogy
University of Heidelberg, Germany

Message 11 of 11

(349 Views)

LabVIEW

Why get arrays copied when a subvi is called?

Re: Why get arrays copied when a subvi is called?