LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

lo labview freezes up

Hello everyone,
 
I'm having some trouble with LabVIEW freezing up as I scroll across my front panel trying to locate indicators.  I'll attach the VI and hopefully some of you can test it out for me, or let me know why this peculiar behavior is occurring.  The VI isn't even running, LabVIEW just doesn't respond when I scroll to the far left of the front panel to locate some indicators.  I'm using LabVIEW 8.2.1, and there is no trouble in terms of memory or running the program on my computer...it is more than capable of running very detailed programs.
 
Thanks in advance,
0 Kudos
Message 1 of 4
(3,032 Views)
Hi Steve,

I could load your vi in LV8.5 and found some controls/indicators to the very left of the front panel (using the navigation window , ctrl-shift-n). I moved them back the to rest of your front panel. I could save the vi in LV8.5...
But then I couldn't save the vi back to LV8.2 - I get an error message from Labview "error in memory.cpp blabla"...
In LV8.2 I get the same error as you - as soon as trying to scroll the front panel LV freezes...

So I attach the LV8.5 version with moved front panel items - maybe someone else has an ideaSmiley Sad

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 2 of 4
(3,021 Views)
Hi Steve,

forgot to say:
those items are named "X" & "Y" (found in case 2); "integration", "light" and those unnamed Smiley Mad boolean arrays (case 7).
I think the problem with this vi is the "displacement" of those indicators - they are moved by more than 10000 pixels to the left. Maybe Labview can't handle such big frontpanels properly...

There are also some parts of your code that can be simplified (you can compare the whole array to a number, no need to compare element-by-element...).


Message Edited by GerdW on 02-12-2008 09:15 PM
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 3 of 4
(3,019 Views)
GerdW,

Your comment about large offsets is a clue. I recall that several years ago a similar topic came up. I do not recall the outcome, but there was some limit to how large the offset could be without causing problems. The maximum usable offset was smaller than the maximum number which could be represented by the datatype. There may also have been variations across OSes.

Lynn
Message 4 of 4
(2,989 Views)