LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

bad lag in vi using "initialize array"

Thanks for posting the solution. That's always helpful to others if they run into the same problem. It also lets NI support that the problem has been solved and they don't need to get involved.


@Ben wrote:

Without it, Christian and myself would have to arm wrestle to settle this mystery. Smiley Surprised

Ben



Who would you put your money on. Smiley Wink

Ed



Ed Dickens - Certified LabVIEW Architect
Lockheed Martin Space
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.
Message 21 of 23
(733 Views)
Hi Candice,

So far these have all been great suggestions.  If possible could you try this?  On the IMAQ ArrayToImage.vi wire the image into the Image Pixels (I16) instead of the Image Pixels (Float).  Then change the IMAQ Create to Grayscale (I16) as the input.  This should cause your VI to run at regular speeds.  I was able reproduce your situation and changing the inputs changed how the VI behaved.

I'm going to look into something on my end but I believe it may be related due to the IMAQ Expand.  I will post back with my findings.

Justin Louie
0 Kudos
Message 22 of 23
(715 Views)
Yes you got it. That's almost exactly what the problem was. Thank you so much for your time!
0 Kudos
Message 23 of 23
(697 Views)