Jump to content
Sign in to follow this  
ThomasGutzler

Bug in parallel foor loop: I can probe it!

Recommended Posts

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.

post-28303-0-78642000-1440749894.png

And no, this VI hasn't been flarned :)

Works in LabVIEW 2014 32 and 64bit.

Share this post


Link to post
Share on other sites

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...

Share this post


Link to post
Share on other sites

LV15 seems to behave itself.  At any rate I would think it is a feature to be able to probe there.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.