07-28-2014 10:13 AM
Why should the Transpose function cause an issue like this then?
This VI was sent to me by someone, so don't ask what I'm trying to do because I'm not trying to do anything, but I am curious about the broken wire, and why converting the datatype from [SGL] to [DBL] and back to [SGL] keeps LV happy.
07-28-2014 10:21 AM
Reminded me of this:
http://forums.ni.com/t5/LabVIEW/Weird-network-stream-broken-wire/td-p/2824640
And I would wager that once again 'Always Copy' would fix your little problem
07-28-2014 10:24 AM
07-28-2014 01:59 PM
Before seeing your latest post I was going to suggest always copy. Lets add it to the list.
http://lavag.org/topic/15069-lv2010-weirdness/
http://lavag.org/topic/16973-bug-when-using-get-wa
http://lavag.org/topic/17833-class-data-inside-dvr
http://forums.ni.com/t5/LabVIEW/WARNING-TDMS-memor
http://forums.ni.com/t5/LabVIEW/EXE-Won-t-Build/m-
One of those is where a nasty memory leak issue with transpose, then a normal TDMS write. At least here it breaks the wire so that memory leak isn't possible.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord