Mike Le Posted January 9, 2015 Report Share Posted January 9, 2015 Last month I ran into a problem building an application with LabVIEW claiming a certain VI was "broken." The VI wasn't broken, but in one of its subVIs there was a FOR loop with a conditional indexing tunnel. When I replaced this with the old-style of conditional indexing (shift register, case register, build array) the program was able to build. Today I ran into the same problem, where adding a conditional indexing tunnel caused a build to fail with the same error. I remember running into LabVIEW crash problems when conditional indexing was first introduced, but I was told it would be fixed for 2013. Is this not the case? Does anyone know if a "real" or "complete" fix has gone in for 2014? Quote Link to comment
JackDunaway Posted January 12, 2015 Report Share Posted January 12, 2015 Last month I ran into a problem building an application with LabVIEW claiming a certain VI was "broken." The VI wasn't broken, but in one of its subVIs there was a FOR loop with a conditional indexing tunnel. When I replaced this with the old-style of conditional indexing (shift register, case register, build array) the program was able to build. Today I ran into the same problem, where adding a conditional indexing tunnel caused a build to fail with the same error. I remember running into LabVIEW crash problems when conditional indexing was first introduced, but I was told it would be fixed for 2013. Is this not the case? Does anyone know if a "real" or "complete" fix has gone in for 2014? Step 1: clear your compiled object cache. Same result? Or do you get a "VI Failed to Compile" error after this action? An issue was reported in 2012 for conditional-autoindexed composite types (e.g., LVClasses) in parallel For Loops. Although not mentioned in your original post, is this a Parallel For Loop or not? And is the datatype primitive (integer/bool/string) or composite (LVClass/typedef)? Quote Link to comment
Mike Le Posted January 12, 2015 Author Report Share Posted January 12, 2015 It's not parallel loop. The indexing type is a cluster typedef. If I have time I'll revert back to the conditional indexing tunnel and see if clearing the object cache helps. But I'd already swapped back to the old style "shift register/case structure" combo and that's a good enough workaround for now. Quote Link to comment
MikaelH Posted January 12, 2015 Report Share Posted January 12, 2015 I remember that we got a issues when using the TimeStamp datatype in combination with Conditional Index Tunnel and running the for loop in parallel. But for LV2014, I haven't had any problems with the Conditional Index Tunnel. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.