ThomasGutzler Posted August 28, 2015 Report Share Posted August 28, 2015 This has got to be a bug. As we know, probes inside parallel loops don't work. That's usually indicated by a slightly greyed-out version of the probe ID in the block diagram (1). However, if I insert a disable structure inside the for loop, I can suddenly have a working probe again (in the Enabled case)! In this picture, probe 3 is a memory I32 probe (old values are shown in the array) and I can actually step through the disabled diagram and get useful readings from the probe. And no, this VI hasn't been flarned Works in LabVIEW 2014 32 and 64bit. Quote Link to comment
Mads Posted August 28, 2015 Report Share Posted August 28, 2015 Recreated here as well, in LabVIEW 2015. My first question was whether the loop was in fact still running in parallell, and it definitely is. So this gap in the "block probes in parallell for loops" logic seems to give access to the values processed by one of the parallel instances... Quote Link to comment
Darin Posted August 28, 2015 Report Share Posted August 28, 2015 LV15 seems to behave itself. At any rate I would think it is a feature to be able to probe there. 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.